Software scope & stack estimator
Explore a reference architecture and an illustrative delivery range for a bounded first software release. The estimator combines platform type, integration count, active-user scale and data-control needs. It is a planning heuristic, not a quote, capacity plan or commitment; discovery must establish workflows, team availability, access and acceptance criteria.
Updated
Use the custom software versus SaaS comparison to establish the gap before estimating a build.
Model a scenario, not a promise.
Explore a reference architecture and an illustrative delivery range for a bounded first software release. The estimator combines platform type, integration count, active-user scale and data-control needs. It is a planning heuristic, not a quote, capacity plan or commitment; discovery must establish workflows, team availability, access and acceptance criteria.
Your illustrative scenario.
Inputs stay in this tab. No calculator values are submitted or saved.
The range assumes one small cross-functional team, a bounded first release, documented integrations and timely decisions. It excludes unknown migration complexity, external approvals, procurement delays and formal certification. User count does not determine concurrent load. Proposed technologies are examples, not proof of JC TechLabs client deployments.
How this calculator works.
Base illustrative weeks: SaaS 8, ERP 10, AI portal 7, web app 5, mobile app 9. Add 1.5 per integration; add 1 above 1,000 monthly active users, 3 above 10,000 or 6 above 100,000; add 4 for sensitive data. Lower bound = rounded-up total; upper bound = rounded-up total × 1.6. These weights are editorial planning assumptions, not a model trained on client delivery data.
Count external systems using the CRM integration checklist, then define recovery and access tests with the resilient systems guide. Monthly active users indicate reach; measured concurrency and workload determine infrastructure needs.
| Choice | Useful when | Boundary to check |
|---|---|---|
| Public experience | Next.js/React or an appropriate mobile client | Accessibility, browser/device support and public-page delivery. |
| Application boundary | FastAPI and PostgreSQL as example choices | Authentication, authorization, validation and tenant isolation. |
| Integration work | Queue, replay handling and reconciliation | Document provider limits and assign an operator for failures. |
A worked example.
A SaaS portal with two integrations, 2,000 monthly active users and sensitive-data controls produces a 16–26-week reference range. That arithmetic does not establish a project schedule: a single undocumented integration or approval requirement can change the scope materially.
These figures demonstrate the formula. They are not client results or delivery commitments.
For a workflow that includes model assistance, the AI and software architecture guide and automation pilot guide clarify validation and human review. Compare the operating workload in the automation capacity planner and financial assumptions in the AI automation ROI calculator.
Use the result to scope the next step.
Follow the connected-delivery principles to agree repository access, acceptance, documentation and support ownership. Custom software development and AI automation services are scoped around those responsibilities, rather than a fixed technology bundle.
Continue with custom software versus SaaS comparison, integration checklist, custom software development. Browse all free planning tools or discuss your assumptions with JC TechLabs.