Unicorn in 18 Months: How Serval Replaced ServiceNow

Jake Stauch's first startup failed after seven years. His second became a unicorn in 18 months. The difference wasn't luck — it was a deliberate strategy to attack a $160B incumbent at its strongest point, not its weakest.

Key Facts

• Founded: April 2024 (Jake Stauch)
• First sale: May 2025 — over a year after founding (Jake Stauch)
• Demo-to-close rate: Over 50% on six-figure enterprise deals (Jake Stauch)
• Seed round: $4.5M led by General Catalyst and First Round Capital, pre-product (Jake Stauch)
• Time to $1M ARR: Within first two months of selling (Jake Stauch)

Why Jake Stauch's First Startup Failed — And What He Learned

NeuroPlus had passionate early customers but a market too small to scale. The real buyers — parents of kids with severe medication side effects — were only 1-2% of the ADHD population. Intense early traction masked a fundamental market size problem, not a product problem.

Jake dropped out of Duke to build NeuroPlus, an EEG-based brain-training game that helped kids with ADHD focus without medication. It worked. Early customers were fanatic. But after seven years, the company wound down.

The problem wasn't the product — it was the market. As Jake explained, the families who truly needed it were those whose kids had severe medication side effects like seizures and growth delays. That was 1-2% of kids taking ADHD medication. Once that niche was saturated, there was nowhere left to grow.

This experience shaped everything about how Jake approached Serval. He left NeuroPlus wanting to understand what product-market fit actually felt like — not just assume he had it.

"We had crazy product market fit, but the market ended up being a very, very small niche of the broader market." — Jake Stauch

"When you're in a startup that doesn't have product market fit, you're constantly optimizing around the edges. It turns out you probably just don't have the right market." — Jake Stauch

The Verkada Lesson: Product-Market Fit Makes Sales Look Easy

At Verkada, Jake watched a junior sales rep fumble a demo — and still close a 30-camera order on the spot. The lesson: great sales technique doesn't create PMF. PMF makes sales look like great technique. If your product is right, execution doesn't have to be perfect.

After NeuroPlus, Jake joined Verkada — a physical security company selling cloud-connected cameras and access control to enterprises. He wanted to see what a working company felt like from the inside.

The moment that crystallized it came on his first sales call. He was expecting to witness sophisticated selling tactics. Instead, a junior rep gave an imperfect demo and the customer said: send me the order form for 30 cameras.

Jake carried this observation directly into Serval's go-to-market strategy. His benchmark for readiness to sell wasn't feature completeness — it was whether he could get through a demo without the customer losing interest before they mentally closed the deal.

"You actually don't have to be perfect and magical to do this. You just have to be selling something people want." — Jake Stauch

"Everything works. If we do it well, everything works. And that, I think, is the clearest explanation of what product market fit feels like." — Jake Stauch

The Customer Discovery Question That Changed Everything

Standard discovery questions like 'what's your biggest pain point?' produce generic answers. Jake's breakthrough question was: 'If you hired someone today to sit next to you and do work, what would you have them do?' This surfaces latent demand — the work people know needs doing but can't prioritize.

During paternity leave, Jake ran over 100 customer discovery calls with IT leaders. Early calls used textbook questions and returned textbook answers — cybersecurity concerns, compliance issues, nothing actionable.

The shift came when he changed his framing entirely. By asking what a hypothetical new hire would work on, he bypassed the 'what's broken' mindset and tapped into 'what's waiting.' IT leaders consistently said they'd have that person build automations — scripts and workflows to stop doing repetitive manual work.

This pattern repeated across companies of all sizes and pointed directly at the same root problem: automation tools existed, but they were too painful to use. The friction of building workflows in no-code tools meant most teams never built them at all.

"If you hired somebody today and you just have them sit next to you and do work for you, what would you ask them to do? That is the question that really started to open people up." — Jake Stauch

"You ask generic questions, you get generic answers. We would go into the call with a more narrow focus on what we were trying to do discovery around." — Jake Stauch

