How we work
Clear stages, clear responsibilities.
This is how we work on a website, an online store or a platform: at every stage you know what you get, what you decide and what comes next, from the first call to ongoing development.
You always know where your project stands. Five stages, each ending in a result you see and approve.
01 / 05
Definition
Together we define what the product has to do, who it is for and what goes into the first version.
You getRequirements, flows and an estimateApproved by you
02 / 05
Design
We draw the screens and link them into a prototype you can try before a single line of code is written.
You getA clickable prototype and final screensApproved by you
03 / 05
Development
We build in short stages. Each version goes to a test environment, where you can see and try it.
You getWorking versions in a test environmentApproved by you
04 / 05
Launch
We launch, move the data over from the old system, train your team and hand over access.
You getA live product, training and access handed overApproved by you
- Tests
- Migration
- Training
- Access
05 / 05
Ongoing development
After launch we monitor how the product runs and improve it, based on priorities we set together.
You getMonitoring and prioritized improvements
Who does what, at every stage. Responsibilities are set from the start, so there are no grey areas.
1Definition
- We
- We talk to your team, analyse the current flows and systems and prioritise the requirements.
- You
- You explain the goal and give us access to the right people and systems.
- You get
- Prioritised requirements, flows and an estimate.
- You decide
- What goes into the first version, and the budget.
2Design
- We
- We design the interface on the approved flows and test it on a prototype.
- You
- You give feedback on the prototype and the screens.
- You get
- A clickable prototype and final screens.
- You decide
- You approve the design before development.
3Development
- We
- We build in iterations, test and publish each version to the test environment.
- You
- You check the versions and answer questions.
- You get
- Working versions in a test environment.
- You decide
- You approve each iteration or ask for changes.
4Launch
- We
- Final testing, data migration, setup, release and training.
- You
- You prepare the final content and the access we need.
- You get
- A live product, training, access and documentation.
- You decide
- You approve the launch.
5Ongoing development
- We
- We monitor, fix and build improvements.
- You
- You set the priorities with us.
- You get
- Improvements delivered by the agreed priorities.
- You decide
- What comes next and the support level.
Three collaboration models. We choose the model by how stable the scope is, not by our preference.
- A good fit for you
Fixed-price project
- Fits when
- The scope is clear and stable: a website, an online store or a well-defined first version.
- How it works
- We agree on the deliverables; price and timeline are fixed on that basis. Changes are estimated separately, before they are made.
- What you control
- You know the total cost and what you get from the start.
- A good fit for you
Dedicated team
- Fits when
- The product keeps evolving and priorities change often.
- How it works
- A team works on your product from a priority list you set with us. The cost is based on the team’s capacity.
- What you control
- You decide the priorities at every iteration.
- A good fit for you
Ongoing development and support
- Fits when
- The product is live and you need improvements and someone to watch over it.
- How it works
- The contract sets what is monitored, how requests are prioritised and how quickly we step in.
- What you control
- You see what was done and what comes next.
How we estimate the budget. No catalogue prices: the estimate starts from what the product has to do.
We split the project into features
Each flow becomes a list of features you can read and discuss.
We estimate each feature
You see where each part of the budget comes from.
We separate the first version from what can wait
You launch what brings value sooner and postpone the rest.
You get the estimate in writing
With the assumptions behind it, so you know what could change it.
What changes the effort
Relative effort: small · A well-defined first version
- Integrations. CRM, ERP, payments: each has its own rules, tests and failure cases.
- Roles and permissions. More user types mean more screens and rules.
- Data migration. Existing data has to be cleaned, mapped and checked.
- AI features. Test data, result validation and running costs.
- Custom design. A visual system of your own takes more than an adapted theme.
- Several languages. Translations, URLs and content for every language.
Illustrative, no prices. You get the real estimate in writing after the first call.
After launch. What is monitored, how it is prioritised and who is responsible for what, all set in the contract.
What we monitor
Uptime, errors, forms and payments, as relevant.
How we prioritise
Together, by business impact and urgency.
What support covers
Fixes, security updates and small improvements, as agreed in the contract.
Response times
Set in the contract, depending on how critical the product is.
Third-party services
Hosting, payments, APIs: we agree who is responsible for each.
Questions about working together. Kick-off, preparation, takeovers and support.
How does the collaboration start?
With a call about your goal and feasibility. Then comes definition: requirements, flows and a prototype. Development starts once you approve the estimate and the plan.
What should I prepare?
A description of the problem, examples you like and access to the systems you use: CRM, ERP, payments. If you don’t have them all, we sort them out together.
Can you take over an existing project?
Yes. We start with an audit of the code and data, then propose the right path: build on what exists, modernize in stages or migrate to a new system.
What happens after launch?
We take care of maintenance: we monitor the product, fix issues and keep improving it, with priorities we set together. The support level and response times are agreed in the contract.
Let’s start with the first call. Goal, feasibility and the next step. Write us a few lines about your project.
What happens next
- You send the requestA few lines about what you want to build.
- We get in touchWe clarify the details and book the call.
- The first callGoal, feasibility, next step.
Prefer to reach us directly?
Thank you! We’ve received your request.
We’ll get in touch to clarify the details and book the first call.
Local demo: the request was not sent anywhere.




