Welcome

StartupBook.in is an operating manual for founders building from India. It is written for the days when you need to decide what to do next, not for the days when you want abstract inspiration.

The central idea of this book is simple: a startup is a search for a repeatable, valuable, scalable business under uncertainty. That means the founder’s job is not to look busy. The job is to reduce the most dangerous uncertainty with the fewest wasted moves.

What this book is for

Use StartupBook when you are trying to answer one of these questions:

Founder question	Where to start
Is this idea worth pursuing?	Finding Startup Ideas and Idea Templates
Who exactly is the customer?	Customer Discovery Fundamentals
What should we build first?	MVP and MVP Scope Playbook
How do we get first customers?	First 10 Customers
How do I sell as a founder?	Founder-Led Sales
Should we raise money?	Funding Paths
Are we running out of time?	Runway and Burn
How do we hire without losing the culture?	Early Hiring

How to read it

Do not read this book like a textbook. Read it like an operating system.

1. Pick the decision causing the most uncertainty.
2. Read the chapter that gives you language for that decision.
3. Run the related playbook if you need a process.
4. Use the related template if you need an artifact.
5. Take one action in the next seven days.

Reading without action becomes another form of procrastination. The book is useful only when it changes a customer conversation, a product decision, a hiring bar, a sales follow-up, a cash review, or a founder habit.

What good use looks like

A founder using this book well will leave with something concrete:

Before reading	After reading
”We should validate the idea."	"We will interview 10 exact-segment buyers by Friday and ask for current workflow artifacts."
"We need an MVP."	"The MVP tests whether users can reach first value without founder explanation."
"Sales is slow."	"Deals stall because the user likes it but the budget owner is not in the process."
"We should raise."	"The round should buy 12 months to prove paid retention in one segment."
"We need to hire."	"The first hire owns onboarding repeatability because founder-led delivery is the bottleneck.”

If the book does not sharpen the sentence, the next step, or the owner, it has not done its job yet.

Choose the first decision

If everything feels important, choose the first decision by risk, not by excitement.

Decision candidate	Choose it first when	Evidence to collect
Customer	You are unsure who has the strongest pain.	Customer conversations, workflow artifacts, urgency, current spend.
Problem	People understand the idea but do not act.	Recent painful examples, consequences, failed workarounds.
Product	You are building too much or users do not reach value.	Activation, time to value, support notes, usage behavior.
Sales	Conversations happen but deals do not move.	Buyer map, objections, next steps, pricing response, payment path.
Cash	Runway, collections, or burn could force a decision soon.	Cash in bank, net burn, receivables, payables, hiring commitments.
Team	Founder capacity is breaking or ownership is unclear.	Role bottlenecks, repeated dropped work, decision delays, morale signals.

The first decision is not always the most interesting decision. It is the one that changes the company’s odds the most this week.

The StartupBook operating note

Keep four notes open as you read:

Note	What to capture
Decision	What choice do I need to make?
Evidence	What do I know because of real customer, product, revenue, or team data?
Risk	What could break the company if I am wrong?
Next action	What will I do this week?

This keeps the book grounded. Founders do not need more opinions floating around their head. They need clearer decisions.

What this book assumes

StartupBook assumes a founder is operating with constraints. You may not have a large team, famous investors, a polished product, or perfect confidence. That is fine. The book is written for the messy middle where founders must decide with partial information.

It assumes:

Assumption	What it means in practice
Reality beats theory	Customer behavior, usage, cash, and retention matter more than elegant plans.
Focus is earned	You start broad, but the work is to narrow the customer, problem, product, and channel.
Founder time is expensive	Every week spent on low-learning work is a hidden burn cost.
India is not one market	A good answer for metro SaaS buyers may fail for tier 2 retailers, students, doctors, factories, or global software buyers.
Funding is a tool	Raising money can help, but it can also create pressure before proof exists.
Useful beats impressive	A simple customer call script can be more valuable than a beautiful strategy deck.

When a chapter gives advice, translate it into your stage, market, team, runway, and ambition. The book is not a substitute for judgment. It is a way to sharpen judgment.

Evidence over confidence

Founders often sound confident before the company has earned confidence. Use this scale to keep yourself honest.

