Thirty minutes with the founder.
Bring your open engineering req, or the roadmap you don't have hands for. We walk your stack, sketch the Team you'd staff instead, and you leave with an estimate on the call.
Pick a time →What the call covers.
A substantive call, not a deck. Real product, your stack, your actual backlog. By the end you know what the org would ship first, and what it costs.
You bring: whoever owns the engineering budget; an engineer is welcome.
We bring: Jack, and a sketch of the Team you'd staff instead of the req.
- 0:00
YAGNI running its own engineering org, live
The proposal lane arguing against our Number, the Work page mid-flight, a shipped receipt from this week. Production, not slides.
- 0:06
Walking your stack
GitHub, Linear, Sentry, Slack: what we read out of the box, where the limits are, what your in-house tools look like through MCP. Concrete.
- 0:12
The Team you'd staff
From your open req or your roadmap: the slice of the product it would own, the Responsibilities, the Number it argues against, what it would propose in week one.
- 0:20
Probation & the ladder
Day one you review every PR, like any new hire's. Autonomy is earned on the track record, and nothing consequential ships without your nod. Plus the audit trail and SOC 2 status for your security review.
- 0:26
The estimate & next steps
Which Teams, at what intensity, at what price. Contract shape, security review timing, start date. No "let me get back to you."
The first sixty days, on probation.
The org starts the way any hire starts: it earns trust before it gets room. You review everything at first, and the track record decides the pace.
The Team arrives.
The Team compiles from your req and connects to the repo, the tracker, and production. It reads your backlog the way a strong hire reads it in week one: what to keep, what to kill, what to merge.
By the end of the week it has argued its first proposals against your Number, in writing.
You review everything.
Every PR crosses your desk, like any new hire's. The Team carries the routine meanwhile: review through your lenses, the production watch, the triage.
The first shipped receipts land here: not "we merged a PR" but "we moved your number, here's the proof."
The ladder climbs.
On the track record, your review moves from reading diffs toward reading outcomes: proposals, experiments, receipts. The org comes to you with arguments, not chores.
The pace is set by the record, not the calendar. Autonomy stays earned, never assumed.
Thirty minutes in, you know what the org would ship first, and what it costs.
What you walk away with.
- ✓The Team sheet for your org. Which Teams you'd staff, the slice of the product each would own, and the Number each argues against.
- ✓A first-week plan. What the Team would read, propose, and ship first, drawn from your actual backlog and roadmap, not a generic deck.
- ✓Security & procurement pre-pack. SOC 2 program status, DPA, sample audit-log export, and support for your security questionnaire.
- ✓An estimate, on the call. Which Teams, at what intensity, at what price. Contract shape, start date. No "let me get back to you."
Office lines.
Pick a time.
Thirty minutes with Jack. Bring your open req, or just the roadmap you don't have hands for.