Discovery, design, development, testing, launch and support — what happens in each stage, what you are asked to do, and how to avoid the usual delays.
If you have never commissioned software before, the process can feel opaque: you send a brief, and weeks later something appears. It does not have to work that way. A well-run project has clear stages, visible progress every week and very few surprises. Here is what happens at each step, and what we will ask of you.
1. Discovery
We turn your idea into a concrete plan: who the users are, what they need to do, which features belong in the first version and which can wait. The result is a written scope with screens listed, an estimate and a timeline.
Your part: explain the business goal, share examples you like and make decisions on priorities. A good discovery saves far more time than it takes.
2. Design
First wireframes — simple layouts of the key screens — to agree the structure. Then the visual design in your brand: colours, typography, components and the main pages for both phone and desktop.
Your part: review and give consolidated feedback within a few days. Collecting comments from several people into one list keeps design rounds short.
3. Development
The work is split into short cycles, usually one or two weeks each. At the end of every cycle you see a working demo on a staging site — real screens you can click, not just a status report.
Your part: attend the weekly demo, test what was delivered and answer questions quickly. Most delays in software projects come from waiting for decisions or content, not from the code.
4. Testing
Every feature is tested as it is built. Before launch there is a full round across real phones and browsers, plus forms, payments, emails and permissions. Speed and security checks happen here too.
Your part: user acceptance testing — trying the system the way your staff and customers will, and confirming it is ready.
5. Launch
Server set-up, SSL certificate, backups, final content, analytics and a planned go-live time, usually outside your busiest hours. For websites we also submit the sitemap to Google and set up redirects from any old pages.
Your part: domain and hosting access, final sign-off and telling your customers.
6. Support and growth
After launch comes a free bug-fixing period, then ongoing maintenance and support: updates, backups, monitoring and small improvements. Real usage always reveals the next features worth building.
How to keep a project on time and on budget
- Protect the first version. Launch with what is essential, then add. Every "small extra" during development adds time.
- Have one decision-maker. One person who can approve designs and answer questions keeps work moving.
- Prepare content early. Texts, photos and product data are often the last thing ready.
- Use change requests. New ideas are welcome — they are estimated and scheduled rather than squeezed in.
What you should expect from your development partner
- A signed NDA and clear ownership of the code and intellectual property.
- A weekly demo and an honest update, including problems.
- Access to the staging site and, ideally, the code repository.
- Written documentation and a proper handover at the end.
That is how we work on every project. If you have an idea ready to plan, tell us about it — or read more about how we work.
