Quotes, jobs and diaries in one place, for trades firms.

Three sizes, all fixed price for the scope written in the quote: Fix One Thing, one narrow job, at £950; a single-job tool from £2,950; and a connected business hub from £5,950, subject to written terms. Before any of those, a 15-minute call is free, and a £500 discovery gives you a written plan and a fixed quote. The £500 is credited to the build if you accept within 12 months, and if the quote is not one you would act on, tell us within 30 days of receiving it and we refund the £500 in full (once per business). There are no per-user fees. Hosting and third-party charges (email sending, payments, a domain) are paid by you or passed on at cost, and the quote lists them. We are not VAT registered, so the figure you see is the figure you pay. Conditions apply to every refund or fix promise: the clock pauses while we wait for you, and you must claim within set windows. They are set out in our written order terms, which come with every quote and which win over this page; ask us for a copy at any time.

The code repository, the hosting account and the domain are set up in your own accounts from day one, with us added as a user, so nothing sits on our side that you cannot see or reach, and we never lock you out over a dispute. When you have paid in full, and any refund window has ended, we assign you the rights we own in the custom code we wrote for you (clause 9 of our written order terms), with a signed assignation sent to you afterwards. We keep our own reusable components and licence them to you, and open-source parts keep their own licences. We build with AI coding assistants, and we do not promise that copyright exists in code an AI wrote. The terms set this out.

We are one person, so we plan for that instead of promising it will not happen. Because the repository, hosting and domain are in your accounts, any competent developer can take over without asking us. Every build comes with a plain-English handover document (what it does, where it lives, how to restore it) kept in your repository, and a Business hub also gets a recorded walkthrough. We use mainstream, widely known tools rather than anything exotic. If Liam cannot continue, the written terms say you get everything in your accounts and a refund for work not yet delivered. We do not yet have a named backup developer. The optional care plan keeps backup checks and monitoring running, and you can end it with 30 days' notice.

Your customer data stays in your own accounts. Where we handle personal data for you (for example on a care plan), you are the controller and we are your processor, under a written data-processing addendum. We build with AI coding assistants. We aim to build and test with made-up data and to keep your customers' and patients' records, passwords and secrets away from them, but we cannot promise that nothing personal is ever included, because the content you give us can contain names and contact details. If we find personal data has reached an AI tool, we tell you. If a fault can only be diagnosed with real data, we ask you in writing first. Only the people you choose can see your data, and we ask for the minimum access we need to do the work.

Not at present. We say so on the page and in the terms rather than leave you to find out. If you need a supplier with that cover, tell us in writing before you accept a quote. If we cannot get it on reasonable terms, you can withdraw before work starts and we refund anything you have paid.

Sometimes. If a standard job app (ServiceM8, Tradify and similar) already covers quoting, scheduling and invoicing for you, If it does what you need, use it: it will cost less and we will say so on the call. We are worth a call when your process has a twist that those tools handle badly, or when you would rather pay once than per user per month for ever.

It has to work on a phone with one hand and wet fingers, so we design the engineer view first and test it with your people before the office screens. If it is not easier than the current way, they will not use it, and we would rather find that out in discovery than after the build.