InterLAB tools · Templates · versions · PDF

Proposal builder

Proposal templates for IT projects: scope, phases, estimate, timeline, assumptions and exclusions. Totals and the payment schedule are computed from line items — they cannot be “adjusted” by hand; revisions are compared by money and timeline, and an accepted one is frozen as read-only.

Free, no sign-up

Loading the builder…

How the builder works

A template or an estimate
Pick a template (MVP, website, mobile app, integration, audit or blank) or load an approved estimate from the scope calculator — a scope-snapshot file. Templates never invent prices: the rates are yours.
Scope, phases, estimate, terms
Line items: work, quantity, unit, price. Phases run one after another: durations build a week-by-week timeline (calendar dates with a start date), payment shares become payment amounts.
Pre-send checks
Published rules with IDs: empty required sections, validity date, assumptions and exclusions, a payment schedule of exactly 100%, zero or negative lines, price and timeline outside the estimate range, phases without deliverables.
Status and revisions
Draft → sent → accepted or rejected. A revision is saved automatically when you send or accept; the accepted one is pinned and the document becomes read-only. Edits go into a new revision only.

Templates

MVP development — A first-version web product: design, build, launch.
Website / landing page — Structure, design, build, CMS, SEO basics.
Mobile app — iOS and Android, store publishing.
Integration and automation — Connecting systems, data exchange, monitoring.
Audit / consultation — A review of code, architecture or process with a report.
Blank — Structure only — you fill in everything.

Switching templates in a non-empty document asks for confirmation: the template replaces the scope, phases, estimate and terms, while the client, contractor, number, dates and currency stay.

Rules and calculation

The table is generated from the same code as the checks — rules v1.0 (13.10.2026). Blocking issues prevent marking the proposal as sent or accepted; warnings and hints are your call.

ID	Rule	Level	Why
PB-R01	Client and project name are filled in	blocks sending	Without them the document cannot be tied to an agreement.
PB-R02	The contractor is named	blocks sending	The client must see who the proposal is from.
PB-R03	The problem and goal are described	warning	The goal explains why the scope exists and prevents “that's not what we asked for”.
PB-R04	There is a scope of work	blocks sending	A price without a scope is a number, not a proposal.
PB-R05	There are phases	blocks sending	Phases set the timeline, deliverables and payment schedule.
PB-R06	The estimate has line items	blocks sending	The total is computed from line items only — it cannot be typed in.
PB-R07	No empty, zero or negative line items	blocks sending	A line without a description, or with a zero quantity or price, signals an unfinished estimate.
PB-R08	The total is above zero	blocks sending	A zero total after discount is an input error.
PB-R09	The payment schedule adds up to exactly 100%	blocks sending	Otherwise the payments will not match the contract total.
PB-R10	Every phase has deliverables	warning	A deliverable is what gets accepted and paid for.
PB-R11	Every phase has a duration	warning	A phase without a duration drops out of the timeline.
PB-R12	A validity date is set	warning	Rates and capacity change; an open-ended proposal can be “accepted” six months later.
PB-R13	The validity date has not passed	blocks sending	An expired proposal should be refreshed, not sent.
PB-R14	Assumptions are listed	warning	Assumptions are the conditions under which price and timeline hold.
PB-R15	Exclusions are listed	warning	An explicit “not included” removes most scope disputes.
PB-R16	Payment terms are described	warning	Percentages alone do not say when and how to pay.
PB-R17	The currency code is three Latin letters	blocks sending	KZT, USD, EUR, RUB: one unambiguous currency for every amount.
PB-R18	The currency matches the estimate's	warning	Amounts in different currencies cannot be compared without an exchange rate.
PB-R19	The price is within the estimate range	warning	Departing from the approved estimate should be deliberate and explained.
PB-R20	The phase timeline is within the estimate range	warning	Total phase weeks are checked against the estimate's timeline.
PB-R21	Warranty and support are described	hint	The client will ask what happens after launch.

PB-R01

Rule: Client and project name are filled in
Level: blocks sending
Why: Without them the document cannot be tied to an agreement.

PB-R02

Rule: The contractor is named
Level: blocks sending
Why: The client must see who the proposal is from.

PB-R03

