156. Startup Checklists

Checklists reduce avoidable mistakes. They do not replace judgment.

Use a checklist when the cost of forgetting something is high, the work repeats, or multiple people must coordinate.

How to use these checklists

Do not use every checklist at once. Pick the one tied to the current decision.

Situation	Checklist to use first
You are still choosing what to build	Idea validation or customer discovery
You are about to start product work	MVP
You are preparing a launch	Launch
You are trying to sell first deals	First 10 customers
You are hiring	Hiring
You are raising	Fundraising and compliance
You are under pressure	Shutdown, cash, compliance, or exit readiness

Each checklist should end with one of three decisions: ready, not ready, or ready if specific gaps are closed.

Idea validation checklist

Target segment is specific.
Problem happens often enough or hurts enough.
Customers can describe a recent real example.
Current workaround is visible.
Existing alternatives are understood.
Customer has a reason to change now.
Founder can reach the customer repeatedly.
There is a path to payment, budget, or serious commitment.

Customer discovery checklist

Interviewee fits the segment.
Questions are about past behavior, not future imagination.
Founder avoids pitching too early.
Current workflow is mapped.
Pain frequency and intensity are captured.
Buying process or influence path is captured.
Exact customer language is saved.
Patterns are reviewed across conversations.
Decision is recorded: continue, change, pause, or stop.

MVP checklist

Riskiest assumption is named.
Must-build scope is tiny.
Manual work is accepted where it accelerates learning.
Success metric is defined before building.
Kill criteria are written.
Onboarding path is clear.
Feedback loop is ready.
Founder knows which users to observe.

Launch checklist

ICP and positioning are clear.
Homepage or landing page explains problem, promise, proof, and CTA.
Analytics capture source, activation, and conversion.
Support channel is ready.
Founder follow-up is scheduled.
First users are known before launch.
Launch story is specific, not generic.
Post-launch review date is set.

First 10 customers checklist

Warm list is built.
Outreach is personalized.
Discovery calls are scheduled before demos where possible.
Pilot promise is narrow.
Pricing or payment signal is tested.
Delivery owner is clear.
Customer success touchpoint is planned.
Reference ask is made after value is delivered.

First 100 customers checklist

Customer segments are separated.
Channel quality is tracked.
Funnel stages are defined.
Activation and retention are measured.
Support load is visible.
Repeat objections are documented.
Referral and expansion signals are tracked.
Founder knows which motion is repeatable.

Fundraising checklist

Funding need is tied to milestones.
Investor narrative is clear.
Metrics are defined honestly.
Data room is organized.
Cap table is current.
Customer proof is ready.
Risks are named directly.
Use of funds is believable.
Founder knows walk-away terms.

Hiring checklist

Role is necessary now.
Scorecard is written.
Sourcing channel is defined.
Interview questions map to the scorecard.
Work sample is relevant and respectful of candidate time.
Reference checks are planned.
Compensation range is realistic.
First 30 days are structured.

Compliance checklist

Use this as a preparation checklist for your CA, CS, or lawyer, not as legal advice.

Entity records are organized.
Board and shareholder records are current.
Tax registrations and returns are reviewed.
Payroll and contractor records are clean.
Invoices and collections are reconciled.
Contracts are stored and searchable.
IP assignment from founders, employees, and contractors is documented.
Data privacy and security obligations are understood.
Compliance calendar owner is assigned.

Security checklist

Password manager is used.
Two-factor authentication is enabled for critical tools.
Admin access is limited.
Employee and contractor offboarding is defined.
Customer data access is logged or controlled.
Backups are tested.
Incident contact list exists.
Security answers for enterprise customers are prepared.

Shutdown checklist

Decision rationale is documented.
Board, investors, and key advisors are informed.
Employee communication is humane and clear.
Customer commitments are reviewed.
Vendor contracts are reviewed.
Legal and financial closure steps are planned with advisors.
Data handling and access shutdown are planned.
Founder recovery time is treated as real work.

Exit readiness checklist

Financials are clean.
Revenue quality is explainable.
Customer contracts are organized.
IP ownership is clear.
Key employees and dependencies are known.
Security and compliance posture is documented.
Founder role after transaction is understood.
Buyer diligence questions are anticipated.

Stage gate checklist

Use this to decide what stage you are actually in.

