InterLAB tools · Your rates · ranges, not guarantees

Scope and cost calculator

Tick your product modules, enter rates and the team — the calculator shows a range of hours, cost and calendar time, explains every number with its formula and compares estimate options. The approved scope exports as a file for proposals and change requests.

Free, no sign-up

How the calculator works

Modules
A catalogue of 36 typical modules in six sections: foundation, accounts, features, integrations, platforms, quality and launch. Each has an hour range at standard complexity, role shares and dependencies. Everything is editable, and you can add your own modules.
Team and rates
You enter the role rates: there are no default money values, and until rates are entered the estimate shows hours only. Capacity is people × focused hours a week (30 by default).
Factors and reserve
Module complexity and five global factors multiply the low and high bounds separately. The risk reserve is suggested by a published rule and can be set manually.
Estimate
Totals as ranges (hours, money, weeks), breakdowns by module and role, the team bottleneck, checks and “Where each number comes from” — a formula with the actual values for every number.
Comparison and approval
Save options (“MVP”, “Full version”) as versions and compare up to three side by side. “Approve the scope” records who agreed the estimate and when, and exports a scope-snapshot file.

Formulas

Module hours = hours (low/high) × complexity coefficient × quantity × factor multiplier (for “Integrations”, also × the integration uncertainty multiplier).
Hours are split across roles by the module's shares; shares that do not add up to 100% are normalised (check CHK-SPLIT).
Project management = PM % × hours of all modules (10% by default); module shares contain no PM, so nothing is counted twice.
Testing = QA % × hours of modules outside “Quality and launch” (15% by default). If the “Manual QA cycle” module is selected, the percentage is not applied — testing is already counted by the module.
Risk reserve = 10% + factor contributions (table below; the integration contribution counts only when the scope has integrations), kept within 10–35%. It applies to modules plus overheads and is spread across roles proportionally.
Role cost = role hours with reserve × role rate. If any role with hours has no rate, the total cost is not calculated — a partial sum would mislead.
Role duration = role hours with reserve ÷ (people × hours a week). The calendar duration is the maximum across roles: roles work in parallel, and the bottleneck is named.

The tables below are generated from the same code as the calculation — rules v1.0 (2026-10-13).

Level	Coefficient	When to choose
Simple	×0.7	Standard solution, few states and edge cases
Standard	×1	As described in the catalogue
Complex	×1.5	Many rules, roles, edge cases or a custom UI

Simple

Coefficient: ×0.7
When to choose: Standard solution, few states and edge cases

Standard

Coefficient: ×1
When to choose: As described in the catalogue

Complex

Coefficient: ×1.5
When to choose: Many rules, roles, edge cases or a custom UI

Module complexity

Rule	Factor	Value	Multiplier	Reserve
F-CLARITY	Requirements clarity	Written and agreed	×1 – ×1	0
F-CLARITY	Requirements clarity	Partly written	×1 – ×1.15	+5%
F-CLARITY	Requirements clarity	Only an idea	×1.05 – ×1.35	+15%
F-TEAM	Team familiarity with the stack	Well known	×1 – ×1	0
F-TEAM	Team familiarity with the stack	Partly	×1.05 – ×1.1	0
F-TEAM	Team familiarity with the stack	New stack or domain	×1.15 – ×1.3	+5%
F-INTEG	Integration uncertainty (integrations only)	Docs and sandbox available	×1 – ×1	0
F-INTEG	Integration uncertainty (integrations only)	Docs incomplete	×1.05 – ×1.2	+5%
F-INTEG	Integration uncertainty (integrations only)	No docs, no access	×1.15 – ×1.4	+10%
F-NFR	Non-functional strictness	Standard	×1 – ×1	0
F-NFR	Non-functional strictness	Elevated	×1.1 – ×1.15	0
F-NFR	Non-functional strictness	Strict (finance, health, public sector)	×1.2 – ×1.3	+5%
F-PLATF	Number of platforms	One	×1 – ×1	0
F-PLATF	Number of platforms	Two	×1.05 – ×1.1	0
F-PLATF	Number of platforms	Three or more	×1.1 – ×1.2	0

F-CLARITY

Factor: Requirements clarity
Value: Written and agreed
Multiplier: ×1 – ×1
Reserve: 0

F-CLARITY

Factor: Requirements clarity
Value: Partly written
Multiplier: ×1 – ×1.15
Reserve: +5%

