We spent 6 months building for enterprise. Nobody bought it.
We thought we were ready.
Bigger deals. Fewer customers. Better margins. That was the dream.
So we built enterprise features. SSO. Advanced permissions. Audit logs. A whole new pricing tier starting at $2,000/month.
We spent 6 months. Three engineers. One dedicated product manager. Endless meetings about "enterprise readiness."
We launched the tier. Sent emails to our biggest users. Ran LinkedIn ads targeting "Head of IT" and "VP of Infrastructure."
Zero.
Not one signup.
Not even a demo request from an enterprise account.
The real cost
Let me put numbers on it.
Cost category | Amount |
|---|---|
Engineering time (3 people × 6 months) | $180,000 |
Product management | $60,000 |
Marketing (ads, content, emails) | $25,000 |
Opportunity cost (features we didn't build) | ~$150,000 |
Total | $415,000 |
That's what we spent to learn we were wrong.
What we thought we knew
We assumed enterprise customers wanted the same things as our small business users, just more of it. More security. More control. More features.
We never talked to them. We read blog posts. We looked at competitor pricing pages. We guessed.
Here's what we missed:
Procurement cycles. Enterprise deals take 6-12 months. We had 30-day sales cycles. We weren't built for that.
Security reviews. We needed SOC2. We didn't have it. Customers asked. We said "coming soon." They moved on.
Implementation. Enterprise buyers don't sign up and start using it. They need onboarding, training, account managers. We had none of that.
Compliance. Data residency. GDPR. HIPAA. We had nothing. Every deal died in legal review.
We weren't an enterprise company. We were a small SaaS with a big ego.
What the data said
We went back and looked at our own analytics.
Feature | Build time | Customer requests | Actual usage after 3 months |
|---|---|---|---|
SSO | 8 weeks | 4 requests | Used by 2 accounts (both internal) |
Audit logs | 6 weeks | 2 requests | 0 accounts |
Enterprise tier | 10 weeks | 0 requests | 0 signups |
API rate limits | 4 weeks | 47 requests | Used by 89% of power users |
The features nobody asked for took 24 weeks to build. The feature 47 people asked for took 4 weeks. We built the wrong things because we were chasing a dream, not data.
What we learned
1. Customers don't ask for enterprise features until they're ready to pay enterprise prices.
The 4 requests for SSO came from users on our $89/month plan. They weren't enterprise buyers. They just thought SSO sounded cool.
2. The features you imagine are always wrong.
Every enterprise feature we built was based on assumptions. Every assumption was wrong. We should have talked to 10 real enterprise buyers before writing a line of code. We didn't.
3. Your current customers are your roadmap.
The feature 47 people asked for? API rate limits. Not sexy. Not enterprise. But it solved a real problem for our power users. We built it in 4 weeks. Adoption was 89%.
What we did instead
We killed the enterprise tier. Dropped the price back down. Spent the next 3 months fixing the things our actual users were complaining about.
Fix | Time spent | Impact |
|---|---|---|
API rate limits | 4 weeks | 89% adoption among power users |
Faster load times | 3 weeks | 22% drop in support tickets |
Simpler onboarding | 2 weeks | 34% increase in activation rate |
Churn dropped from 8.2% to 5.7%. Referrals went up 41%. Revenue grew 18% without a single enterprise deal.
What this means for you
If you're thinking about building enterprise features, ask yourself three questions:
1. Have you talked to 10 enterprise buyers who are not already your customers?
If not, stop. You're guessing.
2. Do you have the compliance, security, and procurement infrastructure to support enterprise deals?
If not, you're not enterprise. You're just expensive.
3. What does your data say about what your current users actually need?
We ignored the 47 requests for API rate limits. We built SSO instead. That was stupid.
The honest truth
We wanted to be an enterprise company because it sounded impressive. Big logos. Big checks. Big validation.
But we weren't ready. And instead of admitting that, we wasted $415,000 learning a lesson we could have learned in a week of customer calls.
Now we have a rule: no enterprise features until someone from an enterprise pays us first. Not asks. Pays.
What I'm curious about
Have you ever built something for a customer you didn't have? How much did it cost you? What did you learn?
Imed Radhouani
Founder & CTO – Rankfender
Evidence over ego. Retention over requests.
Replies
the API rate limits vs SSO table is the part that will stick with people longest. 47 requests versus 4, and you built the one with 4. the painful thing about that pattern is the boring requests rarely come with urgency attached. nobody is writing "we will churn if you don't add API rate limits" but that is exactly what is happening quietly in the background. the rule of paying before building is the right instinct but curious how you handle the version of this problem that shows up earlier, when you have ten feature requests and no clear signal on which one is the API rate limits versus which one is the SSO. how do you weight volume versus who is asking?
The "loud vs. quiet users" insight I'm seeing this exact pattern in real estate SMBs. Vocal users ask for fancy features. Silent ones are drowning in slow response times, but they just leave quietly.
How did you know API limits was the right friction to fix, vs. just another guess?
Thats a lot of money in the beginning...
TYQ: What I'm curious about
Have you ever built something for a customer you didn't have? How much did it cost you? What did you learn?
I did and I am doing it now as we speak - One should extremely rightly placed and the right time to have a customer ready even before the product is in atleast prototype stage - IMO that is extremely rate and perhaps happens to serial entrepreneurs who are have a high 'build' brandname with trust and everything that goes with it - I have neither but I think I can identify gaps in current product-scape and come up with solutions. That leaves me at the same place, where most of the find themselves - Hunting for the first sticky customer!!
Wow - thankyou so much for the honest writeup. We've been tossing and turning on building enterprise pricing (and functionality) for Sharpread and having heard your story, I feel reassured we made the right choice in delaying it till after launch and after some key metrics are hit. It was going to be weeks of Dev work but those big numbers and the 'Enterprise' allure had us going back and forth for some time on if that was the right call or not.
the SSO request from $89/month users is such a tell. saw the same thing fundraising side, founders adding 'institutional features' bcz one angel asked, then no fund actually wants them. one paid pilot beats 50 'this looks cool' calls every time. how did you decide which power user complaints to ignore tho, you can't fix all 47?
This hit close to home. We built a feature for 3 months because a single enterprise prospect kept asking for it in every call. Turns out they were using the calls to shape their internal RFP, not to actually buy from us. The feedback felt real because it was consistent same words, every week. The lesson I keep relearning: frequency of a request is not the same as willingness to pay. The smaller, scrappier customers who just wanted to get something done ended up being far better signal.
Are you going to try again?
This resonates, but in the opposite direction. We set out to build you x you i for SMBs, but once we started doing demos, we quickly identified a need for an enterprise option. We aren't ready to launch to enterprise yet, but it's made its way into our roadmap!
Would you do anything different if you started from scratch today? Like earlier market fit testing before building anything?
Cosmic
The pattern is painfully common: enterprise features get built, but enterprise buyers never show up because the sales motion wasn't designed for them. The product is almost never the reason; it's procurement cycles, internal champions, and legal that kill it. The fastest fix is usually going back to a segment that can say yes in a week, not a quarter.