Jobs to be done · 26 jobs · 4 stages

The job on your plate this week, answered.

Twenty-six specific jobs ecommerce teams hire eCommerce Insights to do, grouped the way the work actually flows: diagnose where your products stand, fix the gaps, monitor for regressions, prove the result. Every page shows the honest manual method first, then the faster one.





Why eCommerce Insights publishes jobs-to-be-done pages

Category overviews help at the start of research. But most weeks, an ecommerce team has a specific task with a deadline — "I need to know whether ChatGPT recommends our best-seller before Friday's trading meeting" — and no amount of category education finishes it. A jobs-to-be-done page is the answer to that task, in that voice. The framing comes from Clayton Christensen's jobs-to-be-done research: customers hire products to finish jobs, so the documentation should be organized around the jobs.

Each page follows the same contract. The job, stated the way buyers state it. The manual method, described honestly — several of these jobs can be done with a private browser window and a spreadsheet, and the pages say so. Then the eCommerce Insights method as numbered steps, what a good result looks like with numbers cited or marked illustrative, and the related jobs in the next stage. For the concepts behind the jobs, see the guides library and the glossary. For the free tools the Diagnose jobs use, see the tools library. For what the paid product adds, see the product and pricing.

Ask AI about this library

Have your favorite AI engine match a job to what you need to finish this week.

Frequently asked questions

What is a jobs-to-be-done page?
A jobs-to-be-done page answers one specific task someone actually has on their plate this week — not a feature pitch, not a category overview. Each page names the job in the buyer's words, walks through the honest manual method, then the eCommerce Insights method step by step, and defines what a good result looks like. The framework comes from Clayton Christensen's work on why customers hire products for specific jobs.
How are the jobs organized?
By journey stage. Diagnose: find out where your products stand in AI answers. Fix: ship the schema, content, and crawler changes that close the gaps. Monitor: keep watch so regressions surface in days, not quarters. Prove: turn the data into numbers leadership and clients accept. Most teams enter at Diagnose and work right.
How is this different from the guides library?
Guides explain concepts — what AEO is, how schema for AI search works, how the Agentic Commerce Protocol fits together. JTBD pages assume you already know the category and need to finish a concrete task: check a product, fix a robots.txt, build the board slide. Each JTBD page links the guide that covers the underlying concept and the free tool that does the work.
Which job should I start with?
If you have never run any AI visibility check, start with Check if my product appears in ChatGPT — it takes about 90 seconds with the free checker. If you already know there is a problem, run Audit my Shopify catalog for AI readiness. If leadership is asking why the line item exists, go straight to Prove AI search ROI to leadership.
Do the jobs require a paid eCommerce Insights plan?
No. Every Diagnose job can be started with a free tool — the AEO Grader, the Agentic Readiness Grader, the Shopify SKU Visibility Grader, or the ChatGPT product visibility checker. The paid plans (Starter $99/mo, Growth $349/mo, Agency & Enterprise custom) add full-catalog coverage, weekly or daily refresh, and the fix-push workflow.

Don't read about the job. Finish it.

Every job links the free tool or product feature that does the work.