F-CLARITY

Factor: Requirements clarity
Value: Only an idea
Multiplier: ×1.05 – ×1.35
Reserve: +15%

F-TEAM

Factor: Team familiarity with the stack
Value: Well known
Multiplier: ×1 – ×1
Reserve: 0

F-TEAM

Factor: Team familiarity with the stack
Value: Partly
Multiplier: ×1.05 – ×1.1
Reserve: 0

F-TEAM

Factor: Team familiarity with the stack
Value: New stack or domain
Multiplier: ×1.15 – ×1.3
Reserve: +5%

F-INTEG

Factor: Integration uncertainty (integrations only)
Value: Docs and sandbox available
Multiplier: ×1 – ×1
Reserve: 0

F-INTEG

Factor: Integration uncertainty (integrations only)
Value: Docs incomplete
Multiplier: ×1.05 – ×1.2
Reserve: +5%

F-INTEG

Factor: Integration uncertainty (integrations only)
Value: No docs, no access
Multiplier: ×1.15 – ×1.4
Reserve: +10%

F-NFR

Factor: Non-functional strictness
Value: Standard
Multiplier: ×1 – ×1
Reserve: 0

F-NFR

Factor: Non-functional strictness
Value: Elevated
Multiplier: ×1.1 – ×1.15
Reserve: 0

F-NFR

Factor: Non-functional strictness
Value: Strict (finance, health, public sector)
Multiplier: ×1.2 – ×1.3
Reserve: +5%

F-PLATF

Factor: Number of platforms
Value: One
Multiplier: ×1 – ×1
Reserve: 0

F-PLATF

Factor: Number of platforms
Value: Two
Multiplier: ×1.05 – ×1.1
Reserve: 0

F-PLATF

Factor: Number of platforms
Value: Three or more
Multiplier: ×1.1 – ×1.2
Reserve: 0

Global factors: low and high multipliers, reserve contribution

Rule	When it fires
CHK-RATES	A role has hours but no rate — cost is not calculated at all rather than partially
CHK-DEP	A module depends on a module that is not in the scope; an “Add” button is offered
CHK-RANGE	Total: the high bound is 3× the low bound or more — high uncertainty
CHK-RANGE-MOD	Module: high is 3× low or more
CHK-ZERO	A module has zero effort
CHK-SPLIT	A module's role shares do not add up to 100% — they are normalised
CHK-CAP	A role has hours but no capacity — the duration is not calculated
CHK-QA	QA is 0% and no module includes QA work
CHK-PLATF	The platform count from modules differs from the “Number of platforms” factor
CHK-RESERVE	The reserve is set manually below the suggested value

CHK-RATES

When it fires: A role has hours but no rate — cost is not calculated at all rather than partially

CHK-DEP

When it fires: A module depends on a module that is not in the scope; an “Add” button is offered

CHK-RANGE

When it fires: Total: the high bound is 3× the low bound or more — high uncertainty

CHK-RANGE-MOD

When it fires: Module: high is 3× low or more

CHK-ZERO

When it fires: A module has zero effort

CHK-SPLIT

When it fires: A module's role shares do not add up to 100% — they are normalised

CHK-CAP

When it fires: A role has hours but no capacity — the duration is not calculated

CHK-QA

When it fires: QA is 0% and no module includes QA work

CHK-PLATF

When it fires: The platform count from modules differs from the “Number of platforms” factor

CHK-RESERVE

When it fires: The reserve is set manually below the suggested value

Estimate checks

Module catalogue: InterLAB starting assumptions

Hours are a range at standard complexity for a small team familiar with the stack; rules v1.0 (2026-10-13). They are a starting point for discussion, not a norm: adjust hours and shares to your team.

Module	What is included	Hours	Roles	Depends on
Discovery and analysis	Interviews, user flows, requirements, priorities, acceptance criteria	24–48	Business analyst 70%, Designer 20%, Backend 10%	—
UX/UI design	Key-screen prototype, mock-ups, UI kit, states	60–140	Designer 100%	—
Project setup and CI/CD	Repositories, structure, linters, build and auto-deploy	12–24	Frontend 15%, Backend 25%, DevOps 60%	—
Environments and DevOps	Staging and production, domains, secrets, backups, monitoring	16–40	DevOps 100%	Project setup and CI/CD

