Skip to content
Critical Launch · Engineering Drawdown

Fix what matters, with engineering hours you control.

Prepaid blocks of senior SRE and DevOps time, worked through an agreed list, with the balance always visible.

01
How it works

How it works.

  • Buy a block of engineering hours up front, at a better rate than ad-hoc work.
  • We agree a prioritised list with you, usually from your Launch Check.
  • You always see the balance: hours used, work done, hours left, what's next.
  • Once a fix becomes routine, we turn it into a fixed-price package.
02
Blocks

Three sizes.

Block
10 hours

Valid for 60 days.

Block
25 hours

Valid for 90 days.

Block
50 hours

Valid for 120 days.

03
Scope

What the hours cover.

  • CI/CD and deployment
  • Monitoring and alerting
  • Security fixes
  • Backups and recovery
  • Database operations
  • Performance and troubleshooting
  • Infrastructure and cloud
  • Development environment improvements
04
Boundary

What they don't cover.

New features, UI or product work, large rewrites, or emergency incident response. For a live app that needs someone to call, see Critical Support Launch.

05

FAQ

What happens to unused hours?

They expire at the end of the block, so pick the size you'll use.

How is time recorded?

In 30-minute steps against the agreed list.

Can we buy more?

Yes, at any time; work beyond your balance always needs your approval first.

06
Next step

Where this fits.

Critical Launch gets modern applications ready for production. Critical Support keeps them there. Engineering Drawdown is step three: build, check, fix, run, grow.

Next: run

Critical Support Launch

Once the fixes are in and the app is live, we look after it.

All steps

Critical Launch

Every step from first check to full support, and the services for founders.

Tell us what needs fixing.

Bring your Launch Check findings or your own list. We'll help you pick the right size of block.