We design and build web-based business software for work that off-the-shelf tools do not fit. We start with a small first release, agreed in writing and formally accepted before anything is added to it.
Custom software makes sense when your process is specific to your business, or when your current tools force staff to work around them. It is not the answer to every problem. In many cases a CRM, an ERP or your existing system can be adapted at lower cost, and we tell you so when that is the better route.
When building is the right choice, we do not build the whole system at once. We agree one small first release with a fixed scope, a list of what it excludes, and written acceptance criteria. You see a working preview before the second payment and accept the release in writing before the last one.
No new phase starts until the previous one is accepted. Large systems, such as multi-branch ones, are accepted only after a paid diagnostic and under written conditions, which are set out in the questions below.
We develop solutions designed specifically for how your organisation works.
A large first scope hides delays until late and makes changes expensive. Cost and dates drift because no single part was accepted before the next one began.
Custom systems carry their own maintenance. If a CRM or your existing system covers most of the need, a new build is money spent for no real difference.
When the only specification is that it should work like we do, each person remembers it differently, and disputes appear at handover.
Small additions during a build pile up. If their price is not agreed first, the final cost comes as a surprise.
If the code, hosting and accounts sit in the supplier's name, changing supplier means starting again.
Every deliverable is written or runnable, and you can check it before you pay for the stage that follows.
A written comparison of adapting what you have against building new, with the reasons for the recommended route. It is part of the diagnostic report.
Screens, user roles and business rules, what is excluded, and what is left to later phases. You approve it before work starts.
A written list, in plain language, of the checks the release must pass. Each criterion is a statement you can try yourself.
Versions you open and use during the build, on test data. The second payment is tied to one of these previews.
The release running in your own accounts, tested against the acceptance criteria, with the test results for you to read.
The final files, a short usage guide, a list of accounts and access, and instructions for running and backing up the system.
A separate, priced offer for what follows the first release. It starts only after the first release is accepted.
Five steps, each with a written output you can check.
After a free call, we run a paid 5-working-day diagnostic. We map workflows and compare adapting the current system with building a new one. You receive a 5–8 page report, an agreed illustrative deliverable, 3 priorities and an implementation offer for a defined scope.
Your part: You read the report and choose the first release. If a project starts within 30 days of delivery of the diagnostic report, the diagnostic fee is credited in full against it.
We write the scope, the exclusions, the milestones and the acceptance criteria into one fixed-price offer. Large work follows extra conditions, set out in the questions below.
Your part: You approve the scope in writing and pay the first payment, which is 40%.
We build in milestones and show a working preview on test data, not still images. Anything outside the written scope is priced before we do it.
Your part: You use the preview for real tasks and send comments in writing, then pay the second payment, which is 30%.
We test the release against the acceptance criteria and share the results. Defects found at this stage are fixed before acceptance.
Your part: You check each criterion and accept the release in writing, then pay the last payment, which is 30%. The final files are handed over after it.
We hand over the release and a short usage guide, with the accounts opened in your name, and then leave them. Fixes for defects are free for 14 days after delivery. The next phase is a separate offer and does not start until this one is accepted.
Your part: You confirm the handover and decide whether to start the next phase or take an optional monthly plan.
Start with the 5-working-day diagnostic. It tells you whether to build, adapt or leave things as they are, and it ends with a fixed offer for a small first release. If a project starts within 30 days of delivery of the diagnostic report, the diagnostic fee is credited in full against it.
For complex work that needs assessment before implementation can be priced. Deliverables are agreed before the start; simple services begin with a free call and a written offer.
Adapt when your CRM, ERP or current system already covers most of the process and only needs changes or connections. Build when the process is specific to your business, when you want one tool in place of several, or when you need access rules your tools cannot provide. Rebuilding an existing system is possible when it is the better route. The diagnostic gives you this recommendation in writing, with reasons, before you commit to a build.
One working part of the system that is useful on its own, such as the booking flow and staff logins. The scope lists the screens, user roles and business rules, and it also lists what is excluded. Acceptance criteria are written before work starts. Everything else is planned as later phases, and each phase has its own offer.
Tell us. If the request is outside the written scope, we price it in writing before doing it, and you decide whether to add it now, move it to a later phase, or drop it. Nothing is added without your approval, so the agreed price does not change silently, and we tell you if a change affects the dates.
Payments are 40% at the start, 30% when you see a working preview, and 30% on acceptance and approval, and you see the evidence for each stage before you pay it. You own everything we deliver, the accounts are opened in your name, and no new phase starts before the previous one is accepted. Final files are handed over after the last payment.
Yes, under written conditions. Large multi-branch systems, and systems that hold sensitive health, financial or personal data, are accepted only after a paid diagnostic. They need a written scope, phases of one first release each, accounts in your name, and a liability cap equal to the fees in the contract. Sensitive data stays inside your own environment, with temporary permissions and a data-processing agreement.
You own everything we deliver. Hosting, licences, domains and external subscriptions are priced separately and opened in your name. We work with temporary access and leave the accounts after handover. We fix defects free for 14 days after delivery, and after that an optional monthly plan covers fixes, changes and support.
Describe the process you want to run in software. We will reply with the next step, which is usually a short conversation before the diagnostic.