Pricing

Transparent starting points for focused technical help.

Pricing depends on scope, access, timeline, and the level of ongoing support needed. Most teams start with an Engineering Health Review, then decide whether fractional engineering leadership or scoped execution makes sense.

Not sure which engagement fits? Start a conversation.

01

Engineering Health Review

Engineering Health Reviews start at $2,000 depending on scope.

Good fit: You know something is wrong but need clarity, risks, recommendations, and a practical roadmap.

  • Scoped to one area of concern
  • Discovery
  • Review
  • Findings
  • Risk summary
  • Diagrams where useful
  • 30/60/90-day roadmap
  • Readout
02

Fractional Engineering Leadership

Monthly retainers are available for ongoing fractional engineering leadership, with work scoped from $175/hour.

Good fit: You need ongoing technical direction without hiring a full-time CTO, VP Engineering, Head of SRE, or Head of Security.

  • Fractional CTO-level support
  • Architecture direction
  • Engineering operations consulting
  • SRE consulting
  • Cloud cost optimization
  • Technical due diligence support
03

Scoped Technical Execution

Quoted based on scope.

Good fit: You have a clear technical initiative and need senior help executing it.

  • Can follow an Engineering Health Review
  • Can begin with a clearly defined project
  • AWS/Terraform work
  • CI/CD cleanup
  • Observability setup
  • Application architecture documentation

How scope is set

Clear scope before commitment.

The first conversation is used to understand the pressure, confirm whether the problem is a fit, and choose the smallest useful engagement. A review may focus on production readiness, security risk review, cloud cost optimization, application architecture, AWS infrastructure, engineering operations, or a custom technical concern.

  1. 01 Concern
  2. 02 Fit check
  3. 03 Scope
  4. 04 Access plan
  5. 05 Review or execution
  6. 06 Readout

Start a conversation

Not sure which engagement fits? Start a conversation.

Send a short note about what is creating pressure: scaling, cloud cost, reliability, security expectations, architecture, engineering process, or something custom.

Start a conversation