From $500/Month to $300K Enterprise Deals: BackOps Playbook

A first-time founder with no VC network cold-emailed his way to a pre-seed round, then paused all sales to rebuild his platform for enterprise — and won two $300K deals against a household-name AI competitor. Sean McCarthy's journey from warehouse observer to Fortune 500 vendor is a masterclass in disciplined discovery and scrappy enterprise sales.

Key Facts

• Customer interviews before launch: 85 warehouse owners and admin staff interviewed before writing a line of code (Sean McCarthy)
• Enterprise deal size: Entry-point contracts of $200K–$300K, with seven-figure potential in year two (Sean McCarthy)
• SOP recording time: Eight minutes of screen recording replaces months of delayed SOP-writing (Sean McCarthy)
• Seed round speed: Six to seven term sheets closed in under two weeks after pitching (Sean McCarthy)
• Enterprise win rate on pointed use cases: Leading with a specific use case converts eight out of ten initial conversations (Sean McCarthy)

85 Warehouse Interviews: How Discovery Revealed the Real Pain Point

Sean McCarthy spent three to four months conducting 85 interviews with warehouse owners before quitting Amazon. The biggest problem wasn't shipping errors — it was admin employee churn caused by repetitive, monotonous back-office tasks like filing claims and reshipping packages.

When McCarthy started building his thesis at Amazon Shipping, he had a specific advantage: a role that required him to spend four days a week inside customer warehouses. That proximity let him watch what back-office workers actually did every day — and the pattern was unmistakable.

Initially, warehouse owners told him their biggest problem was churn. It derailed his fact-finding until he dug deeper. The churn wasn't about physical labor — it was admin staff leaving every six months because the work was unbearable. As McCarthy observed, 'eighty to eighty-five percent is the exact same thing every single day. You know, it's reshipping the package, it's filing the claim with the carrier.' Workers who stayed told him they liked the complex, novel problems — not the daily grind of repetitive claims.

He validated this across all 85 conversations, maintaining a spreadsheet of pain points and keeping his hypothesis honest. Even warehouses without churn problems were receptive to an efficiency pitch. This breadth of validation — not just one or two enthusiastic customers — gave investors enough confidence to fund a pre-product company.

"Eighty to eighty-five percent is the exact same thing every single day. You know, it's reshipping the package, it's filing the claim with the carrier, it's talking to multiple shipping vendors." — Sean McCarthy

"I had kept a spreadsheet of all of the people that I talked to, what pain points that we talked about." — Sean McCarthy

• Asked owners their #1 problem — churn was the answer, but the root cause was task repetition
• Watched employees spend 80–85% of their day on reshipping and claims filing
• Validated across 85 interviews, not just a handful of excited early adopters
• Kept a detailed spreadsheet of pain points to stay data-driven, not gut-driven

Why BackOps Paused All Sales to Rebuild for Enterprise

After acquiring early SMB customers at $20K–$40K ACV, BackOps hit a wall: the platform wasn't built for enterprise scale. In August 2025, McCarthy made the hard call to stop selling entirely and rebuild — adding multi-department support and a critical SOP recorder that cut onboarding from months to eight minutes.

The pull toward enterprise was unmistakable. Mid-market and early enterprise prospects kept saying the same thing: they didn't want ten AI vendors. They wanted one platform that could span operations, finance, customer service, and procurement. The existing Slack-based platform simply wasn't built for that.

McCarthy described the decision plainly: 'Candidly, the platform that we had set was just not built for that scale, and so we made the tough decision to stop selling and just rebuild the platform.' Coming from a sales background, stopping revenue generation was painful — but necessary.

The rebuild introduced two major upgrades. First, genuine enterprise-grade architecture that multiple business units could share. Second, the AI Process Center — a screen recorder built directly into the platform. Instead of asking customers to write SOPs (which nobody did), BackOps let them hit record and walk through the task they were already doing. Eight minutes of recording replaced what had previously caused months of deployment delays. Edge cases could be added with a two-minute supplemental recording, and finance or ops teams could attach their own processes to the same workflow without creating data silos.

"Nobody wants to sit there and write an SOP, or they have them but they're old. So what we did is we created an SOP recorder into the platform — it records the screen, obviously records the audio, and tracks all the metadata from the clicks." — Sean McCarthy

"We made the tough decision to stop selling and just rebuild the platform to make it an enterprise-grade AI platform." — Sean McCarthy

The Scrappy Enterprise Sales Playbook That Wins $300K Deals

BackOps wins Fortune 500 deals through hyper-personalized outreach to SVP Operations, leading with a pointed use case (not open-ended discovery), cross-threading across email, LinkedIn, and phone, and building the customer's board presentation for them — removing every internal barrier to sign-off.

