altoby.

// The offer ladder

One week and one price, before anything else.

Three steps, each with a price you can see. No proposals-by-negotiation, no hourly meters.

01

The Blueprint

$1,000 · one week · fixed

We map how the business runs, audit whatever software exists, and specify the system you need.

  • Full written specification
  • Architecture & fixed build quote
  • Yours to keep — take it to any developer
  • If it doesn't end in a price you could hand anyone, it's free
02

The build

from $3,500 · fixed scope, quoted in your Blueprint

The system, built module by module against the approved spec.

  • Live in production from week one
  • A working demo every Friday, or that week is free
  • Tested, documented, deployed
  • You own code, data, and infrastructure
03

The partnership

from $1,500/mo · cancel monthly

The system grows with the business — and someone senior answers when it matters.

  • New modules & improvements
  • Monitoring, maintenance, hosting
  • A direct line to your engineer

The standing promise: nothing is built before you've approved a written spec, the software is live in production from the first week, and you see a working demo every Friday. If a week ends with nothing to show, that conversation happens in the demo — not in month three.

From first message to live system.

Day 0

You send the form or an email. A human reads it — no qualification bot, no drip sequence.

Day 1

I reply, and we book a 20-minute call. A fit check in both directions; if I'm wrong for it, I say so on the call.

Week 1

The Blueprint: your operation mapped, existing software audited, and a written spec with a fixed quote at the end — yours to keep either way.

Week 2

If you take the build: work starts, and the software is live in production before the week ends. Small, real, growing.

Every Friday

A live demo of the working system. If a Friday comes with nothing to show, that week is free.

Acceptance

The final slice passes your acceptance criteria; docs and accounts are already yours. Partnership continues only if you want it to.

Can I stop after the Blueprint?

Yes — that's the design. The spec and quote are yours to take to any developer. About the worst outcome available is spending $1,000 to discover exactly what your system costs, which is not a bad worst case.

What if the build quote feels too high?

Then you decline it and keep the spec. You've spent $1,000 to avoid guessing at a five-figure decision — and if you build later, with anyone, the Blueprint still holds.

Start the week that answers everything.