Alcove Studio · audience reference
The ecommerce *competence map*.
Where a product founder sits across her ecommerce learning journey, what she says at each stage, and what moves her forward.
Read this before writing anything audience-facing — newsletter, blog, IG, sales page, teardown. It names no service on purpose, so it survives an offer change.
The fastest read. Describing a symptom puts her at second. Requesting a specific solution puts her at third. Asking what the symptom even means puts her at first. Naming architecture unprompted puts her at fourth.
She never narrates her own base. Nobody says "I'm at conscious incompetence about product pages."
Transfer renewal, not acquisition
Vocabulary hand her the word
Recognition a mirror, not information
She starts at first and runs counter-clockwise. She is at fourth base on her own product the entire way round.
First base — ignorance
She does not know the deficit exists, and may deny the skill is useful.
The tell. She asks what a thing is rather than what to do about it. Comparison questions between platforms and tools, with no symptom attached.
What she's asking
- Store & platform — Is Shopify better than Squarespace? Which theme should I buy? Why is my site slow?
- Product pages — Do I need better photos? How long should a description be?
- Email — Klaviyo or Mailchimp? Does anyone even open these? How often should I send?
- Product data — How do I edit more than one product at a time?
- AI & discovery — Is AI going to kill my business? Should I use ChatGPT for captions?
What she says
- "I'm not really aware of what Shopify offers."
- "Can you help flush out what that vision of that retail world would look like online?"
- "I didn't know" — about basic page terminology, mid-diagnostic
- "The website's fine, it's just marketing I need."
- "I should probably post more."
What she believes
Her traffic problem is a traffic problem. If more people came, more would buy. The site is a container rather than a lever.
What she buys
Almost nothing diagnostic. She buys when a date forces her hand — a launch, a market, a season. Peers she trusts are her only referral route.
What repels her
Content assuming she has already identified a fix. Terms she does not have. Being told she is doing it wrong by someone she does not know yet.
What reaches her
Diagnostic tools with a verdict. Teardowns of stores in her category. Founder story. Anything where she recognises herself before she recognises a problem.
Second base — awareness
She recognises the deficit and the value of the skill. She lacks the words.
The tell. She asks you to name it. Second base sounds like an invitation to diagnose rather than a description of confusion. When someone hands you their page and asks what you see, they are standing on second.
What she's asking
- Store & platform — Do I need this app? How should my collections be organised? Why do people leave at checkout?
- Product pages — Why do people look and not buy? What goes above the fold on mobile?
- Email — What is a welcome flow? How many campaigns should I send this season? Should I have an abandoned cart?
- Product data — How do I bulk edit without breaking everything?
- AI & discovery — People find brands through AI now. What does that mean for me?
What she says
- "What's the biggest thing that screams at you?"
- "I definitely think our site can do a better job at that."
- "It's completely two different experiences" — in-store versus online
- "It deserves a bigger place to shine."
- "We haven't created new content in quite a while."
- "Something's off and I can't put my finger on it."
What she believes
There is a specific fixable thing and she lacks language for it. This is when she starts asking peers who they used.
What she buys
Diagnosis. Price sensitivity runs low relative to her uncertainty, because she is buying relief from not-knowing.
What repels her
Being sold the fix before the diagnosis. A five-figure engagement when she cannot yet articulate what it would solve.
What reaches her
Teardowns, diagnostic frameworks, symptom-to-cause content. Naming things she has felt and never labelled.
Third base — learning
She knows what to do. Doing it takes concentration.
The tell. She requests a specific solution rather than describing a symptom. She has a shortlist and is comparing.
What she's asking
- Store & platform — Which sections are reusable? Is my app stack costing me speed? How do I brief a developer?
- Product pages — Where do reviews go? How do I map objections? What is my variant UX doing?
- Email — Segmentation logic, flow branching, sunset policies, campaign versus flow revenue split
- Product data — Variant structure, tagging taxonomy, collection automation
- AI & discovery — How do I structure content so a model can read it?
What she says
- "Our assortment is just way too large on our site."
- "We're looking for someone to revamp the site after the migration."
- "There's a balance we're trying to strike."
- "The product pages are the weak link."
- "I need someone who actually knows this platform."
What she believes
She has named it and is now evaluating who to hire. She is weighing three options including a friend's recommendation.
What she buys
The fix. Projects, intensives, retainers. She shops on proof of competence rather than price justification.
What repels her
Being educated on something she already knows. Third base bounces off first-base content faster than anyone.
What reaches her
Case studies with numbers. Frameworks. Process transparency. Anything answering can this person actually do it.
Fourth base — mastery
The skill is second nature. She can do it while doing something else, and can teach it.
The tell. She names tools, architecture, and gaps without prompting. She has a roadmap and knows what is missing from it.
What she's asking
- Store & platform — Metaobjects, custom Liquid, expansion stores, B2B channel, agentic commerce settings
- Product pages — Metafield-driven dynamic content, templates by category, structured data for AI retrieval
- Email — Deliverability and inbox placement, predictive analytics, dynamic blocks by purchase behaviour
- Product data — Metaobject architecture, marketplace syndication, warehouse and ERP sync
- AI & discovery — GEO as an operating standard, agentic checkout readiness
What she says
- "We have a frontier of content that's on our wish list."
- "Landing pages were one of the known gaps in our conversion optimisation."
- "I wish we were in a place where we could upgrade to the newer underlying architecture."
- "We run our own flows. I want someone to push the thinking."
- "I want a partner rather than an executor."
What she believes
She is competent and stretched. She buys leverage and challenge rather than instruction.
What she buys
Ongoing partnership. Systems she owns. Access to judgment.
What repels her
Onboarding built for someone less capable. Explanation she did not ask for.
What reaches her
Observations, opinions, industry reads. The things you would say to a peer.
The asymmetry that defines this customer
She is fourth base at her product and first or second base at ecommerce.
She has spent five years learning her category. She knows her supplier's failure modes, her margin down to the cent, why the second formulation beat the first. She can tell good from great in her own aisle at a glance. That competence is unconscious now. It runs while she does something else.
Then she opens her store admin and becomes a beginner again.
The gap between those two selves is where the work lives. It is also why she cannot name her problem. She has no vocabulary for the thing she's bad at, because she has never been bad at anything that mattered to her business before.
Consequence one
Never write to her as a beginner. She is a master standing in an unfamiliar room. Beginner-register copy insults the fourth-base woman and she leaves.
Consequence two
Her budget has nothing to do with her base. A woman who cannot describe what a metafield does may well have $20k for a rebuild. Assume competence about money and ignorance about tooling.
What moves her between bases
Identifying the base is the easy half. The transitions are what content has to perform.
| Move | Mechanism | What does it |
|---|---|---|
| First → second | Recognition | She has to see a version of her own situation from the outside. Teardowns do this and explainers do not. She is not short of information, she is short of a mirror. |
| Second → third | Vocabulary | She has to be handed the word for the thing she is feeling. Once she can say it, she can shop for it. Glossary and definition content does this work, and it is usually the most underrated format in a library. |
| Third → fourth | Transfer | She stops needing you for the doing and starts wanting you for the thinking. A renewal motion rather than an acquisition one. |
Where the money sits. Second-to-third converts. First-to-second fills the pipeline six months out. There is direct evidence of the first move landing: a founder walked through a structured page audit said "I didn't know, but I learned" — first base to second inside twenty minutes, with nothing sold.
How to use it
Before writing
Name the base you are writing to and the base you are moving her toward. A piece doing both is doing too much.
When auditing a library
Add a base column. Third-base content sits behind a second-base entry point rather than serving as the front door.
When a season creates urgency
The calendar delivers her to second base without any awareness work. That window is for vocabulary, not for recognition.
Ratio to aim for
Most of what gets published should be first-to-second and second-to-third. Third-base content is for people already reading.
Where the library stands
Audited 2026-08-15. Everything live is third base. The newsletter positioning, the Facet Forward page, the Reality Check workbook and the services page all require her to already believe product pages are the lever. The quiz is the only second-base asset and it is in the footer. Shop Talk is a second-base offer described like a third-base one.
The intent is to catch her at second and walk her to third — second-base assets become the front door. Sequenced entry points, not hedged half-aware copy.
Field notes
Public forums are the wrong place to source her language. Shopify Community threads and ecommerce subreddits are dominated by dropshippers and week-old stores. That is a different buyer at a different base with different money. An established founder does not post there. She asks two peers privately. Her language lives in call recordings and nowhere else.
She does not narrate her base. The base is legible from what she asks for, what she assumes you already know, and whether she is describing a symptom or requesting a solution.
On the ✔ and ✳ marks. ✔ is verbatim from a recorded client or prospect call. ✳ is inferred and worth replacing as real language surfaces. Speaker attribution is deliberately not published here — it lives in the studio's own copy of this reference.
On the model. Four Stages of Competence. Martin M. Broadwell published the four-stage sequence in 1969, describing teaching skill. Noel Burch developed it at Gordon Training International in the 1970s as "Four Stages for Learning Any New Skill." Often misattributed to Maslow, where it does not appear. Little formal validation exists, so treat it as a working heuristic rather than a measured instrument, and footnote it if anything built on it gets published.