Studio Core

Everything else runs off what this knows.

Nineteen Skills, in every account from the first day. They work from one picture of your company, so what goes out is aimed rather than guessed.

A Tuesday
09:10Open the dashboard. One move at the top.
09:40Four replies triaged, four drafts waiting for a yes.
13:00One-screen brief before the call, with the ask and its fallback.
14:15Transcript in. Follow-up drafted, deck built, CRM updated.
17:30Pipeline read, with what the CRM says kept apart from what it implies.
Each of these is something you run when you want it. Nothing here watches you, and nothing fires on its own.
One picture, underneath all of it

Nobody has to keep four documents in sync.

Because there is one document. Every Skill reads it before it acts.

An objection your buyer raised on Tuesday is available to everything by Wednesday.

One document Skills that read it
## ICP24 of 31
## Personas22 of 31
## Offer21 of 31
## Voice20 of 31
## Company20 of 31
## Goals & Metrics18 of 31
## Outbound State17 of 31
## Proof Library16 of 31
## CRM & Stack16 of 31

Counted from the shipping Skill files. Sharpen the ICP once and twenty-four Skills behave differently on their next run.

Before the call

You walk in already knowing who is in the room.

Who is in the room is the most commonly wrong thing in a briefing, and only the invite knows. Without one, you tell it who is coming.

Then the threads with those people, your CRM including other reps’ notes, what has already been sent them, and the company itself. One screen, with the ask and its fallback near the top because that shapes every other choice you make in there.

A talking point, in three parts
The factTwo RevOps roles opened and pulled since May
The question it makes natural“Who owns reporting while that seat is open?”
If they confirmThe consolidation case, with the matched proof
If they do notNamed too, so you are not delivering the pitch regardless
Naming the second branch is what stops a prospect feeling handled rather than heard.
After the call

The follow-up is written before the hour is gone.

Up to seven outputs, and only the ones the call actually warranted.

The follow-up email

In your voice, staged, never sent.

The deck

Where your slide tool is connected, four slides built inside your own template, inheriting your fonts and spacing rather than reproducing them. Where it is not, the same four arrive as content to paste in.

The qualification record

Written to your CRM’s own fields where they exist and to a file where they do not, dated, in the buyer’s words. It appends rather than overwrites, so a timeline that slipped stays visible.

The coaching read

Against your own playbook, not generic best practice.

Every line traces to something actually said.

Where the transcript is unclear about who said what, it paraphrases rather than putting words in someone’s mouth. And an inference is never filed as established, because the next briefing reads this record and has to be able to trust it.

When you read the numbers

What your CRM says, what that calculates to, and what it only implies.

Kept in three tiers, so a projection never arrives wearing the confidence of a fact.

State

What the CRM actually records.

Rates

What is calculated from that.

Projections

What is inferred, and labelled as inference.

Every reading is kept, so a trend is something recorded rather than reconstructed later from memory. And each finding names the route that would fix it rather than leaving you with a problem.

Set up once, read by everything

Not once per Skill. Once.

One pass over how yours is actually configured, and everything else reads that.

Which means no two Skills can disagree about what a field means.

crm-map.mdread 4 days ago
## Discovered
Pipelines2 · New business, Expansion
Stages7
Lifecycle stages5
Custom properties18
## Could not determine
what “Qualified — tier 2” requires
whether Renewal shares the New business stages
Every Skill that touches your CRM reads this before it introspects anything itself.

The boring hours, done properly.

Everything is staged for you to read and change. Nothing sends itself.

Get set up