Pre-sales architecture diagram: drawing the solution during the call

Discovery calls capture the same short list every time: what systems exist today, which integrations are mandatory, what the constraints are, and who owns each boundary. Prose captures that badly, because the interesting part is the shape, not the sentences. A diagram drawn while the prospect talks turns the call into a review, and the corrections you get in the last ten minutes are worth more than the notes from the first fifty.

Two views usually cover it. A context view, showing the prospect systems and where your solution attaches, and a target view, showing what the architecture looks like once the project is done. Sales engineering that skips the context view tends to lose to the objection that nobody accounted for the existing warehouse.

Name the integration points explicitly on the edges. An arrow labelled with the actual mechanism, a change data capture stream, a nightly extract, an API call, is what the prospect architect will react to. An unlabelled arrow lets everybody agree while meaning different things.

Two minutes of drawing is a pause in the conversation. Ten minutes of drawing is the end of the conversation. The practical approach is to describe the architecture in a sentence, let the canvas produce a first version with real vendor icons, then move and rename during the call rather than building shape by shape.

Vendor icons carry more weight in pre-sales than anywhere else. A prospect who sees the Snowflake mark, their orchestrator, and their identity provider on the canvas reads a diagram about their estate. The same picture in grey boxes reads as a generic slide, and generic slides invite generic objections. The registry behind that is 2,095 marks: 624 Azure, 438 AWS, 226 GCP, and the rest data tools, Kubernetes, networking and general shapes, which is deep enough that the specific service a prospect names mid-call usually has its own glyph rather than a category stand-in.

Prepare a starting point for the deals you run repeatedly. Duplicating last quarter target architecture and editing the three things that differ is faster than starting empty, and it keeps the vocabulary consistent across the deals your team is running at the same time. The canvas editor is where that editing happens.

The follow-up email is where most pre-sales diagrams die: exported to an image, attached, and immediately superseded by the version you fixed after the internal debrief. Sending a link instead means the prospect opens the corrected diagram, not the one from the call.

The rule that makes this safe is that a public link is view only. Visitors pan, zoom, and open fullscreen without signing in, and no link exists that turns a stranger into an editor. The share dialog exposes two URLs and the distinction matters here: the preview link is the one you send, and the editor link opens the real canvas only for signed-in invited members.

A signed-in visitor who can view but not edit gets a request-access button, and the owner decides. On a competitive deal, that button is worth watching: a prospect architect asking for access is a stronger buying signal than a reply to the email.

A POC turns the pre-sales diagram into a working document shared with people on both sides. Put it in a restricted folder in your team workspace so the account team sees it and the rest of the company does not, and invite the prospect engineers to the specific project rather than to the workspace.

Team workspaces cover up to 5 seats under one subscription, and members plus pending invitations count against that number. On an account team that changes shape between deals, revoking stale invitations is what frees a seat for the next engineer joining the POC.

Two mechanics surprise people once a POC diagram is shared across two companies. A prospect engineer without a paid plan or an active trial behaves as a viewer whatever role the invitation dialog was told to grant, and that is enforced by the server rather than by the interface, so it does not depend on which screen they came in through. And an invitation nobody accepts expires after 14 days, which on a POC that stalls over a holiday is the usual explanation when an engineer reports that the link does nothing.

• The canvas editor
• Sharing and permissions
• Cloud architecture diagram generator
• Datadef compared with Lucidchart
• Team workspaces and folders