What pre-revenue really means
A pre-revenue solo founder has not yet collected meaningful customer revenue, even if the product is being built, pilots are underway, or users are testing it. This is not the same as having no progress. At this stage, your strongest assets are usually customer insight, a working prototype, distribution access, technical capability, or evidence that a painful problem exists.
The goal is not to look like a larger company. It is to reduce uncertainty in a disciplined order:
- Prove that a specific customer has the problem.
- Show that your proposed solution works well enough to test.
- Secure commitments such as paid pilots, letters of intent, design partnerships, or waitlist sign-ups.
- Build a path to repeatable revenue before adding unnecessary complexity.
For Indian founders, this often means starting with one city, language, industry, or buyer segment rather than attempting a national launch immediately.
Choose a narrow wedge before building
Write a one-sentence definition of your first customer: “I help [specific buyer] solve [costly problem] by [clear outcome].” Avoid broad descriptions such as “AI for businesses.” A sharper wedge might be a multilingual support assistant for Indian D2C brands, an invoice workflow for small distributors, or a compliance tool for a defined professional segment.
Interview at least 15-25 potential users, but do not ask whether they like your idea. Ask how they solve the problem today, what the workaround costs, who approves a purchase, and what would make them switch. Look for evidence of urgency: spreadsheets, manual staff effort, missed leads, delayed collections, or money already spent on an imperfect solution.
Keep a simple evidence log with the interview date, customer type, current workflow, quantified pain, objection, and next step. This prevents confirmation bias and gives you useful material for product decisions and investor conversations.
If you are still studying or working full-time, structured entry points can help. The guide to startup opportunities for computer science students in India is useful for finding competitions, communities, and early technical collaborators without hiring too soon.
Build the smallest credible MVP
An MVP is not a stripped-down version of every feature. It is the smallest product that tests the riskiest assumption. For a workflow product, that may be one end-to-end use case with manual operations behind the scenes. For an AI product, it may be a focused model evaluation and a human review layer rather than a complete platform.
Set a two- to six-week build target and define success before you start. Useful measures include:
- Five users complete the target workflow without founder intervention.
- Three design partners use the product weekly for a month.
- A buyer agrees to a paid pilot or signs a letter of intent.
- The system reaches a defined accuracy, latency, or cost threshold.
- Users return because the product saves measurable time or money.
Use off-the-shelf tools where they reduce risk, but protect the parts that create differentiation. For AI products, track prompt or model versions, input quality, failure cases, latency, inference costs, and human escalation. Rapid AI prototyping services for startups can help you compare build, API, and specialist support options before committing scarce cash.
Do not confuse a polished landing page with validation. A landing page is useful when it produces qualified conversations, pilot requests, or deposits—not merely traffic.
Create a path to first revenue
Decide what you can sell before the product is fully complete. Common early offers include a paid discovery project, implementation fee, limited pilot, annual prepayment with a discount, or a service-assisted version of the product. Pricing should reflect the value of the problem and the buyer’s budget, not only your development cost.
For B2B products, identify the economic buyer, daily user, technical approver, and procurement or finance contact. Ask for a concrete next step after every serious conversation: access to sample data, a pilot date, a proposal, or an introduction to the decision-maker.
Your first revenue model should be simple enough to explain in one sentence. Track pipeline stages in a spreadsheet or lightweight CRM: qualified lead, discovery complete, pilot proposed, pilot active, paid, and retained. If outreach is consuming your week, explore automated lead generation tools for Indian B2B startups, but automate research and follow-up only after you understand which messages convert.
Fund the next proof point, not the whole company
A pre-revenue founder should raise or spend against a specific milestone. Examples include completing a pilot, reaching a target number of active users, obtaining a regulatory approval, or demonstrating a cost-efficient technical workflow.
Start with the least dilutive capital that matches the risk:
- Customer-funded work: paid pilots, implementation, or consulting that directly informs the product.
- Bootstrapping: savings or founder income, with a strict monthly budget and runway limit.
- Grants and challenge programmes: suitable for research, deep tech, public-interest applications, and early technical validation.
- Incubators and accelerators: valuable when they provide relevant customers, mentors, infrastructure, or capital—not just a logo.
- Angels and pre-seed investors: approach once you can show a sharp problem, credible execution, and evidence of demand.
Prepare a one-page data room: founder background, problem evidence, product demo, customer pipeline, pricing hypothesis, market logic, 12-month plan, cap table, incorporation details, and a use-of-funds breakdown. Indian investors will also expect clarity on entity structure, intellectual-property ownership, GST applicability, contracts, and data handling. Get a qualified chartered accountant or lawyer involved when the decision has tax, employment, securities, or privacy consequences.
Do not take equity investment simply to postpone a difficult customer conversation. Capital increases expectations; it does not replace validation.
Work solo without becoming the bottleneck
Your scarce resource is attention. Choose one primary objective per quarter—usually validation, first revenue, or retention—and limit active product bets. Maintain a weekly operating review covering customer conversations, shipped work, cash balance, runway, pipeline, and the next highest-risk assumption.
Outsource repeatable specialist tasks such as design, bookkeeping, legal review, or cloud setup, but retain ownership of customer learning and core product decisions. Document workflows so contractors can deliver without repeated explanations. Build a small advisory circle with complementary strengths: one customer-domain expert, one technical reviewer, and one commercially experienced founder can be more useful than a large informal network.
Protect personal runway as carefully as company runway. Set a monthly founder draw, define the point at which you return to consulting or employment, and avoid personal debt for an unvalidated product unless you fully understand the downside.
Measure evidence that matters
At the pre-revenue stage, vanity metrics can conceal weak demand. Track leading indicators that connect to payment:
- Percentage of interviewed users with the problem today.
- Activation and completion of the core workflow.
- Weekly retention among pilot users.
- Time or cost saved per customer.
- Conversion from qualified conversation to pilot.
- Pilot-to-paid conversion and sales-cycle length.
- Gross margin and AI or infrastructure cost per transaction.
For feedback-heavy products, a repeatable tagging system is more useful than a folder of comments. Automated user feedback categorization for Indian SaaS can help once feedback volume justifies automation; before that, manually review every important objection.
If your product uses voice, regional languages, or sensitive customer data, validate quality and trust in the actual Indian context. Test accents, code-switching, noisy environments, consent flows, data retention, and escalation to a human. Compare the economics and user experience of a voice interface with text using the voice agent vs chatbot guide.
A practical 90-day plan
Days 1-30: select one customer segment, conduct interviews, map the existing workflow, define the riskiest assumption, and secure three to five design partners.
Days 31-60: ship the narrow MVP, run weekly tests, measure one outcome metric, document failures, and ask for paid pilots. Stop features that do not support the core workflow.
Days 61-90: convert the strongest pilot, refine pricing and onboarding, calculate unit economics, formalise contracts and data practices, and decide whether to bootstrap, apply for grants, or raise a focused pre-seed round.
By the end of 90 days, success is not necessarily a large user count. It is a defensible answer to three questions: Who pays? Why now? Can you deliver the outcome repeatedly?
FAQ
Can a solo founder raise before revenue?
Yes, but investors will look for unusually strong evidence elsewhere: domain expertise, technical progress, proprietary access, design partners, or a large and urgent problem. A clear milestone-based plan is stronger than a large speculative market slide.
Should I incorporate before validating the idea?
Not always. Validate the problem and customer first, then get professional advice on incorporation, contracts, tax, grants, and intellectual-property ownership before accepting money or signing material commitments.
When should I bring in a co-founder?
Add a co-founder when a persistent capability gap materially limits progress and the person shares your working style, commitment, and risk tolerance. Do not add equity merely because solo building feels lonely.
What should my investor update include?
Send a concise monthly update covering progress against the milestone, customer evidence, product changes, key metrics, cash and runway, risks, and specific asks. Consistency builds trust even when the news is mixed.
Apply for support
If you are building an AI product from India, AI Grants India can help you identify relevant grant and ecosystem opportunities. Apply when you can explain the problem, technical approach, milestone, budget, and expected impact clearly—not only when you need cash.