Founder belief	Evidence level	What to do
”I think this is a problem.”	Opinion	Talk to exact-segment customers.
”People said it is interesting.”	Weak signal	Ask about past behavior, current workaround, cost, and urgency.
”People want to try it.”	Medium signal	Ask for time, data, workflow access, pilot, payment, or internal intro.
”People pay or commit seriously.”	Stronger signal	Deliver value, measure activation, and learn who repeats.
”Similar customers stay, pay, expand, or refer.”	Operating signal	Start improving repeatability, onboarding, pricing, and distribution.

This book should move you up that evidence ladder. If it only gives you sharper language without stronger evidence, keep going into the field.

The founder’s weekly question

At the end of every week, ask one question:

What do we now know that should change what we do next week?

If the answer is “nothing”, inspect the week. Maybe you shipped, but did not learn. Maybe you met people, but did not ask direct questions. Maybe you got praise, but no commitment. Maybe you stayed busy because the hard decision was uncomfortable.

Use this small review:

Area	Weekly check
Customer	Did we speak to the right people, not just available people?
Product	Did the work reduce uncertainty or only add features?
Sales	Did any prospect move to a clearer next step, payment, pilot, or refusal?
Cash	Did runway, collections, or spend change the next decision?
Team	Did the week clarify ownership or create more ambiguity?
Founder energy	Are we building a sustainable operating rhythm or surviving on panic?

This is the heartbeat of the book. Read, act, learn, decide, repeat.

What to ignore for now

Founders often lose time because they try to consume the whole startup world at once. In the first pass, ignore anything that does not connect to your current decision.

If you are here	Ignore for now
You have no customer conversations	Advanced fundraising language, growth hacks, hiring plans, elaborate product roadmaps.
You have no repeat usage	Scale metrics, management layers, brand polish, broad PR, enterprise dashboards.
You have no pricing evidence	Complex financial models, valuation debates, vanity market sizing.
You have no clear role bottleneck	Recruiting channels, interview panels, culture documents.
You have no runway pressure	Shutdown content, unless you need it for scenario planning.

This is not because those topics are unimportant. It is because sequencing matters. The right advice at the wrong stage becomes noise.

A simple first-week path

If you are starting from zero, do this over one week:

Day	Work
1	Read the Founder Map and name your current stage.
2	Write one problem hypothesis using the Idea Templates.
3	Build a list of 20 people who might feel the problem.
4-5	Speak with at least five people and record exact words.
6	Review patterns: customer, trigger, workaround, buyer, urgency.
7	Decide: continue, narrow, change, or stop.

That week will teach more than a month of polishing a pitch deck.

What makes this India-aware

Indian founders often build in mixed conditions: price-sensitive customers, relationship-led trust, fragmented markets, strong talent pools, uneven payment behavior, global ambition, regulatory complexity, and family/social pressure. This book treats those as normal constraints, not footnotes.

It also does not assume that every company should raise venture capital. Bootstrapped, service-to-product, SaaS, marketplace, consumer, AI, fintech, B2B, and global-from-India paths all appear in the book.

Start here

If you are new, go in this order:

1. The Founder Map
2. What Is a Startup?
3. The India Founder Context
4. How to Read This Book by Stage
5. How to Use Playbooks

If you are already building, skip to the page that matches this week’s hardest decision.

The founder operating promise

StartupBook is most useful when you use it as an operating system, not a motivational library. Every page should eventually connect to one of five founder moves.

Founder move	What it looks like
Decide	Choose customer, scope, price, channel, hire, fundraising path, cut, pivot, or shutdown.
Test	Run interviews, sales calls, MVP usage, pricing asks, onboarding review, or cash review.
Write	Create a memo, scorecard, tracker, decision log, roadmap, or update that clarifies thinking.
Communicate	Align co-founders, team, customers, investors, advisors, family, or vendors.
Stop	Remove distracting features, segments, channels, hires, spending, or narratives.

If a reading session does not create one of these moves, make the session smaller and more practical.

The first serious artifact

Before building too much, write a one-page founder memo.

