How to Use Templates

Templates are useful when they make thinking visible. They are harmful when they become paperwork theatre: clean-looking documents with no decision behind them.

Use templates to create shared clarity, preserve context, and make follow-through easier.

The template rule

Every template should answer at least one of these:

What are we deciding?
What evidence do we have?
What is still unknown?
Who owns the next step?
When will we review it?

If a template does not improve a decision, shorten it or skip it.

How to use a template well

Step	What to do
Copy	Copy only the relevant section, not the whole page.
Adapt	Change fields to match your business model, stage, and team.
Fill fast	Use plain language. Do not wait for perfect formatting.
Mark uncertainty	Write assumptions clearly instead of hiding weak evidence.
Review	Share with the person closest to the work.
Decide	Turn the document into a next action.
Archive	Save the final version where the team can find it later.

Which template to use

Need	Template page
Capture and compare ideas	Idea Templates
Run customer discovery	Customer Discovery Templates
Scope product work	Product Templates
Launch and sell	GTM Templates
Prepare fundraising	Fundraising Templates
Hire and onboard	Hiring Templates
Run operating cadence	Operations Templates
Track runway and money	Finance Templates

Template hygiene

Habit	Why it matters
Put dates on decisions	Prevents old thinking from looking current.
Name owners	Reduces founder bottlenecks.
Keep evidence and opinion separate	Makes weak assumptions visible.
Review periodically	A startup changes quickly; stale docs mislead.
Delete unused fields	Shorter templates get used more often.

Template lifecycle

Treat every template as a living artifact with a short lifecycle.

Stage	What to do
Draft	Fill quickly with current thinking and obvious gaps.
Evidence pass	Replace guesses with customer quotes, usage, revenue, pipeline, cash, or team facts.
Decision pass	Write the decision the template supports.
Owner pass	Add owner, deadline, and next review date.
Archive or refresh	Keep the final version, or update it when the business changes.

If a template keeps growing but no decision improves, cut it down. The template serves the company; the company does not serve the template.

Template anti-patterns

Templates fail when they create the feeling of progress without changing founder behavior.

Anti-pattern	What it looks like	Better move
The museum document	A beautiful Notion/Google Doc nobody opens again.	Add owner, review date, and decision at the top.
The copy-paste business	Borrowed words from another startup that do not match your customer.	Rewrite using your buyer’s actual language.
The everything template	Too many fields, most of them blank.	Keep only fields that affect a decision this week.
The no-evidence memo	Strong claims with no quotes, metrics, artifacts, or examples.	Label claims as facts, quotes, assumptions, or risks.
The founder-only file	The founder fills it, but the team does not use it.	Review it with the person closest to the customer, product, money, or candidate.
The stale plan	Old pricing, old ICP, old runway, old roadmap.	Add “last reviewed” and “next review” dates.

If a document is not helping you sell, build, hire, raise, collect, decide, or reduce risk, it is probably admin theatre.

Minimum viable templates by stage

Do not start with a full operating system. Start with the few templates that match your current stage.

Stage	Minimum templates	Why these first
Idea	Idea capture, problem hypothesis, founder-market fit worksheet	Forces customer, problem, and founder advantage into plain language.
Discovery	Prospect list, interview notes, pattern review, continue/change/stop decision	Turns conversations into evidence instead of scattered memory.
MVP	MVP scope, assumption test plan, product analytics plan	Keeps the first build tied to the riskiest assumption.
First customers	Sales call notes, pilot proposal, pricing test, collections tracker	Connects interest, value delivery, payment, and follow-up.
Fundraising	Investor memo, CRM, data room checklist, use of funds	Makes the round logic and diligence readiness visible.
Hiring	Role scorecard, work test, reference check, 30/60/90 plan	Prevents desperate hiring and unclear onboarding.
Operating	Weekly review, decision log, runway tracker, monthly update	Keeps cash, customers, decisions, and priorities from living only in the founder’s head.

The correct template stack should feel slightly boring and very useful. If it feels impressive but nobody uses it, simplify.

When to update a template

Update a template when reality changes, not when you feel guilty.

Trigger	Template to update
Customer language changes	Positioning, homepage copy, sales call notes
ICP narrows or changes	Idea scorecard, GTM, sales notes, roadmap
Pricing changes	Pricing test, pilot proposal, finance forecast
Runway changes materially	Runway calculator, 13-week cash forecast, hiring plan
A new role opens	Job description, scorecard, work test, onboarding plan
Fundraising starts	Deck outline, investor memo, data room, investor CRM
A serious mistake happens	Incident report, SOP, checklist, decision log

This is how templates stay alive. They should change when the company learns.

Evidence labels

Use simple labels inside templates so the team can see how strong each claim is.

Label	Meaning
Fact	Observed in real customer, product, revenue, cash, legal, or team data.
Quote	Exact words from a customer, buyer, user, investor, candidate, or partner.
Assumption	Believed but not yet tested.
Risk	Could seriously harm the company if wrong.
Decision	A choice already made.
Next check	The test or review that will improve confidence.

This keeps founders honest. A weak assumption is acceptable. A weak assumption disguised as fact is dangerous.

The two-page rule

Most early-stage templates should fit into two pages or less. If a template is longer, split it into:

Page	Purpose
Page 1	Decision summary: what we believe, evidence, risk, owner, next action.
Page 2	Supporting details: notes, examples, calculations, links.

