Why we stopped building custom enterprise features until prospects signed a paid pilot

by•

year our team spent six weeks building a custom single sign-on integration because a large prospect promised that prospect would sign an annual contract once it was ready. Soon as we shipped the feature prospect’s internal priorities changed and prospect went completely silent.

After that experience we made a rule: we never write custom code for a prospect without a signed paid pilot agreement upfront. If a feature is truly critical to prospect’s workflow prospect will gladly pay a setup fee or commit to a refundable deposit to prioritize it on our roadmap.

Since we adopted this policy we have avoided three dead-end builds. Closed four paid pilots that turned into full annual contracts.

Prospect’s willingness to pay upfront is the reliable filter, for separating real product needs from casual feature requests. How do you validate enterprise feature requests before committing engineering time to prospect?

1 view

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.