Services · custom software, built properly

What we build

A focused set, done properly.

We would rather do a small number of things well than claim everything. Here is what we take on, and how we think about each.

Web applications

Production-grade apps on a stack chosen to still make sense in three years. Fast to load, accessible by default, and instrumented from day one so you can see how people actually use it. Built to grow with you, not to be rewritten in a year.

SaaS products

The parts that are easy to underestimate: authentication, billing, multi-tenancy, roles and permissions, and the infrastructure beneath them. The unglamorous foundations that decide whether a product survives its first hundred users. We have built all of those already, for Dachshund, so we are not learning them on your budget.

Mobile apps

iOS and Android that feel native, not a website in a frame. We will tell you up front whether your idea wants a full app, or whether a good mobile web experience serves you better and cheaper.

Desktop software

Windows-native tools that run at the speed of the machine and keep working when the line drops. Desktop is where we are most at home: fast, local, and built to survive a bad connection instead of assuming a good one.

Cloud & backend

The APIs and infrastructure your product runs on. Built to stay up, scale cleanly, and never turn into a system nobody understands. We document what we deploy so you, or whoever comes after us, can reason about it.

AI & integrations

Practical AI and tidy integrations that do real work, not demos. We wire your tools together and add intelligence where it earns its place. If an idea does not actually need AI, we will say so instead of selling you a buzzword.

How it runs

Six steps. You approve each one before it costs you anything.

01 · Define: We work out what you actually need, which is often not what the first conversation describes. You get a written scope, and a read on cost, risk and what we would leave out.
02 · Design: Screens and flows before code, so we are arguing about a picture, not a half-built product. Cheap to change at this stage, expensive later.
03 · Build: Built in stages you can see, against the scope we agreed. If something turns out to be a bad idea once it is real, we will say so instead of building it quietly.
04 · Test: Automated tests on the paths that would cost you money if they broke, running on every change. Where the project handles money, accounts or customer data, the heavier end of the standard applies.
05 · Launch: Shipped carefully and handed over in full. See exactly what handover contains below.
06 · Support: Launch day is the start, not the end. Defect cover runs for ninety days at no charge, and ongoing work is on terms that suit how much you actually need.

What it costs

Three ways to work, and a written quote before anything.

We do not publish rates, and here is why. A price with no scope attached is a guess, and a guess you have already budgeted against is worse than no number at all. So the number you get is for your project, in writing, after we have talked about it.

Discovery sprint: A short, paid piece of work that ends in a written scope, an approach, and a read on cost and risk. If you go ahead, this fee comes off the build.
Fixed-scope project: Most of what we take on lands here. Agreed scope, agreed price, staged payments. If we misjudge the estimate that is our problem, not your budget.
Monthly partnership: For products that keep evolving. A set number of days a month, on a notice period we agree up front so neither of us is trapped.

Tell us your budget on the first call, even if you think it is too low. We will either tell you what is achievable at that number, or tell you that we are not the right fit, which is cheaper for both of us than three meetings finding out. Not VAT registered: the price you are quoted is the price you pay.

Handover

"You own it", itemised.

Most studios assert this. Here is exactly what it means, so it is a commitment rather than a comforting phrase.

The source code: In your company's repository from day one, not handed over at the end. We are a collaborator on your repo.
Every account: Hosting, domain, database and third-party services registered to your company with billing under your control. No account of ours that your business depends on.
Every credential: In a password vault your business owns.
Documentation for a stranger: A README a competent engineer who has never met us can use to get it running. We test that by following it ourselves, cold, before handover.
A written record: What was built, and why the significant decisions went the way they did.
A call with whoever takes over: Thirty minutes with the next engineer, whenever that happens, at no charge. Even years later.

Start here

Tell us what you want built.

A rough description is enough to start. You will get a straight answer about whether we are the right person for it, and a written quote before anything is committed.

Start a project Read the awkward questions first

Six things we build, properly.