Welcome
PROTOTYPE · DUMMY DATALet's set up your GTM OS.
Setup is three things. Your data sources, your definitions, your rules on who approves what. The engines come preloaded, the same plays that work everywhere. The more context you give here, the sharper every draft gets. Everything you type lands in your OS brief on the right, in your words.
Your company
Where do you sell?
Average deal size
Sales cycle length
What is your motion?
How far along are you?
What hurts most right now?
In your words
Who runs it
Whose hands are on it
Hours per week they can give it
Your current stack
Honest expectation. This takes about 25 minutes plus your API keys. You bring your own model keys, the OS itself is open source. A smart revops person can do this alone.
Connect your data.
Around 26 integrations cover 80% of companies. Everything connects read-only. Nothing is copied out, the OS keeps read-only mirrors, your data stays yours. Your existing tools keep running, the OS orchestrates them. Hover any tile for why it matters.
Why this number matters. A CRM alone sees roughly a tenth of the buying signals. Product usage, site behavior, calls, replies, ads, the warehouse, each source widens what the scoring can read. Hover for how we estimate it.
Skipping a source never blocks setup. It just tells you what waits.
The access request list
Your definitions, drafted for you.
Every company's schema differs, so a coding agent reads yours while you watch. It drafts your semantic layer from what it finds plus what you told us in step one. You correct it, you own it.
Rules + who approves what.
The OS drafts around the clock. Sending is a different matter. Set autonomy per engine, cap the volumes, name the approvers. The recommended positions carry a SUGGESTED mark, move any of them.
Every engine starts in dry mode. It watches, scores and drafts, sends nothing. You flip each engine live yourself when its drafts have earned it. Two weeks in dry mode is normal, going live on day two is not.
One rule we hold. Net-new outreach never gets the auto position. Every first message to a stranger waits for a human, whatever else you loosen. The stop rule. The OS never silently changes what you approved. If a draft needs to deviate, it stops and asks. A system that quietly edits your titles is a system you stop trusting.
Quiet hours + channels
Send window
Channels the engines may use
Brand safety
Every outgoing draft gets checked against this list before it reaches a queue.
Who else shows up
EU mode is on. Enrichment pulls only from consented sources, suppression lists are respected everywhere, personal data never leaves your region. Turning any of this off requires the ops lead + a written reason. We keep the audit log either way.
Watch it build your OS.
This is the part no template can do. The agent assembles a workspace around your schema, your definitions, your rules, your own words. It takes a moment, watch the log.
Your OS is ready.
Mission control, rendered for Meridian Foods. Every number below is invented.
| ACCOUNT | SCORE | WHY |
|---|
Shadow mode. Engines run in shadow for the first week. You watch it be right before anything sends. Score accuracy shows up next to every prediction so you can judge it on record, on your data.
Your first motion + the next 90 days.
Suggested from your picks in step one. Remove anything, add anything from the full catalog below. The plan is yours.
NOW · WEEKS 1 TO 2 0
NEXT · WEEKS 3 TO 6 0
LATER · TO DAY 90 0
Browse all plays
Run it yourself, it's yours. Or have it deployed for you.
The OS is open source, free, running on your keys. Deployment help exists for teams that want the shortcut.
This is where your OS opens.
In the real product this lands in mission control, the workspace you saw in the build step. Below, the brief you built along the way. It ships with your OS, it belongs to you.