The handbook on Startup Friendly

Validate the problem before the product

Mon, 01 Jan 0001 00:00:00 +0000

The first job is not to sell the solution. It is to learn whether a specific group of people repeatedly experiences a problem important enough to change their behavior.

Write the risky assumption

Name the belief that would break the idea if it were false. Keep it behavioral and specific:

Operations leads at 20–100 person software companies lose at least three hours a week assembling customer-health reports, and they already use workarounds to reduce that time.

Define an ideal customer with observable criteria

Mon, 01 Jan 0001 00:00:00 +0000

“Small businesses” is not a customer segment. Neither is “developers.” A useful ideal customer profile helps you decide who to interview, what to build, where to find prospects, and which opportunities to ignore for now.

Start with the urgent situation

Define the moment that makes someone look for help. Good segments often share a trigger:

a team just crossed a size threshold;
a new regulation or customer requirement appeared;
an existing workflow broke under higher volume;
a person took responsibility for a metric; or
a deadline made the old workaround unacceptable.

The trigger is often more predictive than industry alone.

Scope a first product that can teach you something

Mon, 01 Jan 0001 00:00:00 +0000

An MVP is not a low-quality version of a big product. It is the smallest complete experience that delivers one meaningful outcome and teaches you whether the underlying bet is worth expanding.

Name the learning goal

Write the decision this release should help you make. For example:

Will support leaders connect their data and review a generated weekly risk list without hands-on prompting from us?

This is more useful than “launch dashboard v1.” The learning goal determines what must be real and what can remain manual.

Price the first version

Mon, 01 Jan 0001 00:00:00 +0000

A credible first price gives a real buyer enough information to make a real buying decision.

Choose the value unit

Find the unit that grows when customer value grows: seats, transactions, locations, managed assets, usage, or a meaningful outcome. Avoid a metric customers cannot predict or one that punishes the behavior you want.

For an early product, simple usually wins. One package and one value unit create cleaner feedback than four tiers with invented distinctions.

Set up product analytics around the value moment

Mon, 01 Jan 0001 00:00:00 +0000

Early analytics should make product decisions easier. Tracking every click usually creates maintenance work and a dashboard nobody trusts.

Define the value moment

Name the action that indicates a user received meaningful value. A visit or sign-in alone does not qualify. The value action might be publishing a page, completing a workflow, inviting a collaborator, or receiving a useful result.

Then define the shortest path from account creation to that moment.

Prepare to incorporate a US startup

Mon, 01 Jan 0001 00:00:00 +0000

Incorporation turns a project into a legal entity with ownership, governance, tax, and reporting obligations. The goal is not to become your own lawyer. It is to arrive prepared enough to make good decisions and keep the records clean.

Decide whether now is the time

Common triggers include signing contracts, accepting payment, issuing founder equity, hiring, protecting intellectual property, or raising money. Waiting can be sensible when the idea is still casual. Waiting after value, obligations, or multiple contributors exist can create cleanup work.

Launch your first product

Mon, 01 Jan 0001 00:00:00 +0000

A launch is useful when it gives a specific audience a clear reason to act now. The goal is not to make the entire internet notice. It is to create a concentrated wave of qualified attention your team can support and learn from.

Choose one launch objective

Pick the result that matters most:

recruit 20 design partners;
convert the first five paying customers;
learn which message earns replies;
establish credibility in a narrow community; or
create enough usage to expose product problems quickly.

The objective changes the channel, call to action, and measurement. “Get buzz” is too vague to guide a decision.

Find your first ten customers

Mon, 01 Jan 0001 00:00:00 +0000

Before a channel is repeatable, customer acquisition is usually manual. That is a feature: founder-led outreach gives you direct contact with the language, objections, and buying process your later marketing must encode.

Set the list criteria

Use your ideal customer profile to define five observable filters: account type, size or complexity, trigger, role, and exclusion. Build a researched list of 50 accounts that fit those filters now.

Add a short reason for each account: a job posting, new executive, product launch, funding event, technology change, or public statement that suggests the problem is timely.

Choose one growth channel to test

Mon, 01 Jan 0001 00:00:00 +0000

Early teams often run five weak channels at once and learn little from any of them. Choose one plausible path, give it enough focused effort to reveal its mechanics, and define in advance what would make you continue.

Start from buying behavior

Ask where customers already discover, evaluate, and discuss solutions like yours. Consider:

direct founder sales;
partner or ecosystem referrals;
practitioner communities;
search and educational content;
product-led invitations or sharing;
events and field marketing;
paid acquisition; and
targeted outbound.

Do not choose a channel because another startup made it look glamorous. Choose it because your buyer is reachable there and the economics could eventually work.

Hire your first employee

Mon, 01 Jan 0001 00:00:00 +0000

The first hire changes how the company works. Define the important outcome that founders can no longer achieve alone, then hire against that outcome.

Write the outcome before the title

Describe what should be different in 6–12 months because this person joined. Then list three to five measurable outcomes and the capabilities needed to reach them.

Separate must-have evidence from preferences. “Has done enterprise sales from zero to first repeatable motion” is more useful than “five years of SaaS experience.”

Prepare a seed fundraise

Mon, 01 Jan 0001 00:00:00 +0000

A seed round works best as a focused process built around a clear company milestone. Before starting, decide why outside capital is the right tool and what the company can prove with it.

Write the financing case

Answer:

What is true about the customer and market now?
What evidence suggests this team can win?
What important milestone will the round fund?
How much time and money are required, with a buffer?
What becomes possible after that milestone?

Build a bottom-up operating plan, then use it to set the raise amount and runway target.

Run a founder weekly review

Mon, 01 Jan 0001 00:00:00 +0000

Founders need a recurring review that compares current evidence with the operating plan. A good review compresses information, resolves tensions, and turns priorities into explicit commitments.

Prepare asynchronously

Before the meeting, each owner updates a shared page with:

the handful of company measures and their definitions;
notable customer evidence;
progress against last week’s commitments;
decisions or help needed; and
risks that changed.

Do not spend meeting time reading updates aloud. Missing data is itself a signal to improve the system.

Send a useful investor update

Mon, 01 Jan 0001 00:00:00 +0000

An investor update is an operating tool. It creates a record of the company’s trajectory and gives informed supporters a chance to help while the need is still timely.

Keep the structure stable

Use the same sections each month:

Headline: one sentence on the most important change.
Numbers: a small set of consistently defined metrics with prior-period comparison.
Wins: two or three meaningful developments.
Challenges: the real constraints or misses.
Focus: what the company is prioritizing next.
Asks: specific, forwardable requests.

The update should take a few minutes to read. Link to supporting detail and keep the full board deck separate.