Real-World Scenarios & Access

How do I know if this enterprise deal is a real repeatable market or a one-off custom project that will trap me?

A starting point

If closing the deal requires you to build something only this customer needs, you're taking on a services project wearing a product costume, and it will eat the roadmap. Test repeatability by asking whether three other companies would buy the same thing without changes, and whether you can charge for it as a product rather than for your time. Take the occasional custom deal early for cash and learning, but cap it, keep the IP, and refuse to let one big customer's wishlist become your entire product plan.

Go deeper

Hand-picked from around the web, each with a note on why it earns your time.

3 resources 2 link-checked

Read

📄 Article
✓ Link checked Free Intermediate

Why we picked it When half your revenue comes from one customer's custom asks, the real risk is not the roadmap slipping, it is quietly becoming a dev shop wearing a software costume. This piece names that trap plainly and gives you a litmus test: if you added 100 customers tomorrow, would software handle them or would people? That is the question to hold up against every custom feature that big customer requests.

Service as a Software: The Startup Trap That Looks Like SaaS but Scales Like Consulting

From Startup Folsom by Rich Foreman

  • Scalability comes from repeatability, so treat manual, one-off custom work as temporary learning, not the business model.
  • Use a simple test on each ask: would this still be handled by the product if you had 100 customers, or only by human effort for this one?
  • Revenue concentrated in a single customer's bespoke needs can look like traction while quietly locking you into a services business.
Open startupfolsom.org →
📄 Article
✓ Link checked Free Intermediate

Why we picked it When the big customer's wishlist lands on your desk, this gives you a hard gate instead of a gut call: build the custom feature only if it is already on your 24-month roadmap, the contract is 1+ year and paid a lot (never for a pilot), the customer does not demand exclusivity, and you have met them yourself. Lemkin's reframe is the repeatability test in action: if one enterprise wants it and it fits your roadmap, at least nine more will, so it stops being custom and becomes product direction. His "do 1 to 2, not the 10 to 12 sales asks for" line is the discipline that keeps one account from eating the plan.

One Simple Rule on When to Build a Custom Feature

From SaaStr by Jason Lemkin 6 min read

  • Only build the custom ask if it is already on your roadmap AND a paid 1+ year contract, otherwise it is a services project in disguise.
  • If a big customer wants something on your roadmap, treat it as a paid preview of what nine other big customers will want, which is the definition of repeatable.
  • Sales will surface 10 to 12 custom features a year; you can only afford 1 to 2 that reshape timing, so the CEO, not sales, holds the gate.
Open saastr.com →
✍️ Essay
Free Intermediate

Why we picked it Before you say yes to the custom features nobody else wants, this essay makes you sit with the real risk: one account that pays a lot can quietly take over your roadmap and turn you into its in-house vendor. McAfee tells the story of a company that let one customer reach 80 percent of revenue, bent the product to that customer's demands, and collapsed when the customer's funding dried up. It is a starting point for weighing when a big customer's asks are worth it and when they are a trap dressed as a win.

The One Big Customer Trap

From Startup Patterns (Medium) by Sam McAfee

  • A single dominant customer can mask the fact that you do not yet have real product-market fit, so the revenue feels like validation when it is actually dependence.
  • Every custom request pulls capacity away from the product you meant to build; if you lose that one customer, you lose the revenue and the roadmap you traded away for it.
  • Keep some engineering capacity reserved for work that serves the whole market, not just your biggest account, and be wary of open-ended custom scopes.
Open medium.com →

People also ask

How do I land my first enterprise customer when nobody has heard of us? You don't win the first logo with a brand, you win it with a relationship and a sharply-scoped problem you can prove you solve. Mine your network, ... Intermediate 3 resources → How long is a B2B sales cycle and how do I not run out of money waiting? Enterprise cycles routinely run 3 to 9 months (longer with security and procurement), so assume every deal takes twice as long as the champion prom... Intermediate 3 resources → Who do I actually sell to inside a big company, and how do I find the decision-maker? Big companies have three roles you must map: the champion who feels the pain daily, the economic buyer who controls budget, and the blockers in sec... Intermediate 3 resources → They want a free pilot, should I do it? Free pilots attract tire-kickers and give you no signal on real buying intent, so default to a paid pilot, even a small refundable one, to force th... Intermediate 3 resources → Should I use design partners, and how do I structure the deal? Design partners are your cheat code to product-market fit: a handful of committed early customers who co-build with you in exchange for influence, ... Intermediate 3 resources → How do I survive procurement, legal, and security reviews as a tiny startup? Procurement, legal, and security exist to slow you down, so prepare the paperwork before they ask: a standard MSA, a security one-pager, a data-han... Advanced 3 resources →