Discovery and analysis

What is included: Interviews, user flows, requirements, priorities, acceptance criteria
Hours: 24–48
Roles: Business analyst 70%, Designer 20%, Backend 10%
Depends on: —

UX/UI design

What is included: Key-screen prototype, mock-ups, UI kit, states
Hours: 60–140
Roles: Designer 100%
Depends on: —

Project setup and CI/CD

What is included: Repositories, structure, linters, build and auto-deploy
Hours: 12–24
Roles: Frontend 15%, Backend 25%, DevOps 60%
Depends on: —

Environments and DevOps

What is included: Staging and production, domains, secrets, backups, monitoring
Hours: 16–40
Roles: DevOps 100%
Depends on: Project setup and CI/CD

Foundation

Module	What is included	Hours	Roles	Depends on
Email/phone sign-up and sign-in	Sign-up, sign-in, password recovery, code verification	24–48	Frontend 40%, Backend 60%	—
OAuth / SSO sign-in	Google, Apple or corporate SSO, account linking	16–40	Frontend 35%, Backend 65%	Email/phone sign-up and sign-in
Roles and permissions	Roles, permission checks on the server and in the UI	24–56	Frontend 30%, Backend 70%	Email/phone sign-up and sign-in
Profiles and account area	Profile, settings, user activity history	16–32	Frontend 60%, Backend 40%	Email/phone sign-up and sign-in

Email/phone sign-up and sign-in

What is included: Sign-up, sign-in, password recovery, code verification
Hours: 24–48
Roles: Frontend 40%, Backend 60%
Depends on: —

OAuth / SSO sign-in

What is included: Google, Apple or corporate SSO, account linking
Hours: 16–40
Roles: Frontend 35%, Backend 65%
Depends on: Email/phone sign-up and sign-in

Roles and permissions

What is included: Roles, permission checks on the server and in the UI
Hours: 24–56
Roles: Frontend 30%, Backend 70%
Depends on: Email/phone sign-up and sign-in

Profiles and account area

What is included: Profile, settings, user activity history
Hours: 16–32
Roles: Frontend 60%, Backend 40%
Depends on: Email/phone sign-up and sign-in

Accounts and access

Module	What is included	Hours	Roles	Depends on
Catalogue or content	List, detail page, categories, record management	40–80	Frontend 50%, Backend 50%	—
Search and filters	Full-text search, filters, sorting, pagination	24–60	Frontend 40%, Backend 60%	Catalogue or content
Forms and workflows	Multi-step forms, request statuses, approvals	24–56	Frontend 50%, Backend 50%	—
Booking and calendar	Slots, schedules, rescheduling and cancellation, reminders	48–100	Frontend 40%, Backend 60%	Notifications: email, SMS, push
Cart and checkout	Cart, delivery, checkout, order statuses	48–96	Frontend 50%, Backend 50%	Catalogue or content
Payment integration	Payment provider, webhooks, refunds, reconciliation	24–60	Frontend 25%, Backend 75%	—
Subscriptions and billing	Plans, recurring charges, invoices, plan changes	40–96	Frontend 25%, Backend 75%	Payment integration, Email/phone sign-up and sign-in
Chat and messaging	Conversations, attachments, unread state, real time	60–140	Frontend 45%, Backend 55%	Email/phone sign-up and sign-in
Notifications: email, SMS, push	Templates, providers, queues, subscription settings	24–56	Frontend 20%, Backend 80%	—
File uploads and media	Upload, storage, previews, limits and checks	16–40	Frontend 40%, Backend 60%	—
Maps and geolocation	Map, addresses, distances, geo search	24–56	Frontend 60%, Backend 40%	—
Reports and export	Filtered reports, CSV/Excel/PDF export	32–72	Frontend 40%, Backend 60%	—
Analytics dashboard	Metrics, charts, periods, comparison	40–80	Frontend 55%, Backend 45%	—
Admin panel / CMS	Managing users, content and reference data	48–120	Frontend 50%, Backend 50%	Email/phone sign-up and sign-in, Roles and permissions

Catalogue or content

What is included: List, detail page, categories, record management
Hours: 40–80
Roles: Frontend 50%, Backend 50%
Depends on: —

Search and filters

What is included: Full-text search, filters, sorting, pagination
Hours: 24–60
Roles: Frontend 40%, Backend 60%
Depends on: Catalogue or content

