BackOps won large deals against a major competitor by providing customers with a complete use case and ROI analysis deck, branded for them, to present internally. This significantly reduced the lift for their champions, embedding BackOps' solution into the internal narrative.
BackOps faced a major bottleneck where customers delayed implementation for months because they disliked writing Standard Operating Procedures (SOPs). They solved this by building a screen and audio recorder into their platform, allowing users to create an SOP simply by performing the task once.
Despite having traction, BackOps stopped selling to rebuild its platform. This tough decision was driven by mid-market and enterprise customers demanding a single, scalable AI platform for multiple business units, not a siloed tool for one department.
BackOps built its initial product as a Slackbot. This was an effective MVP strategy because their target 3PL customers already managed dozens of client communications in separate Slack channels. The bot integrated directly into their primary, existing workflow, reducing friction for adoption.
Founder Sean McCarthy assumed the core problem was workflow inefficiency. Customer discovery revealed the true pain was high employee churn among admins doing repetitive tasks. This shifted the focus from a simple efficiency tool to a solution for a major operational and HR issue.
In the AI era, enterprises reject the fragmented, best-of-breed SaaS model. They prefer a single AI platform that handles entire workflows across departments. This avoids data silos and streamlines compliance, making end-to-end automation the key value proposition.
To prevent getting stuck after a successful pilot, BackOps includes the pilot phase within a full one-year contract. The 30-day pilot automatically converts to the annual term, getting all legal and procurement approvals done upfront and de-risking the transition to a commercial agreement.
BackOps found that generic efficiency pitches fail with enterprises. Their breakthrough came from leading with a hyper-specific, high-value use case like "we solve temperature breaches on grocery trucks." This targeted approach resonates immediately and secured meetings 8 out of 10 times.
To avoid wasting time on low-impact pilots, BackOps asks prospects to rate a potential use case's importance from 1 (irrelevant) to 10 (business-critical). They only proceed with use cases that score a 7 or higher, ensuring genuine business impact and stakeholder buy-in.
A first-time, non-YC founder raised a pre-seed round through cold emails before building a product. Key factors were his deep domain expertise from Amazon, a spreadsheet detailing 85 customer pain point interviews, and VCs validating his thesis by visiting customer sites.