A major enterprise prospect is offering our SaaS startup a one hundred and fifty thousand dollar contract, but they require a custom on-premise installation. We are strictly cloud-only. Do I take the cash?

Question

Tyler Smith · Accepted Answer

This is a crucial moment for your SaaS startup, and the answer is clear: Decline this contract immediately. Accepting it is a short-term cash injection that will permanently derail your engineering roadmap.

The Risks of Custom On-Premise Deals

When a cloud-native software company builds an on-premise version for a single, heavy client, that client effectively hijacks your engineering team. This seemingly lucrative deal comes with significant, hidden costs and strategic risks:

• Engineering Drain: You will spend the next two years writing custom patches, managing legacy infrastructure, and delaying core product updates.
• Opportunity Cost: This single client will consume a disproportionate amount of your engineering capacity, taking focus away from ninety-nine percent of your market. The math simply does not work; $150,000 is often less than the cost of one dedicated engineer for two years.
• Scalability Blockade: Your core value proposition as a SaaS company is rooted in multi-tenancy and scalability. Deviating from this for a custom deployment compromises your ability to scale efficiently. To protect your future growth, you must preserve your scalability.

How to Decline Gracefully

The key is to decline the offer without burning the relationship. Frame your refusal around your core architectural principles and your commitment to service quality.

You can tell the prospect:

• "Our core architecture is built entirely on multi-tenant cloud infrastructure."
• "This design guarantees daily security patches and zero-downtime updates for all our clients."
• "Because we do not support on-premise environments, we cannot deliver the level of service you deserve for a custom deployment."
• "We would be happy to help you configure our cloud solution to meet your security requirements, but we cannot build a custom on-premise deployment."

If they refuse to accept a cloud-based solution, you must be prepared to walk away.

Protect Your Strategic Focus

Use this experience as a catalyst to reinforce your strategic alignment. In your next weekly meeting, double down on your true target market. If you are using a tool like the V/TO™ to track your [ideal customer profile](/qa/setting-10-year-target-with-rapid-tech-changes), update your sales criteria. This will filter out any prospect requesting custom deployments before they even reach a sales demo. Keeping your sales team aligned on this filter prevents these distracting deals from getting to your desk in the first place, allowing you to focus on your [vision and strategy](/qa/proving-structural-ceiling-vs-founder-fatigue).

This proactive approach helps avoid situations where [leadership team members subtly fail to execute](/qa/stop-passive-resistance-after-planning) or where your [weekly leadership meetings](/qa/fixing-ineffective-weekly-leadership-meetings) devolve into debating reactive issues rather than strategic problem-solving.

Related questions

• [How do I set a 10-year target when rapid technology shifts make the future of our industry impossible to predict?](/qa/setting-10-year-target-with-rapid-tech-changes)
• [My co-founder wants a $100M 10-year target, but I think $25M is the realistic ceiling. How do we resolve this gap without destroying our alignment?](/qa/resolving-co-founder-gap-on-10-year-target)
• [My leadership team agrees to decisions in our quarterly offsites, but then they subtly fail to execute or actively sabotage the plan when they get back to their departments. How do I stop this passive resistance?](/qa/stop-passive-resistance-after-planning)
• [Our weekly leadership meetings are turning into status updates instead of strategic problem solving. How do I force my team to shift from reporting to actually resolving issues?](/qa/stop-weekly-leadership-meetings-devolving-into-status-reports)
• [I have realized our current business model has hit a hard ceiling, but my board thinks I am just suffering from founder fatigue. How do I prove this is a structural strategic necessity?](/qa/proving-structural-ceiling-vs-founder-fatigue)