Services
For the jobs a website can only describe.
A website tells someone you take bookings. An app takes the booking. The line between them is whether the thing has to hold state, do sums or talk to something else, and it is worth being honest about which side you are on before anyone spends money.
- Leeds
- Fixed prices
- No VAT
What's included
Everything below is in the price.
Not a menu of upgrades. If something is genuinely extra it is in the not-included list on the pricing page, in writing, before you commit.
-
A scoping phase you pay for separately, or not at all
Custom work goes wrong when it is priced before anyone knows what it is. So the first stage is a written scope: what it does, what it does not, what it talks to, and what it costs. If you take the scope and build it elsewhere, that is a legitimate outcome and the document is yours.
-
Built on boring, well-supported foundations
Nothing here depends on a framework that will be abandoned in eighteen months or a service that will triple its prices once you are locked in. That is a deliberate constraint and it is the reason these things are still running in five years.
-
The integrations you already rely on
Payments, calendars, email, your accounting software, the spreadsheet the whole business secretly runs on. Most useful software is mostly plumbing between things you already use.
-
Written down, so somebody else could pick it up
The code is commented, the setup is documented, and the handover includes how to run it and where everything lives. If you and I stop working together, another developer can take it on without starting again. That is the test of whether you actually own it.
-
A real staging environment
Changes get tried somewhere that is not your live business. Obvious, and routinely skipped by people quoting half of this.
How it runs
Four steps, and you know the price before the second one.
Numbered because it genuinely is a sequence: each step depends on the one before it.
-
A conversation about whether you need this at all
Quite often the answer is a website with a good form, or an off-the-shelf product that costs £30 a month. I will say so. Custom software you do not need is the most expensive thing on this site.
-
Scope, written down and priced
Screens, rules, edge cases, what happens when something fails. Fixed price per phase, so you can stop at the end of any of them.
-
Build in phases you can see
Something usable at the end of each phase rather than a six-month silence. You use it while it is being built, which is when you find out what you actually wanted.
-
Handover, then support if you want it
Every login, the code, the documentation and a walkthrough. Ongoing support is a separate monthly arrangement and it is optional.
From
£4,500
No VAT
What this costs.
App work is Bespoke, from £4,500, scoped and priced in writing before anything starts, and phased so you can stop at the end of any phase.
See the full pricesQuestions
Apps, specifically.
The general ones are answered on the homepage. These are the ones that only come up about this kind of work.
Do I need an app or a website?
A website, almost certainly, unless the thing has to remember something between visits. Bookings, accounts, stock, orders, anything with a login. That is app territory. Opening hours, prices, photographs and a contact form are not, and building an app for them is a way to spend four times as much for a worse result.
Does this mean something in the App Store?
Usually not, and usually that is good news. Most small businesses are better served by something that runs in a browser and installs to a home screen: one thing to build, nothing to submit for review, no 30% cut, and it works on everything. A real store app is worth it when you genuinely need the hardware or push notifications, and I will tell you when that is.
What does it cost to run afterwards?
Depends on what it does, and I will give you the number as part of the scope rather than after launch. A small booking tool is a few pounds a month. Anything storing a lot of data or sending a lot of email costs more. It goes in writing before you commit.
What if you get hit by a bus?
The code is in a repository in your name, the documentation is written for somebody who has never seen it, and nothing runs on an account only I can access. That is not a comfortable question to be asked but it is a fair one, and the answer has to be structural rather than reassuring.
The next step
Let's find out if I'm the right fit.
Twenty minutes on the phone. You tell me what isn't working, I tell you what I'd do and what it costs. If it's not me you need, I'll say so.
Or call 07700 900123. I reply within one working day.