2 builders who never spoke to each other

Attach a number to every promise you make

Counts and percentages do work that adjectives cannot, so give each element of the offer its own quantified outcome rather than naming the feature alone. Put real figures on the problem too, since a vague problem does not feel urgent enough to act on. Money and hours are the two units buyers weigh, so convert into them wherever you can.

The method

1. 01

   Write the benefits as counts and percentages rather than adjectives, and list the supported cases in full so a reader can find their own situation on the page.

2. 02

   Attach real figures and concrete detail to the problem description, since a vague problem does not feel urgent enough to act on.

3. 03

   Give every component in the inclusion list its own quantified outcome instead of naming the feature alone.

4. 04

   Describe the transformation rather than the feature list, and tie it to money or hours saved, because those are the two things buyers weigh.

What it returned

• 70%

  The post promises files 70% smaller and support for 69 or more sites, then lists them by category from AWS and Tailwind to PyTorch and PostgreSQL

• $3.50

  The sample bullets pair an AI ad builder with a $3.50 per dollar return, an image generator with 271% more clicks than hand-built Canva creative, and a dashboard with the ability to concentrate spend on the best channels.

Sources

• A 5-day email sequence that converts: A step-by-step guideJustin Welsh · justinwelsh.me · Day 1: Agitate The Problem · 2024-08-31
• llm.codes: Make Apple Docs AI-Readable | Peter SteinbergerPeter Steinberger · steipete.me · Enter llm.codes · 2025-06-14