8 回答
Ruthless prioritization is my mantra for the first 90 days: pick very few things and do them extremely well. Start with clarifying the problem you solve and who actually needs it, then validate with real conversations and quick tests (landing page, short survey, or a simple prototype). Build the tiniest MVP that proves value, focus on one acquisition channel, and measure the core funnel—how people discover you, convert, and come back. Don’t forget basics like pricing, simple bookkeeping, and a basic legal structure so nothing surprises you down the road.
I also keep a tiny playbook of experiments: three-week tests with clear metrics, an onboarding checklist to remove friction, and a customer feedback loop to prioritize features. Hire one reliable person only when necessity is clear, and use cheap collaboration tools to keep costs low. By day 90 I expect some early users, a small amount of revenue or committed trials, and a clear list of what to double down on next. Those early wins—no matter how small—give me this weird rush of confidence and keep me going.
I like to design the first 90 days backwards: pick one ambitious but measurable milestone, then stitch together weekly goals that lead there. That reverse planning forces discipline—without it you’ll chase shiny features and vague metrics. Pick a North Star metric early (activation, revenue, or weekly active users) and three monthly objectives that ladder up to that metric. Keep your plan to one page so it’s readable and actionable.
Tactically, my weeks look like this: Week 1–2, talk to twenty potential customers and validate demand; Week 3–6, build a pared-down MVP focusing solely on the core value; Week 7–9, run sustained acquisition experiments and iterate onboarding; Week 10–13, lock the operational basics (legal, accounting), refine messaging, and prepare materials for partners or investors. Use experiments with clear hypotheses, short durations, and defined success criteria—if an experiment fails, you learned something; if it works, scale incrementally.
I also carve out routines: a weekly review, a daily 15-minute sync with collaborators, and a one-page metrics dashboard that everyone can read in 30 seconds. That rhythm keeps momentum and prevents decisions from being made in panic. By the end of 90 days I want a repeatable growth loop and a truthful picture of product-market fit. It’s not glamorous, but that structure keeps me grounded and oddly satisfied.
Break it down into weekly rhythms and rituals — that's my favorite trick. Week 1 is orientation: refine the value prop, outline assumptions, and list critical metrics. Weeks 2–4 are rapid validation: run ads, collect signups, and interview customers until patterns appear. Weeks 5–8 center on building the core loop and improving activation flow; I stay ruthless about scope and focus on one retention lever. Weeks 9–12 are about scale and ops: optimize the best acquisition channel, set basic dashboards, and prepare a concise pitch or progress report.
I also build a decision calendar: every Friday I review numbers, then make a binary call — iterate, pause, or pivot. I emphasize early documentation: onboarding notes, a product backlog, and an investor one-pager that shows traction in numbers. Don't forget to handle the boring but necessary stuff like incorporation, payment rails, and a basic privacy policy early on. That combination of discipline and hustle has helped me avoid flailing and keep momentum steady, which feels oddly satisfying.
My baseline method is simple: learn fast, ship fast, measure fast. In the first 90 days I set three measurable goals — prove there's a customer, ship an MVP they can use, and validate at least one acquisition channel. I start by doing heavy customer discovery for two weeks, then I build the thinnest viable product that answers the most painful problem. I track cohorts: did users who signed up on day 1 come back on day 7? What's conversion from trial to paid?
If unit economics look promising, I spend the remaining time scaling the channel with the best ROI and tightening onboarding. If metrics are flat, I pivot hypothesis and iterate. I also try to lock down legal and accounting basics early so operations don't derail product work. By day 90 I usually know whether to double down or change course, and that clarity is worth its weight in gold.
I usually think of the first 90 days like curating a playlist: start with the loudest singles to grab attention, add deeper tracks to build loyalty, and repeat the best ones to create a vibe.
In practice, I spend the first month on discovery and a landing page that either captures emails or payments — anything that proves willingness to engage or pay. Month two I ship the MVP and obsess over the first-run experience: onboarding, activation, and one small retention mechanic. I keep experiments short and metric-focused, A/B testing copy, pricing, and onboarding steps. Month three is storytelling and partnerships: I polish the narrative, recruit a few micro-influencers or partners, and collect testimonials or case studies to fuel PR and sales.
I also keep an eye on runway and simple unit economics so I don’t scale a leaky funnel. By the end of 90 days I want either a steady little engine that grows or a crystal-clear reason to change direction. It’s a jittery, creative sprint, but that momentum is what keeps me hooked.
Launching a startup in the first 90 days feels like sprinting a marathon—fast, painful, and oddly addictive. I break it into three clear chunks so I don't drown in glorious chaos. Days 1–30 are all about learning: validate the problem with real people, write a one-sentence value proposition that makes strangers nod, and run small smoke tests (a landing page, a paid ad, or ten in-depth interviews). I aim for quantitative signals—email signups, demo bookings, click-throughs—plus the qualitative notes that reveal why customers care.
Days 31–60 shift to building a no-frills MVP and locking down the core funnel. Focus on the path from awareness to first meaningful action: onboarding, first purchase, or retention loop. Ship the smallest thing that can teach you something, instrument every step with simple metrics (conversion rates, activation rate, churn), and iterate weekly. Use cheap tools—Notion for docs, Figma for quick UI, Stripe for payments, basic analytics—and keep communication tight with any collaborators.
Days 61–90 are about amplifying what works and cleaning what doesn't. Double down on one acquisition channel, tighten onboarding based on user feedback, and get your basics in order: incorporation, bookkeeping, founder agreements, and a one-page roadmap for the next quarter. If fundraising is on the table, polish a concise deck that tells a crisp story: problem, traction, unit economics, and your ask. Expect missteps, celebrate small wins, and remember that momentum beats perfection. I always finish this sprint a little exhausted and a lot wiser—those first 90 days are brutal but they teach you what actually matters, and I love that part.
I've come to think of the first 90 days as a compressed season of a show: you need a pilot that hooks viewers, a mid-season twist that proves the premise, and an ending that convinces investors to sign on for season two.
First 30 days: obsess over the problem. I schedule interviews like auditions, watch people use existing solutions, map out their pain points, and write a one-sentence value proposition. I also sketch the simplest possible MVP — not pretty, just testable. I use cheap tools (Typeform, a single landing page, a prototype in Figma or a bare-bones product) and run tiny experiments to see if anyone clicks, signs up, or pays.
Days 31–60: iterate rapidly. I build the core onboarding loop, measure activation and retention cohorts, and pick two KPIs to optimize (usually activation rate and conversion to paid). I lock down basic unit economics — CAC, LTV, payback period — so I know whether the idea can scale. I also begin community seeding: early users, a small email list, and a handful of evangelists.
Days 61–90: focus on scaling and decisions. If metrics show promise, I double down on the highest-ROI channels and document everything for investors or partners. If not, I pivot or pause those features and rerun quick experiments. That rhythm — learn, build, measure, decide — saved me from sunk-cost traps more than once. It’s intense but clarifying, and I always come away with a much clearer map of what to do next.
Imagine treating the launch like a co-op game: the first 90 days are your coop session where you recruit the party, learn the boss patterns, and test strategies.
I begin with a manifesto and a one-page roadmap. Month one is reconnaissance: 40 to 60 customer interviews, one landing page that captures email or payments, and three hypotheses about my core metric (activation, retention, or revenue). I run pay-per-click or organic experiments to validate demand and tweak messaging until something clicks. Month two is prototype and onboarding: get an MVP in real hands, obsess over first-run experience, and watch where people drop off. I use heatmaps, session recordings, and direct chats to understand friction.
Month three scales what worked and kills what didn’t. I look at acquisition channels that hit a CPA target, refine pricing, and prepare a one-pager for potential partners or investors that includes real metrics. Throughout, I treat feedback as gold and keep a public changelog or community thread to keep early users engaged. After three months I usually have either a repeatable acquisition loop or a stack of lessons that make the next 90 days surgical — and honestly, that feeling of momentum is the best part.