Stage	Must be true before moving on
Idea to discovery	Segment is specific enough to find real prospects.
Discovery to MVP	Repeated pain, current workaround, and reachable buyer are visible.
MVP to first customers	First value can be delivered to a narrow segment.
First customers to repeatable GTM	A customer type, promise, channel, and onboarding path repeat.
Repeatable GTM to hiring	Founder can teach part of the motion and measure quality.
Hiring to scaling	Metrics, culture, management rhythm, and cash discipline are stable enough.
Scaling to exit readiness	Financials, contracts, IP, security, team, and customer concentration can survive diligence.

The checklist should slow down premature scaling. Moving stages too early is one of the quiet ways startups burn money and morale.

Readiness score

Use this score when the team disagrees about readiness.

Score	Meaning	Action
0	Unknown	Gather evidence before deciding.
1	Weak	Do not proceed unless risk is low and reversible.
2	Partial	Proceed only with owner, deadline, and mitigation.
3	Strong	Ready enough to proceed and review later.

For a major decision, score the relevant checklist items. Any 0 on a critical item should stop the decision or force a smaller test.

India operating checklist

Use this before a major launch, fundraise, hiring push, or enterprise sale.

Invoices, GST treatment, TDS expectations, and collections owner are clear with advisors where relevant.
Customer support channel is explicit: product, email, phone, WhatsApp, field visit, training, or partner.
Vendor/customer contracts are stored and searchable.
Founder, employee, contractor, and advisor IP/confidentiality paperwork is organized.
Payment path is tested, including refunds or failed payments if relevant.
Compliance calendar owner is named.
Data access and admin access are reviewed.
Founder knows which professional advisor to call for CA, CS, legal, payroll, and tax questions.

This is not a legal checklist. It is an operating hygiene checklist to prevent avoidable mess.

Checklist operating rule

Every checklist item should have one of four states:

Done
Not needed
Owner assigned
Blocked with next action

Avoid vague states like “in progress” unless the next action is clear.

Checklist owner table

For important checklists, assign owners:

Checklist	Owner	Review rhythm	Evidence
Idea validation	Founder/product	Weekly during discovery	Notes, artifacts, decision memo
Launch	Founder/GTM	Before launch and 7-14 days after	Metrics, leads, activation, support notes
Fundraising	Founder/finance/legal	Before and during raise	Data room, CRM, memo, model
Hiring	Founder/hiring manager	Per role	Scorecard, interview notes, references
Compliance/security	Founder/ops/advisors	Monthly or quarterly	Calendar, access review, records
Shutdown/exit	Founder/board/advisors	As needed	Decision memo, closure or diligence plan

If nobody owns a checklist, it is a wish.

Escalation checklist

Some checklist failures are minor. Some should stop the decision.

Area	Stop or escalate if
Idea validation	No real customer has described the problem from recent experience.
MVP	Success and kill criteria are not written before building.
Launch	No one owns follow-up, support, analytics, or post-launch review.
First customers	The pilot has no price, scope, owner, success criteria, or next decision.
Fundraising	Cap table, use of funds, runway, and milestone story do not match.
Hiring	The role has no scorecard, manager, compensation range, or first 30-day plan.
Compliance	Core documents, IP ownership, contracts, or filings are unknown before diligence.
Security	Customer data, admin access, backups, or incident owner are unclear.
Shutdown	Employees, customers, legal/financial closure, data, and founder recovery are not planned.

Use escalation to prevent false readiness. A checklist should sometimes say, “Not yet.”

Evidence column

Add an evidence column to any serious checklist.

Checklist item	Weak evidence	Strong evidence
Customer pain exists	Founder believes it; survey says yes.	Multiple target customers describe recent costly examples.
MVP scope is clear	Feature list exists.	Riskiest assumption, must-build, manual work, success metric, and kill criteria are written.
Launch is ready	Website is live.	ICP, message, analytics, support, follow-up, and review date are ready.
Hiring bar is clear	Interviewers have opinions.	Scorecard, questions, work test, and decision rule exist before interviews.
Fundraising is ready	Deck looks good.	Memo, data room, metrics, cap table, use of funds, and risks are consistent.
Security is ready	Founder says “we use cloud tools.”	Access, backups, secrets, data map, and incident contacts are documented.

Founders should ask: what artifact proves this item is true?

90-day operating checklist

Use this when a founder wants to turn a vague startup attempt into a concrete 90-day operating cycle.

