Solo founders evaluating Tycoon for the first time, or existing customers deciding which second or third role to add. Works whether you're pre-revenue, past $10K MRR, or running an agency.
First hire operational in 30 seconds. First visible output in the first conversation. Measurable impact within 14 days.
The playbook
- 1
Step 1 — Diagnose your true bottleneck
Write down what consumed your last 7 days honestly. Was it customer calls (hire SDR/AE first), content and marketing (CMO), bookkeeping and admin (accountant), code (CTO), or strategy and delegation (CEO). Most founders mistake their bottleneck — they think it's 'product' when it's actually distribution, or 'engineering' when it's actually decision load. The bottleneck is what you keep pushing to midnight, not what you enjoy most.
Rescuetime or Reclaim calendar auditA blank page and 20 minutes - 2
Step 2 — Match bottleneck to the right first hire
The playbook: if you're pre-revenue, hire the CEO first (priority coordination). If you're past $1K MRR but content-starved, hire the CMO. If you're drowning in code work, hire the CTO. If your problem is ops and finance chaos, hire the Accountant before anyone else. Most founders benefit from CEO first because it coordinates every subsequent hire — but if there's a specific fire, hire the specialist for that fire before the generalist.
hire/ai-manager, hire/ai-cmo, hire/ai-cto, hire/ai-accountant as candidate roles - 3
Step 3 — Run a 3-day shadow onboarding
Don't delegate immediately. For the first 3 days, let the AI hire observe — read your existing work, your Notion, your Slack history you authorize, your CRM. Answer its first-week questions in detail. This is the equivalent of shadowing a new human hire, compressed into hours. Founders who skip this step report 50% lower quality output in the first month. Founders who do it report the AI hire feels like an insider by week two.
Notion or Google Drive accessSlack read permissions for relevant channelsTycoon chat for the first week's questions - 4
Step 4 — Set autonomy expectations explicitly
Start at autonomy level 2-3 out of 5: the AI drafts, you approve before external action. Over weeks 2-4, raise to level 4 (AI acts on routine work, escalates judgment calls). By month 3, most founders run at level 5 for their first hire — full autonomy on defined scope. Setting this explicitly in the first conversation prevents the two failure modes: micromanaging (useless, slow) and over-delegating (mistakes you can't roll back).
Tycoon autonomy settings per role - 5
Step 5 — Establish the 30-day scorecard
Define three outcomes you'll measure in 30 days, specific and verifiable. For the CEO: weekly cadence running, escalation quality high, strategic drift reduced. For the CMO: content calendar live, two landing pages shipped, organic impressions trending up. For the Accountant: books closed on day one, zero uncategorized transactions, one surprise caught. Measurable outcomes prevent the 'this is vaguely useful' trap.
Notion scorecard template30-day retrospective on calendar - 6
Step 6 — Decide at day 30 whether to expand
Three possible outcomes: (1) Hire is working, add the second role — pick based on the next bottleneck. (2) Hire is partially working — tune autonomy, give more context, try 30 more days. (3) Hire is wrong for your shape — swap roles, not tools. See hire/ai-manager for how to do this without drama. Most first hires land in (1) or (2); (3) is rare if step 1 was honest.
Tycoon role swap (one click)hire/ai-manager for the swap protocol
Pitfalls to avoid
- Hiring the role you want to hire (the fun one) instead of the role you need (the bottleneck one).
- Skipping the shadow period and delegating on day one — quality collapses and you blame the AI.
- Trying to hire all five roles in week one — no context sticks and every role is half-onboarded.
- Setting autonomy too low forever — if you keep approving every draft at week 6, the AI is not compounding.
- Not writing down a 30-day scorecard — without measurement, you can't tell signal from vibes.