Apps
When a spreadsheet or a brochure site is no longer enough, we build the software. Internal tools, customer logins and small products, on a staging URL you can use before anyone else can. You can pay us to build it and own it. Or, when other businesses would buy the same thing, we may build it without a build fee and you stay a customer. Hosting and care sit alongside either path.
How the build is paid for
Both start with a conversation about whether we are the right people, then paid discovery. That is where we say if this is only your app, or an app other businesses would buy. App Care, the hosting plans, sits beside either path. It is not how the build is paid for.
You pay for the build. The app is yours.
If discovery says we should build it, we agree a contract and a fixed price before we start. We build it and hand it over. We can host it and we can manage it. You can also take it somewhere else. If the first conversation shows we are the wrong fit, we say so and stop.
No build fee, if other businesses would buy it.
If discovery shows the same job exists elsewhere, we may waive the build fee. In return you contract to stay a customer for two or three years. The length depends on the project. We design it around your work, and we build it so other businesses can use the same product. The product is ours to sell. Once it is live we try to sell it on, and what you pay falls as new customers join. If the idea works, you could end up paying nothing for software that would normally carry a serious fee. That is possible. It is not a promise. We only offer this when we believe we can sell it.
What we build
Most of this work is for a business with a process stuck in email and spreadsheets, or a product people need to log into. We are not interested in a prototype that looks finished and cannot be used on a Tuesday.
Jobs, stock, training records, bookings. The spreadsheet three people are afraid to touch, turned into one place where the right people can change the right things.
A portal, an account area, or a workflow your customers or staff finish themselves. It runs in the browser, including on a phone, so there is no app-store release to wait on.
Software you charge for, or a tool we already run. TrackQUAL is the live example: qualification and training tracking, built for the people doing the admin.
How a build runs
You should be clicking the real thing early, not approving a picture of it. Nothing goes live until you have used it yourself, on a staging URL, so there is no half-finished product sitting where your customers can find it.
01
A conversation first, to see if we are the right people. If we are, discovery is paid. That is where we agree what the first version leaves out, and whether this is Build for you or Build because of you.
02
We put a working piece on staging. Not every screen. Enough that you can try the actual job and tell us what is missing while it is still cheap to change.
03
Permissions, emails, the records that do not fit a simple case, and the bits that only show up when a real person uses it. Those get tested before anyone else sees the app.
04
We switch it on and watch it. On Build for you, we hand it over: the app is yours, and we can host it and manage it if you want. On Build because of you, it goes live as a product we run, with you as the first customer.
What is live
We would rather show you something that exists than a mock-up. TrackQUAL is live. EasiAsset is still being built, so there is nothing to sign up to yet.
Hosting and care
App Care is how we look after a live system on your cloud account. Azure, Vercel, Supabase, or another platform we already work on. You pay that provider yourself. Our fee is for watching it, and it is quoted separately from a Build for you project. On Build because of you we run the product, so your deal is the customer contract, not one of these tiers.
When the app is yours
See the tiers
Five tiers, from a monthly health check through to staging, managed deploys and included time. Prices are on the App Care page and exclude VAT. The cloud invoice is not included in the fee.
On request
Further features are quoted before we start. A quiet month of care is not a bank of build time. Send the list and we will price it.
Questions
A tight internal tool is often a few weeks once we agree what the first version leaves out. A product with several roles, payments or a lot of existing data takes longer. The delay is usually the decisions, not the typing.
Discovery is paid, and quoted before it starts. Build for you is a fixed build price, agreed before we start. Build because of you has no build fee, and a customer contract of two or three years. There is no single number on this page, because the jobs are not the same.
On Build for you, you do. The code and the cloud account stay in your name. On Build because of you, we do. That is how we can sell it to other businesses. You are the first customer, and the one the product is designed around.
You still have the app, and you are still in the contract you signed. The discount depends on new customers. If none join, your price does not fall. We will not pretend it is guaranteed to reach nothing.
Tell us what it needs to do and who will use it. We will tell you if we are the right fit, and which of the two paths makes sense.
Cookies
We use Google Analytics to see which pages people actually read. Nothing is sold on. Decline and we will not set analytics cookies.
Read our cookie policy