Week range	Checklist	Evidence
Weeks 1-2	Segment chosen, customer list built, interview script written, runway known.	ICP note, prospect list, interview notes, cash view.
Weeks 3-4	15-25 customer conversations, workflow artifacts collected, current alternatives mapped.	Call notes, screenshots/docs where permitted, alternative table.
Weeks 5-6	Problem pattern review, willingness-to-pay asks, MVP or manual offer scoped.	Pain scoring table, pricing notes, MVP scope.
Weeks 7-8	First value delivered manually or through MVP, support issues tracked, success metric reviewed.	Usage notes, support log, customer outcome notes.
Weeks 9-10	First serious commitments pursued: paid pilot, LOI, data access, intro, renewal, or expansion.	Pipeline, signed/paid evidence, next-step records.
Weeks 11-12	Continue/change/stop decision written, next 90-day plan drafted.	Decision memo, assumptions changed, next milestone.

Do not judge the 90 days by activity. Judge it by changed beliefs:

Which customer became sharper?
Which assumption became weaker?
Which evidence made the founder more confident?
Which evidence made the founder less confident?
Which next step is now obvious?

Checklist quality test

A checklist is good only if it prevents a real mistake.

Test	Good checklist	Weak checklist
Specific	Names the exact artifact, owner, or decision.	Uses vague words like “align”, “review”, or “prepare”.
Evidence-based	Requires proof, not opinion.	Can be checked without doing real work.
Stage-aware	Matches the company’s current stage.	Asks pre-seed founders to do scale-stage work.
Actionable	Produces ready, not ready, or ready after gaps.	Produces a feeling of progress.
Owned	Each critical item has an owner.	Everyone assumes someone else has it.
Reviewable	Can be inspected later.	Disappears after the meeting.

Rewrite weak checklist items:

Weak item	Better item
”Validate idea”	Speak to 20 target customers and record recent painful examples, current workaround, owner, and commitment signal.
”Prepare launch”	Confirm ICP, message, CTA, analytics, support owner, follow-up list, and 7-day review date.
”Get investor-ready”	Align deck, memo, model, data room, cap table, use of funds, risks, and target investor list.
”Hire engineer”	Write role scorecard, 30-day outcome, interview plan, work sample, manager owner, and runway impact.

The founder should be able to point to the artifact that proves each important item.

Decision record

After using a checklist, save the decision.

Field	Notes
Checklist used
Decision	Ready / not ready / ready after gaps
Top 3 gaps
Risk accepted
Owner
Review date
Evidence link

The decision record is useful later when founders ask, “Why did we do this?” A startup should remember its own reasoning.

Checklist packs by stage

Do not run every checklist every week. Use the pack that matches your stage.

Stage	Checklist pack	Output
Idea/discovery	Idea validation, customer discovery, India context.	Problem hypothesis, prospect list, evidence review, continue/change/stop.
MVP	MVP, launch, security basics, product analytics.	Small scope, success metric, support plan, review date.
First customers	First 10 customers, pricing, pilot, collections.	Buyer map, pilot criteria, payment path, follow-up owner.
Fundraising	Fundraising, compliance, data room, finance.	Investor memo, diligence gaps, use of funds, round readiness.
Hiring	Hiring, onboarding, access/security, culture.	Scorecard, work test, offer checklist, 30/60/90 plan.
Scaling	First 100 customers, metrics, security, operations.	Growth review, quality risks, owner table, operating cadence.
Survival	Runway, shutdown, stakeholder, legal/finance advisor prep.	Options memo, cash plan, communication plan, responsible next step.

The pack should reduce confusion. If it creates more work than judgment, make it smaller.

Red-yellow-green gate

For important decisions, mark each checklist area as red, yellow, or green.

Color	Meaning	Founder response
Green	Evidence is strong enough for the decision.	Proceed, but keep owner and review date.
Yellow	Gaps exist but are understood and manageable.	Proceed smaller, add guardrails, or close gaps first.
Red	A critical risk is unknown, unowned, or contradicted by evidence.	Stop, escalate, or change the decision.

Do not average colors. One red item in cash, legal, data, customer proof, or hiring ownership can matter more than ten green items.

Checklist meeting format

Use this format for a 30-minute review.

Minutes	Activity
0-5	Name the decision the checklist supports.
5-15	Review only red and yellow items.
15-20	Decide which gaps block the decision.
20-25	Assign owner, evidence needed, and date.
25-30	Record ready / not ready / ready after gaps.

The meeting should end with fewer unknowns, not a longer checklist.

Ready-to-act checklist rule

A checklist is useful only when it changes action. End every checklist with one of these outcomes:

