The First 100 Days of a B2B SaaS Startup: What to Focus on Before You Think About Funding
The First Question Is Always Wrong
The most common first question I get from founders at the zero stage is some version of: "How do I raise funding?" It is the wrong question — not because funding doesn't matter, but because at day zero through day 100, funding is not your problem. Customer discovery is your problem. Product definition is your problem. Founder-market fit is your problem. Getting those right makes funding a consequence. Getting them wrong makes funding an expensive way to fail faster.
Here is what I would actually focus on in the first 100 days of a B2B SaaS startup in India, based on building Intugine and watching dozens of other founders navigate this phase.
Days 1–30: Obsessive Discovery
Talk to 50 Potential Buyers — Not Users
There is a critical distinction in B2B between the user of a product and the buyer of a product. The logistics manager who tracks shipments is the user. The VP Supply Chain who signs the purchase order is the buyer. You need to understand both, but your first 50 conversations should heavily favor the buyer. What does their P&L look like? What keeps them up at night? What have they already tried? What made them reject the last vendor who pitched them?
Map the Problem Ecosystem
Every B2B problem exists inside an ecosystem of adjacent problems, existing solutions, internal politics, and budget cycles. Map it. Who else is trying to solve this? Where are the current solutions breaking down? What is the switching cost for a buyer to change from what they do today to what you're proposing? This map will become your go-to-market strategy.
Days 31–60: The Ugly First Version
Build the Minimum That a Buyer Would Pay For
Not the minimum viable product — the minimum billable product. The distinction matters. An MVP optimizes for learning. An MBP optimizes for a paying relationship, which is the most important form of learning. In B2B, someone paying you — even a small amount — tells you more than 50 free pilots combined.
Do Things That Don't Scale
Intugine's first "product" was a manually updated Excel sheet. We did it because building the automated version before we understood the data model would have taken 4 months and produced the wrong thing. Whatever the equivalent of your Excel sheet is — build that first. Serve 2 customers manually. Understand the problem at depth. Then automate.
Days 61–100: First Revenue and What It Tells You
Close Your First Paid Customer
The target for day 100 is not a product demo. It is a signed contract — even a small one. ₹50,000 is more valuable than a ₹0 pilot with a Fortune 500 company at this stage, because it answers the core question: will someone exchange money for this? Everything else is noise.
Read the Contract Like a Product Doc
Your first enterprise contract will tell you exactly what the buyer actually values. Read every clause. The SLAs they demand tell you what they fear. The metrics they want reported tell you what their internal KPIs are. The carve-outs they negotiate tell you where their current pain is greatest. This is your real product spec.
What Not to Do in the First 100 Days
Do not hire a full engineering team before you have validated the product. Do not build a sales deck before you have talked to 50 buyers. Do not register a company in Delaware before you have an Indian paying customer. Do not raise a seed round before you have answered — with evidence — why you, why this problem, why now.
The first 100 days are for questions, not answers. Ask better questions than anyone else in your market, and the answers will tell you what to build.