Forms and workflows

What is included: Multi-step forms, request statuses, approvals
Hours: 24–56
Roles: Frontend 50%, Backend 50%
Depends on: —

Booking and calendar

What is included: Slots, schedules, rescheduling and cancellation, reminders
Hours: 48–100
Roles: Frontend 40%, Backend 60%
Depends on: Notifications: email, SMS, push

Cart and checkout

What is included: Cart, delivery, checkout, order statuses
Hours: 48–96
Roles: Frontend 50%, Backend 50%
Depends on: Catalogue or content

Payment integration

What is included: Payment provider, webhooks, refunds, reconciliation
Hours: 24–60
Roles: Frontend 25%, Backend 75%
Depends on: —

Subscriptions and billing

What is included: Plans, recurring charges, invoices, plan changes
Hours: 40–96
Roles: Frontend 25%, Backend 75%
Depends on: Payment integration, Email/phone sign-up and sign-in

Chat and messaging

What is included: Conversations, attachments, unread state, real time
Hours: 60–140
Roles: Frontend 45%, Backend 55%
Depends on: Email/phone sign-up and sign-in

Notifications: email, SMS, push

What is included: Templates, providers, queues, subscription settings
Hours: 24–56
Roles: Frontend 20%, Backend 80%
Depends on: —

File uploads and media

What is included: Upload, storage, previews, limits and checks
Hours: 16–40
Roles: Frontend 40%, Backend 60%
Depends on: —

Maps and geolocation

What is included: Map, addresses, distances, geo search
Hours: 24–56
Roles: Frontend 60%, Backend 40%
Depends on: —

Reports and export

What is included: Filtered reports, CSV/Excel/PDF export
Hours: 32–72
Roles: Frontend 40%, Backend 60%
Depends on: —

Analytics dashboard

What is included: Metrics, charts, periods, comparison
Hours: 40–80
Roles: Frontend 55%, Backend 45%
Depends on: —

Admin panel / CMS

What is included: Managing users, content and reference data
Hours: 48–120
Roles: Frontend 50%, Backend 50%
Depends on: Email/phone sign-up and sign-in, Roles and permissions

Product features

Module	What is included	Hours	Roles	Depends on
CRM integration	Leads and deals hand-off, status sync	32–80	Backend 100%	—
1C / accounting integration	Exchange of items, stock, orders and documents	40–120	Backend 100%	—
External REST API	One third-party API: auth, errors, retries	16–48	Backend 100%	—
Webhooks	Receiving and sending webhooks, signatures, delivery log	12–32	Backend 100%	—

CRM integration

What is included: Leads and deals hand-off, status sync
Hours: 32–80
Roles: Backend 100%
Depends on: —

1C / accounting integration

What is included: Exchange of items, stock, orders and documents
Hours: 40–120
Roles: Backend 100%
Depends on: —

External REST API

What is included: One third-party API: auth, errors, retries
Hours: 16–48
Roles: Backend 100%
Depends on: —

Webhooks

What is included: Receiving and sending webhooks, signatures, delivery log
Hours: 12–32
Roles: Backend 100%
Depends on: —

Integrations

Module	What is included	Hours	Roles	Depends on
Responsive web	Layouts for phone, tablet and desktop, browser checks	24–60	Frontend 100%	UX/UI design
iOS + Android app (cross-platform)	App shell, navigation, builds, store publishing	80–180	Mobile 100%	UX/UI design
Native per-platform work	Platform-specific code for one platform (quantity = number of platforms)	40–120	Mobile 100%	iOS + Android app (cross-platform)
Telegram bot	Commands, flows, buttons, notifications via the bot	32–80	Backend 100%	—

Responsive web

What is included: Layouts for phone, tablet and desktop, browser checks
Hours: 24–60
Roles: Frontend 100%
Depends on: UX/UI design

iOS + Android app (cross-platform)

What is included: App shell, navigation, builds, store publishing
Hours: 80–180
Roles: Mobile 100%
Depends on: UX/UI design

Native per-platform work

What is included: Platform-specific code for one platform (quantity = number of platforms)
Hours: 40–120
Roles: Mobile 100%
Depends on: iOS + Android app (cross-platform)

Telegram bot

What is included: Commands, flows, buttons, notifications via the bot
Hours: 32–80
Roles: Backend 100%
Depends on: —

