The program · Day 0 to Day 90

The work,
in full.

Everything the ninety days contain: the standing weekly schedule, the two systems you learn to run, the week-by-week curriculum, every artifact that ships, and the assets that leave with you whichever way the verdict goes.

01 · The work

We build it with you.
You keep the how.

A studio that builds for you leaves you dependent. Ninety days of building together leaves you able to do it again without us.

01

We are on the build, not on a call about the build.

The studio writes code, wires the infrastructure, and ships to production alongside you. Two reviews a week with a partner who has closed enterprise software, on the same repository you own.

02

You are in every buyer conversation.

Our sales bench builds the account list and runs the outbound against it. We book the meetings. You take them. By Day 90 you have run discovery and closed price yourself, dozens of times over.

03

Nothing is held back for leverage.

Rubrics, thresholds, playbooks, prompts, CRM, and the credit stack are yours to read from Week 1. We are trying to make ourselves unnecessary by Day 90.

What leaves with you

Even on a KILL.

A negative verdict ends the studio’s operating role. It does not take anything back. You walk out with the company and the capability to run the next one.

The stack
The AI build environment, the accounts, and the credits, all in the company's name.
The pipeline
The account list, the sequences, the CRM, and the objection library.
The method
How to scope a wedge, ship it in weeks, and price it in front of a buyer.
The record
A public, dated evidence trail an investor can verify without asking us.

“The goal is a CEO who can ship and sell without us in the room.”

02 · The week, every week

Thirteen weeks of the same five commitments.

No office hours, no mentor roulette. This is the standing schedule from Week 1 to Day 90.

  • Mon

    Week open

    One number to move this week, one wedge to ship, one thing we stop doing. Written down before anyone opens an editor.

    45 min
    Founder + build partner
  • Tue–Thu

    Build block

    Shared repository, shared branch reviews. You ship with us rather than watching a demo on Friday.

    Async, daily
    Founder + studio engineers
  • Wed

    Pipeline review

    We rebuild the account list, rewrite the sequences that died, and hand you the meetings booked for the week. You run every call.

    45 min
    Founder + sales bench
  • Thu

    Buyer calls

    Discovery and pricing in front of real buyers. We stay on mute, then debrief the objections into the library the same day.

    3–6 calls
    Founder leads, partner listens
  • Fri

    Evidence commit

    Metrics land in the record: revenue, early churn, weekly usage, calls run. Dated, immutable, and readable by the review panel.

    30 min
    Founder + partner
Weeks 1–2

Wedge and stack

Pick the wedge, stand up the build environment and the credit stack in the company's name.

Weeks 3–6

Ship and knock

First production release. Outbound starts against a named list. First priced conversations.

Weeks 7–10

Price and repeat

Close, then close again. We tune the offer until the same pitch works twice without us.

Weeks 11–13

Hand over

You run the cadence solo while we watch. Day 90 verdict off the record you built.

03 · What exists that did not before

Every phase ships artifacts you own.

Not advice, not frameworks. Working assets, dated as they land, and they stay with the company whichever way Day 90 goes.

  1. Weeks 1–2

    Foundation

    Pipeline
    Named account list of 300+ qualified buyers, scored and loaded into the CRM.
    Landing
    Live site with the wedge stated in one sentence, pricing visible, and a booking flow.
    Stack
    Build environment, repository, analytics, and the credit accounts in the company's name.
  2. Weeks 3–6

    First contact

    Outbound
    Three sequences shipped across email and LinkedIn, with reply handling and an objection library.
    Product
    First production release of the wedge, deployed and instrumented.
    Dashboards
    Live revenue, usage, and pipeline dashboard wired to the record.
  3. Weeks 7–10

    Repeatability

    Onboarding
    Self-serve onboarding path plus a documented white-glove runbook for the first cohort of accounts.
    Pricing
    A tested price sheet with signed terms behind it, not a guess on a slide.
    Retention
    Early churn and weekly usage tracked per account, with alerts on the accounts drifting.
  4. Weeks 11–13

    Hand over

    Operating docs
    The playbook: how the build ships, how the pipeline runs, who owns which number.
    Data room
    Metrics, contracts, cap table, and the dated evidence trail an investor can verify.
    Verdict pack
    The Day 90 memo with the rubric scores and the reasoning behind the call.
