3of 6
Prove demand before investing in product building
Building software is easier than ever, but that doesn't mean customers want what you build. Proving demand before investing heavily helps separate a promising product from a promising business.
Adapted by the EWOR Team from Florian Huber’s article (opens in a new tab)2 min read
A working product leaves demand unanswered
Building software has become easier, but reaching customers and establishing demand remain hard. Florian Huber, EWOR's co-founder and Chief Investment Officer, argues that faster development doesn't remove the need to establish who will use a product, why they would switch and whether the business can support its delivery.
Ship a testable slice
Define a specific customer, problem and action the product should help them complete. Build a narrow version that lets a customer try that action. Whether AI-assisted tools speed up this work depends on the product, the team and its quality requirements. Ensure the initial version is safe and reliable enough for its intended use. Speed is no reason to conceal limitations from prospective customers.
Before adding features, identify what the first version needs to reveal. A successful build confirms that the team can deliver a workflow. It doesn't show that customers will adopt it, pay for it or prefer it to their current approach.
Do the early customer work yourself
Make time for persistent outreach and hands-on work with your first customers. Speak to a defined group, record why people decline and observe what happens when interested customers try the product. Onboarding and support may need to be unusually hands-on at this stage because they expose friction that a dashboard cannot explain. Record which work was bespoke so you don't mistake it for a repeatable sales process.
Look for evidence across the full journey, from first contact to continued use or payment. Revise your customer profile when actual responses challenge your assumptions. A positive conversation, a trial and a paying customer are different signals; keep them separate. If the evidence is weak, refine the offer or investigate the problem before increasing acquisition spend.
Let evidence inform funding
Florian's approach postpones a major funding decision until customer traction makes the options clearer. Consider whether this fits your business: estimate the capital needed to deliver responsibly and reach the next meaningful customer test. Would funding accelerate a repeatable opportunity or extend an unproven approach? Some products need substantial capital much earlier.
Don't adopt revenue, timing or funding-round figures from a playbook as benchmarks without independent verification and context. Tool capabilities and market conditions also need reassessment. Choose your next customer test and financing step based on the business in front of you.





No comments yet.
Be the first to comment on this signal.