McCarthy is explicit that he had to 'dogfight' his way into enterprise without a rolodex of C-suite contacts. The playbook starts with identifying the Senior VP of Operations — the ICP in 90% of cases — then exhausting every back-channel connection before going cold. When crafting warm intro messages, BackOps writes the copy for the referrer: 'We built this, we believe he has this problem, and this is what we've built to solve it.' This removes ambiguity and ensures the pitch lands correctly.

The biggest tactical shift was abandoning open-ended discovery. Asking 'what are your problems?' fails in enterprise because prospects don't know where to start. Instead, BackOps arrives with a specific, pre-built use case matched to the customer's vertical. McCarthy reports this approach converts eight out of ten initial conversations into a next meeting.

The final unlock is building the customer's internal business case for them. Enterprise buyers need to present to their ELT or board to get AI spend approved. BackOps builds that entire deck — complete with the customer's branding, ROI analysis, and use case data. As McCarthy put it: 'The deck that's being presented is hopefully the one or the majority of what we send to them.' This single tactic is what McCarthy credits most for beating a well-known large AI competitor on two simultaneous six-figure deals.

"Going to these customers as an AI company and saying, hey, we're going to make you more efficient. What are your problems? Works almost never." — Sean McCarthy

"We started doing was just building the use cases for the customer and giving them the entire use case, and the ROI analysis that they could present to their board with their branding." — Sean McCarthy

• Target SVP Operations first — the economic buyer 90% of the time
• Write the warm intro message for your referrer — don't make them do the work
• Lead with a pointed vertical use case, never open-ended 'what are your problems?'
• Send donuts, champagne, or tailored case studies when outreach stalls
• Build the customer's board deck for them — branding, ROI analysis, and all

Two Intentional Wow Moments: How BackOps Demos to Enterprise Buyers

BackOps deliberately engineers two wow moments into every demo: first, showing the AI autonomously chasing information across multiple systems in real time after a voice intake; second, showing those systems — QuickBooks, the ERP, the warehouse management system — automatically updated at resolution, with no human in the loop.

McCarthy's demo philosophy is straightforward: enterprise buyers need to see it to believe it, so BackOps demos on the first call rather than spending the full meeting on discovery. The team maintains multiple demo variants and selects based on what the prospect reveals in the opening minutes.

The first wow moment is the intake. A warehouse worker calls in from a loading bay to report a problem. The AI simultaneously sends a Slack message, makes a call, and logs into FedEx — all visible on screen, all at once. For buyers used to manual, siloed processes, watching autonomous multi-system action in real time is visceral.

The second wow moment is the resolution: systems updated automatically. 'Actually showing the systems being updated and the ticket being resolved across the board' closes the loop. McCarthy explains the dual purpose: 'They're worried about the customer experience, but they're also worried about the employee experience.' Each wow moment is designed to speak to one of those two audiences simultaneously, making the demo land across a mixed stakeholder room.

"Voice tends to get a better wow factor where it can be in a warehouse — calling in with a problem. And then very clearly, the AI will start to go chase the information. Send a Slack to Pablo, call Sean, log into FedEx, like all at the same time." — Sean McCarthy

"We try to always have at least two wow factors in the demos so that they can understand not only what this looks like in practice, but internally what it's going to look like as well for them." — Sean McCarthy

Structuring Pilots That Auto-Convert and Avoid Post-Pilot Purgatory

BackOps builds pilots directly into one-year contracts: a 30-day (60-day max) pilot auto-converts to a full commercial agreement if the customer doesn't opt out. All legal work is done upfront, eliminating the most common failure mode — signing a pilot, delivering results, then spending months renegotiating a commercial contract.

Pilots are dangerous for AI startups, McCarthy warns, because success doesn't guarantee conversion. Finishing a successful pilot and then re-entering the legal and procurement cycle can leave a vendor's product deployed but the deal in limbo for months. BackOps solves this by making the pilot a clause inside a pre-signed one-year agreement.

Before agreeing to any pilot, McCarthy applies a quick qualification filter. He asks prospects to rate the use case on a one-to-ten business criticality scale and asks how frequently the problem occurs. A rating below six or infrequent occurrence is a red flag — those pilots rarely convert because the problem doesn't hurt enough. A seven or eight that happens daily, combined with a clear statement that it's a budget priority, is the green light to proceed.

The closing language plays off the prospect's own words: 'You just told me this is a really high priority. So let's get this in flight for you.' That reframe shifts the dynamic from vendor pitching to founder helping — and it accelerates signature without pressure.

"We'll build the pilot into the one year contract. So it's a one year contract, but it will include a thirty day pilot that will auto convert to a one year. And that way, all of the legal documentation is pre-approved." — Sean McCarthy

"If they say, oh, this is like a two or a three, you shouldn't take that use case. It doesn't mean that much to them and your pilot is probably not going to go very well." — Sean McCarthy

SMB vs. Enterprise Sales Approach at BackOps