04 · The ropes

The two systems you learn to run.

One ships the product. One finds the buyer. We wire both in front of you, then hand you the keys and the paperwork.

Infrastructure
Build environment
Repository, CI, and preview deploys wired with proper secrets handling. You push to production yourself in Week 1.
AI stack
Model routing, prompt versioning, evals, and cost ceilings so inference spend stays a line item you control.
Data and auth
Schema design and row-level security, with migrations and backups behind it. Who can read what, and how you prove it.
Instrumentation
Event taxonomy, activation and churn definitions, and the dashboard that feeds the Day 90 record.
Sales
List building
How to define the buyer, source the accounts, and disqualify fast instead of chasing everyone.
Outbound
Sequence structure, subject lines, follow-up spacing, and deliverability that keeps you out of spam.
Discovery
The call structure: current process, cost of the problem, who signs. Questions, not a demo.
Pricing and close
Anchoring, holding price under pressure, and the paper that turns a yes into revenue.
System map · how the two loops meetHover or focus a block
EVIDENCE FEEDS BACK INTO THE NEXT WEEK’S TARGETSSALES LOOPBUILD LOOPAccount listICP + disqualifiersSequencesEmail + LinkedInCRMStages, ownersCallsYou run themRepositoryShared, you own itCI + deployPreview, prodProductThe wedge, liveEventsUsage, churnDashboardOne shared viewThe recordDated, public
05 · Week by week

What gets taught, and when.

Both curricula run in parallel across the thirteen weeks. Each lesson lands on live work in your own company, not a case study.

  1. Week 1
    Wedge and stack
    Infrastructure

    Repo and entity set up, with environments split. Auth and database schema stood up on the shared stack.

    Sales

    Buyer definition and the disqualifier list. First hundred named accounts scored.

  2. Week 2
    Wedge and stack
    Infrastructure

    CI with preview deploys, behind a written deploy checklist. Secrets handling and access rules.

    Sales

    Sequence structure and the first outbound copy. Domain warmup and deliverability.

  3. Week 3
    Ship and knock
    Infrastructure

    The AI stack wired into the product path. Model choice and cost per call, with fallbacks when a provider fails.

    Sales

    Sending starts. Reply handling and objection capture. Booking mechanics that hold.

  4. Week 4
    Ship and knock
    Infrastructure

    Event taxonomy defined before features ship. Activation and usage instrumented.

    Sales

    Discovery call structure. Current process, cost of the problem, and who signs.

  5. Week 5
    Ship and knock
    Infrastructure

    First production release behind the checklist. Error tracking and alerting.

    Sales

    Sequence rewrite off reply data. Cutting the segments that do not answer.

  6. Week 6
    Ship and knock
    Infrastructure

    Dashboard build. Pipeline and usage read from the same source.

    Sales

    Demo discipline. Showing the wedge only, and naming the next step on every call.

  7. Week 7
    Price and repeat
    Infrastructure

    Multi-tenant data boundaries and row-level security under real accounts.

    Sales

    Pricing model and the anchor. Tiers and floors, plus the discount authority you keep.

  8. Week 8
    Price and repeat
    Infrastructure

    Onboarding flow in product. Time to first value measured, not guessed.

    Sales

    First paid asks. Holding price under pressure and reading a stall.

  9. Week 9
    Price and repeat
    Infrastructure

    Reliability work. Backups, restores, and the incident path when something breaks.

    Sales

    Contracting basics. Order form, terms, and turning a yes into revenue.

  10. Week 10
    Price and repeat
    Infrastructure

    Early churn and weekly usage definitions locked. Cohort views in the dashboard.

    Sales

    Account handoff to onboarding. The runbook that keeps a new customer alive.

  11. Week 11
    Hand over
    Infrastructure

    Ownership transfer. Accounts, billing, domains, and admin move to you.

    Sales

    Pipeline review with forecast rules. What counts as real and what does not.

  12. Week 12
    Hand over
    Infrastructure

    Operating docs written. Deploy, on-call, and the cost model per customer.

    Sales

    Hiring the first rep or running it yourself. Comp and quota, with the ramp math behind both.

  13. Week 13
    Hand over
    Infrastructure

    Data room assembled from the record. Metrics reproducible from raw events.

    Sales

    Investor narrative built off the evidence. Verdict pack and the ask.

