InterLAB tools · 5 steps · 3 MVP options · requirements baseline

Idea → Product: from an idea to a product plan

Five interview steps — idea and problem, product type, roles and scenarios, features, constraints. You get a Product Blueprint: feature priorities, three MVP scope options with dependencies, risks with mitigations, open questions and next steps.

Free, no sign-up

Step 1 of 6Idea

Versions (0)

Versions

No versions yet. Save one before big changes — you can return to it and compare.

Data is stored only in this browser; nothing is sent to a server.

How it works

Idea and problem
One sentence about the idea, the problem, target segments and how the problem is solved today.
Product
Product type, platforms and monetization. The type drives role and feature suggestions and the backbone features (rule P1).
Roles and scenarios
“As <role> I want …, so that …”. The primary role and its key scenario are what the minimal option validates.
Features
A catalogue of 33 features with relative complexity and dependencies, plus your own. Features are linked to scenarios (suggested by keywords); rules propose a priority you can override.
Blueprint
Three MVP options with dependency closure, a comparison, risks, consistency checks and open questions. Export: Markdown, PDF, JSON and requirements-baseline for the Requirements interviewer.

Rules

The tables below are generated from the same code as the Blueprint — rules v1.0 (2026-10-13). There is no AI inside the tool: the same answers always give the same result.

ID	Condition	Result
P0	A priority you set by hand always overrides the rules.	your choice
P1	The feature is the backbone of the chosen product type (e.g. a catalogue for a store, booking for a booking service).	Must
P2	The feature is linked to a key scenario of the primary role.	Must
P3	The feature is linked to a key scenario of another role or to any non-key scenario.	Should
P4	The feature is selected but not linked to any scenario.	Could
P5	A dependency of a Must feature becomes Must, of a Should feature — at least Should (unless set by hand).	at least the dependant's
P6	The feature is not selected but required by selected ones: it is added to the options automatically with its dependant's priority.	Must / Should / Could

Condition: A priority you set by hand always overrides the rules.
Result: your choice

Condition: The feature is the backbone of the chosen product type (e.g. a catalogue for a store, booking for a booking service).
Result: Must

Condition: The feature is linked to a key scenario of the primary role.
Result: Must

Condition: The feature is linked to a key scenario of another role or to any non-key scenario.
Result: Should

Condition: The feature is selected but not linked to any scenario.
Result: Could

Condition: A dependency of a Must feature becomes Must, of a Should feature — at least Should (unless set by hand).
Result: at least the dependant's

Condition: The feature is not selected but required by selected ones: it is added to the options automatically with its dependant's priority.
Result: Must / Should / Could

MoSCoW priority rules (applied in order)

Option	What it validates	Composition rule
Minimal — demand validation	Check that the primary role completes the key scenario and comes back	V1: Must features + their dependencies; one primary client platform (+ admin panel if selected).
Base — first paying customers	Check that people will pay in the chosen way	V2: Must + Should + monetization features (subscriptions, payments) if selected, + dependencies; up to two client platforms.
Extended — growth	Retention, new channels and scaling after proven demand	V3: every selected feature except Won't, + dependencies; all selected platforms.

Minimal — demand validation

What it validates: Check that the primary role completes the key scenario and comes back
Composition rule: V1: Must features + their dependencies; one primary client platform (+ admin panel if selected).

Base — first paying customers

What it validates: Check that people will pay in the chosen way
Composition rule: V2: Must + Should + monetization features (subscriptions, payments) if selected, + dependencies; up to two client platforms.

Extended — growth

What it validates: Retention, new channels and scaling after proven demand
Composition rule: V3: every selected feature except Won't, + dependencies; all selected platforms.

Three MVP scope options

