After raising over $500M, taking a company public, and selling others for billions, Rajiv Khemani has a clear playbook. His success comes from building the infrastructure for new tech waves (internet, cloud, now AI/blockchain), deliberately transitioning from a technical expert to a business leader, and mastering the unique art of funding capital-intensive deep tech. His recent $81M Series A for Auradine is an outlier that proves the rules for ambitious, infrastructure-level startups are different.
Key takeaways
- Build the core infrastructure for the next tech wave, not just an app on top of it.
- Master the transition from a technical founder to a business-savvy CEO.
- Recognize that funding deep tech requires a different playbook than SaaS.
- Raise your investor IQ by learning to see your startup from their perspective.
- Don't use outlier rounds like an $81M Series A as your benchmark; understand the context.
- Network relentlessly and build human relationships before you need them.
The Playbook of a Serial Unicorn Founder
Rajiv Khemani has raised over $500 million across a string of wildly successful companies. He’s taken a company public, sold one for $6 billion, another for $1.2 billion, and just closed an $81 million Series A for his new venture, Auradine.
When a founder builds multiple billion-dollar companies from scratch, you don’t just read their press release. You deconstruct their playbook. This isn't about one lucky break; it's about a repeatable method for building and funding ambitious, category-defining companies. We’ve broken down the core lessons from his journey.
Lesson 1: Build the Infrastructure for the Next Wave
Look at Khemani's pattern. At Sun Microsystems, he worked on the foundations of internet infrastructure. At Cavium, he helped build the hardware that powered the rise of e-commerce and SSL, growing it to $1B in annual revenue. His next startup built the chips that enabled the migration to the cloud. Now, with Auradine, he’s building infrastructure for blockchain, AI, and privacy.
The non-obvious insight here is strategic positioning. While others build apps on the new platform, Khemani builds the platform itself. This is a harder, more capital-intensive path with a longer time horizon. But the rewards are exponentially greater. You become the tollbooth owner for an entire ecosystem, not just one car driving on the road.
Common Founder Mistake: Chasing the Application Layer
Most founders default to building a SaaS app for an existing platform. It’s faster and requires less capital. But it also means you’re subject to the whims of the platform owner (think Apple’s App Store rules or changes in an API). You have less defensibility and a smaller potential outcome.
How to avoid it: Ask yourself: "What is the enabling technology that everyone in my industry will need in the next five to ten years?" It could be a new security protocol, a specialized data processing pipeline, or a hardware component. Building that is a harder problem, but solving it makes you essential.
Lesson 2: Master the Technical-to-Business-Leader Transition
After starting as a software engineer, Khemani was told he was "too technical" for a business role. His response was to get an MBA at Stanford, where he was exposed to the thinking of VCs and entrepreneurs. This was the catalyst for his entire entrepreneurial career.
You don’t have to get an MBA. But you must master the transition from building a product to building a business. Khemani’s time as an early-stage investor showed him countless passionate technologists who failed because they couldn't figure out the business side.
Checklist: Are You a Founder or Just a Technologist?
Can you explain what you do in one sentence without using technical jargon? · Have you spoken to 50 potential customers about their problems (not your solution)? · Can you build a simple financial model showing revenue, costs, and cash flow for the next 24 months? · Do you understand what a "go-to-market" strategy is and have a hypothesis for yours? · Can you articulate why your company will be worth $1B+ in a way that doesn’t sound like a fantasy?
If you answered no to more than two of these, you have work to do. You need to either learn these skills yourself or find a co-founder who has them.
Lesson 3: The Deep Tech Fundraising Playbook
Khemani raised over $300M for a semiconductor startup at a time when he says VCs had stopped investing in the space. He then raised an $81M Series A for another one. This is not the standard SaaS fundraising playbook.
Raising for deep tech or hard tech is a different sport. Investors can’t look at your MRR or LTV/CAC ratio. They are making a bet on three things:
The Team: Does the team have unique, world-class expertise to solve a problem others can’t? Khemani’s teams were composed of veterans from places like Cisco, Broadcom, and Intel. · The Technological Moat: How profound is the technical breakthrough? Is it 10% better or 10x better? This is your defensibility. · The Market Impact: If you succeed, do you unlock a multi-trillion-dollar market, as Khemani believes Auradine will for decentralization and privacy?
Why the $81M Series A for Auradine Makes Sense
For a typical SaaS startup, an $81M Series A would be absurd. A standard Series A is in the $8M-$15M range, buying 15-20% of the company on a post-money valuation of roughly $40M-$80M.
Auradine’s round is an outlier because it’s not a typical startup. Building "breakthrough software, hardware and cloud solutions" requires massive, upfront capital for:
Silicon design and fabrication: A multi-year, multi-million-dollar process. · Hiring elite, specialized talent: PhDs in cryptography, hardware engineers, and AI researchers command top salaries. · Long R&D cycles: Unlike a web app, you can't ship an MVP chip in two weeks.
The lesson isn't to seek an $81M round. It's to match your fundraising ask to the capital requirements of your ambition. If you are truly building infrastructure, you need the fuel for a long journey.
Lesson 4: Think Like An Investor
Between founding companies, Khemani spent time as an early-stage investor. He sat through "hundreds and maybe thousands" of pitches. This experience is an unfair advantage. It teaches you pattern recognition: what a great team looks like, what a fundable idea sounds like, and what derails a promising company.
He saw those that were driven and passionate. Though with great ideas and lots of potential. As well as the technologists that really needed to put in more work to figure out a business.
You don't have to become a VC to gain this perspective. You can start by ruthlessly analyzing your own venture from the outside in. An investor asks:
Market Risk: Is this a real, big market? Or a niche solution? · Product Risk: Can this team actually build what they say they will? · Execution Risk: Can this team build a company around the product? Can they hire, market, and sell? · Why now?: What has changed in the world to make this possible and necessary today?
Common Founder Mistake: Pitching the Solution
Founders are obsessed with their solution. Investors are obsessed with the problem and the market. Your pitch shouldn’t start with what your tech does. It should start with who has the problem, how painful it is, and how big the market is for solving it. Your solution becomes the inevitable conclusion to a compelling story about a market opportunity.
How to Apply This Playbook This Week
Audit Your Ambition: Are you building an application on a platform, or could you be building the platform itself? Spend one hour whiteboarding what the "infrastructure level" of your industry looks like. · Fill Your Skill Gap: Honestly assess yourself against the "Founder vs. Technologist" checklist. Pick one area you are weak in (e.g., financial modeling, customer interviews) and find a book or short online course to start learning this week. · Reframe Your Pitch: Take the first three slides of your pitch deck. Do they focus on your solution, or do they focus on the customer, their problem, and the size of the opportunity? Rework them to tell the story from the investor's perspective. · Start Networking Now: Khemani regrets not building relationships earlier. Identify 5 people on LinkedIn who are one step ahead of you (e.g., just raised a seed round, have the job you want in 3 years). Send them a concise, respectful message asking for 15 minutes of their time to learn from their experience. Don't ask for anything else.
Frequently asked questions
- Why was the Auradine Series A $81 million? Isn't that huge?
- Yes, it's an outlier. The round is large because Auradine is building capital-intensive infrastructure (hardware and software) for the blockchain and AI space. This requires massive R&D, specialized talent, and silicon development, unlike a typical SaaS company.
- Should a technical founder get an MBA like Rajiv Khemani did?
- Not necessarily. An MBA is one path to gaining business acumen, but you can also learn by hiring a business co-founder, finding strong mentors, or taking short courses in finance and marketing. The goal is to learn to speak the language of customers and investors, not just technology.
- What's the main difference between raising for a SaaS startup and a deep tech one?
- SaaS fundraising focuses on metrics like MRR, churn, and CAC. Deep tech fundraising, especially early on, is a bet on the team's unique insight, the size of the technical moat they can build, and the scale of the market they can unlock. The story and team credibility often matter more than early traction.
- What's the biggest mistake technical founders make when pitching VCs?
- They pitch the technology instead of the business. Investors assume the tech is brilliant; they need to understand the customer problem, market size, go-to-market plan, and financial projections. You must translate your technical advantage into a compelling business case.