Sample templates

A sample of what sits in the shared drive from Week 1. Filled in with your data as the quarter runs, and yours to keep at the end of it.

  • icp-scoring.csv

    Account scoring sheet with the disqualifiers weighted.

  • outbound-sequence.md

    Five-touch sequence with the rewrite notes on each touch.

  • discovery-call.md

    Question script, note structure, and the next-step ask.

  • objection-library.md

    Live objections with the responses that closed and the ones that stalled.

  • pricing-sheet.xlsx

    Tiers, floors, and the discount authority you keep.

  • onboarding-runbook.md

    Day 0 to Day 14 for a new account, with the owner on each step.

  • metrics-spec.md

    Event names, activation, early churn, and weekly usage definitions.

  • deploy-checklist.md

    What has to be true before anything reaches a customer.

06 · What you keep

The company and the capability. The paperwork to run either again.

A negative verdict ends our operating role. It does not take anything back. You leave with working assets, written methods, and the documents to run the next attempt without us.

Infrastructure

  • Company-owned repository with full commit history and CI history.
  • Production and preview environments, domains, and DNS records transferred to you.
  • Cloud accounts (Azure, AWS, GCP) and active credit awards in the company's name.
  • AI provider accounts and model routing. Prompt versions and cost ceilings are set before the first inference call.
  • Database schema and migrations. Backups and row-level security policies for who can read what.
  • Error tracking and alerting, plus the incident runbooks that go with them.

Sales assets

  • CRM with stages, owners, and the full account list scored and loaded.
  • Outbound sequences across email and LinkedIn, with reply data and rewrites.
  • Objection library: what stalled and what closed, with the responses that worked.
  • Discovery call recordings and note structure, with the next-step scripts that close the call.
  • Pricing sheet with tiers and floors. Discount authority and signed order forms are included.
  • Pipeline forecast rules and the weekly review format.

Product and data

  • Production code for the shipped wedge, deployed and instrumented.
  • Event taxonomy and activation definition. Early churn definitions are locked per cohort.
  • Live dashboards for revenue and usage, plus pipeline and cohort health views.
  • Onboarding flow and the first-cohort white-glove runbook.
  • Analytics stack and the queries that feed the record.
  • Data room folder with contracts, metrics, and the dated evidence trail.

Operating docs

  • Deploy checklist and the on-call rotation for the first six months.
  • Build-week playbook: the path from scope to shipped work in one week.
  • Sales operating rhythm: Monday targets, Wednesday reviews, Friday commits.
  • Hiring plan and comp math for the first rep or engineer.
  • Investor narrative and the Day 90 verdict pack with rubric scores.
  • Cap table, SAFE terms, and the corporate documents from formation.

Templates

  • icp-scoring.csv — account scoring with weighted disqualifiers.
  • outbound-sequence.md — five-touch structure with rewrite notes.
  • discovery-call.md — question script and next-step ask.
  • objection-library.md — live objections and responses.
  • pricing-sheet.xlsx — tiers and floors, plus your discount authority.
  • onboarding-runbook.md — Day 0 to Day 14 for a new account.
  • metrics-spec.md — event names and activation, plus churn definitions.
  • deploy-checklist.md — what must be true before a customer sees it.

The apprenticeship is the asset. The company is just the first project you build with it.

07 · The infrastructure

Cheap enough to run many.

Evidence only beats judgment while it stays cheap to collect.

Non-dilutive infrastructure · per company · Day 1
up to$500Kin stackable maximums

The higher tiers normally require venture backing. As a registered provider, we place them into every company on Day 1. Across the ninety days a company usually draws $50–75K, weighted to compute and outbound.

Provider 01
Microsoft Founders Hub
up to $150K

Azure + Azure OpenAI + GitHub Enterprise

Provider 02
AWS Activate
up to $100K

Portfolio tier, via our Provider ID + Bedrock

Provider 03
Google for Startups
up to $350K

AI-First track + Vertex + Gemini

Provider 04
NVIDIA Inception
$100K+

for compute-heavy builds

Stacked provider maximums · verified quarterly · actual allocation varies by tier

Cohort 01 · Applications open

Ninety days to an answer.

Apply →The terms →