Employee Number Two walks you through twelve structured projects — each one building on the last, each one producing real deliverables you can use. Here's what you'll build along the way.
Define who you are as a founder and articulate your startup hypothesis.
This is your starting point. Through guided conversation, you'll create a founder profile that captures your background, goals, and working style — then articulate your startup hypothesis in a structured format that every downstream project can reference.
Clarity on what you're building and why. A correctly configured workspace where every future project inherits your context automatically.
Pressure-test your hypothesis against real-world signal before building anything.
Discover what is actually true about the problem, the people who experience it, and what already exists to solve it. This isn't about confirming what you believe — it's about finding out what the market actually says.
Evidence-based answers to critical questions before you invest in building. A realistic picture of who your customer actually is — not who you think they are.
Turn market research into a defensible position, messaging framework, and brand voice.
Your research told you who the customer is and what the competition looks like. Now you define where your brand stands in that landscape — a positioning statement, a messaging hierarchy for buyers and users, and a voice that every piece of content will follow.
A clear market position you can explain and defend against named competitors. A concrete voice that anyone creating content or copy can reference consistently.
Develop the visual language — colors, typography, logo direction, and a design system.
Translate your brand strategy into a complete visual identity. Every decision — color psychology, typeface pairing, logo direction — is grounded in the positioning and voice you defined in the previous project, not arbitrary aesthetics.
A coherent visual identity you can hand to any designer or apply in any tool. Design tokens that downstream projects consume programmatically — no ambiguity, no drift.
Build a focused content strategy and start capturing early demand.
Turn strategy into content the market can see. You'll choose 2–3 high-fit channels (not everything), create a content calendar mapped to your messaging pillars, draft actual content across formats, and build a waitlist that becomes your beta recruitment pool.
Publish-ready content across multiple formats. A structured waitlist of real prospects — not vanity metrics — that feeds directly into beta testing later.
Identify high-fit prospects, craft personalized outreach, and build a pipeline.
Your ICP and brand voice are defined. Now put them to work — systematically identify prospects, generate personalized outreach that speaks to real pain points, and build a pipeline you can actually manage.
A repeatable outbound process grounded in your research — not spray-and-pray. Real conversations with potential design partners and early customers.
Translate validated market needs into requirements, epics, and a roadmap.
Everything you learned about the market, the customer, and the competition now shapes what you build. Define product requirements grounded in real needs, break them into epics, prioritize, and create a roadmap that guides development.
A product definition grounded in evidence — not assumptions. A clear sequence of what to build first and why, so you don't waste cycles on the wrong features.
Turn epics into engineering specs, then validate with QA and UX review.
Translate each epic into requirements an engineer can implement without ambiguity. After implementation, run structured QA validation and UX review against your brand identity to ensure what was built matches what was specified.
A development process with built-in quality gates. Confidence that what you ship matches your requirements and brand identity — not just "works."
Recruit beta users, collect structured feedback, and synthesize it into action.
Your waitlist from inbound marketing becomes your beta recruitment pool. Structure the feedback process so you capture actionable signal — not noise — then synthesize it into clear product inputs: what to fix, what to build next, what to cut.
Real user validation before full launch. Feedback that's structured enough to act on — not a pile of anecdotes. Evidence for what your customers actually value.
Develop evidence-based pricing grounded in beta feedback and competitive research.
Move beyond guesswork. Use what you've learned from beta users, your competitive landscape, and your cost structure to evaluate multiple pricing strategies and choose the one that fits your market and business model.
Pricing grounded in evidence — competitive positioning, cost structure, and what beta users indicated they'd pay. Not intuition. Not what some blog post said.
Navigate entity selection, domain strategy, banking, and early legal considerations.
Get the structural foundation right. Evaluate entity options for your specific situation, develop a domain strategy that protects your brand, and build a legal checklist you can bring to an attorney — preparation, not legal advice.
Frameworks for structural decisions matched to your stage and intentions. Preparation that makes your first attorney meeting productive instead of exploratory.
Identify investors, recruit advisors, and build your pitch narrative.
Everything you've built — research, brand, product, pricing, traction — now becomes your investor story. Identify funding sources at your stage, target the right investors, recruit advisors, and develop a pitch deck narrative that ties it all together.
A pitch narrative built on twelve projects of accumulated evidence — not a story you made up over a weekend. Targeted investors, not a spray list. Advisors who strengthen your credibility.
Model revenue, costs, unit economics, and runway scenarios from your actual data.
Build a financial model grounded in your actual pricing, cost structure, and product roadmap — not generic SaaS benchmarks. Run scenario analysis, calculate unit economics, plan hiring against revenue milestones, and model runway under different growth paths.
Financial projections an investor can interrogate — because they're built on eleven projects of real work, not a template with placeholder numbers.
Every project builds on the one before it. Context accumulates. Nothing is lost.
Get Started