How Ross McNairn Grew Wordsmith AI to Millions in ARR in 18 Months

Ross McNairn deliberately picked fights with his co-founders before committing to build Wordsmith AI together. That contrarian instinct — test conflict early, stay small, attack the annoying parts of the job not the core — turned out to be the exact formula for reaching PMF in 18 months.

Key Facts

• Funding raised: $5M seed + $25M Series A = $30M total in ~18 months (Pablo Srugo)
• Team size at PMF: 8 people until Series A close (Ross McNairn)
• Slack-first build period: 10 months of native Slack product before any web interface (Ross McNairn)
• Early webinar ROI: $5K spend → 200 lawyer attendees → ~20 demos → ~5 clients (Ross McNairn)
• ACV at scale: Average deal ~$50K–$60K; early deals at $12K/year (Ross McNairn)

How Ross McNairn Tested Co-Founders by Starting Fights on Purpose

Before committing to Wordsmith AI, Ross spent three months deliberately provoking his potential co-founders to test how they handled conflict. His thesis: conflict is inevitable in any founding team, so test it early in low-stakes situations rather than discover incompatibility after you've built something real.

Most founders pick co-founders based on skills or prior relationships. Ross added a third filter: conflict management. After watching founding teams implode from the inside at multiple companies, he built a deliberate stress-testing process before anyone signed anything.

He would code something with his technical co-founder Giggs, then critique it harshly — even when the work was perfectly reasonable. The goal wasn't to be difficult; it was to see how the other person responded under pressure. Could they push back as a peer? Could they disagree without it getting personal? Both co-founders passed.

Ross then extended this to a four-day hike on the Camino de Santiago — no plan, hissing rain, middle of nowhere. His logic: if you can construct uncomfortable situations and people still enjoy it, you have a good founding team. They got through it, found a bar, and moved forward together.

"I constructed situations to fight early on with these folks to work out, could we do it in a good way? And could we fight as peers?" — Ross McNairn

"If I can construct a few uncomfortable things and the guys enjoy it, then we'll be a good founding team." — Ross McNairn

• Critique reasonable work intentionally to observe the response, not judge the output
• Get co-founders to also conflict-test each other, not just you
• Use physical hardship (hike, travel, time off-grid) as a team compatibility test
• Prior history of rejection tolerance — like door-to-door sales — is a useful co-founder signal

The Accidental Fundraising Playbook: How Ghosting VCs Created a Bidding War

Ross didn't engineer a hot seed round — he stumbled into one. A casual message to an Index Ventures partner led to a meeting, which led to a term sheet. Then Ross simply didn't respond to anyone else, and the silence created urgency. The real lesson: clean cap table hygiene and the right anchor investor matter more than fundraising tactics.

With money to self-fund and no formal deck, Ross pinged an Index Ventures partner just to get market feedback. The partner asked him to come in. Instead of building slides, Ross and his co-founders built an MVP in days, stapled it to a rough deck, and walked in. Index backed them almost entirely on team signal.

What followed was unplanned. Word spread through VC networks. Ross's inbox exploded. He didn't respond — not as a strategy, but because he was building. VCs interpreted the silence as exclusivity. 'My inbox went completely nuts. I had everybody in VC try and get in touch. I just didn't respond to anybody, which was step two of the master plan that wasn't planned,' he told host Pablo Srugo.

The actual strategic move came after: Ross called a school friend who was a partner at another firm to pressure-test valuation and cap table structure. He wanted to price the round like 'Goldilocks' — not greedy, not underselling — so the Series A wouldn't be complicated by a messy seed.

"I totally didn't plan to do it that way at all. I was thinking of bootstrapping. I completely by accidented and everybody went wild." — Ross McNairn

"Right investors, right incorporation basis, right valuations, right cap table and some of the hygiene factors — that made a huge difference to the A." — Ross McNairn

Why Attacking the Core Job Kills Your Sales Cycle (And What to Do Instead)

Wordsmith's first product reviewed contracts faster and cheaper than in-house lawyers. Nobody bought it. The insight: when you threaten someone's core job, they become your enemy, not your customer. Pivot to eliminating the peripheral work they hate, and the same person becomes your biggest internal champion.

