CXOwork
All articles
Case StudiesApril 2, 20268 min read

Case study: How Thikiq rebuilt its GTM engine with a fractional CRO — and lifted ACV 3.8× in two quarters

Thikiq — a Series A AI platform for mid-market manufacturers — was stuck in pilot purgatory. Nine-month sales cycles, deals that stalled at procurement, and a founder-led motion that had hit its ceiling. Here's what two quarters with a fractional CRO actually changed.

CX

CXOwork Editorial

Editorial

Thikiq — our sister company, which builds AI software for mid-market manufacturers — had a problem that looked different from the outside than it did from the inside. From the outside: a hot Series A company with marquee logos in automotive and industrial, a product that customers loved once they saw it, and a founder who could walk into any plant manager's office and walk out with a pilot. From the inside: a pipeline that kept widening at the top and collapsing before contract, an average sales cycle that had stretched to eleven months, and a POC-to-paid conversion rate that was barely better than a coin flip.

This is a case study of what happened across two quarters when Thikiq's founder stepped away from owning revenue and a fractional CRO stepped in. Specific customer names have been generalized, but the numbers are real.

The setup

  • Stage: Series A, roughly $4.8M ARR at start of engagement
  • Market: AI-powered process intelligence for discrete and batch manufacturers, $100M–$1B revenue
  • Team at engagement start: 38 people, 3 AEs (all sub-18-months tenure), 1 founder-led enterprise pipeline
  • The problem: founder bandwidth maxed, POCs stalling, ACV stuck around $85k, sales cycle drifting from 8 months to 11, two large deals slipped quarter for the third time

Why manufacturing sales is its own animal

Most SaaS playbooks break inside manufacturing accounts. A mid-market manufacturer buying a new AI platform runs a committee that typically includes the plant manager (technical champion), the COO (executive sponsor), IT (security, integration, data sovereignty), procurement (contract terms, vendor risk), and operations finance (CapEx vs. OpEx framing, ROI model). Every single one of them has the power to say no. None of them has unilateral power to say yes.

Thikiq had been selling as though the plant manager was the buyer. He wasn't — he was the champion. That misread was baked into the pricing, the POC structure, the deck, the discovery motion, and the contract template. The product was winning the technical evaluation and losing every other lane of the committee.

The CRO search

The founder and CXOwork scoped the engagement over two calls. The thesis was narrow: we needed a fractional CRO who had sold enterprise software into operations buyers at industrial companies, who had run a GTM motion that included POC-heavy sales cycles, and who had done this work at the $5M–$20M ARR band at least once before. Industry adjacency mattered more than logo prestige.

We surfaced four advisors from the CXOwork bench inside 48 hours. Three took intro calls with the founder that week; two did structured working sessions on Thikiq's pipeline the following week. The engagement was signed on day nine: a 6-month CRO retainer at $18k/month, 20 hours a week, with four explicit 90-day milestones covering qualification rigor, committee mapping, pricing, and pipeline velocity.

The first 30 days: diagnose, don't build