Outcome	Meaning	Next step
Ready	Evidence is good enough to proceed.	Execute with owner and review date.
Ready with guardrails	Some risk remains but is visible and owned.	Proceed smaller, monitor specific signals.
Not ready	A critical gap could break the decision.	Close the gap or change the plan.
Escalate	Founder cannot responsibly decide alone.	Bring advisor, board, expert, customer, or co-founder into the decision.
Stop	Evidence contradicts the plan.	Record why and release the team from the work.

Add this footer to important checklists:

Decision:
Owner:
What evidence changed our mind:
What risk we accept:
What we will monitor:
Review date:

This turns checklists from “did we do tasks?” into “are we ready to act?”

Copy-paste launch checklist

Use this before a public launch, pilot launch, Product Hunt-style launch, community launch, or founder-led announcement.

Area	Checklist item	Owner
Customer	ICP and launch audience are specific.
Message	Homepage, post, email, and pitch use the same promise.
Product	Core flow works for the intended use case.
Analytics	Activation, signup, source, conversion, and support events are visible.
Support	Founder/team knows who responds and where.
Sales follow-up	Every qualified lead has an owner and next step.
Proof	Demo, screenshots, case study, or customer quote is ready if available.
Risk	Known bugs, limitations, and sensitive claims are reviewed.
Review	Launch review date is scheduled.

Launch decision:

Launch type:
Audience:
Primary goal:
Success metric:
Stop/change rule:
Owner:
Review date:

Copy-paste fundraising readiness checklist

Use this before starting investor outreach.

Area	Ready?	Gap
One-line story is clear.
Customer segment is precise.
Problem evidence exists.
Product status is honest: live/manual/planned.
Traction metrics are defined consistently.
Round size and milestone logic are clear.
Use of funds is tied to milestone.
Cap table and company documents are clean enough for diligence.
Deck, memo, CRM, and target investor list are ready.
Top risks and FAQ answers are written.
Minimum viable runway is known.

If three or more major gaps are red, fix the fundraising system before burning warm intros.

Copy-paste hiring readiness checklist

Use this before opening a role.

Question	Yes / no
Does this role map to a business bottleneck?
Do we know what the founder/team will stop doing after this hire?
Is there a 90-day outcome?
Is the manager clear?
Can we afford salary, tools, onboarding, and management cost?
Is the scorecard written before sourcing?
Is the work sample fair and role-relevant?
Is the compensation range clear?
Is onboarding ready enough for the person to succeed?

Red flag: “We need someone senior to figure it out” often means the founder has not defined the problem.

Copy-paste shutdown readiness checklist

Use this when runway, market evidence, founder energy, or legal obligations make shutdown a responsible option.

Area	Checklist item
Cash	Remaining cash, liabilities, receivables, payroll, and vendor dues are known.
Legal/advisor	Lawyer/CA/CS/advisors are consulted before action.
Customers	Customer obligations, data, refunds, access, and support are mapped.
Employees/contractors	Final pay, notice, access removal, references, and communication are planned.
Investors	Update is factual, timely, and clear about options.
Data/IP	Data retention, deletion, export, and IP ownership are handled.
Founder	Personal runway, health, family, and next-step support are considered.
Record	Decision memo records why shutdown/pause/sale was chosen.

Responsible shutdown is founder work. It is not failure theatre; it is stewardship.

Checklist Cadence By Founder Stage

Do not use every checklist every week. Use the right checklist for the company’s current risk.

Stage	Weekly checklist	Monthly checklist	Event-trigger checklist
Idea/discovery	Customer discovery, idea evidence, founder-market fit.	Segment choice and assumption review.	Stop/change/continue decision.
MVP	MVP scope, launch readiness, analytics, support.	Product evidence and technical risk.	Public launch, pilot launch, first payment.
First customers	First 10 customers, onboarding, sales follow-up, collections.	Retention, support, finance, compliance basics.	First enterprise buyer, first refund, first churn.
Fundraising	Investor CRM, story, metric consistency.	Data room and runway review.	Term sheet, diligence request, bridge decision.
Hiring	Role urgency, scorecard, interview evidence.	Team capacity and founder delegation.	Offer, firing, co-founder conflict.
Scaling	Operating dashboard, security, finance, leadership.	Board/advisor packet and risk review.	Incident, expansion, major vendor, new country.

The best checklist is not the longest one. It is the one that changes behavior before a mistake becomes expensive.

Checklist failure review

When something goes wrong, review whether the checklist failed, the owner failed, or the company ignored the signal.