Feature	Units	Depends on	Backbone of type (P1)
Sign-up and sign-in	3	—	Marketplace, SaaS / B2B portal, Internal tool / automation, Mobile-first consumer app
User profiles	2	Sign-up and sign-in	Mobile-first consumer app
Roles and permissions	3	Sign-up and sign-in	SaaS / B2B portal, Internal tool / automation
Companies and teams (B2B accounts)	3	Sign-up and sign-in, Roles and permissions	SaaS / B2B portal
Catalogue of products or services	3	—	Marketplace, E-commerce store
Listings by sellers	3	Sign-up and sign-in, Catalogue of products or services	Marketplace
Search and filters	3	—	Marketplace
Favourites	1	Sign-up and sign-in	—
Cart and checkout	5	Catalogue of products or services	E-commerce store
Orders and their statuses	3	E-commerce store: + Cart and checkout; Marketplace: + Cart and checkout	E-commerce store
Delivery and logistics	3	Orders and their statuses	—
Online payments	5	Sign-up and sign-in; E-commerce store: + Cart and checkout; Marketplace: + Cart and checkout	—
Subscriptions and recurring billing	5	Sign-up and sign-in, Online payments	—
Online booking and calendar	5	—	Booking and services
In-app chat	5	Sign-up and sign-in, Notifications: email, SMS, push	—
Notifications: email, SMS, push	3	—	Booking and services
Reviews and ratings	2	Sign-up and sign-in	—
Content publishing	3	—	Content and community
Comments and community	3	Sign-up and sign-in, Moderation	—
Moderation	3	Admin panel	—
Admin panel	5	Sign-up and sign-in, Roles and permissions	—
Requests and approvals	3	Roles and permissions	Internal tool / automation
Analytics dashboard	3	Sign-up and sign-in	—
Reports and export (Excel, CSV, PDF)	2	—	—
File and image uploads	2	—	—
Maps and geolocation	3	—	—
Integrations: CRM, 1C, accounting	5	—	—
Multiple interface languages	2	—	—
Offline mode and sync	8	Sign-up and sign-in	—
AI features	5	—	—
Referrals and promo codes	3	Sign-up and sign-in	—
Onboarding	1	—	—
Audit log	2	Sign-up and sign-in	—

Sign-up and sign-in

Units: 3
Depends on: —
Backbone of type (P1): Marketplace, SaaS / B2B portal, Internal tool / automation, Mobile-first consumer app

User profiles

Units: 2
Depends on: Sign-up and sign-in
Backbone of type (P1): Mobile-first consumer app

Roles and permissions

Units: 3
Depends on: Sign-up and sign-in
Backbone of type (P1): SaaS / B2B portal, Internal tool / automation

Companies and teams (B2B accounts)

Units: 3
Depends on: Sign-up and sign-in, Roles and permissions
Backbone of type (P1): SaaS / B2B portal

Catalogue of products or services

Units: 3
Depends on: —
Backbone of type (P1): Marketplace, E-commerce store

Listings by sellers

Units: 3
Depends on: Sign-up and sign-in, Catalogue of products or services
Backbone of type (P1): Marketplace

Search and filters

Units: 3
Depends on: —
Backbone of type (P1): Marketplace

Favourites

Units: 1
Depends on: Sign-up and sign-in
Backbone of type (P1): —

Cart and checkout

Units: 5
Depends on: Catalogue of products or services
Backbone of type (P1): E-commerce store

Orders and their statuses

Units: 3
Depends on: E-commerce store: + Cart and checkout; Marketplace: + Cart and checkout
Backbone of type (P1): E-commerce store

Delivery and logistics

Units: 3
Depends on: Orders and their statuses
Backbone of type (P1): —

Online payments

Units: 5
Depends on: Sign-up and sign-in; E-commerce store: + Cart and checkout; Marketplace: + Cart and checkout
Backbone of type (P1): —

Subscriptions and recurring billing

Units: 5
Depends on: Sign-up and sign-in, Online payments
Backbone of type (P1): —

Online booking and calendar

Units: 5
Depends on: —
Backbone of type (P1): Booking and services

In-app chat

Units: 5
Depends on: Sign-up and sign-in, Notifications: email, SMS, push
Backbone of type (P1): —

Notifications: email, SMS, push

Units: 3
Depends on: —
Backbone of type (P1): Booking and services

Reviews and ratings

Units: 2
Depends on: Sign-up and sign-in
Backbone of type (P1): —

Content publishing

Units: 3
Depends on: —
Backbone of type (P1): Content and community

Comments and community

Units: 3
Depends on: Sign-up and sign-in, Moderation
Backbone of type (P1): —

Moderation

Units: 3
Depends on: Admin panel
Backbone of type (P1): —

Admin panel

Units: 5
Depends on: Sign-up and sign-in, Roles and permissions
Backbone of type (P1): —

Requests and approvals

Units: 3
Depends on: Roles and permissions
Backbone of type (P1): Internal tool / automation

Analytics dashboard

Units: 3
Depends on: Sign-up and sign-in
Backbone of type (P1): —

Reports and export (Excel, CSV, PDF)

Units: 2
Depends on: —
Backbone of type (P1): —

File and image uploads

Units: 2
Depends on: —
Backbone of type (P1): —

Maps and geolocation

Units: 3
Depends on: —
Backbone of type (P1): —

Integrations: CRM, 1C, accounting

Units: 5
Depends on: —
Backbone of type (P1): —

Multiple interface languages

Units: 2
Depends on: —
Backbone of type (P1): —

Offline mode and sync

