Translation and notes
A readable adaptation of the article's core ideas, with the original source clearly credited.
Asking how to make more money matters, but it often produces incremental improvements. A more useful question is what would make the company more powerful for customers over time. This is a free adaptation of the source, not a complete translation; the examples and exercises here are independent applications. Power does not mean controlling customers. It means creating more value, keeping a useful relationship with them, and building an advantage that compounds.
Start by naming the constraint. Is the company only a technical component while someone else owns the customer relationship? Does money or data flow around the product instead of through it? Consider three paths: let other products build on yours, take on more of the customer's difficult work, or move closer to the point where the final customer outcome is decided. None is automatically correct. Each needs a concrete customer benefit and a bounded test.
Unexpected usage can reveal a stronger business. When users apply a product to a peripheral job, record who does it, what outcome they get, and what they would pay to improve. A side feature may become a standard, a marketplace, or the real product, but do not redesign the company overnight. Test the behavior first. Customer choice is the constraint that keeps an ambitious strategy honest.
Customer timing is strategic too. Smaller, fast-moving customers can install a product now, decide on quality, and grow with it. Usage-based pricing can align their growth with yours. APIs, extensibility, documentation, or open source can build trust and distribution, but only when they make the customer's world better. Review one question each week: where did the company become more useful and structurally stronger, and what customer behavior proves it?
Selected advice from the article
- Map one constraint, one structural option, and the evidence that would show customer benefit.
- Test onboarding with five fast-deciding customers and record time to decision and first value.
- Choose one unexpected use case and interview users before building around it.
- Require a customer-result metric and a stopping condition for each power-building experiment.
Operating takeaways
- Name the structural constraint: customer relationship, money, data, distribution, or an intermediary.
- Pair every ambitious move with a visible customer benefit and a bounded test.
- Treat unexpected usage as evidence of demand before treating it as misuse.
- Prefer customers who decide quickly and can grow with the product.
- Use APIs, extensibility, or open source when they improve trust, distribution, or customer outcomes.
- Review weekly which customer behavior demonstrates increasing company power.
Quick feedback
What did this article make clearer for you?
Choose a reaction or share a question or experience. Useful responses can shape future notes.
This is a free adaptation, not a word-for-word republication of the original article.