We were eleven people when the first enterprise contract showed up. A procurement team on the other end of a call, legal counsel we'd never met, and a dollar figure that would have covered our runway for the better part of a year.
We said yes fast. Too fast to understand what we were actually agreeing to.
This is the story of what that deal did to our culture — the changes that stuck, the ones we reversed, and why I'd tell any founder to treat enterprise revenue as a strategy decision, not a sales win.
The contract came with a security questionnaire. Forty-seven questions. Some we could answer honestly and well. Others exposed gaps we'd been comfortable ignoring: formal access reviews, audit trails, data residency commitments.
We spent six weeks closing those gaps before the contract was even signed. Six weeks where nothing shipped for any other customer.
The real cost wasn't the calendar time. It was the precedent. Once you build a compliance muscle, it wants to be used. Every feature conversation started to include a new question: "Does this create a compliance surface we'll need to document?" That question is healthy in moderation. But it crept into decisions where it had no business — internal tooling, experimental prototypes, weekend hacks. The mood shifted from "ship and learn" to "check and ship."
We kept the compliance rigor. We walked back the instinct to apply it everywhere. That took longer than building it in the first place.
Before the deal, on-call meant watching alerts and responding when things broke. After, it meant being available for a named account manager on the customer's side who expected a human response within thirty minutes, including weekends.
We didn't have an account manager. We didn't have a support rotation built for that cadence. So engineers became the support layer. Two of our strongest builders started spending Friday afternoons on status calls instead of writing code.
The strain showed in standups. People were tired in a new way — not from hard problems, but from context-switching between building and performing. One engineer described it as "wearing a costume." That phrase stuck with me.
We eventually hired a dedicated support person and restructured on-call into tiers. But for three months, we ran our best people through a job they didn't sign up for. Some told me later that was the closest they came to leaving.
The lesson: support expectations in enterprise deals aren't a line item. They're a staffing plan. Budget for the people before you sign for the revenue.
When one customer accounts for a third of your revenue, every product decision bends toward them. Not because anyone mandates it. Because the gravity is just there, pulling on every conversation.
We started hearing a phrase in planning meetings: "Well, [the enterprise customer] needs this by Q3." That framing turned a request into a constraint. Features for smaller customers got pushed — not canceled, but "not canceled" and "not built" look the same from the outside.
The harder effect was psychological. We became afraid of the contract not renewing. That fear made us reactive. We said yes to scope changes we should have pushed back on. We absorbed costs we should have negotiated. We treated the relationship like something fragile, when the customer had chosen us because we solved a real problem for them. They had switching costs too.
It took almost a year to rebalance the portfolio enough that losing any single customer wouldn't be existential. During that year, the fear was a constant background hum.
Three durable changes came out of that deal:
Formal access controls. Before the deal, permissions were loose. After, they were explicit and audited. This made us better for every customer, not just the enterprise one.
Structured incident communication. The enterprise customer demanded clear, written updates during outages. We adopted that across the board. It reduced confusion and built trust with smaller accounts too.
Honest capacity planning. We stopped pretending engineers had infinite hours. Support costs became visible in how we planned sprints.
What we reversed: the instinct to gate every experiment behind a compliance review. The habit of deferring small-customer requests. The belief that "important customer" and "loud customer" are the same thing.
The deal worked out. The customer renewed. We grew past the concentration risk. But I wouldn't describe the experience as a straightforward win.
Enterprise revenue reshapes your team's daily experience — who gets paged, what gets prioritized, how meetings feel. Those shifts happen whether you plan for them or not. The difference is whether you choose them deliberately or discover them in retrospect.
If you're a founder staring at your first big contract: don't just model the revenue. Model the org chart, the on-call rotation, and the roadmap six months after signing. If you like what you see, sign. If you don't, negotiate until you do — or walk away.
The deal is never just the deal. It's the company you become on the other side of it.
Be the first to comment.
0 comments
Loading comments...