Your About Page Tells Your Story, Not Your Customer's Job

The number that doesn't add up

Hannah sells a daily planner and journal system — one SKU on Amazon, the full line on her Shopify storefront. Her Storefront About tile gets real traffic and real dwell time; people click through, read for the better part of a minute, and leave without touching a single category tile or the buy button. Whatever the About page is doing, it isn't moving anyone toward the product.

She rewrote it twice this year already — tightened the sentences, added a photo of her actual desk, cut it from four paragraphs to two. Dwell time held. Click-through to product still sat under 4%.

Why a better-written story doesn't fix it

The instinct here is to treat this as a writing problem: make the founder story punchier, more vulnerable, more "authentic." Hannah did that. It read better. It didn't convert better, because craft was never the gap.

Her About page tells a true, well-written story about why she started the company — a chaotic year, a system she built for herself, a decision to sell it. What it never does is connect that story to why someone else, mid-scroll on a Tuesday, should buy this planner. She's answering "why does Hannah care about this" when the buyer standing on that page is really asking "does this fix the thing that's actually wrong with my week."

That gap between the founder's reason and the customer's reason shows up as engagement without action almost every time.

The diagnosis lens: job-to-be-done, not backstory

The IDEA framework's Empathetic pillar asks whether the copy understands what the customer is actually going through, not just what the brand went through. Hannah's About page scores fine on Authentic — nobody doubts she's a real founder with a real reason. It fails on Empathetic, because "organization" is the word she reaches for, and it's too abstract to be a job anyone hires a product to do.

"Organization" isn't a felt problem. Nobody wakes up frustrated about organization in the abstract. They wake up having missed a habit they promised themselves they'd keep — the gym session, the journaling streak, the meal prep — for the third week running, and they're looking for something that makes the next attempt stick. That's a job. "Organization" is a category label for a shelf of products that could all plausibly claim it.

The working session

Hannah brought the coach her About page copy and the storefront click-through numbers, with one question: is this a writing problem or something else.

The coach ran build_avatar_stage, starting at S1 to pull the actual vocabulary her customers use, then moving into S2 — the job-map stage, which asks what the customer is actually hiring the product to do in their life, distinct from the feature list or the category name.

What the coach said: "Your copy says 'stay organized.' Nobody hires a planner to be organized in general — they hire it to stop the specific thing where they start a habit, feel good for eight days, and then quietly let it slip. That's the job. Your About page needs to name that moment, not the word 'organization.'"

S2 surfaced the real job cleanly once the coach reframed it: Hannah's customers weren't buying a system, they were buying a way to not have this be the year they gave up again. The founder story wasn't wrong — it just needed to end somewhere the customer could see themselves, instead of ending on Hannah's own resolution.

Rebuilding the About page around the real job

The rewrite kept Hannah's actual founding story — that part was true and worth keeping — but changed where it landed. Instead of closing on "so I built this for myself," it closed on naming the slipping-habit moment directly, in language pulled from S1: the specific frustration of starting strong and quietly stopping, stated in words her own customers already use to describe it. The founder story became the proof that she understood the job, not the entire point of the page.

This same gap — a founder's true story that never quite lands on the buyer's actual reason — shows up constantly once you know to look for it. A bike-mount brand's Brand Story spoke fluently to sport cyclists while the real buyer was a nervous urban commuter, a different flavor of the same mismatch: story built for the wrong audience rather than the wrong job. It isn't only About pages, either: featured reviews chosen around durability missed the guilt-free-relief job parents were actually buying for, and reviews highlighted for eco-material praise missed that real buyers write about grip and smell instead — proof and story both drift toward what the brand assumes matters instead of what the customer's actual job requires.

If Hannah ever wants founder-on-camera content to reinforce the rewritten About page, the job-map work here becomes the spine of that script, the same way it does for a founder with no idea what to say on camera — trigger and job work don't just fix a page once, they become reusable direction for every piece of founder content downstream.

For founders who suspect their own listing has this kind of "true but wrong angle" gap somewhere, the free trust gap diagnostic is a faster first read than a full storefront audit — six questions, no account needed, and it flags which pillar is actually weak before you touch a word.

What to measure after

Watch click-through from the About tile to any product or category tile specifically — not general storefront traffic, and not dwell time, which was never the problem. Give it two to three weeks of steady traffic before judging. If click-through moves while dwell time holds roughly flat, the job-map rewrite is doing its work: people are still reading the same amount, but now they're reading toward a decision instead of just reading. If click-through doesn't move, the issue likely isn't the About page at all — it's worth running get_funnel_coverage to check whether a different storefront touchpoint is where the real leak is happening.

The one next action

Reread your own About page and cross out every sentence that's about you — your reason, your journey, your decision. What's left is what's actually landing on the customer. If almost nothing survives that cut, the job-map work above is where to start.