FRACTIONAL CTO  · 
ST. LOUIS + REMOTE

Your company needs a CTO. Without another full-time hire.

30 years of engineering leadership — teams of 6 to 40, across healthcare, fintech, insurance, and logistics.

Get a technical assessment  →

Two weeks. Written findings.
No obligation.

Who calls me

Founders with 5 to 30 engineers who have outgrown their first developer.

01  ·  What’s broken

The three calls that brought you here

  • 01

    No technical leader

    The founder is making architecture calls between sales calls. Decisions get deferred, then made twice.

  • 02

    The team ships too slowly

    Good developers, no process. No roadmap anyone in the room actually believes in.Good developers, no process, no roadmap they believe in.

  • 03

    Investors asking hard questions

    Due diligence, security posture, a scaling story that holds up past the next round.Diligence, security posture, a scaling story that holds.

02  ·  The record

The rooms I’ve been accountable in

Not a stack list. Increasing scope, in industries where a wrong architecture decision is a regulatory problem rather than a refactor.

  • 40

    developers led across two continents

  • 4

    regulated industries — SOX, GDPR, HIPAA-adjacent

  • [PLACEHOLDER]
    OUTCOME METRIC

  • [PLACEHOLDER]
    OUTCOME METRIC

Platform Architect

FIS

Architected the Virtus Core Services Platform and led 40 developers across teams in India — the delivery model, the review discipline, and the architecture were all mine to own.Architected the Virtus Core Services Platform; led 40 developers across India.

Engineering Manager

Degreed

Ran Core Services and designed the GDPR single-tenant model — the answer to the data-residency question that was blocking enterprise deals.Core Services, plus the GDPR single-tenant model that unblocked enterprise deals.

Technical Architect

RehabCare

Technical architect for a national provider network, owning SOX compliance across the application estate and the audit conversations that came with it.Owned SOX compliance across the application estate — and the audits.

Director of IT

Profiles / M3

The whole function reporting in: infrastructure, applications, vendors, and the budget that paid for all three.Infrastructure, applications, vendors, and the budget for all three.

Now

Your engineering org

Same job, fewer days a month. Start with the assessment.

03  ·  How I work

How I work

Availability
One or two engagements at a time. Named days, on a calendar your team can see.One or two engagements at a time, on named days.
Location
St. Louis. Remote by default, on-site when the quarter calls for a roomit matters.
Shape
Monthly retainer, three-month minimum. I lead your engineers; I don’t replace them.
Starting
Every engagement opens with the two-week assessment. No exceptions.

04  ·  Engagements

Start at four days a month.

A day is up to seven hours of delivered work. Allotments are monthly., so a heavy week borrows from a light one.

Retainer

Starting point

4 days/mo

Standing time with your engineers, ownership of the plan, and a technical voice in the decisions that matter — roadmap, hiring, architecture, the investor conversations.Standing time with your engineers and ownership of the plan.

$8,000

per month

Above four days there is no menu. Some engagements settle a little higher; some run close to full-time through a rebuild, a migration, or a diligence window. The shape follows the work rather than a package, so anything beyond the starting point is scoped with you.

Retainers begin with a three-month commitment and continue month to month after that. Rates above the starting point are confirmed in writing before any work begins.

Start here  ·  Two weeks

Before either of us commits to a retainer.

A fixed-fee technical assessment. You get a written answer about your engineering organization whether or not we work together afterward.

$5,000 Fixed fee

Credited toward your first month if we continue.

  1. Up to five interviews — founders, engineers, whoever owns the pain
  2. One codebase and one cloud environment, reviewed in depthOne codebase, one cloud environment
  3. Written findings document — risks, sequence, what to do first
  4. Live readout with you and your team, questions includedyour team

05  ·  Contact

Tell me what’s happening.

I answer personally, usually the same day. If I’m not the right fit I’ll say so, and where I’d point you instead.

St. Louis, Missouri — remote or on-site
No list, no sequence — just a reply.
Also Available for architecture reviews and hands-on build — .NET, Azure, React Native. Ask.