Approve +1 US headcount for Ryan to build forward-deployed engineering in-house for Citadel; re-evaluate in six months rather than scale per customer

July 24, 2026 at 8:18 PMpeoplehigh

Situation

In the 7/23 Ryan 1:1 Peter resolved the forward-deployed-engineering disagreement between Ryan and Bjorn. He drew a boundary - Bjorn gets to decide he wants the capability in-house, Bjorn does not get to decide that Ryans team has capacity - then asked Ryan what he needs to build it. Ryan asked for one US-based head who would serve as TAM plus Fuzzball subject-matter expert and half-operate as an SE. Peter granted it, confirmed the separate APAC backfill rec for Owen is already Ryans, and said he would get it across the line with Gordon. He also set the guardrail explicitly - the story to Bjorn is not plus-one-head-per-customer; it is one head now, scoped to Citadel, re-evaluated in six months.

Reasoning

Peter backed Bjorns strategic call - we want this muscle in-house, not outsourced to Cutting Edge - while refusing to let the capacity assertion travel with it. His line was that certain things Bjorn gets to wade in on and certain things Bjorn does not get to have an opinion on, and whether Ryans team has capacity is the second kind. Having conceded the strategy, the only honest follow-up is to fund it, so he moved straight to what do you need rather than debating capacity. The six-month re-evaluation exists to stop a single grant becoming an open-ended entitlement, and to keep the scope anchored to Citadel rather than a hypothetical twenty-customer future neither of them can size yet.

Additional Context

Resolves the 7/21 decision to back keeping forward-deployed/TAM in-house under Ryan and own the capacity assessment. Ryan flagged real fragility - Owen departing, Arsalan about to have a first child and told to take days off - which is why capacity was not a rhetorical objection. Ryan also raised discomfort about eventually reporting to a CRO; Peter declined to treat that as a live question, noting there is nowhere else to put him right now and he is not religiously attached to the move.

Observed Evidence

Direct transcript: I need a headcount. / Yeah, you got it. Plus one. Also: theres certain things Bjorn gets to wade in on, and theres certain things Bjorn doesnt get to have an opinion on. And one of them is, hes decided that your team has capacity. And: Ill get that across the line with Gordon.

Matching Patterns

40%
Protect Engineering Capacity(3 keyword matches (headcount, capacity, resources), require the demand to come with additional resources rather than absorb it)
30%
Accountability Follow-Through(same category (people), committed to carrying the rec to Gordon himself)

Confidence Breakdown

34/35
Evidence
28/30
Pattern
20/20
Source
11/15
Corroboration

Reasoning Depth Analysis

Org Signal:Strategy is Bjorns lane; staffing consequences are Peters. Directs learn that if Peter accepts a strategic demand on their behalf, he will fund it rather than expect absorption - and that they should answer capacity challenges with a number, not a protest.
Who Affected:Bjorn Hovland (whose capacity assertion was overridden without a confrontation), Gordon (approval path), Steven and Arian who were babysitting the Citadel work, Ramesh and Cutting Edge who lose the intended handoff, and Howard in APAC who gets relief from the Owen backfill.
Precedent:Sets the exchange rate for accepting new in-house capability - one head, scoped to the triggering customer, six-month review. Future capability grabs will be measured against this, which is deliberately cheaper than a standing per-customer formula.
Consequences:Real - two open recs (one US, one APAC) and an escalation to Gordon, not just verbal support.
Timing:Now because Citadel is live and Ryans team is short two bodies (Owen departing, Arsalan out); waiting would have meant either dropping the capability or burning the team through the gap.

Source

reflection

AI Confidence

93%

Related Context

🎥
Ryan <> Peter Weekly 1:1 - 7/23

fathom

Peter: where I do support Bjorn, is hes saying I want this functionality, this capability in-house... Then I turn to you and I say, okay, what do you need in order to build it? Ryan: I need a headcount. Peter: Yeah, you got it.

🎥
Ryan 1:1 - guardrail on scaling

fathom

Peter: Now, I want to make sure were not telling Bjorn a story of plus one headcount for every customer that comes in. Ryan: Six months pre-evaluated. Peter: And you got a headcount for Owen. You got that one right now, as far as Im concerned. Peter: Okay. Ill get that across the line with Gordon.

Outcome

Role specified Aug 24 with Ryan and Bjorn; JD in first draft and a named candidate identified

Rating: 4/5

Decision ID: a23ed425-6f41-41d7-800d-1c8e21fef2d1