Make vs Zapier for Architecture Studios: Revisions and Billing

A contractor or consultant working from a superseded drawing set is a classic, expensive mistake, and it usually happens because the notification that a new revision went out didn't reach everyone who needed it, or reached them without making clear it superseded the last one. An automation that fires a clear notification with revision number and what changed, to the full current distribution list, closes that gap.

The harder part is keeping that distribution list accurate as a project's consultant team shifts phase to phase. Make's ability to pull the current team roster from the project record at the moment of each notification, rather than a static list set once, keeps this accurate through a project's full life; a Zapier flow built against a fixed list drifts out of date as soon as a consultant changes.

A revision notification that keeps everyone on the current set covers these points:

• State the new revision number at the top of the message so no one has to open the file to learn which set is current.
• Summarize what changed since the last revision, so each consultant can judge whether the update affects their scope.
• Say plainly that this revision supersedes the previous one, and name the set it replaces.
• Pull the recipient list from the current project roster at send time instead of relying on a static list set once.

A client's markup on a drawing set generates a list of comments, and each one needs to be tracked to resolution, not just acknowledged in an email thread that gets harder to follow with every reply. Logging each comment as a discrete item, with a status, is worth automating so nothing gets lost between a markup PDF and the revised drawing.

Either tool can log incoming comments into a tracker. Make's advantage is checking that every comment from a round is marked resolved before the revised set is allowed to move to the next approval stage, which catches the case where a comment quietly got missed rather than assuming, just because the drawing was updated, that every single comment was actually addressed.

Phase-based billing depends on a genuine approval, not on a drawing set simply existing in a finished-looking state. Tying an invoice trigger to an explicit client sign-off, rather than to a file being marked complete in your project tool, avoids the awkward situation of billing for a phase the client hasn't actually accepted yet.

Make's ability to check for both a completed deliverable and a logged approval before firing an invoice is the more accurate version of this. A Zapier flow keyed only to file status can trigger before approval actually happened, especially on a project where sign-off comes through a separate channel like email rather than the project tool itself.

A commercial project usually has several consulting disciplines working against the architect's base drawings, and each discipline needs the current version without needing constant manual check-ins to confirm they have it. An automated distribution tied to revision events, rather than a periodic manual send, keeps every consultant working from the same current set.

This coordination problem gets harder, not easier, the more disciplines are involved, which is exactly where Make's ability to manage a longer, more varied distribution list with discipline-specific routing rules pulls ahead of a flatter Zapier setup built for a simpler, smaller team.

None of this automation should touch actual design decisions, how a comment gets resolved, what a revision changes, those are the studio's core expertise and have to stay with the licensed architects and designers doing the work. Automation's job here is tracking and distribution, making sure the right people see the right version at the right time.

Time-to-fill for technical and design hires has stretched in recent years¹, and a studio running lean benefits most from automation that removes coordination overhead, freeing designers to spend their limited hours on the work that actually needs their judgment rather than chasing down who has the current file.

Give the studio's junior staff a clear, written sense of where that line sits too, not just the principals. A junior designer fielding a rushed request from a contractor needs to know instantly that resolving a markup comment is their call to make, while confirming who's on the current distribution list is something the automation already handles, so nobody wastes time second-guessing which parts of the process are theirs to own.