Practical CTO Education for Builders Scaling Fast

Engineering leadership, written down, rehearsed, and signed off by operators who have done the job.

FoundrySprint is a working block for first-time CTOs, technical co-founders, and engineering leads moving from individual contribution to team strategy. We do the writing, the rehearsal, and the honest review — you leave with artefacts your team can actually run on Monday.

9 live programs 120+ alumni Seoul + remote

A note from the studio

"We do not teach founders how to feel about leadership. We teach them how to write it down."

First five minutes

Try a working block for free; we will not sell to you afterwards.

The trial is a single ninety-minute working block, no credit card, no automated drip, no upsell email after.

Open a trial slot
  • Write the first paragraph
    • Describe one engineering decision you have been quietly avoiding
    • Name the failure mode that decision is shielding
  • Receive a written response
    • From the program director, by the next working day
    • One page; no automated grading; no marketing follow-up
  • Choose a route
    • Book a thirty-minute intake call to discuss a real cohort
    • Or close the tab and keep the written response

Membership

One membership covers programs, peer pairing, and the alumni reading list — switch monthly or save by paying annually.

  • Annual billing carries an eighteen percent discount baked into every tier
  • Switch tier any time; the change is reflected on the next billing cycle
  • Pause for a quarter without losing alumni access or peer pairing
  • One free intake call with the program director before you decide

All tiers include access to the alumni cohort, a written intake call, and a refund window described on the Returns & Refunds page.

Studio guarantee

Refund within fourteen days, in writing, no questions asked.

  • Within fourteen days
    • Full refund, no clauses, no exit interview
    • Processed within fourteen working days
  • If we cancel
    • Full refund regardless of cohort progress
  • After day fourteen
    • Pro-rated refunds reviewed individually

Why we publish this in plain sight

Our guarantee exists because the working contract between a studio and a participant cannot rest on hope.

Within fourteen calendar days from the start of any cohort, you can request a refund in writing and receive the full amount back to the original payment method, with no exit survey and no informal pressure to reconsider. We handle the request through a single email thread with a real person from our team rather than a ticketing system, and we confirm receipt within two working days. Approved refunds reach the original payment method within fourteen working days from confirmation, including domestic transfers within the Republic of Korea and international card networks. The clause is not a marketing courtesy; it is the term we are willing to put in writing because we have shipped this curriculum across enough cohorts to know that retention bought through friction is not retention worth keeping. The full text and the small number of statutory exceptions live on the Returns & Refunds page, and our intake team is happy to walk through the wording in advance for any founder who wants the comfort of reading the policy before enrolling.

From intake to artefact

Five working steps move you from a written intake question to an artefact your team can run with on Monday. The cadence is steady, the writing is honest, and nothing happens off the cohort schedule.

  1. Written intake

    You write the question you want answered before the call. We respond on paper before we respond on camera.

  2. Cohort kickoff

    The first live session establishes the working contract for the cohort and the rhythm of the writing assignments.

  3. Working blocks

    Every week is a working block: a written draft, a live review, a peer reading, then a revision before the next session.

  4. Operator review

    The midway artefact is reviewed by an outside operator who has shipped the same problem and who has nothing to sell.

  5. Final brief

    A single, written, defensible brief lands on your desk; the cohort closes; your peer pair stays open.

Three pillars, one program at a time

The studio runs a small library of programs; the three below are the most reused. Each one is a single working block, not a course catalogue.

CTO Leadership · 6 weeks · 18 hours live

Engineering Strategy For First-Time CTOs

A six-week working block that turns vague platform anxiety into a written engineering plan you can defend in any board meeting.

  • Weekly two-hour live working session with the cohort
  • A written architecture brief reviewed by two seasoned operators
  • Hiring sequence template tuned to your cap table and runway
View this program

Engineering Management · 4 weeks · 12 hours live

Hiring Senior Engineers Without Burning Months

A hiring operating system for technical co-founders who keep losing senior candidates at offer stage and cannot diagnose why.

  • Sourcing message templates that survived three quarters of A/B testing
  • A two-stage technical evaluation that respects senior candidates
  • Closing call playbook with three branching scenarios
View this program

CTO Leadership · 2 days · 14 hours live

Founder–Engineering Alignment Workshop

A two-day intensive that resets the working contract between a non-technical founder and the engineering organization.

  • Two intensive days, in-person or fully remote
  • A written working contract between CEO and CTO
  • Three rehearsed escalation patterns
View this program

A small, deliberate ask

If your engineering operating doc fits on a sticky note, we should talk.

The intake call is a written prelude and a thirty-minute conversation. No PowerPoint, no upsell, and we will tell you on the call if a cohort is the wrong fit.

Schedule the intake call

Open the disclosure for what to bring

What you can prepare in fifteen minutes before the call
  • One paragraph describing your team today, not your team in two years
  • One engineering decision you keep quietly relitigating with a co-founder
  • One artefact (doc, slack thread, JIRA epic) that you wish you had written six months ago
  • One question you want a working operator to answer before you enrol
  • One disqualifier — the thing that would make you walk away from a cohort
  • A rough date you would want a written follow-up by, if not enrolment