Platforms

Module	What is included	Hours	Roles	Depends on
Automated tests	Unit and integration tests of key logic, tests in CI	40–100	Frontend 30%, Backend 40%, QA engineer 30%	Project setup and CI/CD
Manual QA cycle	Test plan, runs, regression, bug reports. Replaces the QA percentage	40–100	QA engineer 100%	—
Load testing	Load scenarios, run, report, recommendations	16–40	QA engineer 50%, DevOps 50%	Environments and DevOps
Security review	Permissions, input handling, secrets, dependencies, headers	16–40	Backend 60%, DevOps 40%	—
Launch and handover	Production cut-over, checks, hand-over of access and code	16–32	Frontend 25%, Backend 25%, DevOps 50%	Environments and DevOps
Documentation	Admin guide, README, API description	12–32	Business analyst 50%, Backend 50%	—

Automated tests

What is included: Unit and integration tests of key logic, tests in CI
Hours: 40–100
Roles: Frontend 30%, Backend 40%, QA engineer 30%
Depends on: Project setup and CI/CD

Manual QA cycle

What is included: Test plan, runs, regression, bug reports. Replaces the QA percentage
Hours: 40–100
Roles: QA engineer 100%
Depends on: —

Load testing

What is included: Load scenarios, run, report, recommendations
Hours: 16–40
Roles: QA engineer 50%, DevOps 50%
Depends on: Environments and DevOps

Security review

What is included: Permissions, input handling, secrets, dependencies, headers
Hours: 16–40
Roles: Backend 60%, DevOps 40%
Depends on: —

Launch and handover

What is included: Production cut-over, checks, hand-over of access and code
Hours: 16–32
Roles: Frontend 25%, Backend 25%, DevOps 50%
Depends on: Environments and DevOps

Documentation

What is included: Admin guide, README, API description
Hours: 12–32
Roles: Business analyst 50%, Backend 50%
Depends on: —

Quality and launch

Limitations

The calculator does not know your product: the estimate is only as good as the module choice and the hour adjustments.
Roles working in parallel is a simplification: real hand-offs (design before layout, API before client) lengthen the timeline. Account for that in the reserve or capacity.
Rates, taxes, exchange rates and third-party costs are not checked.
Approval is a note, as stated by the user, of who agreed the estimate and when — not an electronic signature and not a contract.
For a quick complexity category without hours or money, use the MVP complexity estimator.

Privacy

The estimate is calculated in your browser: the calculator itself does not send modules, rates or text to a server, and they never appear in the page address.
The draft and versions are stored only in this browser (localStorage); “Clear all” deletes them. Move to another computer via JSON export.
Analytics receives only the fact of a calculation or export and categories (rates present, scope size, file format) — no numbers or text.
The result reaches us only if you send a request yourself and keep the “Attach the result” box ticked — the form shows exactly what will be sent.

Related tools

All tools · 40

Idea → Product blueprintAn interview about your idea → roles, features, three MVP scope options, priorities and risks. You get a Product Blueprint to start development from.

MVP complexity estimateProduct type, platforms, modules and integrations → a complexity band, workstreams and the questions you need answered before any honest price.

Technical brief generatorBuild a brief step by step: goal, roles, scenarios, integrations, data, acceptance criteria. You get Markdown to copy or download.

Requirements interviewerAn adaptive client interview → roles and permissions, functional and non-functional requirements, conflicts, acceptance criteria and an approved baseline with sources.

Tech Stack AdvisorCompare technologies within one layer by product fit, team experience, maintenance cost, performance and security — with hard constraints, the conditions that change the answer, and an ADR export.

Architecture CanvasA visual graph of services, APIs, databases, auth and integrations with structural checks, versions and Mermaid/JSON export.

Tell us about your task — we'll review your request and get back to you

Need an estimate for your project?

MVP development at InterLAB starts with a requirements review and an estimate with explicit assumptions. The first conversation is free; the cost is set after a brief and an agreed scope.

The first short conversation is free — we choose the format
NDA — yours or ours
Pricing after a brief and an agreed scope

Message on WhatsApp

Scope and cost calculator

Foundation

Accounts and access

Product features

Integrations

Platforms

Quality and launch

Your modules

How the calculator works

Formulas

Module catalogue: InterLAB starting assumptions

Limitations

Privacy

Related tools

Need an estimate for your project?