App development effort calculator: team and weeks.
Pick the shape your build starts from, tick the features you actually need, and see the team, the calendar weeks and the phases it usually takes. Every line shows the engineer-weeks behind it, so you can see what drives app development cost before anyone talks money.
It is a realistic picture of the effort, good enough to plan a timeline and a budget conversation. It is not a quote: integrations, compliance, data migration and the reliability you need on day one all move it. You get a fixed quote in writing after a free 4-hour workshop.
Choose a starting point, then add features.
Pick a starting point above and the feature checklist opens here.
Questions people ask about this estimator
Put it in a brief. A senior engineer reads it and replies within one business day.
Why does it show weeks and not a price?
Because a price named before anyone has seen your systems is a guess, and a guess with a number on it tends to stick. At this stage effort is the useful unit: which roles, how many engineer-weeks, how many calendar weeks. CODT Technologies turns that into a fixed quote after a free 4-hour workshop, once the integrations and the v1 scope are on the table.
Is this a quote?
No. It is an estimate of effort: a starting point that covers the foundation, plus the engineer-weeks for each feature you ticked. What it cannot see is your data model, your legacy systems, the quality of the APIs you need to integrate with, or the reliability you need on day one. Those move the real number. The fixed quote comes in writing after the free 4-hour workshop; if the scope is still open, a paid discovery sprint comes first and is credited in full against the build.
Where do the weeks come from?
From the way our teams plan this work. Each feature block carries the engineer-weeks it usually takes and the role that does it, and each starting point carries the team and the calendar time of a first production release. Platform and design choices add a share of the feature effort; compliance adds fixed weeks. The added engineer-weeks are then spread across the team to give the calendar time.
What does the starting point already include?
The foundation (architecture, the design system, CI/CD, QA, a delivery lead and the release) plus the scope its own description names. Those building blocks are pre-ticked and marked included, so nothing is counted twice. Only what you add beyond them moves the timeline, and each addition shows as its own line with the engineer-weeks and the role behind it.
Why a range and not a single number of weeks?
The gap between the low and the high end is what nobody knows yet: how clean the integrations are, how much edge-case behaviour shows up once real users arrive, and how strict the compliance evidence has to be. The workshop narrows that gap. The written scope closes it.
Do you quote in Swiss francs, euros or US dollars?
Swiss clients get their fixed quote in Swiss francs, EU clients in euros and clients elsewhere in US dollars. The amount you sign, in that currency, is the amount you pay for the agreed scope.
Is anything I enter stored or sent anywhere?
No. The estimator runs entirely in your browser: nothing you tick is saved, transmitted or attached to analytics, and no email address is required to see the result. The project brief leaves the page only when you copy it and choose to send it to us.
What happens after I copy the brief?
Send it, and we set up the free 4-hour workshop: your workflows, the systems it has to talk to and where the v1 line sits. A written scope and a quote follow within 3 working days. If the scope is still open, we propose a paid discovery sprint first, with an architecture and a costed roadmap you keep whatever you decide; its cost is credited in full against the build. If we build, 100% of the code and IP transfers to you.
Have a problem worth
solving well?
Tell us what you are building and the deadline it has to meet. You will get a clear read on whether we fit and what the work would take.