The question

We’ve just raised and hired our first seller. What should the first 30 days look like?

Until now the founder has sold from memory. The first seller can’t borrow that memory, so whatever lives only in the founder’s head has to be written down, and the numbers that will tell you whether it’s working need enough volume to mean something.

Where it sits on the loop

The foundations of the whole loop. Who you sell to feeds Imported; what you say feeds Working, Engaged and Replied; how you qualify feeds Pipeline and Won. It ends with the first recurring meeting: a short weekly look at the loop.

How to think about it

Four weeks, four moves: write the bets, get real data in, get enough volume to read, start one rhythm.

Week 1: write the bets. Who buys, what you say to them, and how you decide a deal is real. Each is a guess you’ll test, so write it where the team can see it.
Week 2: bring the team in. The seller works from the same written bets and the same pipeline, and their access matches their job.
Week 3: get enough volume. A rate on eight leads is noise. Aim for about 20 leads scored against your ideal customer profile (ICP) and at least five people in a live sequence.
Week 4: start the rhythm. One short weekly review: where is the loop stuck, three actions, and last week’s changes checked. Start it even if the honest answer is “not enough data yet”.

Common mistakes

Configuring before writing. Weeks go into tools and fields while the ICP is still in the founder’s head.
Hiring into a vacuum. The seller starts with a lead list and no written bets, and copies whatever the founder did last.
Waiting for perfect data. The weekly review never starts because the numbers aren’t ready, so the habit isn’t there when they are.

In Summit53

Most of the first month runs from Build your engine at /build, a seven-step checklist where each step ticks itself when Summit53 sees the real thing.

Week 1: real data and written bets

Bring in your deals: use Connect a CRM or import a spreadsheet, which opens Integrations (/admin/integrations). See Integrations.
Publish your ICP, Publish your positioning and Choose how you qualify deals: each button opens Knowledge with the right asset type. See Blueprint & Knowledge.
If your team works in Gmail and Google Calendar, connect each seller’s mailbox. See Google Workspace.

Week 2: the team

Invite your team: on that step, use Invite a teammate (email, Role: Member or Admin, Send invite). Only a workspace owner or admin can invite.
The seller accepts the invitation and joins your workspace. Their functional role starts as Individual Contributor, so their home is My Engine.
Check each person’s functional role on the Roles page; it decides their home page, action plan and digest. See Teams, roles & invites.
Point everyone at the Learning Hub. Leaders and founders start with its Build your engine camp; a new user picks their route in the Welcome to Summit53! window.

Week 3: enough volume to read

Score your first 20 leads against the published ICP (Import and score leads).
Start your first sequence with at least five leads enrolled (Build a sequence).
Watch the progress lines, for example 8 of 20 leads scored. See Build your engine.

Week 4: the first weekly review

Open the Revenue Engine and read the first constraint. If it says Not enough data yet., that’s the honest answer for now.
Pick three actions for the week from the Action Brief, each with an owner.
Run the same review next week. The full routine is in Where is the engine stuck?

From Claude or Codex

Install the Summit53 plugin and sign in with your Summit53 account; see the MCP setup guide. Then check the connection:

Set up Summit53 for me — is it connected?
Which Summit53 organisation am I connected to?
What can Summit53 do?

The summit53 skill confirms the connection, names the organisation and user it’s signed in as, says if it’s a demo workspace, and points you to the right skill for your question. It doesn’t change anything.

When the data is thin

Steps check themselves. Nothing on Build your engine is ticked by hand, and a step can go back to To do: publish a new ICP version and the lead-scoring step returns to 0 until leads are rescored.
Demo records don’t count. Demo deals and sequences are ignored, so a demo workspace doesn’t look set up.
Not enough data yet is expected. Under about 20 leads at a step, the Revenue Engine shows the count, not a rate, and names no constraint.
Invitations expire. An invite link works once and lasts seven days. If your workspace is out of seats, the new member waits for an admin’s approval.
Whose data. Each person sees what their role allows; in Claude or Codex, everyone signs in with their own Summit53 account.

Do it this week

On one page, write your ICP in five lines, your positioning in three, and the three questions every deal review will ask.
Put every open deal in one list with its stage, amount and next step.
Score your last 20 leads strong, good or weaker fit against the ICP.
Put five strong-fit leads into one sequence and note the date you’ll check replies.
Book a 30-minute weekly review for the next four Mondays.

Troubleshooting

A step stays To do after I did the work. Some steps take up to five minutes to show; switch tabs and back. A CRM connection counts once its first sync finishes.
I can’t send invites. You need to be a workspace owner or admin. Others see Ask an admin to invite your team.
The new seller sees My Engine. That’s expected for an Individual Contributor. Change their role if they lead a team.
Claude answers without Summit53 data. The connector isn’t attached or signed in. See the MCP setup guide.

The first 30 days: from first hire to a weekly rhythm