How a software project runs, from first conversation to go-live
A software project at Aziri has six steps: introduction, a scan or straight to a proposal, analysis on site with a fixed price, building with a weekly demo, testing with your own people, and support. A first working version is usually running 2 to 6 weeks after the build starts.
Below you can read what happens at each step, what we need from you and where you make the decisions.

Some of our clients
How does a software project run at Aziri?

Introduction
We ask how your business works, where the process gets stuck and what software you already have. Then we tell you honestly whether custom software makes sense. Sometimes the answer is a standard package or better settings in what you already use.
A scan or straight to a proposal
If the question is clear, we make a proposal straight away. If it is broad or still vague, we suggest a digital scan: a few working sessions and a concrete plan that you can also carry out without us.
Analysis and a fixed price
We visit, look at your Excel files, forms and documents, and talk to the people who work with them every day. You get a scope description to approve and a proposal, preferably with one fixed price for analysis, build, testing and delivery. You do not pay for the analysis separately: it is part of the digital scan or of the price of the project. What has not been discussed is not included.
Building, with a weekly demo
Your dedicated project lead shows you every week what has been added. Comments, questions and changes are logged as tickets on a project board you can follow yourself. So nothing gets built in the dark for months.
Testing and going live
Your team tests with real data, we make adjustments and put the software live. For the first three weeks after that we stay especially close, because that is when the questions come up that no test finds.
Support and further development
After the aftercare period we stay available for questions, changes and maintenance, with fixed response times that we set out in the proposal. If you want to build further, we do that in new phases, with the same people who already know your process. If your own people want to build along, that works too: co-development.
How long does each step take, and what does it ask of you?
How long it takes to have software built depends mainly on the number of processes and integrations. This table shows a typical project for one process.
| Step | Duration | What you do | What you get |
|---|---|---|---|
| Introduction | Half an hour | Explain where things get stuck and which software you have | An honest answer on whether custom software makes sense, and the order of magnitude |
| Scan (optional) | A few weeks, sessions of ±3 hours | Free up your people for working sessions | A plan with priorities, timing and budget, from €2,000 |
| Analysis and proposal | A few working sessions of a few hours | Show your Excel files, forms and documents | A scope to approve and preferably one fixed price |
| Building | Usually 2 to 6 weeks to a first version | Half an hour a week for the demo | Working software every week and a project board with tickets |
| Testing and go-live | A few weeks | Key users test with real data | Go-live only after your approval, then three weeks of aftercare |
| Support | For as long as you use the software | Pass on reports to the service desk | Fixed response times, set out in the proposal |
Larger platforms we build in phases over 2 to 4 months, so you are working with a first part after a few weeks.
![]()
A web app that shows how accessible cafés and restaurants are
There was little digital information on how accessible cafés and restaurants are. For Inter we built a web app in two months where owners and visitors fill in that information, with a medal and a place on Google Maps.
Read the caseThe framework offered for efficient cooperation, and the openness to discuss things properly, thoroughly and in depth, were of great added value to us.
- 2 months
- of development, within budget
- 3,000
- cafés and restaurants reached
- 600K
- people with a disability in Flanders
Frequently asked questions
Question not listed? Ask us directly.
How long does it take to have custom software built?
A first working version is usually running 2 to 6 weeks after the build starts. That is faster than it used to be because we build with AI: AI helps write the code, and our developers steer it and check every line. Before that come the introduction and an analysis of a few working sessions. A platform for several departments is built in phases over 2 to 4 months.
Who is my point of contact?
One dedicated project lead, from analysis to delivery. Internally we call this role the product owner. They know your process, make the choices with you and direct the developers.
How do you keep scope and budget under control?
The scope is fixed before we build, and you approve it. If something is added along the way, you get a price first and you decide whether we do it. Nothing is carried out without your approval.
How much time does it take from my people?
Mainly during the analysis and testing. Expect a few working sessions of a few hours, half an hour a week for the demo, and a test period in which your key users really use the software.
How do you test?
We test ourselves while building, including the permissions per role, then your team tests with real data. We only go live once you give the go-ahead. At go-live we also test a full restore of the backup. More on technology and security.
What if we need to change course?
That is normal, and it is why we show you every week what has been added. We absorb small adjustments; larger changes get their own price so you know where you stand.
Is training included?
Not as standard. Because we build with and for the people who use it, most of them already know the software by go-live. If you still want training, we price it separately.
Do you outsource the build?
No. We do analysis, build, testing and support with our own team of 14 people. That way you talk to the same people from start to finish.
And if things do not go to plan?
Who owns the software?
The code we write for you and all your data belong to you, and you can always export your data. If part of it runs on a third-party platform, your proposal says so up front, along with how a handover would work.
What if your project lead leaves?
Your project does not live in one person’s head. Agreements, scope and tickets are on the project board, so a colleague can take over without you having to start again.
What if an update to my accounting software breaks the integration?
Then you report it to us, not to your vendor, and we follow it up through support. If rework is needed because of a change on the package’s side, we agree that with you in advance.
Where is my data stored?
In a European cloud region: the database runs on Supabase, the application on Vercel. A daily backup, with point-in-time recovery. Hosting, backups, updates and maintenance are included in the annual licence. More on technology and security. If you have specific requirements around privacy or data location, raise them in the first conversation.
Tell us where things get stuck
Tell us briefly how your process works today. We’ll let you know whether custom software makes sense, roughly what a first version costs and how quickly it can be running.
We reply quickly.