Failure question	What to inspect
Was the item missing?	Add it if the risk is likely to repeat.
Was the item present but vague?	Rewrite it with evidence and owner.
Was the owner unclear?	Assign one accountable person, not “team.”
Was evidence weak?	Define what would count as proof next time.
Was the checklist too long?	Remove low-value items so critical risks stand out.
Did the founder override the checklist?	Record why and whether the override was justified.

Use this short postmortem:

Decision:
What failed:
Checklist item involved:
Signal we missed:
Owner/process change:
New stop rule:

Checklists are living operating tools. They should improve after launches, bad hires, failed pilots, missed compliance items, painful fundraising conversations, and customer escalations.

Pre-decision stop rules

Some decisions should pause automatically when a stop rule appears.

Decision	Stop rule
Build MVP	No named user will try the MVP within 7 days of release.
Launch	No owner exists for follow-up, support, analytics, or review.
Start fundraising	Round size, use of funds, runway, and milestone do not agree.
Hire	No scorecard, manager, compensation range, or 30-day outcome exists.
Sign enterprise customer	Scope, success criteria, payment, data, support, and owner are unclear.
Take funding	Founder cannot explain dilution, repayment, rights, and downside in plain language.
Enter new segment	No evidence the segment has repeated pain and reachable buyers.
Shut down	Employee, customer, cash, legal, data, and communication plans are unmapped.

Stop rules should be written before emotion peaks. They protect the company from momentum decisions.

Founder checklist dashboard

For a small startup, keep a one-page dashboard of only the active checklists.

Active risk	Checklist	Owner	Next evidence
Example: first paid pilot	Pilot/customer checklist	Founder	Signed scope, price, success criteria
Example: first hire	Hiring checklist	Founder	Scorecard and 30-day plan
Example: runway below 6 months	Cash/fundraising checklist	Founder/finance	13-week cash view

Update it weekly. If a checklist is not tied to an active risk, archive it. The founder’s operating system should be simple enough to use during pressure.

Checklist Evidence Review

Before a high-stakes decision, do not only ask whether a checklist item is ticked. Ask whether the evidence behind the tick is strong enough.

Use this evidence review:

Evidence level	What it means	Example
Claim	Someone says it is done.	”Legal is fine.”
Artifact	A document or system exists.	Signed agreement, dashboard, invoice, support runbook.
Review	A qualified owner checked it.	Lawyer reviewed contract, CA reviewed tax item, engineering reviewed security risk.
Stress test	The item was tested under realistic conditions.	Launch support drill, payment failure test, onboarding rehearsal.
Operating habit	The item is reviewed repeatedly.	Monthly compliance calendar, weekly cash review, recurring customer health review.

For important decisions, aim for review or stress-test evidence, not only claims.

Examples:

Decision	Weak checklist evidence	Stronger evidence
Launch MVP	”Analytics are set up.”	Test user event path captured, dashboard owner assigned, review date set.
Hire first salesperson	”We need sales help.”	Role scorecard, pipeline stage definitions, first 30-day outcomes, founder manager time blocked.
Start fundraising	”Deck is ready.”	Investor memo, data room, metric definitions, use-of-funds milestones, target investor list.
Sign enterprise customer	”Contract is okay.”	Scope, payment, data, support, liability, success criteria, and implementation owner reviewed.
Shut down	”We told everyone.”	Employee, customer, vendor, investor, data, finance, legal, and records plan with owners.

The checklist is not the proof. The evidence is the proof.

Copy-paste decision day checklist

Use this on the day of a high-stakes founder decision. It is deliberately short: launch, hire, raise, sign, cut, pivot, pause, or shut down.

Decision:
Date:
Decision owner:

1. What are we deciding?
[one sentence]

2. What happens if we do nothing for 30 days?
[cost of delay]

3. What evidence supports the decision?
- Customer:
- Product:
- Revenue/cash:
- Legal/compliance/security:
- Team/operations:

4. What evidence argues against the decision?

5. What is the smallest safer version of this decision?

6. What must be true in 7 / 30 / 90 days for this to be working?

7. What would make us reverse, pause, or escalate?

8. Who owns follow-through?

9. Who must be informed?
Customers:
Team:
Investors/advisors:
Vendors/partners:
Family/co-founders, if relevant:

10. Final call:
Proceed / proceed with guardrails / wait / stop / escalate

Decision day rule: if the founder cannot write the downside, owner, reversal signal, and next review date, the decision is not ready. Speed is useful only when it is paired with responsibility.