//architecture-estimator
Mobile & Spatial Software Architecture Estimator
A planning model, not a price list. Configure the architecture you think you need and see what it implies for effort, timeline, delivery risk and budget order-of-magnitude.
Mobile & Spatial Software Architecture Estimator
Planning model · not a quote
Payments, ERP, CRM, identity, logistics, IoT and similar systems.
Engineering effort
214person-days
Indicative timeline
11weeks · 5 people
Delivery risk
33/ 100 · Contained
Indicative planning range
€102,500 – €162,500
Derived from 214 person-days at a blended €480–€760 per engineering day, excluding VAT. A maintenance year of roughly 33 days is quoted separately and is not included above. Indicative planning figures only. This is not a quote, not an offer and not a contract. Actual scope, effort and fees are agreed in writing after a technical scoping session.
Effort by discipline
- Mobile engineering70d
- Backend & cloud44d
- Architecture17d
- QA & test automation33d
- Security18d
- Product design16d
- Delivery management16d
Delivery phases
Phases sum to the full 214 person-days.
What this configuration implies
- Personal data is in scope, so the engagement includes a data-processing agreement and a documented data-flow map.
No account, no sign-up, no obligation.
What the model assumes
- Effort unit
- One person-day is one engineer working one day. It is not a calendar day and not a billable hour count.
- Team velocity
- The timeline assumes 4.2 productive days per person-week, which allows for meetings, review and the rest of a real week.
- Day-rate band
- The planning range uses a blended EUR 480-760 per engineering day across all disciplines, excluding VAT. Your actual proposal may sit outside it.
- Maintenance
- A maintenance year is estimated at 15% of build effort and is always quoted separately from the build.
- Not included
- Cloud infrastructure, third-party licences, app-store fees, translation, content and hardware are yours to procure directly.
What it is not
These figures are indicative planning numbers. They are not a quote, not an offer capable of acceptance, and they do not form a contract. Nothing here binds us or you.
A real estimate needs the things a form cannot capture: the state of the systems you already run, what your users actually do, which integrations have test environments, and what your deadline is driven by. That is what a scoping session is for, and it is where a written proposal comes from.
The same calculation runs on our server as in your browser, from one shared model. The build fails if the two ever disagree, so the number you see here is the number our API produces for the same inputs.
Turn a configuration into a real proposal.
Send the shape you arrived at and we will tell you what it would actually take, including where we think the model is wrong for your case.