Currently taking · One engagement · Q3 2026

Fixed scope.
Fixed team.
No retainers.

We take one engagement at a time. Every engagement is scoped upfront, priced as a single number, and delivered with the client’s team in the room. When we leave, you own it.

01SCOPE
Bounded. Agreed before kickoff.
02PRICE
Fixed. No change orders under scope.
03TEAM
3 SPN engineers. Same three, start to finish.
04HANDOFF
Runbooks, decision log, training. Non-negotiable.
§01 · SHAPES

Three engagement shapes.

Most engagements begin with an Assessment and move into an Engagement. A few skip straight to Engagement with a clear brief. Extended handoff is optional, rarely used, and capped at four weeks. We do not offer retainers, staff augmentation, or ongoing managed services.

01 · 2–3 WEEKS · FIXED

Assessment

We read your system and tell you what we see.
Fixed fee

For teams that suspect their architecture is the constraint and want an outside read before committing to a rebuild. No code. One diagram, one report, one hour with your leadership.

DURATION
2–3 weeks
TEAM
2 SPN engineers
INCLUDES
+Full system read — source, infra, runtime behavior
+Interviews with six engineers and two stakeholders
+Risk surface — what breaks first, what breaks worst
+Reference architecture — what we would build instead
+Written report, ~40 pages, yours to share internally
+One 90-minute debrief with your leadership
DOES NOT INCLUDE
−Implementation
−Post-delivery advisory
BEST FOR
When you are one meeting away from a rebuild decision.
02 · 8–16 WEEKS · FIXED
CORE

Engagement

The build. Start to finish. Cutover included.
Scoped to fit

The core of what we do. A single engineering problem — a ledger, a pipeline, a control plane — scoped, built, cut over, and handed off. Your team is in the room from week one; they own the outcome from week one after.

DURATION
8–16 weeks
TEAM
3 SPN engineers + your team
INCLUDES
+Full implementation against agreed reference architecture
+Production cutover rehearsed at least twice
+Full handoff package — runbooks, decision log, training
+Three weeks of paired on-call before exit
+Post-cutover audit — 30 days of independent reconciliation
+Source + tooling owned by you, no licensing
DOES NOT INCLUDE
−Ongoing operation
−Retainer continuation
BEST FOR
When the system has to change and cannot go down.
03 · +2–4 WEEKS · OPTIONAL

Extended handoff

We stay on call while your team takes the wheel.
Optional handoff tail

An optional tail to an Engagement. We remain available for incident escalation, code review, and architectural questions while your team operates the system solo. Capped duration, capped hours, clearly bounded.

DURATION
2–4 weeks
TEAM
1 SPN engineer, on call
INCLUDES
+On-call escalation, 24/7, < 30 min response
+Code review of all changes to delivered system
+Weekly architecture office hours
+Written incident postmortems if any trigger
DOES NOT INCLUDE
−Continued development
−Net-new scope
−Longer than four weeks under any conditions
BEST FOR
When the first month post-cutover carries real risk.
§02 · PROCESS

What a typical 14-week Engagement looks like.

This is the shape of a standard Engagement. Shorter scopes compress weeks 4–10 and weeks 13–14; longer scopes rarely extend the build past week 12. Rehearsal and handoff never compress.

  1. W 00
    Intake
    One call. We either take it, refer it, or decline. Typically decided within a week.
  2. W 01–02
    Read
    Two engineers embed with your team. Pure reading — source, runtime, interviews. No code written.
  3. W 03
    Architect
    Reference architecture + risk surface delivered. Decision: proceed, revise, or stop. Stopping is a valid answer.
  4. W 04–10
    Build
    Shadow deploy, reconciliation, parity. Weekly demo. Your engineers pair on every commit.
  5. W 11
    Rehearse
    Two full cutover rehearsals against production shadows. Rollback drilled.
  6. W 12
    Cutover
    The flip. Typically off-hours, typically five lines of config, typically boring. Boring is the goal.
  7. W 13–14
    Handoff
    Runbooks finalized. Decision log signed. Paired on-call. We leave.
§03 · WHAT WE DON’T DO

Things we will decline, politely.

− DECLINE

Retainers

No ongoing contracts. When we leave, we leave.

− DECLINE

Staff augmentation

We deliver systems, not seat-hours. You do not get “our engineers” on Jira.

− DECLINE

Managed services

We do not operate what we build. Your team does, from week one.

− DECLINE

Parallel engagements

One engagement at a time. Full attention, for the scope agreed.

− DECLINE

Greenfield products

We work on systems that exist and matter. Not 0→1.

− DECLINE

Discovery phases that run long

Assessment is capped at three weeks. Engagement scope is capped at sixteen.

§04 · FAQ

The six we get asked most.

T&M rewards slow work and punishes scope discipline. Fixed pricing forces us to scope honestly up front and fail the assessment rather than the engagement. If scope grows mid-engagement, we re-scope — a new agreement, not a change order.
§05 · ENGAGE

Send us one page.

No decks. One page — what the system is, what has to change, what cannot go down. We’ll reply within the week with yes, refer, or decline.

Send →