What can you remove without making the offer worse?

More features and service aren’t always better. Find out what customers genuinely value, then test whether removing or redesigning lower-value work can improve both the offer and its economics.

Build & Validate
DistributionVenture Finance

By the EWOR Team2 min read

Adding features can increase delivery effort without giving customers a stronger reason to choose you. Instead, look for ways to improve the offer while preserving the outcome customers value and removing work that costs more than it contributes.

Test both sides of the change: the value delivered to the customer and the cost of delivering it.

Identify work customers do not value

Start by examining what existing solutions require customers and suppliers to do. Look beyond feature lists to onboarding, customisation, reporting, training and ongoing support. Which activities contribute to the outcome customers want, and which are simply inherited conventions?

Consider a hypothetical scheduling product for small field-service teams. The founder suspects that elaborate analytics and bespoke configuration matter less than helping dispatchers quickly identify unassigned jobs. This is worth investigating through customer conversations and workflow evidence, but it is not yet a reason to remove reporting.

Some features that appear excessive may serve important users, approval processes or exceptional situations. Understand whose needs would go unmet before concluding that an existing solution is overbuilt.

Check how each change affects the customer

Sketch a specific change to the offer. The scheduling product could use standard setup templates instead of bespoke configuration, simplify rarely used reports and invest more in a clear view of scheduling exceptions.

For each change, write down two expected outcomes. What should improve or remain unchanged for the customer, and which delivery activities should become cheaper or unnecessary? If neither outcome is specific, the redesign may be cosmetic.

Check whether you are simply shifting work to the buyer. Self-service onboarding might reduce internal effort while leaving customers confused for hours. Removing a report could save engineering time but force dispatchers to maintain a separate spreadsheet.

Compare the customer's total effort with the startup's ongoing delivery and support costs, not just the number of features.

Measure where the improvement actually happens

Be clear about where you expect the improvement to appear. Would a clearer package make evaluation easier? Could standardisation reduce implementation time? Might a more useful daily workflow encourage continued use? Could the buyer justify the purchase more easily within an existing budget?

Test the specific mechanism you expect to improve. Evidence of one benefit does not establish the others.

Run a limited pilot or reversible packaging test with a suitable customer segment. Track customer outcomes, onboarding effort, support requests and remaining workarounds. Compare the results with the assumptions behind the redesign.

Lower delivery costs are not an improvement if the essential customer outcome suffers. Better outcomes do not guarantee better economics if they cost more to deliver. Keep both sides visible and adjust the offer accordingly. A successful small pilot justifies the next step, not a claim of a durable competitive advantage.

Get the next signal before everyone else.

Frameworks and contrarian theses for outlier founders, straight to your inbox. No fluff, no recycled advice, weekly.

The EWOR Signals newsletter