A business does not need a pretend flaw to sound human. It already has real boundaries: the projects it suits, the conditions it needs and the work it does not do. Explaining those boundaries can make the rest of the offer more credible.

01

Choose a meaningful boundary

An agency might specialise in projects with an established product. A software plan might support one workflow particularly well. A service might require the customer to supply approved content before production starts.

These are useful facts because they help a buyer judge fit. A line such as “we care too much” performs honesty without providing information. A clear scope limit gives the customer something they can use.

02

Connect the trade-off to the design

Suppose a hypothetical implementation service offers a fixed launch package. It can explain that custom integrations are scoped separately so the standard package has a predictable process. The limitation and the benefit belong together.

Do not use a minor admission to distract from a material problem. If the product cannot meet the customer's requirement, say that plainly. A charming explanation will not repair a mismatch discovered after purchase.

03

Keep the evidence proportional

My notes include familiar advertising stories about brands presenting a weakness alongside a strength. The transferable idea is honest comparison. It does not establish that admitting any flaw will automatically increase trust or sales.

Review your most common pre-sale misunderstandings. Which one could be prevented by a sentence on the page? Add that sentence where the expectation forms. Good positioning makes the right sale easier and the wrong sale less likely.

Share this article

Continue the thread

Field Notes

Free still needs a clear explanation.

Field Notes

Offer the next useful thing.

Field Notes

Explain the cost of inaction without manufacturing fear.