Nobody Says 'Simple' When the Invoice Arrives: Decoding the Real Price of 'Easy' Features
Ask a room full of executives to describe a 'simple' app and you'll get five different products, four timelines, and one budget that works for exactly none of them. Then the development contract gets signed, reality shows up, and suddenly the 'simple' project is six months late and 60% over. Sound familiar?
Here's the truth nobody puts in the pitch deck: 'simple' is not a specification. It's a vibe. And vibes don't compile.
The Word 'Simple' Is Doing Illegal Overtime
When a stakeholder says simple, they usually mean "simple for me, on my device, with my permissions, in my workflow." Your CFO means a clean spreadsheet view. Your sales lead means it works on her phone between client meetings. Your IT director means it plugs into the company's identity system without a security audit nightmare.
Each of those is a legitimate want. Stacked together, they're an enterprise platform wearing a startup's hoodie.
The problem isn't that stakeholders want too much. The problem is that nobody prices the wants until the change orders start rolling in. So let's price them now.
What 'Just Add SSO' Actually Costs
Single sign-on is the king of the 'shouldn't this be easy?' requests. It's just a login button, right?
Wrong. Real SSO means supporting SAML or OIDC, handling multiple identity providers (Okta for one client, Azure AD for another), debugging certificate rotations at 2 a.m., managing just-in-time provisioning, and writing fallback flows for the customer whose IT department configured everything weird in 2019.
A competent shop quotes SSO as a feature, not a line item. Realistic range for doing it right: $25,000–$60,000+, plus ongoing maintenance. If a quote says $3,000, either they're reusing a battle-tested component (fine, ask about it) or they're going to learn SAML on your dime (not fine).
Dashboards: Where 'Just Show the Data' Goes to Die
'Can we get a dashboard?' is the most expensive eight words in software.
A real dashboard means: data pipelines that stay current, aggregation logic that doesn't melt your database, role-based visibility so managers don't see each other's numbers, export functionality, date-range filtering, and mobile layouts that don't look like a crashed helicopter.
The chart itself? Maybe a day with a library like Recharts. Everything behind the chart? That's where the six figures live. When you hear 'dashboard,' mentally translate it to 'data infrastructure project with a pretty face.'
'It Should Work on Mobile' Is Not a Requirement
There are three things a stakeholder might mean by mobile-friendly:
- The site doesn't break on a phone. Cheap. Responsive CSS. Mostly fine.
- The experience is genuinely good on mobile. Redesign, touch targets, performance budgets, offline considerations. Real money.
- We need an app in the App Store. Congratulations, you just added Apple's review process, push notification infrastructure, a second codebase (or a cross-platform compromise), and 15–30% platform fees on any revenue.
The gap between #1 and #3 is easily $80,000–$250,000. If your contract says 'mobile responsive' and your brain says 'App Store,' you're about to have a very educational dispute.
Why Shops Lowball (and Why You Let Them)
Some dev shops pad quotes. Plenty more lowball to win the deal and plan to make it up on change orders — because they know 'simple' will metastasize. And you let it happen because the cheap quote felt like a win in the board meeting.
The fix isn't finding mind readers. It's scoping like an adult before signature day.
The Pre-Contract Honesty Checklist
Run every quote through this before you sign:
- Make every stakeholder write their own definition of 'simple' in one paragraph. Compare them. Disagreements found now cost nothing; disagreements found in month four cost everything.
- Ask what's explicitly excluded. A quote that doesn't list exclusions isn't cheap — it's unfinished.
- Demand the SSO/mobile/dashboard specifics in writing. 'Supports SAML 2.0 with Okta and Azure AD' is a requirement. 'SSO included' is a hostage situation.
- Ask how change requests are priced. Fixed hourly rate? Blended rate? 'We'll discuss it then' means you've already lost.
- Ask what happens when the quote is wrong. Every shop has a story about a project that blew up. The good ones will tell you theirs and explain the guardrails. The bad ones will promise it won't happen to you.
- Get a phased plan. Version 1 with real scope, version 2 with the wish list. If a shop won't phase the work, they're either hiding complexity or don't understand it yet.
Simple Is a Destination, Not a Starting Point
The best software teams make hard things look simple after they've built them — that's the craft. But the process of getting there is full of decisions, tradeoffs, and honest conversations about money.
If a shop tells you everything you want to hear for a price that seems too good, they're not agreeing with your vision. They're agreeing with your budget, and the vision can wait until the invoice does.
Scope it straight. Price it true. Then 'simple' might actually mean simple — or at least, you'll know exactly what it costs.
