How We Work
The steps a software project goes through from first call to launch and beyond, what we deliver at each step and what we need from you.
Most software projects get hard not for technical reasons but because of uncertainty: work starts before anyone is clear on what will be built, when it will be done and what it will cost. Our process is designed to reduce that uncertainty at every step. Here is how a project runs from start to finish, and what you have in hand at the end of each stage.
1. Discovery call (free)
Before proposing anything, we listen: which process, run by whom, with which tools — and where is the most time or money lost? Where useful, we talk to your team and review existing screens and documents.
Output: a written summary of the problem and a measurable goal (for example, "halve the time it takes to prepare a quote").
2. Scope and proposal
We define the shortest path to the goal: which screens, which user roles, which integrations — and, just as important, what is out of scope. The proposal includes milestones, an estimated timeline and the engagement model. See pricing for details.
Output: written scope, milestone-based proposal, timeline.
3. UX design and architecture
Before code is written, we turn user flows into wireframes and a clickable prototype and test them with your real users. In parallel we design the data model, integration points and hosting architecture. Risky parts — such as integrating with a legacy system — are validated with a small spike.
Output: approved prototype, technical architecture document.
4. Development in two-week cycles
Development runs in two-week sprints. We agree priorities at the start of each one and review working software together in a staging environment at the end. Misunderstandings surface within two weeks, not months.
Every change goes through code review and automated tests. Security checks and data protection requirements are never left to the end.
Output: a working release in staging every two weeks, plus a short progress note.
5. Testing, training and launch
We run acceptance testing with you, rehearse any data migration, train users and plan a zero-downtime release. For critical systems, old and new run in parallel for a while.
Output: live software, user and admin documentation, transfer of source code and access rights to you.
6. Support and growth
Launch is the beginning of a product's life. During the warranty period we fix defects at no cost. After that, software support continues with defined response times: security updates, monitoring and new features driven by real usage data.
Output: monthly status report and a prioritised improvement backlog.
What we need from you
- A decision-maker: someone who can set priorities and give approvals
- Sprint reviews: about one hour every two weeks
- Access to users: a few real users for prototype and acceptance testing
Where to start
A few sentences about your project are enough. Fill in the quote form or write to us — we reply within one business day. Not sure which service fits? Browse our services.
Frequently Asked Questions
How often will we hear from you during the project?
We review working software together every two weeks and share a short progress note. A shared channel is opened for urgent topics.
What if the scope changes mid-project?
Change requests are assessed in writing, with their impact on time and cost, and added to the plan after your approval.
When is the source code handed over?
The code can live in a repository in your own account from day one. At the latest on launch, full rights to code, documentation and infrastructure access transfer to you.
How long is the warranty?
The warranty period is stated in the proposal. In-scope defects found during that period are fixed at no cost.