The original Wordsmith proposition was simple: send in a contract, get it reviewed in an hour for 10% of the normal cost. Objectively better, faster, cheaper. And yet, the lawyers who would buy it were the same lawyers whose job it was to review contracts. Ross realized the error: 'You're the buyer, and you're going to send me your job.'

The team pivoted after observing what legal teams were actually trying to procure. The real pain wasn't contract review itself — it was fielding a constant stream of questions from sales, procurement, and operations teams before any legal work could even begin. These interruptions were what lawyers actually hated.

Wordsmith built a Slack-native agent that let legal teams deploy an AI layer to handle inbound business questions — with a 'lawyer in the loop' approval mechanism that gave legal full control. The result: legal teams loved it because it removed noise without removing authority. 'Attacking their core job was not that exciting for them. But getting rid of the tangential bits of their job that were irritating — that was in a bit that was kind of forgotten by the other legal tech players,' said Ross.

"If you're the contract dude in company X and somebody comes to you and says I'm going to literally do your job — it's not that surprising why Bob is like, you can get out of my office." — Ross McNairn

"Attacking their core job was not that exciting for them. But getting rid of the tangential bits of their job that were irritating — that was an excellent wedge." — Ross McNairn

Building in Slack for 10 Months: The Strategy Behind Wordsmith's Defensible Moat

Wordsmith had no web interface for its first 10 months. Everything ran natively inside Slack. When the web product launched, usage tripled overnight. The Slack-first approach wasn't just about distribution — going so deep into the platform created a technical moat competitors who bolt on Slack integrations can't easily replicate.

Most SaaS products treat Slack as a notification layer. Wordsmith built its entire product inside it — smart routing between agents, permission management, file ingestion, approval workflows, channel-based controls. 'If you want to go deep into our Slack world, it's just a whole new company,' Ross said.

The decision was driven by the ICP, not a platform bet. In-house legal teams live in Slack. The rest of the business already pings lawyers there. Meeting users exactly where the problem occurred — rather than asking them to log into another tool — reduced friction to near zero.

When Wordsmith eventually launched a web assistant after 10 months, usage tripled. The web layer added a surface for the legal team themselves to interact directly, expanding from 1-2 administrators to the entire legal team. That jump in surface area accelerated word-of-mouth: 'We started getting inbound from people talking about us. Everything changed at that point.'

"We were at nine months of just every single — our Slack product is deep. Sometimes people try and add a Slack integration. It's pretty unbeatable in that sense." — Ross McNairn

"We launched a web assistant, usage tripled overnight with those users." — Ross McNairn

Why Ross Kept His Team at 8 People Until Series A

Ross deliberately capped Wordsmith's team at 8 people through the entire PMF search. His reasoning: small teams make fast decisions, avoid ego overhead, and stay focused. Once you have PMF, scaling is a solvable problem. Before PMF, every extra hire adds noise without adding signal.

With $5M in the bank and a clear market, most founders hire aggressively. Ross didn't. He stayed at 8 people for over 10 months, prioritizing decision speed over organizational capacity. 'I intentionally did not want a big team because I didn't want to debate,' he explained.

The analogy he used was Delta Force operators: people who handle discomfort without complaint and solve whatever problem is directly in front of them. That's what pre-PMF demands. Hiring process-oriented people before the process exists creates friction, not momentum.

His view on scaling: 'Scaling isn't the bit that I'm worried about because I've done it before.' Having gone from 20 to 1,600 people at TravelPerk, Ross knew the hiring playbook. He also knew it was irrelevant before you know what you're scaling. Now at nearly 40 people post-Series A, the growth has begun — but only after the product earned it.

"Hiring a bunch of people that you then have to get up to speed, explain to them, worrying about their burn — there's a time and place for that, and it's not when you are pre a million revenue." — Ross McNairn

"You want people that can deal with being on the Camino in the middle of the night and are not going to whine about anything, and are just going to get stuff done." — Ross McNairn

• Small teams eliminate alignment overhead that slows iteration speed
• Every early hire should function as a generalist problem-solver, not a specialist
• Don't scale the team until revenue is scaling — ARR is the signal to hire against
• Having scaled before means you can move faster pre-PMF knowing you can catch up

Law Firm AI vs. In-House Legal Team AI: Why the Market Splits