PIPELINEGuide
Custom software: process, approach, and what we need from you
The process for custom software from the first question to live operation — including what you need to contribute to make it work.
A custom software project runs in 4 steps: from “understand the process” to “handover,” a total of 8 weeks or more to the first version. Each step ends with a clear approval before the next one begins.
01 — Process
The steps in detail
Understand the process
We watch how work is done today. This regularly uncovers requirements no one would have mentioned.
Minimum usable version
What's the smallest piece that already helps in daily work? That's where we start.
Expand
In two- to four-week increments, each with something you can use.
Handover
Documentation, training, source code. You shouldn't be tied to us.
02 — Participation
What we need from you
- A contact person who can make decisions — not just forward them.
- Access to the affected systems, in time and not on launch day.
- Real examples from daily business — the messier, the more useful for testing.
- Two to four hours for coordination, distributed over the project duration.
- An answer to the question of what success means. Without it, nothing can be assessed afterward.
03 — Scope
What's included
- Requirements gathering with the people who will be working with it
- Implementation in small, usable steps instead of as a large-scale project
- Migration of existing data from spreadsheets and legacy systems
- Roles and permissions, logging, and backup from the start
- Integration with your existing systems instead of creating another silo
- Documentation and source code that belongs to you
04 — Questions
Frequently asked questions
How many users can a system like this handle?
That depends on the architecture, which we plan according to your expected growth — from a few users in your own business to several hundred across multiple locations.
Does this run on our own servers or in the cloud?
Both are possible. For most businesses, a cloud solution is lower-maintenance; where data must not leave the premises, we set it up on your own infrastructure.
Who owns the source code?
You do, completely, upon payment. That's in the contract. You can take it to any other developer — that's the point.
When does custom software pay off compared to standard software?
When your process is a genuine competitive advantage, when standard software only fits seventy percent and the rest ends up as manual work, or when license costs per user exceed the development cost over a few years. If it's only about convenience, standard software is cheaper.
How do we avoid the project going off the rails?
Small steps with usable results, fixed budgets per step, and the option to exit after each step. Large fixed-price projects over twelve months are the most reliable path to disappointment — for both sides.
What if we discover new requirements during development?
That's normal and planned for, because we work in small steps. A new requirement is incorporated into the next step, instead of stalling the entire project.
What happens if we no longer work together?
You have the code, documentation, and access. We deliberately use widespread technologies so that a switch is possible without someone having to rebuild everything.
05 — Decision
How to move forward
The most affordable next step is a conversation, not a quote. Twenty minutes is usually enough to clarify whether a project makes sense, what scope it involves, and whether we're the right fit.
If we're not, we'll say so. An honest no costs less than a project you abandon after three months — for both sides.
06 — Next
Related pages
- Custom software — Overview
- Custom software — Practical examples
- Custom software — Cost-effectiveness
- Custom software — Duration
- Custom software — Common mistakes
- Custom software — Do it yourself
- Custom software — Prerequisites
- Custom software — Funding
- Process automation
- CRM integration
- API Interfaces
- All guides
Custom software by region
Next step
Initial assessment, no obligation.
Briefly describe what you need. You'll get an honest answer about what's realistic and what it will roughly cost.