The part your users touch.
Web and mobile apps with a designed interface, not a default one — accessible from the first checkpoint.
Product engineering →9io is a small team of senior engineers, with a fractional CTO, a designer, a product manager and QA. We build your product, keep it running, and bill only for the hours we work. You get a whole tech team without having to hire one.
Most builds are bought in pieces — design here, code there, hosting somewhere else. We take a product from the screen your users touch to the servers it runs on, and keep it running afterwards.
Web and mobile apps with a designed interface, not a default one — accessible from the first checkpoint.
Product engineering →APIs, payments and the third-party systems nobody documented — with the architecture decided by someone accountable for it.
Fractional CTO →Pipelines you can trace, and AI features tested on every change — plus the honest answer when you don't need AI at all.
AI engineering →Infrastructure as code, continuous deploys and alerting from day one — live before the product is even finished.
How we work →Most products don't stall on the idea. They stall between the demo and production. That's the part we're for.
Web and mobile apps taken from a blank repository to real users — or a stuck one rescued and finished.
Product engineering →A fractional CTO who owns the technical decisions — architecture, security, what to build first. A day a week, or more.
Fractional CTO →Engineers, design, product and QA working as one team on your product, sized up or down as the work changes.
Dedicated team →AI features that work in production, not just in the demo — and honest advice when you don't need AI at all.
AI engineering →One email is enough. No forms, and no sales call you have to sit through.
Who'd do the work, how many hours, and the rate for each person. No management fee, no hidden extras.
A staging link early on and a short update every Friday. You're invoiced only for work that's landed, and 10% waits until you've accepted it.
Roughly what a full-time CTO in the US costs, all in. That's one person — the team still has to be hired around them, and the salary runs whether or not there's product to build that month.
The same seniority, for the hours the work actually needs — a day a week or a full push. It comes down between pushes and stops when there's nothing to build.
$300k–$400k is a commonly quoted range for a fully loaded US CTO, not a researched statistic. We don't publish rates, because they depend on which roles you need and for how long — the proposal sets them out before you sign anything.
It scans two stock markets every day, runs AI research on what it finds, and connects to two brokers. We designed it, built it and keep it running — the same way we'd build yours.
Take a look →An engineering showcase, not investment advice.
You pay by the hour for the people doing the work, invoiced twice a month for work that is already done. Rates depend on which roles you need and for how long, so they are written into the proposal before you commit to anything.
Usually within a couple of days of agreeing a proposal. If we cannot start that quickly, we will say so rather than take the work and sit on it.
A first version that does one thing properly usually takes weeks. Live data, a pile of integrations or rules you have to comply with will push that out, and we will tell you before you start rather than halfway through.
Yes. It sits in your repository from the first commit and becomes yours as you pay for it. There is no handover at the end, because nothing was ever kept on our side.
The first stretch of work is meant to leave you with something whole: a running foundation, the architecture written down, and a fixed price for the rest. After that you can carry on with us, take it to another team, or stop. There's no retainer to unwind.
If you will need twenty engineers on staff this year, that team belongs in-house. If a form or a database query solves your problem, you do not need AI for it. We would rather tell you than sell you the bigger version.
A few lines is enough: what it is, where it's at, and what's missing. You'll get a straight answer about what it would take — and if we're not the right fit, we'll say so.
Replies come from the person who'd do the work.