A delivery method designed for accountability.
Working software early and often. Decisions recorded, changes controlled, nothing goes live without acceptance, training and documentation. This is the method behind every custom build and every product onboarding.
Because a scope written before understanding is a guess.
Most software projects go wrong before they start: a proposal written from a one-hour call, a price fixed against assumptions, and six months of change requests to close the gap. The discovery sprint replaces that with a short, paid piece of work whose output is a written scope in your language and a working prototype you can click through.
If, at the end of discovery, a smaller build will do, or software is not the answer, we say so. The scope and prototype are yours either way.
- What you get from discoveryA process map of how the work actually happens, a written scope, a working prototype, and a proposal you can read in ten minutes.
- What happens every two weeksA demonstration of working software on your data, a written record of decisions and changes, and a clear statement of what is next and what is blocked.
- What go-live requiresAcceptance testing passed, training delivered, user and admin guides issued, and a formal sign-off from your side.
- What continues afterwardsHosting, monitoring and security updates, plus a monthly hours bank for changes, all under a written support agreement.
Not extras we charge for. How we work.
Frequently asked
Who do we deal with during a project?
A senior engineer leads the engagement from the first discussion to operation. There is no account manager relaying messages.
How are changes handled during the build?
Changes are discussed at the fortnightly demonstration, recorded in writing and approved before work starts. Nothing is built on a verbal instruction.
Who owns the code?
For custom builds, you do. Source code, data and documentation are handed over, and the repository is held privately with your access on request. Licensed products remain Hikstech platforms, with your data owned by you.
What happens if we want to stop?
You keep everything delivered to date: the scope, the prototype, the code and the documentation. Support agreements set out notice terms in plain language.
Start with discovery. Decide with a prototype in hand.
Describe the problem in a few lines and an engineer will come back to you within one working day.