How We Earned Our First Enterprise Contract

The Cold Email

Our first enterprise conversation started with an email I almost didn't send. I'd been reaching out to mid-market companies for weeks with minimal traction. Enterprise felt aspirational—we were a twelve-person startup with a product that had been live for four months.

But a friend who'd worked at Salesforce told me something that stuck: "Enterprise buyers don't care how old your company is. They care how well you solve their specific problem." So I wrote a highly specific email to the VP of Operations at a logistics company with 3,000 employees. I'd noticed they used nine different SaaS tools for internal communication and task management (their job postings mentioned all of them). My pitch: "What if your team could interact with all nine tools from one interface?"

She replied in 40 minutes.

Due Diligence

What followed was three months of the most thorough evaluation I've ever experienced. Their IT team wanted architecture documentation. Their legal team wanted to review our terms of service and data processing agreements. Their security team wanted a SOC 2 report we didn't have yet and a detailed explanation of our encryption model.

Every question was reasonable. Every request was an opportunity to demonstrate that we took this seriously. We didn't have a SOC 2, but we had our encryption architecture documented and could explain every security decision we'd made. Marcus (our CTO) did a 90-minute technical walkthrough with their security team that apparently went very well—the security lead later told me it was "the most transparent vendor conversation we've had."

The timeline looked like this:

• Month 1: Initial contact, discovery calls, demo
• Month 2: Technical architecture review, security questionnaire (47 questions)
• Month 3: Legal review, DPA negotiation, penetration testing
• Month 4: Pilot setup, user onboarding, success criteria definition
• Month 5: Pilot execution, weekly check-ins, integration requests
• Month 6: Pilot results review, contract negotiation
• Month 7: Signed. Champagne. Sleep.

Seven months felt like forever. In enterprise sales, it was fast.

Security Review

The security review was the most stressful part. Their team ran penetration tests against our staging environment. They reviewed our infrastructure configuration. They asked about our incident response plan, our data retention policies, and our approach to subprocessor management.

We passed. Not because we had everything perfect—we didn't. We had gaps in our monitoring and our incident response documentation was thin. But we were honest about the gaps and had concrete plans to address them. The security lead told me later that vendors who claim to have zero gaps are either lying or haven't looked hard enough. Honesty about limitations built more trust than a perfect scorecard would have.

The Pilot

After due diligence, they wanted a pilot. Fair enough. We set up a 30-day trial with their operations team—about 40 people. The success criteria were specific: reduce time spent switching between tools by at least 25%, and achieve a user satisfaction score of 4.0 or higher.

We hit both targets in the first two weeks. Tool-switching time dropped 43% based on their internal measurements. User satisfaction scored 4.3. The operations team started asking for integrations we hadn't built yet—they wanted Billix connected to their logistics management system, their fleet tracking software, their warehouse management platform.

We built two of those integrations during the pilot. Jack's team pulled some long nights, but seeing enterprise users enthusiastically request features was the kind of validation no amount of market research can provide.

Lessons Learned

Seven months from first email to signed contract. Here's what I'd tell other startups pursuing enterprise:

• Don't wait until you feel "ready." We weren't ready when we sent that first email. We got ready during the process. The due diligence forced us to mature faster than we would have otherwise.
• Invest in security documentation early. Not for compliance—for conversation. Being able to articulate your security model clearly and confidently is the fastest way to build trust with enterprise buyers.
• Be honest about gaps. Enterprise buyers know no product is perfect. They're evaluating whether you'll be a trustworthy partner, not whether you're flawless.
• The pilot is your real pitch. All the slide decks and demos in the world matter less than 40 people actually using your product and asking for more.

That first contract changed our trajectory. Not because of the revenue—though that was nice—but because it proved our product worked at a scale and in a context we hadn't fully tested before. It gave us the confidence to pursue enterprise aggressively, and it gave prospective customers a reference they could call.