Write your own construct in the Construct Studio
The Construct Studio lets a firm write its own recipe for first messages in Stage 1, test it on its own sends and keep it private.
· 3 min read
Your firm has a way of opening conversations that works. Maybe it's a peer company's move, or a dated ask tied to a deadline the buyer can't ignore. No built-in recipe knows that.
The Construct Studio lets you write it down as a construct and test it on your own sends.
What you set
A construct is the recipe Stage 1 drafts a first message from. In the Studio you build one from the same pieces the built-in ones use.
You name it and give it one line on what it does. You pick the parts and their order, from the hook, the personal trigger, the hypothesis, proof, an insight, the mutual connection and the exit.
Then the details. The hook can name the event, quote the buyer's own words, point to a peer company's move or open with the mutual connection. The exit can be a yes or no correction, a correct-me, an open question, a direct meeting ask, a who-owns-this or no ask at all. The hypothesis can be stated plainly, put as a strong guess, turned into an insight or left out.
You set the most words, from 15 to 120, and the most questions, from none to three. You pick the door it belongs to. And you can say it only runs when the Brain has proof to cite, or only when there's a warm path.
Last, you write how to write it, in a sentence or two, and one example with made-up names. Something like this.
Open with their own words, quoted exactly. Then ask one question about what's behind them.
How it drafts
Stage 1 turns the recipe into instructions for Claude, with the house rules on top. No sentence opens with I or We. No pitch, no flattery, no "just checking in", no brackets or placeholders. Use only the facts given and never invent what a person said or did. Your example shows the shape, and its facts are never copied.
The draft is built from the same 3x3 research and the same Brain as every other message. Then the checklist runs on it, and the seller reads it before it goes when review is on.
Where it tests
Open Insights, then Constructs, and tap Write a construct. Only the workspace owner can write one. Tap Start testing it and it goes live.
A Studio construct is private. It tests only on your own firm's sends and learns only from them. It joins the constructs in testing for its door and shares the slice of first messages that goes to testing, about 15 percent.
From there it's your call. Make it your default and Stage 1 pins it for cold first messages when it fits. Retire it when it isn't earning its place. The daily pipeline promotes and retires the platform constructs on pooled results. Your private ones move when you move them.
Once a construct is live, its recipe is locked. A record has to mean one thing, so a change means a new construct.
Why a firm should write its own
The built-in constructs come from the Inversion Selling method and learn from every firm's sends. That's a strong starting point. It's still the average firm.
Your best sellers know things about your buyers that the average doesn't. The firm that sells to health systems knows which opener gets a CIO to forward the note. The firm that sells modernization knows which hook lands after a failed migration. Writing that down turns one seller's instinct into a recipe the whole team drafts from, with a record that tells you whether it's real.
It keeps your voice too. A construct with your phrasing and your proof sounds like your firm, not a template. More on that in writing in your firm's voice.
You don't have to start from a blank page. Stage 1 mines your own winning messages for patterns and proposes them as private constructs for you to approve.
The recipe is yours. The record decides whether it stays.