Long documents are fine for diligence, legal review, technical design, or board material. For day-to-day founder work, short documents win because people actually read and update them.

Team usage rule

Every recurring template should have a meeting or habit attached to it.

Template	Habit
Customer discovery notes	Review after every 5 to 10 useful conversations.
Decision log	Update after pricing, ICP, hiring, fundraising, or product direction decisions.
Runway tracker	Review weekly when cash is tight, monthly when stable.
Hiring scorecard	Review before interviews start, not after candidates appear.
Investor CRM	Update after every investor touch.
Weekly review	Run on the same day each week.

Without a habit, the template will decay.

The template owner rule

Every serious template needs one owner. Without an owner, the template becomes a shared dumping ground: everyone expects it to be useful, nobody keeps it true.

Use this ownership model:

Template type	Owner	Review rhythm
Idea and market templates	Founder closest to customers	After every 5 to 10 meaningful conversations
Product scope templates	Product/engineering founder or product owner	Before each build cycle
Sales and GTM templates	Founder-led sales owner	Weekly while pipeline is active
Finance templates	Founder/finance owner	Weekly when runway is under 12 months; monthly otherwise
Hiring templates	Hiring manager or founder	Before sourcing, before offer, after 30 days
Fundraising templates	CEO/fundraising owner	Before outreach, weekly during a raise
Operations templates	Founder/ops owner	Weekly or monthly depending on risk

The owner is not a secretary. The owner is responsible for making sure the template changes decisions.

Template review questions

Use these questions before keeping, expanding, or deleting a template.

Question	Good sign	Warning sign
What decision does this template support?	The decision is obvious.	The template exists because “we should track this.”
Who updates it?	One owner is named.	Everyone assumes someone else will update it.
When was it last used?	It affected a decision recently.	It is updated but ignored.
What changed because of it?	Scope, segment, price, hiring, cash, or priority changed.	It only created a prettier record.
What can be removed?	The template is getting shorter as the company learns.	The template keeps accumulating fields.

If a template cannot answer these questions, simplify it or delete it.

Founder template stack

A founder does not need fifty templates. A founder needs a small stack that covers the operating truth of the company.

Company question	Template to maintain
Who is the customer and what pain is real?	Customer discovery pattern review
What are we building and why?	MVP or roadmap decision note
What creates revenue?	Sales pipeline and call notes
Is cash safe?	Runway and collections tracker
What did we decide?	Decision log
Who owns what?	Weekly review and priority board
What are we telling outsiders?	Investor/customer/company update

This stack is enough for most early teams. Add more only when a real recurring decision demands it.

India template notes

For Indian founders, templates should not ignore the details that often decide outcomes: GST paperwork, payment terms, collections owner, founder relationship, WhatsApp follow-up, implementation effort, and advisor dependencies.

Add fields only when they change behavior. For example:

Field	Use it when
Payment terms	B2B customers pay by invoice, PO, milestone, or delayed approval.
Collection owner	Cash collection requires follow-up beyond issuing an invoice.
Trust source	Warm intro, reference, community, advisor, or founder access affects conversion.
Implementation effort	Delivery requires setup, training, migration, or custom support.
Compliance/advisor question	CA, CS, legal, data, sector, employment, or tax guidance is needed.

The best India-aware template makes hidden operating friction visible early.

Source-of-truth rules

Every important template should have a clear source of truth. Otherwise founders end up with five versions of the same plan.

Artifact	Source-of-truth rule
Customer discovery notes	Raw notes stay unedited; pattern summary links back to raw evidence.
ICP and positioning	One current version, with old versions archived and dated.
Product scope	The current build cycle has one scope document; backlog stays separate.
Sales pipeline	CRM or spreadsheet is updated after every material customer touch.
Investor CRM	Every investor has status, next action, owner, and last touch date.
Runway tracker	Finance owner updates actuals and assumptions on a fixed rhythm.
Hiring scorecard	Scorecard is final before sourcing begins; changes are dated.
Decision log	Every major decision links to evidence or memo.

If people are asking “which version is right?”, the template has already failed its operating role.

Template maturity ladder

Templates improve as the startup learns. Do not expect a perfect template on day one.

Level	Template behavior	Founder action
1. Blank	The team knows a decision needs structure.	Fill the minimum fields quickly.
2. Assumption-heavy	Many fields contain beliefs.	Label assumptions and choose tests.
3. Evidence-backed	Quotes, metrics, cash, pipeline, or examples support claims.	Use it to decide.
4. Operational	The template is reviewed on a rhythm and changes behavior.	Assign owner and cadence.
5. Institutional	New team members can understand decisions from it.	Keep it short, current, and archived.

Most early teams should aim for level 3 or 4. Level 5 matters more as the team grows.

Template audit

Once a month, audit the templates that matter.

Question	Action if weak
Does this template still match the company stage?	Replace or simplify it.
Does it have a named owner?	Assign one or delete it.
Was it used in a real decision recently?	Add a review habit or archive it.
Are facts, assumptions, and decisions clearly separated?	Add labels and rewrite claims.
Is the latest version obvious?	Move old versions to an archive folder.
Is it too long for regular use?	Split decision summary from supporting detail.

Templates should earn their place. A startup’s document system should get clearer as the company learns, not heavier.

Reader action

Pick one template for this week and write:

This template will help us decide [decision]. It will be reviewed by [person] on [date].