altoby.

Questions operators ask.

The honest answers, including the ones other shops keep for the sales call.

Why are your prices a fraction of US agency quotes?

No downtown office, no account managers, no bench of juniors billed to your project. One senior engineer, AI-accelerated, working from Nairobi with clients in the US and Europe. The structure costs less, and the margin goes to you — the contracts, the process, and the code are what you'd expect at five times the price. It's not a discount. It's a different shape of company.

You're in Kenya — how does that work for us?

The way it already works for my clients in Cyprus and the US: contracts on your jurisdiction's terms, invoices in USD, IP assigned in writing, your code in your GitHub organization from the first commit, your infrastructure in your accounts. Nairobi is 3 hours ahead of London — full UK overlap — and US East Coast mornings are my afternoons. The Friday demo is a call; everything else is asynchronous and documented.

How do I know you won't disappear like the last developer?

You can't know it from promises — mine or anyone's. So the structure protects you instead: you own the repository from day one, every week ends with a live demo or that week is free, the spec and docs live in your repo, and payment is staged against delivered scope. If I vanished tomorrow, you'd hold everything any engineer needs to continue. That's the test worth applying to anyone you hire — including me. (For what it's worth: the worst rescue I've done was a build from a developer in Canada. Geography doesn't cause bad software. Missing process does.)

Do you build websites at all?

Only when they're a door into the system — a portal login, a booking flow, a member signup. A marketing site on its own: not my work, and any web designer will serve you well.

I have software that's half-built. Can you take it over?

That's half my work. The Rescue Blueprint starts with an audit of what exists; you get an honest keep-or-rebuild verdict with reasoning you can check — about a third of audits end in "keep most of it."

What's the smallest engagement?

The $1,000 Blueprint. It's deliberately small: you risk one week and one price to find out exactly what your system costs before committing to it.

What stack do you use?

TypeScript end to end — React and Next.js, Postgres, deployed on infrastructure you own in the EU or US. Deliberately boring: hireable worldwide, stable for a decade, fast enough for almost everything.

How does "a demo every Friday or that week is free" actually work?

Literally: every Friday you see the real system running in production. If a Friday arrives with nothing to show and no written explanation, that week isn't billed. It goes in the contract, not just on this page.

Who owns the code?

You do — code, data, infrastructure, and documentation, in your accounts, with IP assigned in writing on payment. Leaving me is a decision, never a hostage negotiation.

Do you use AI to build?

Yes — Claude Code, openly. You'll see it in your commit history. Every change is reviewed by the engineer who answers to you, and nothing ships until the tests built from your acceptance criteria pass. The speed is already in the price.

Can we sign an NDA first?

Yes, before we talk specifics. The honest caveat: execution is the moat, not the idea — the Blueprint exists to find out if yours is worth executing.

What happens after launch?

Your choice: hand over and walk away with full documentation, or the partnership from $1,500/month — modules, maintenance, monitoring, and a senior engineer on call. Cancel monthly.

Question not here? It fits in the form.