← Back to Patterns

Route Non-Differentiating FTE Classes to Partners

strategy78% Medium

22

Occurrences

67%

Success Rate

3.8

Avg Rating

Description

When CIQ would otherwise need to staff a function whose work does not differentiate the company — compliance bureaucracy, audit/cert paperwork, ongoing regulatory attestation, etc. — Peter routes the load to a partner who already owns adjacent capability rather than adding the FTE class internally. Org-shape decision dressed as a partnership decision.

Typical Approach

Identify FTE classes whose work is recurring, non-strategic, paperwork-heavy, and not engineering-core. Find a partner whose existing scope can absorb that load (Atomicorp for compliance, others TBD). Expand partner scope rather than open internal headcount. Hold the line even when customer demands surface gaps — gaps surface the partner-expansion lever, not an internal hiring track.

Trigger Conditions

Keywords:
compliancecertificationauditFIPSSTIGFedRAMPattestationregulatorypartner expansionscope expansionatomicorp
Constraints: FTE class would not differentiate CIQ, partner already owns adjacent capability, work is recurring and paperwork-heavy
People: Nathan Blackham (Linux Eng) on compliance scope, Bjorn Hovland (Product) on partner commercials

Last applied: September 7, 2026

Created: April 27, 2026

Example Decisions (22)

Defend the net-new engineering reqs to Greg by naming them - and pay for them with an explicit churn commitment

Sep 7, 2026 · strategy

Pending

Take the KT 9.8 one-year bridge - engineering will figure it out as long as the million dollars comes with headcount

Sep 7, 2026 · strategy

Pending

Refuse an SDLC release-cadence contract that would bind engineering - prioritization authority stays with Product

Sep 7, 2026 · strategy

Pending

Refuse to green-light the HPE indemnity escalation - this is a Bjorn call, not an Engineering call

Sep 3, 2026 · strategy

Pending

Refuse the 9.10-as-of-today letter for KT - give them 9.6 LTS now with its real support window and a required migration, and correct the numbers publicly when they turn out to be wrong

Sep 2, 2026 · strategy

Pending

Put the Core42 deployment on Ryan org to resource - Nathan stays advisor and the unfilled Forward Deployed Engineer goes on the contract list

Aug 31, 2026 · strategy

Pending

Hold the Core42 commitment at five weeks, signal two-to-three as likely, and trade the compression for topology data

Aug 31, 2026 · strategy

Pending

Attack the live-patching gap through Google co-development as a paid deliverable while keeping the req open - buy the timeline, do not just wait for the hire

Aug 28, 2026 · strategy

Pending

Hold the CISO requisition and the September security hire pending the Atomicorp acquisition

Aug 28, 2026 · strategy

Pending

Broken-in-production is an automatic fast path - small thing with embarrassing impact jumps the queue regardless of the size of the epic around it

Aug 28, 2026 · strategy

Pending

Accept Bjorn conclusion on the Stratum name while refusing his reason - dont make a decision now that you dont have to make

Aug 24, 2026 · strategy

Pending

Call the Core42 SOW1 won mid-call and forbid reopening anything that does not need reopening

Aug 24, 2026 · strategy

Pending

Claim the Core42 Dubai build-out for engineering outright - there is no sales engineering function, so if it gets built it gets built by engineering, and every scope increase still arrives with headcount

Aug 21, 2026 · strategy

★★★★

Show Core42 the responsibility matrix filled in, not blanked - a first cut we are flexible on beats arriving with an empty working sheet

Aug 19, 2026 · strategy

Pending

Pre-empt a three-week delivery commitment to Core42 before the deal closes - hand Bjorn the real sequencing mid-call so the number dies before it is said

Aug 19, 2026 · strategy

★★★★★

Value delivering things over doing work - ship three items all the way out the door and nothing elsewhere, rather than move nineteen forward

Aug 19, 2026 · strategy

Pending

Fork the Core42 engagement into two SOWs and let nothing delay the first - land the GB300 paper now, put the expanded security architecture in a separate SOW

Aug 19, 2026 · strategy

★★★☆☆

Ask Greg to take Peter off the RESF directive so it reads as CEO-to-RESF instead of CEO-correcting-his-CTO - and pair it with a standing Lee status cadence

Aug 18, 2026 · strategy

Pending

Refuse to debate the cause of the Rocky download reversal until the metric itself is validated - either it is the number we track and it warrants attention, or we track a different one

Aug 18, 2026 · strategy

Pending

Redirect the entire Core42 solution-review effort away from the people on the call and toward whoever watches the recording afterward - and make every answer technical, never personal

Aug 13, 2026 · strategy

★★★★

Ratify sales engineers owning first-pass demos as the permanent structure - reframing Chris Wolfords self-reported staffing error as having kickstarted the right thing

Aug 11, 2026 · operational

★★★☆☆

Expand Atomicorp partnership scope to absorb compliance load CIQ will not staff

Apr 27, 2026 · strategy

★★★★

Pattern ID: 121fef96-4a5c-4adf-b617-fbe09ba77c20