Rule: The problem and goal are described
Level: warning
Why: The goal explains why the scope exists and prevents “that's not what we asked for”.

PB-R04

Rule: There is a scope of work
Level: blocks sending
Why: A price without a scope is a number, not a proposal.

PB-R05

Rule: There are phases
Level: blocks sending
Why: Phases set the timeline, deliverables and payment schedule.

PB-R06

Rule: The estimate has line items
Level: blocks sending
Why: The total is computed from line items only — it cannot be typed in.

PB-R07

Rule: No empty, zero or negative line items
Level: blocks sending
Why: A line without a description, or with a zero quantity or price, signals an unfinished estimate.

PB-R08

Rule: The total is above zero
Level: blocks sending
Why: A zero total after discount is an input error.

PB-R09

Rule: The payment schedule adds up to exactly 100%
Level: blocks sending
Why: Otherwise the payments will not match the contract total.

PB-R10

Rule: Every phase has deliverables
Level: warning
Why: A deliverable is what gets accepted and paid for.

PB-R11

Rule: Every phase has a duration
Level: warning
Why: A phase without a duration drops out of the timeline.

PB-R12

Rule: A validity date is set
Level: warning
Why: Rates and capacity change; an open-ended proposal can be “accepted” six months later.

PB-R13

Rule: The validity date has not passed
Level: blocks sending
Why: An expired proposal should be refreshed, not sent.

PB-R14

Rule: Assumptions are listed
Level: warning
Why: Assumptions are the conditions under which price and timeline hold.

PB-R15

Rule: Exclusions are listed
Level: warning
Why: An explicit “not included” removes most scope disputes.

PB-R16

Rule: Payment terms are described
Level: warning
Why: Percentages alone do not say when and how to pay.

PB-R17

Rule: The currency code is three Latin letters
Level: blocks sending
Why: KZT, USD, EUR, RUB: one unambiguous currency for every amount.

PB-R18

Rule: The currency matches the estimate's
Level: warning
Why: Amounts in different currencies cannot be compared without an exchange rate.

PB-R19

Rule: The price is within the estimate range
Level: warning
Why: Departing from the approved estimate should be deliberate and explained.

PB-R20

Rule: The phase timeline is within the estimate range
Level: warning
Why: Total phase weeks are checked against the estimate's timeline.

PB-R21

Rule: Warranty and support are described
Level: hint
Why: The client will ask what happens after launch.

Pre-send check rules, v1.0, 13.10.2026

Line amount = quantity × price, rounded to cents. The discount applies to the line total, tax to the amount after discount.
A phase payment = total × the phase share. When shares add up to exactly 100%, the last payment absorbs the rounding remainder — payments match the total to the cent.
Estimate check: the price before tax against the scope-snapshot cost range, total phase weeks against its timeline range. Different currencies are not compared without an exchange rate — you get a separate warning.

Limitations

The builder does not estimate effort or suggest rates — you or the scope calculator do. Checks catch inconsistencies in the document, not errors in the estimate.
The “accepted” mark is entered by you based on the client's word. It is not an electronic signature or legal proof of a contract.
The document and revisions live only in this browser. There is no multi-user editing or link sharing — share the PDF, Markdown or JSON file.
Tax rates and invoicing rules in your country are not checked.

Privacy

Everything is computed in your browser: the tool itself sends nothing to a server; client data, prices and contacts never appear in the page address.
The draft and revisions are stored only in this browser's localStorage; “Clear all” deletes them. Exports are files you download yourself.
Analytics receives only the fact of an export or a status change with categories: template, status, file format — no amounts 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. The summary holds the template, total, phases with payments, timeline, status and checks; client and contractor contacts are never included.

Related tools

All tools · 40

MVP validation toolkitHypotheses with thresholds, a landing page and lead form, UTM links, a funnel, interviews and an experiment report → continue, pivot or stop.

Change request calculatorAn approved scope + new requirements → affected modules, extra cost, time and risk, a before/after comparison and a change order that leaves the original agreement intact.

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.

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.

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

Need help estimating the project?

A technical consultation is a paid review of scope, risks and timeline before you send a proposal. The first short conversation about the format is free; the cost is set after a brief.

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