Units: 8
Depends on: Sign-up and sign-in
Backbone of type (P1): —

AI features

Units: 5
Depends on: —
Backbone of type (P1): —

Referrals and promo codes

Units: 3
Depends on: Sign-up and sign-in
Backbone of type (P1): —

Onboarding

Units: 1
Depends on: —
Backbone of type (P1): —

Audit log

Units: 2
Depends on: Sign-up and sign-in
Backbone of type (P1): —

Feature catalogue: relative complexity and dependencies

Platform	Units
Web app	4
Admin panel (web)	0
iOS	6
Android	6
Telegram bot	3
Desktop app	6

Web app

Units: 4

Admin panel (web)

Units: 0

iOS

Units: 6

Android

Units: 6

Telegram bot

Units: 3

Desktop app

Units: 6

Platform overhead (same units)

Band	Units
S — small	≤ 20
M — medium	21–40
L — large	41–70
XL — very large	> 70

S — small

Units: ≤ 20

M — medium

Units: 21–40

L — large

Units: 41–70

XL — very large

Units: > 70

Option size bands

ID	Risk	Fires when	Level	What to do
R01	Online payments	payments or subscriptions are selected, or payments are marked “Yes” (for an option — only its own features)	high	Use the provider’s hosted payment page (card data never touches you), choose the provider early and check online cash-register requirements. In the minimal option, invoice or link payment is acceptable.
R02	Personal data	personal data is marked “Yes” or “Not sure”, or sign-up or profiles are selected	high	Items to check with a lawyer (this is not legal advice): consent, where data is stored, retention and deletion periods, who has access, the privacy policy. Collect only the data you need.
R03	Two-sided cold start	the product type is a marketplace	high	Start with one narrow category and one city, recruit the first side by hand (sign up sellers personally) and measure the share of searches that end in a deal.
R04	External integrations	integrations are selected	medium	Get the API documentation and test access before estimating; plan a manual fallback (file export) in case of delays.
R05	Offline mode and sync	offline mode is selected	medium	Start with offline reading of already loaded data; offline writes as a separate phase with written conflict rules.
R06	AI features: cost and quality	AI features are selected	medium	A test set of examples before building, a spending limit per user, human review where mistakes are costly, and a fallback path without AI.
R07	Tight deadline and many Musts	the deadline is tight and Must features exceed 30 units	high	Take the “Minimal” option and revisit the other Musts: what can be done by hand for the first clients?
R08	Several client platforms at once	more than one client platform is selected	medium	Validate demand on one platform; for mobile consider cross-platform development or a PWA (see the stack helper).
R09	Regulated domain	a regulated domain is marked “Yes”	high	Before building, ask a specialist lawyer which requirements apply and record them as constraints.
R10	Chat and user content	chat, community or reviews are selected	medium	Platform rules and a “Report” button from day one; in the minimal option use a messenger link instead of an in-app chat.
R11	Double booking and time zones	online booking is selected	medium	Hold the slot during checkout, explicit cancellation and rescheduling rules, every time stored with its time zone.
R12	Scope larger than the team	a team of 1–2 people and an extended scope above 70 units	medium	Ship the “Minimal” option and grow only after you have demand data.

R01

Risk: Online payments
Fires when: payments or subscriptions are selected, or payments are marked “Yes” (for an option — only its own features)
Level: high
What to do: Use the provider’s hosted payment page (card data never touches you), choose the provider early and check online cash-register requirements. In the minimal option, invoice or link payment is acceptable.

R02

Risk: Personal data
Fires when: personal data is marked “Yes” or “Not sure”, or sign-up or profiles are selected
Level: high
What to do: Items to check with a lawyer (this is not legal advice): consent, where data is stored, retention and deletion periods, who has access, the privacy policy. Collect only the data you need.

R03

Risk: Two-sided cold start
Fires when: the product type is a marketplace
Level: high
What to do: Start with one narrow category and one city, recruit the first side by hand (sign up sellers personally) and measure the share of searches that end in a deal.

R04

Risk: External integrations
Fires when: integrations are selected
Level: medium
What to do: Get the API documentation and test access before estimating; plan a manual fallback (file export) in case of delays.

R05

Risk: Offline mode and sync
Fires when: offline mode is selected
Level: medium
What to do: Start with offline reading of already loaded data; offline writes as a separate phase with written conflict rules.

R06

Risk: AI features: cost and quality
Fires when: AI features are selected
Level: medium
What to do: A test set of examples before building, a spending limit per user, human review where mistakes are costly, and a fallback path without AI.

R07

Risk: Tight deadline and many Musts
Fires when: the deadline is tight and Must features exceed 30 units
Level: high
What to do: Take the “Minimal” option and revisit the other Musts: what can be done by hand for the first clients?

