Landing Your First Whale

You can go from idea to deployed product in a weekend. AI writes the code, Vercel deploys it, Stripe takes the first payment. A task that took a team of engineers three months now fits between Friday evening and Sunday night.

Your first users are individuals. Then small teams sign up. You start seeing the same company email domain appearing across multiple accounts—people from the same organisation finding you independently. This is bottom-up adoption, and it's the first signal that enterprise interest is forming.

Then the questions change. "Can we get an invoice instead of paying by credit card?" "Can one person manage billing for our whole team?" "Do you have a security policy we can review?" The first enterprise signals are mundane, and you've probably already seen some of them.

The gap between a product people love and one their procurement team can sign off on is real, but it's smaller than it looks. Even before enterprise is on your radar, you should be thinking about the basics: least privilege access, whether data is encrypted in transit, whether you could hand someone a written security policy if they asked. These aren't enterprise requirements. They're good practice at any stage. If you've been building with those foundations in place, the enterprise conversation starts from a position of strength rather than scrambling to catch up.

Founders who close that gap are setting themselves up to tap a different tier of revenue. Enterprise deals average $100K–$500K in annual contract value, with net dollar retention rates between 120% and 140%. A single enterprise customer can outweigh hundreds of self-serve signups.

The Product Was the Easy Part

Slack launched in February 2014 with per-seat pricing: free for small teams, paid per user when you outgrew the free tier. Their S-1 filing describes what happened next as "organizational virality"—one team would adopt Slack, colleagues in other departments would notice, and usage spread organically across the company. By the time IT and procurement got involved, Slack was already embedded in daily workflows.

The problem was that none of this organic adoption came with the infrastructure enterprises needed to formalise it. IT wanted centralised provisioning, security wanted audit trails, and finance wanted consolidated billing across divisions. Slack had built a product enterprises were already using. Now they needed to build the wrapper that let enterprises pay for it properly.

Three years after launch, Slack shipped Enterprise Grid: centralised administration, SSO, compliance controls, and consolidated billing across departments. Capital One and IBM were among the launch customers. Their S-1 reported 575 customers paying more than $100K a year, with IBM running 360,000 seats. That enterprise packaging turned a chat tool into a $27.7 billion acquisition.

Dropbox, GitHub, and Zoom followed a similar pattern. Usage spread organically, executives noticed, and when those companies added enterprise infrastructure, large customers formalised what was already happening. None of them rewrote the core product. They added the compliance and billing layer that procurement teams require.

Some companies reject this path and do well. Basecamp built a $25–30 million-a-year business with fifty employees by refusing enterprise complexity: flat-rate pricing, no sales team. David Heinemeier Hansson called per-seat pricing "a tax on growth." Mailchimp skipped enterprise sales too, and Intuit bought them for $12 billion. But if an enterprise buyer has found your product and wants to write a six-figure cheque, the question is whether you're ready when they show up.

The Compliance Conversation

Enterprise compliance sounds intimidating, but the requirements are well-documented and the path is incremental. The conversation usually starts with a security questionnaire—a standard form asking how you handle data, who has access, and what controls you have in place. Knowing what to expect makes it easier to prepare.

SSO comes first. Enterprise organisations manage employee access through centralised identity providers like Okta and Azure AD. SAML or OIDC support lets employees log in through systems their security team trusts, and it unblocks the rest of the compliance conversation. Libraries like WorkOS and Auth0 have solved the hard parts. You're looking at days of integration work.

SOC 2 comes next, and it's more accessible than its reputation. Platforms like Vanta and Drata have turned what used to be a six-figure consulting engagement into a guided, automated process. A SOC 2 Type I report is a point-in-time assessment. An auditor confirms your security controls are designed well. Most mid-market security reviews accept Type I, and you can complete it in weeks. SOC 2 Type II evaluates whether those controls worked over a sustained period, six to twelve months. Larger enterprises require it, but by the time you need Type II, Type I revenue is helping fund the process.

Beyond SOC 2, enterprise buyers expect encryption at rest and in transit as a baseline, plus documented security policies and data processing agreements for EU customers. If you're selling internationally, ISO 27001 may come up. You build each requirement on the last. The security practices you implement for SOC 2 form the foundation for what follows.

Compliance is incremental. Each certification opens new market segments that help justify the investment in the next. Slack built its compliance portfolio over years—SOC 2 first, then Enterprise Key Management and HIPAA support in 2019, FedRAMP Moderate in 2020, and GovSlack with FedRAMP High in 2022.

Pricing That Doesn't Break at Scale

When Flat-Rate Falls Apart