• Generic questions get generic answers — narrow the focus before the call
• 'What would a new hire do for you?' surfaces priority work, not just pain
• Consistent answers across 100+ calls validated the automation gap
• The real problem wasn't tickets — it was the cost of building workflow automation

Why Serval Replaced ServiceNow Instead of Building On Top of It

Jake chose full-platform replacement from day one for two reasons: you can't build a differentiated product when you're limited by someone else's platform, and IT buyers want to consolidate vendors, not add them. A rip-and-replace story captures existing budget; an add-on story competes for discretionary spend.

Most AI startups entering established software categories pick a wedge — a narrow use case where they can win without confronting the full incumbent. Jake explicitly rejected this.

He pointed to Moveworks as a cautionary tale: by building on top of ServiceNow rather than replacing it, the company remained constrained by the platform it depended on. Serval's bet was that owning the full stack — ticketing, workflow automation, access management — was the only way to deliver a meaningfully better experience.

The business logic reinforced the product logic. IT departments are under pressure to reduce vendor count and cut software spend. Walking in with a replacement that costs less and does more is a fundamentally stronger conversation than asking for a new budget line.

"You can't build a differentiated product on top of somebody else's product if you're fundamentally reliant on their product for your product performance." — Jake Stauch

"We'd much rather go to them with the story of how they're replacing vendor spend, replacing existing budget categories, instead of adding on to their budgets." — Jake Stauch

• Moveworks stayed a layer — Serval chose to be the platform
• IT buyers want fewer vendors, not more — replacement beats addition
• ServiceNow's strength is configurability — Serval attacks exactly there
• Full platform ownership = better product experience, stronger pricing power

How Gen AI Made a Year-One Platform Rebuild Possible

Gen AI compressed years of engineering into months. Jake says building a competitive ticketing system pre-AI would have required hundreds of engineers and years of work. AI let a five-person team ship table-stakes feature parity fast enough to compete with a 20-year-old incumbent.

ServiceNow took two decades and thousands of engineers to build. Serval's core team was five people at the end of 2024. The gap was closed by AI — both as a development accelerator and as the product's core differentiator.

On the build side, AI let the team rapidly ship features that would have taken months per engineer-year in a traditional setup. Forward-deployed engineers working with customers could push feature requests into production in days.

On the product side, Serval's natural-language-to-code workflow engine directly attacks ServiceNow's configurability advantage. The promise: build any workflow your business needs, in minutes instead of months, described in plain English rather than assembled block by block.

Jake also made an explicit bet on AI model improvement. The system didn't work perfectly at launch — but he and his co-founder judged that the remaining gaps were small enough that model progress would close them. That calculated risk paid off.

"We could not have built this company before we built it. The timing could not have been better for us." — Jake Stauch

"We had to take this calculated risk of whether we think the models are going to get good enough where this actually works, because it did not work yet." — Jake Stauch

The PMF Signal: When Customers Start Rounding Up

Jake's PMF signal wasn't a revenue milestone — it was a behavioral shift in demos. Prospects stopped focusing on missing features and started assuming Serval would build everything they needed. When customers 'round up' on what your product can do, you've crossed a critical belief threshold.

For over a year, Jake ran demos that went nowhere. Customers saw the product and could immediately list 20 things it didn't do. He treated every conversation as a practice sales call and consistently found he couldn't get to a close.

Then, in one week in April 2025, something shifted. Ten demos in a row ended with customers excited — not about the complete product, but about the product they believed Serval would become. They stopped rounding down and started rounding up.

That psychological shift — from skepticism to projected belief — became Jake's definition of product-market fit. And it preceded the revenue confirmation. His demo-to-close rate crossed 50%, and Serval hit $1M ARR within two months of its first sale.

"It was almost like we'd crossed this fifty percent threshold where they started rounding up what the product could do versus rounding down." — Jake Stauch

"When I get an intro into a customer, I kind of mentally bank it and I'm always shocked if we don't win it." — Jake Stauch

Serval vs. Traditional AI-on-Top-of-ServiceNow Approach