R08

Risk: Several client platforms at once
Fires when: more than one client platform is selected
Level: medium
What to do: Validate demand on one platform; for mobile consider cross-platform development or a PWA (see the stack helper).

R09

Risk: Regulated domain
Fires when: a regulated domain is marked “Yes”
Level: high
What to do: Before building, ask a specialist lawyer which requirements apply and record them as constraints.

R10

Risk: Chat and user content
Fires when: chat, community or reviews are selected
Level: medium
What to do: Platform rules and a “Report” button from day one; in the minimal option use a messenger link instead of an in-app chat.

R11

Risk: Double booking and time zones
Fires when: online booking is selected
Level: medium
What to do: Hold the slot during checkout, explicit cancellation and rescheduling rules, every time stored with its time zone.

R12

Risk: Scope larger than the team
Fires when: a team of 1–2 people and an extended scope above 70 units
Level: medium
What to do: Ship the “Minimal” option and grow only after you have demand data.

Risk catalogue

ID	What is checked
C01	A scenario mentions a role missing from the role list, or belongs to a deleted role
C02	A feature is selected without its dependencies (the options add them automatically)
C03	Too many Musts: over 60% of selected features (with 5 or more features)
C04	A role has no scenarios
C05	A key scenario of the primary role is not linked to any feature
C06	The “Admin panel” platform is selected without the “Admin panel” feature (or vice versa)
C07	A mobile-first product without a mobile platform
C08	Monetization is not backed by a feature (subscription without subscriptions, commission or sales without payments)
C09	A dependency is set by hand below the feature that relies on it

C01

What is checked: A scenario mentions a role missing from the role list, or belongs to a deleted role

C02

What is checked: A feature is selected without its dependencies (the options add them automatically)

C03

What is checked: Too many Musts: over 60% of selected features (with 5 or more features)

C04

What is checked: A role has no scenarios

C05

What is checked: A key scenario of the primary role is not linked to any feature

C06

What is checked: The “Admin panel” platform is selected without the “Admin panel” feature (or vice versa)

C07

What is checked: A mobile-first product without a mobile platform

C08

What is checked: Monetization is not backed by a feature (subscription without subscriptions, commission or sales without payments)

C09

What is checked: A dependency is set by hand below the feature that relies on it

Consistency checks

ID	When it appears
Q01	How target users solve the problem today is not described
Q02	Monetization is missing or “not decided yet”
Q03	No success metrics
Q04	Deadline, team or budget is “not sure yet”
Q05	Personal data, payments or regulated domain is “not sure”
Q06	The primary role has no key scenario
Q07	Integrations are selected — which systems, and do they have an API
Q08	Payments are selected — which provider and who owns the contract
Q09	A scenario lacks “so that…” — the value is unclear
Q10	AI features are selected — on what data and how to check quality

Q01

When it appears: How target users solve the problem today is not described

Q02

When it appears: Monetization is missing or “not decided yet”

Q03

When it appears: No success metrics

Q04

When it appears: Deadline, team or budget is “not sure yet”

Q05

When it appears: Personal data, payments or regulated domain is “not sure”

Q06

When it appears: The primary role has no key scenario

Q07

When it appears: Integrations are selected — which systems, and do they have an API

Q08

When it appears: Payments are selected — which provider and who owns the contract

Q09

When it appears: A scenario lacks “so that…” — the value is unclear

Q10

When it appears: AI features are selected — on what data and how to check quality

Open questions: interview gaps

Limitations

Complexity units are an InterLAB expert scale for comparing options with each other. They are not an hour estimate or a price: a quote at your rates needs a separate calculation.
The catalogue covers typical features; describe rare or specific ones as custom features — you set their complexity.
Personal data, payments and regulation risks are items to check with a lawyer, not legal advice.
Keyword-based links between features and scenarios are a hint: review them and untick the wrong ones.
The Blueprint does not validate demand — it shows what to validate and at what scope.

Privacy

Everything runs in your browser: the tool itself does not send your answers 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.
Analytics receives only the fact of building or exporting, the product type, the size band and the file format — never the answers.
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

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

Scope and cost calculatorModules, effort, your rates, complexity factors, dependencies and a risk reserve → a cost and timeline range with every number explained, plus estimate comparison.

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

Want to turn the Blueprint into a development plan?

Let’s go through scope, risks and the first release together. The first conversation about the format is free; development 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

Idea → Product: from an idea to a product plan

Idea and problem

Versions

How it works

Rules

Limitations

Privacy

Related tools

Want to turn the Blueprint into a development plan?