Your $29/month plan works for individual users. Then a 500-person company asks about pricing, and you realise the plan wasn't designed for this conversation.

Charge $29 per seat and the enterprise buyer sees a $174,000 annual commitment, more than they've validated in their pilot. Offer a flat $29/month regardless of team size and you've left six figures on the table while absorbing the infrastructure costs of five hundred users. Neither option works because neither accounts for the reality that more users means more load on your systems, more support, more storage—costs that scale with headcount even if your pricing doesn't.

This is where volume discounts become attractive. Offering a lower per-seat price at higher quantities gives enterprise buyers a reason to consolidate and commit, while keeping your revenue closer to the actual cost of serving them. Volume pricing sets a single per-unit rate based on quantity—the more seats, the lower the price per seat. Graduated pricing takes a different approach, charging each tier at its own rate so the first fifty seats cost more than the next hundred. Most SaaS products selling to enterprises do better with graduated pricing because it rewards growth without punishing early commitment, and it keeps your revenue aligned with the infrastructure costs each tier of usage creates.

Slack solved a different pricing problem with "fair billing," charging only for users active in the last twenty-eight days. IBM was considering a 360,000-seat rollout, and paying for thousands of inactive accounts would have killed the deal. With fair billing, IBM could roll out across the company and pay only for seats people used.

Designing for Land-and-Expand

Enterprise deals start small: a team of eight on your free tier, a department of forty on a paid plan, then a VP asking procurement to formalise what three hundred employees are using. Consolidation is a priority for large organisations where possible—five teams paying full price on separate accounts costs more than one negotiated contract. The trade-off is dead seats: bulk deals inevitably include people who rarely log in, which is why models like Slack's fair billing work well at this stage. Your pricing needs to accommodate that growth, from a free signup to a formal enterprise contract, without forcing a migration along the way.

Mailchimp proved this. After introducing a generous free tier, their user base jumped from 85,000 to 450,000 in a year. Most free users didn't upgrade right away, but they planted Mailchimp inside organisations. A marketing team that needed email automation at scale upgraded the tool they knew rather than evaluating competitors. Remove the entry barrier and your existing users sell the product for you.

You also compound revenue from customers you've already landed. Slack's net dollar retention of 143% came from more teams within each organisation adopting the product and upgrading to higher tiers, year after year. Price for the pilot and design for the expansion.

Start with Pricing

Volume discounts, graduated tiers, per-seat proration, annual contracts—you can set all of this up today with existing tooling. Enterprise pricing on your page tells buyers the door is open, and when one of them bites, you're talking numbers rather than scrambling to figure out what to charge. SSO, security audits, certifications are a longer road. They don't need to be finished before your pricing says you're serious.

Enterprise billing introduces two wrinkles that catch founders off guard. A 500-person company buying your product splits into two relationships: the person who signs the contract and the people who use it. The CTO or finance team manages billing; 500 employees need access. Your billing system needs to separate the payment relationship from the access grants, or you end up building multi-tenant billing logic from scratch. Salable's owner/grantee model handles this by design. The owner holds the subscription, grantees get access through groups under that owner, and you control the mapping.

The second wrinkle is feature access. Enterprises expect different capabilities at different price points, and your pricing will evolve as you learn what customers need. If you've hardcoded checks like if (plan === 'enterprise') throughout your codebase, changing a plan means redeploying code. Salable's entitlement system lets you define named capabilities and assign them to plans in a dashboard. Your code checks for can_export_data or seats_over_100. You adjust which plans grant those capabilities in Salable without touching your codebase.

You configure all of this in a dashboard, and your engineering team stays on the product and compliance.

That investment matters most during growth. Zoom went from 344 customers paying more than $100K to 1,999 in two years. If you're adding enterprise customers that fast, your billing infrastructure needs to handle the volume.

From First Whale to Enterprise Motion

Your first enterprise customer teaches you what your market requires: the security questionnaire, the procurement sticking points. That knowledge turns one deal into a repeatable process. And the revenue from that first deal, $100K or more in annual contract value, funds the compliance and billing infrastructure that makes the second deal faster to close.

Slack built the infrastructure to land Capital One. That same infrastructure later supported IBM. Slack used the same playbook to reach 1,183 customers paying more than $100K a year, accounting for 49% of their revenue. Each deal funded the infrastructure for the next.

If enterprise is your path—if someone's asking for invoices, team billing, or a security policy—the gap between your product and their procurement process is smaller than it looks. The playbook is documented, each step funds the next, and you don't have to build the billing layer yourself.

You've built something enterprises want. The rest is execution.

---

Salable handles tiered pricing and per-seat billing with entitlement enforcement so you can focus engineering time on your product and compliance.