The CRO spent his first four weeks almost entirely in listening mode. He sat on seven live customer calls, interviewed six of Thikiq's won accounts and four of its lost-to-status-quo accounts, and pulled every SFDC record for the 14 deals that had stalled at POC over the prior two quarters. The pattern he came back with was uncomfortably consistent:

  1. POCs were being scoped technically (can the model detect defects at 92%+ precision?) rather than commercially (what changes in the plant's P&L if we succeed?). Procurement had no ROI story to defend.
  2. IT was being engaged in month 6 of an 8-month cycle — far too late. In the deals that died, IT raised concerns that a $500M manufacturer takes 90+ days to resolve.
  3. Pricing was a flat $85k/year platform fee, site-licensed. At the committee level, a three-plant rollout looked like a $255k decision that no single executive could approve without full CapEx review.
  4. The deck opened with product architecture and closed with ROI. The order was backwards for this buyer.

The next 60 days: rewire the motion

From day 31 to day 90, the CRO ran parallel workstreams that would have been impossible for the founder to own alongside his CEO responsibilities. He rewrote the qualification framework around a 6-point committee map — no deal was allowed to advance past discovery without a named champion at plant, an engaged executive sponsor, and an identified IT stakeholder. Roughly 40% of the existing pipeline failed the new qualification criteria and was either rescoped or deprioritized. Forecast accuracy improved in the first 30 days of this change alone.

Pricing was restructured from a flat platform fee into a three-tier model: a Pilot tier ($45k, single line, 90-day commitment, explicit go/no-go criteria), a Plant tier ($180k, annual, single site, unlimited lines), and an Enterprise tier (annual ramping license, multi-site, custom). This did two things: it gave procurement a smaller first decision to champion, and it gave the COO a defensible path from pilot to full rollout that didn't require re-approval at each step.

The CRO also installed what he called a 'security-day' cadence: every pilot kicked off with a mandatory IT working session in week two, not week twenty. This was the single most consequential change. It pulled the longest delay in the sales cycle forward by four months and turned IT from a deal-killer into a deal-accelerator.

The next 90 days: hire, measure, compound

By month 4, Thikiq's numbers had moved enough that the founder was ready to invest in headcount. The CRO ran the hiring process for two enterprise AEs — both of whom he personally knew from prior tours of duty. Both hires closed inside six weeks (vs. the 4–5 month average for senior AE searches in this segment). He onboarded them onto the new playbook he'd authored rather than the legacy one, which meant they ramped to first meaningful deal in 10 weeks rather than the 5–6 months that had been the pattern.

In parallel, he rebuilt the weekly revenue operating rhythm: a Monday pipeline forum with CEO, CRO, and AEs; a Wednesday deal desk for any opportunity above $150k; a Friday forecast update that rolled into the board reporting. Previously, pipeline was discussed informally in the all-hands. Now it had its own operating cadence and its own documented accountabilities.

The 180-day result

  • Qualified pipeline: $2.1M → $8.9M (4.2×)
  • POC-to-paid conversion: 22% → 58%
  • Average ACV: $85k → $320k (3.8×)
  • Average sales cycle: 11 months → 6.5 months
  • New enterprise AEs hired and ramped: 2 (both signed first deal inside 14 weeks)
  • Forecast accuracy: ±38% → ±9% quarter over quarter
I'd been running sales because nobody else could. What I didn't know was that running sales was the thing that was keeping sales stuck. Having a fractional CRO of this caliber inside the company for two quarters didn't just fix our metrics — it rebuilt how we think about revenue. And because it was fractional, I could afford to hire someone three stages ahead of where we were.
Founder & CEO, Thikiq

What we take from this

Three lessons stand out. First: founder-led sales is a phase, not a strategy. Most founders hold on to it for two quarters too long, and the cost of that delay shows up as elongated cycles and compressed ACVs that are very hard to recover. Second: in complex enterprise motions — and manufacturing is among the most complex — the biggest leverage isn't in a better pitch. It's in requalifying the pipeline, resequencing the committee, and pulling the slowest workstream (usually IT) to the front of the cycle.

Third: the right fractional CRO at Series A isn't a stopgap on the way to a full-time hire. In many cases it is the hire for the next 18 months, and the operators on our bench who can run this playbook at this stage are often more experienced than anyone a retained search would surface on a 6-month timeline. Thikiq's CRO is still engaged today, running a 2-day-per-week cadence and coaching the two AEs he brought in. The founder has a real revenue function — and a real window to decide, from a position of strength, what he wants the long-term leadership structure to look like.

If you're reading this as a founder of an AI or deep-tech company selling into industrial, healthcare, public sector, or any other committee-heavy buyer — this pattern is almost certainly your pattern. The math of fractional works especially well here, and the number of senior CROs on our bench who've done exactly this motion is larger than it's ever been. Talk to us when you're ready.

Tagged:case studyCROmanufacturing AIenterprise salesthikiq
CX

Written by

CXOwork Editorial

Editorial

More articles