Section	Prompt
Customer	Who exactly has the problem?
Problem	What painful situation happens in their current life or work?
Alternative	What do they do today instead?
Trigger	Why would they act now?
Promise	What outcome will we create first?
Business model	Who pays, how much, when, and why?
Distribution	How will we reach 50 more similar people or companies?
Evidence	What have we already observed, not merely believed?
Risk	What would make this idea false?
Next action	What will we do this week to learn?

This memo is not for investors. It is for founder honesty. Keep rewriting it until reality starts repeating.

The founder evidence inbox

Create one place where raw evidence lands before it becomes strategy. This can be a document, spreadsheet, CRM notes, Notion database, Linear issue, or simple folder. The tool matters less than the habit.

Evidence type	What to save	Why it matters
Customer conversations	Exact quotes, role, segment, trigger, current workaround, urgency.	Prevents founders from remembering only the supportive parts.
Product behavior	Activation, drop-offs, repeated workflows, support questions, bugs.	Shows whether the product creates value without founder explanation.
Sales signals	Buyer, objection, price reaction, next step, close risk, lost reason.	Separates real pipeline from friendly conversations.
Cash facts	Bank balance, receivables, payables, payroll, tax/advisor obligations.	Keeps survival decisions grounded.
Team signals	Repeated blockers, ownership gaps, hiring needs, conflict patterns.	Shows where the operating system is breaking.
Founder notes	Energy, avoidance, decisions delayed, family constraints, personal risk.	Keeps founder reality visible instead of hidden until crisis.

Do not turn the inbox into a museum. Review it weekly and ask what changed your mind.

What to do after the first week

After the first week, choose a 30-day operating theme. A theme is not a slogan. It is the main uncertainty the company will reduce.

Theme	Use when	Example 30-day output
Customer truth	Segment or pain is still vague.	25 interviews, pattern table, narrow ICP decision.
First value	Product exists but users do not reliably reach value.	Activation definition, onboarding fixes, usage review.
Paid proof	People like the idea but do not commit.	Pricing asks, paid pilots, buyer objections, commercial next steps.
Repeatable sales	Revenue exists but sales is founder-chaotic.	Sales notes, objection map, demo script, pipeline stages.
Cash clarity	Runway, burn, or collections are stressful.	13-week cash view, spend cuts, collections owner, decision date.
Team clarity	Founders or early team are overloaded.	Role scorecard, ownership map, weekly review rhythm.

The book becomes powerful when each 30-day theme ends with a decision: continue, narrow, change, stop, hire, raise, cut, or pivot.

The first 60-minute session

If you are opening StartupBook during a real founder problem, do not browse. Run one focused session.

Minutes	Work	Output
0-10	Write the current problem in one sentence.	”We are stuck because…“
10-20	Name the stage you are actually in.	Idea, discovery, MVP, first customers, revenue, fundraising, hiring, scaling, survival.
20-30	Pick the most dangerous uncertainty.	Customer, problem, product, sales, cash, team, founder energy.
30-45	Read one page tied to that uncertainty.	One page, not ten tabs.
45-55	Choose one field action or artifact.	Call list, pricing ask, MVP scope, cash view, role scorecard, investor memo.
55-60	Set owner, deadline, and review evidence.	Who does what by when, and what proof will count.

Use this rule:

One StartupBook session should produce one decision, one artifact, or one field action.

If you finish the hour with only more interesting ideas, you probably used the book as content. Restart the session with a sharper operating question.

The founder anti-library rule

Startup content can become a hiding place. A founder can read about ideas, PMF, sales, fundraising, hiring, AI, exits, and failure while avoiding the one conversation or decision that would change the company.

Use this anti-library rule:

If you are tempted to read about…	First do this
More startup ideas	Write the exact customer and painful situation for the current idea.
More product strategy	Watch one target user try to reach first value.
More marketing	Ask five target customers how they currently discover and trust alternatives.
More fundraising	Write the milestone this round buys and the evidence investors will inspect.
More hiring	Write the role outcome and what founders will stop doing after the hire.
More scaling	Identify which current motion is already repeatable without founder heroics.
More failure stories	Write the failure signal already visible in your own company.

Read to act. Read to decide. Read to make the next week less vague.