What print shops actually "hire" you for — Jobs-to-be-Done for Print-Flow-360
Why this matters first
At pre-PMF, the single most expensive mistake you can make is building (and pitching) a better tool when what Maria is actually trying to buy is a different Monday morning. Features and personas tell you who and what; Jobs-to-be-Done tells you why she switches — the struggling moment that makes her finally rip out the Wix site + the email-and-spreadsheet quoting routine she’s tolerated for three years. That “why” is the spine of everything else in this GTM series: it dictates the words on your homepage, the first three milestones in onboarding, and which of your known gaps (preflight, partial fulfillment, tracking) actually block deals versus which are nice-to-have. Get the job right and your messaging writes itself; get it wrong and you’ll out-feature a competitor on a job nobody’s hiring for.
TL;DR — Key Recommendations
- Lead with one primary job, not a feature list: “When a customer asks me for a price or wants to place an order, I want them to self-serve online so I can stop spending my evenings quoting and emailing files back and forth.” Everything on the homepage should ladder up to that. (This is the job behind the GTM_01 category claim “online storefront + design studio for print shops.”)
- Name the four jobs you keep hearing and pick your wedge. Our candidate set: (1) Stop being my customers’ unpaid designer, (2) Let customers order + pay online without me touching every job, (3) Look as legit as the franchise down the road, (4) Stop losing nights/weekends to manual quoting. Job #4 (quoting) is your sharpest push wedge — it’s painful, frequent, and measurable in hours.
- Run 10–12 switch interviews before you write another line of copy. A widely-cited Moesta rule of thumb: ~10 well-chosen switch interviews surface 3–5 buying patterns that cover the large majority of a market. Interview recent switchers (shops that adopted — or seriously trialed — ANY web-to-print or online-ordering tool in the last 6 months), not prospects describing hypotheticals.
- Engineer the Four Forces deliberately. Your push (quoting hell, after-hours file emails) and pull (branded storefront, self-serve design studio) are strong. Your job is to crush anxiety — “will I lose my personal touch / will it look cheap / can I move my catalog / will print-ready files actually be right” — because anxiety + habit are why shops stay on Wix even while hating it. Preflight/CMYK maturity is an anxiety item, not a feature item; treat it as such.
- Write desired-outcome statements and score them (ODI). Use
Opportunity = Importance + max(Importance − Satisfaction, 0)— the formula intentionally double-weights importance (it isImportance + the gap, NOT an average). Underserved (high importance, low satisfaction) outcomes around quoting accuracy/speed, hands-off orders, and “files print correctly the first time” are where your roadmap dollars go. - Convert jobs → onboarding milestones. Time-to-value = the moment Maria sees the job done once: first product priced correctly, first storefront link she can paste to a customer, first online order received without an email. Make those the three “aha” milestones in CONVERSION_FUNNEL.
- Use the job map to find the gaps that lose deals. Map the universal 8 steps against your product and you’ll see your weakest steps are Confirm (preflight/proof) and Conclude (fulfillment/tracking) — exactly the PLATFORM_GAP items. JTBD tells you which to fix first by tying each to a job force: Confirm (anxiety that blocks the sale) before Conclude (post-sale satisfaction).
1. The core idea: people hire products to make progress in a struggling circumstance
Theory (done right). JTBD says customers don’t “buy products,” they hire a product to make progress in a specific circumstance. The unit of analysis is the job — the progress someone is trying to make — not the customer (persona) and not the product (features). Clayton Christensen’s canonical framing: people don’t fundamentally want a quarter-inch drill, they want a quarter-inch hole — and, more precisely, the shelf on the wall and the satisfaction of having done it themselves. The job is stable over time and across solutions; the products that get hired change. The famous “milkshake” study (Christensen / Moesta) showed the same milkshake was hired for two completely different jobs — a boring solo morning commute vs. a treat for a child after an errand — and each job implied a different product.
Two consequences that matter for you:
- The competition is anything that does the job today, including non-consumption and duct-tape. Maria’s current “solution stack” for online ordering is: a Wix/Shopify site that takes a deposit + a phone call + a chain of emails with PDFs + a spreadsheet to track quotes. That is your competitor, not just another web-to-print SaaS.
- The struggling moment is the trigger. Nobody switches because a feature exists. They switch because something broke their tolerance for the status quo on a specific day.
Applied to Print-Flow-360 — the struggling moment. Picture Maria’s actual trigger events (these become your interview gold and your ad hooks):
- It’s 9:40pm Sunday. A B2B client emailed at 4pm Saturday asking to reorder 5,000 flyers “same as last time but change the date.” Maria is digging through her email to find last year’s file and her spreadsheet to find last year’s price. She’s annoyed she’s even doing this on a Sunday.
- A walk-in wanted “business cards like these” and handed Maria a photo. Maria spent 35 minutes in Canva for free making the artwork, the customer said “let me think about it,” and never came back.
- A bride asked for a quote on invitations. Maria typed out a custom email with sizes/stocks/prices, the bride replied with 4 follow-up questions, and three days later went with the franchise that “had a website where I could just see prices.”
Each of these is a circumstance + struggle + desired progress. That’s the hire.
2. Functional vs. emotional vs. social jobs (and why you must serve all three)
Theory. Every job has three layers:
- Functional — the practical task to accomplish (“produce a correct price for a custom print order”).
- Emotional — how the person wants to feel doing it (“not stressed,” “in control,” “competent”).
- Social — how they want to be perceived by others (“a real, professional business,” “not a hobbyist with a Gmail address”).
Most B2B vendors only sell the functional layer and wonder why “objectively better” loses. For a non-technical owner-operator, the emotional and social layers often decide the purchase.
Applied to Print-Flow-360. Take the job “Look as legit online as the franchise down the road.”
| Layer | What Maria is really after | Product proof Print-Flow-360 must show |
|---|---|---|
| Functional | A storefront where customers can browse products, see prices, design, and order/pay | Branded storefront + CMS blocks + price calculator + design studio + Stripe/Razorpay |
| Emotional | Pride, relief, “I finally look like I have my act together”; no embarrassment when sending the link | Polished default theme that looks premium out-of-box (UX-first, no “built on a template” feel) |
| Social | To be seen by B2B buyers and the community as a real company, peer to the franchise, worthy of corporate accounts | Custom domain, branded emails, B2B portal with pay-on-account → signals “we serve serious clients” |
Worked example — the quoting job, three layers:
Functional: turn a customer request into an accurate, fast price. Emotional: stop dreading the inbox; stop feeling like a doormat who works for free at 10pm. Social: look responsive and professional (“they got back to me in 2 minutes with exact pricing” beats “I’m still waiting on a quote”).
Your messaging fails if it only says “automated price calculator” (functional). It wins when it says “Customers get instant, accurate prices themselves — you get your evenings back, and you look faster than the big guys.” (all three).
3. JTBD vs. features vs. personas — keep them in their lanes
Theory. These are complementary, not competing — but confusing them is the classic trap.
| Lens | Question it answers | Failure mode if you lead with it |
|---|---|---|
| Persona (GTM_01: “Maria”) | Who is buying, demographics, context | Builds empathy but predicts little about when/why they buy; “35-year-old shop owner” doesn’t tell you the trigger |
| Job | What progress are they trying to make, in what circumstance | — (this is your strategic anchor) |
| Feature | How a specific solution does the job | Feature wars; you build things no job demands |
The relationship: persona tells you whom to recruit for interviews; the job tells you the strategy and messaging; features are how you deliver the job better than the current solution. GTM_01’s “Maria” persona is the recruiting filter; this doc supplies the job she’s hiring for.
Applied — a quick translation table for your team:
| Feature you built | Job it actually serves | Don’t say… | Say… |
|---|---|---|---|
| Price calculator | ”Stop losing nights to manual quoting" | "Configurable tiered pricing engine" | "Customers see exact prices instantly; you stop quoting by hand” |
| Design studio (Fabric.js) | “Stop being my customers’ unpaid designer" | "Browser-based vector editor" | "Customers create print-ready artwork themselves” |
| B2B portal | ”Win/keep corporate accounts without manual reorders" | "Account hierarchy with approval workflows" | "Your corporate clients reorder and pay on account, on their own” |
| CMS blocks + themes | ”Look as legit as the franchise" | "Block-based page builder" | "A storefront that looks like you hired an agency” |
4. The lineage: Christensen, Moesta, Ulwick — two complementary schools
Theory. Two streams both fly the JTBD flag and you should use both:
- Demand-side / “switch” school — Clayton Christensen & Bob Moesta (Re-Wired Group). Focus: why people switch. Tools: the switch interview (timeline of a real purchase) and the Four Forces of Progress. Best for: discovering the job, the trigger, the buying decision, and the messaging. Qualitative, ~10 interviews.
- Supply-side / quantitative — Tony Ulwick, Outcome-Driven Innovation (Strategyn). Focus: what outcomes define success on the job, scored at scale. Tools: the job map (8 universal steps), desired-outcome statements, and the opportunity algorithm. Best for: prioritizing roadmap and finding under/over-served outcomes. Quantitative survey, run after the qual.
How to sequence them for Print-Flow-360 (do it in this order):
- Switch interviews (Moesta) → discover the real job + forces + the words shops use. (§5–§7)
- Job map (Ulwick) → lay out the whole job to find gaps. (§9)
- Desired-outcome statements + opportunity survey (Ulwick) → score what to build next. (§10)
Don’t skip straight to the ODI survey — you’ll write outcome statements for the wrong job. And don’t stop at interviews — you’ll prioritize roadmap by anecdote.
5. The Four Forces of Progress — engineer them, don’t just observe them
Theory. Whether someone switches is a tug-of-war between four forces (Moesta):
- Push (of the situation): frustration with the current way. Drives toward change.
- Pull (of the new solution): attraction of the new thing, the vision of a better life. Drives toward change.
- Anxiety (of the new solution): fear/uncertainty about the new thing — “will it work, will I lose something.” Resists change.
- Habit (of the present): inertia, comfort, sunk cost in the current way. Resists change.
The rule: switching happens only when Push + Pull > Anxiety + Habit. Most vendors over-invest in Pull (more features) and ignore Anxiety + Habit — which is why “better” products lose to “good enough” incumbents. Your job is to amplify push, sharpen pull, and systematically dismantle anxiety and habit.
Applied to Print-Flow-360 — the forces map for “Maria switches from Wix+spreadsheet to Print-Flow-360”:
| Force | What it sounds like for Maria | Your move |
|---|---|---|
| Push (toward you) | “I’m quoting at 10pm again.” “I made art for free and they ghosted.” “My site can’t take a real print order — it’s just a brochure.” | Amplify in marketing: name the Sunday-night quote, the unpaid-designer moment. Mirror her words. |
| Pull (toward you) | “Customers could just order and pay themselves.” “I’d look like a real company.” “I’d get my weekends back.” | Sharpen: demo the storefront with HER products, not a generic demo. Show the link she can text a customer today. |
| Anxiety (away from you) | “Will the files actually print right?” “Will I have to rebuild my whole catalog?” “Will it look cheap/templated?” “Is my data safe?” “Will I lose the personal relationship customers expect?” | Crush: done-for-you catalog import/setup; preflight/proof story; premium default theme; “we set up your first 5 products with you” onboarding. This is where preflight/CMYK maturity earns its keep — as anxiety reduction. |
| Habit (away from you) | “Email-and-spreadsheet works, sorta.” “I already paid for Wix.” “I know my way around my current mess.” | Reduce: migration help, run-in-parallel period, import existing customers, keep her phone number prominent so it feels additive not replacement. |
Worked numeric intuition (illustrative ratings, not a measured stat). If you rate each force 1–10 from an interview: Push 8 + Pull 8 = 16 vs Anxiety 9 + Habit 6 = 15 → barely switches, and only if a salesperson removes anxiety. Knock anxiety from 9→5 (with a “we import your catalog + guarantee print-ready files” promise) and you get 16 vs 11 → easy switch. Your highest-leverage GTM work is the anxiety number, not the pull number. This directly informs which gaps (PLATFORM_GAP_ASSESSMENT) to close first.
6. The switch interview — the technique that finds your real job
Theory. The switch interview reconstructs the timeline of one real purchase decision, in forensic detail, from “first thought” to “now.” You are a documentary detective, not a focus-group moderator. Rules:
- Interview people who recently switched (bought/adopted within ~60–90 days) so memory is fresh.
- Anchor everything to a specific instance and date (“walk me back to the day you first thought about this”) — never hypotheticals (“would you like a feature that…”).
- Find the first thought, the passive looking, the active looking, the deciding event, the first use, and ongoing. Map the Four Forces along the way.
- Chase energy and emotion — when their voice changes, dig. Ask “what else?” and tolerate silence.
- ~10–12 interviews typically reveal 3–5 patterns covering most of the market (Moesta’s rule of thumb).
Who to recruit for Print-Flow-360 (recruiting screen): owner/decision-maker at an independent print/sign shop, $200K–$5M revenue, 1–30 staff, who adopted any online-ordering / web-to-print / new storefront / online quoting tool in the last 6 months (including DesignNBuy, Printavo, OrderDesk, a Shopify print plugin, or even seriously trialed one and didn’t switch — losses are gold for GTM_03). Use the GTM_01 ICP as the filter.
Reusable switch-interview guide (copy/paste):
PRINT-FLOW-360 — JTBD SWITCH INTERVIEW GUIDE (45–60 min, record with consent)
GOAL: reconstruct the timeline of ONE real decision to adopt (or seriously
consider) an online-ordering / web-to-print / quoting tool. Find the job,
the trigger, and the Four Forces. Use THEIR words.
WARM-UP (5 min)
- "Tell me about your shop — what you print, who buys, how many of you there are."
- "Walk me through a normal day. When does it get stressful?"
THE FIRST THOUGHT — find the trigger (10 min)
- "Think back to the FIRST time you thought 'there has to be a better way to
take orders / quote / sell online.' What was happening that day?"
- "What were you doing right before that thought? Time of day? Who was involved?"
- "What was the last straw — was there a specific order or customer?"
[Listen for PUSH. Note the exact scene and emotion.]
PASSIVE LOOKING (5 min)
- "After that, what did you do? Google? Ask a peer? A Facebook group?"
- "What were you secretly hoping to find?" [Listen for PULL / desired progress]
- "What made you stop and go back to how you'd been doing it?" [HABIT]
ACTIVE LOOKING (10 min)
- "When did you start seriously looking? What changed?"
- "What did you try / demo / sign up for? In what order?"
- "What worried you about each one?" [ANXIETY — list every fear, verbatim]
- "Who else weighed in? Spouse, staff, an accountant, a key customer?"
- "What did you compare it against — including just keeping email + spreadsheets?"
THE DECISION (10 min)
- "What finally made you decide on ___ (or decide to wait)?"
- "What was the deciding moment — the thing that tipped it?"
- "If you didn't switch, what stopped you?" [ANXIETY + HABIT that beat you]
- "What did you have to give up or stop doing to make the switch?"
FIRST USE & NOW (10 min)
- "Walk me through the first week. What was the first thing that made you think
'yes, this was right' — or 'uh oh'?"
- "What does a good day look like now vs. before? What did you get BACK?"
[This is the JOB DONE — the progress. Capture the before/after life.]
- "What still annoys you / what do you still do by hand?" [next opportunity]
WRAP
- "If a shop owner like you asked 'should I bother?', what would you tell them?"
- "Is there anything I should have asked but didn't?"
DON'T: ask about features, ask hypotheticals, pitch, or fill silences too fast.
DO: anchor to specific dates/scenes, follow emotion, ask "what else?" 3x.What “good” looks like in the data. After ~10 interviews you should be able to write 3–5 one-sentence patterns, e.g.: “Solo shops switch when after-hours quoting eats their personal life (push), pulled by self-serve ordering, blocked by ‘will files print right’ anxiety.” vs “3–10 staff shops switch when a B2B client demands online reordering they can’t provide (push), pulled by the B2B portal, blocked by catalog-migration effort (habit).” Those two patterns imply different homepages and different onboarding — feed them into GTM_01 segmentation and GTM_03 win/loss.
7. The Job Story format — “When ___, I want to ___, so I can ___”
Theory. A job story (Alan Klement / Intercom variant) captures a job in a solution-agnostic, context-rich sentence:
When [situation/trigger], I want to [motivation/desired action], so I can [expected outcome].It deliberately omits the persona (“As a user…”) because the situation matters more than the demographic. Good job stories are causal (the situation explains the motivation) and outcome-led (the “so I can” is the progress, not a feature).
Worked examples for Print-Flow-360 (your starter library — refine with interview language):
PRIMARY (quoting):
When a customer asks me for a price on a custom job after hours,
I want them to get an accurate price themselves online,
so I can stop quoting at night and look fast and professional.
UNPAID-DESIGNER:
When a walk-in hands me a photo and says "make it look like this,"
I want them to design their own print-ready artwork before they commit,
so I can stop giving away free design work to people who don't buy.
SELF-SERVE ORDERING:
When a repeat B2B client needs to reorder the same job,
I want them to reorder and pay on account without emailing me,
so I can stop touching every order and keep the account happy.
LOOK-LEGIT:
When a new customer is deciding between me and the franchise downtown,
I want my online store to look as polished and trustworthy as theirs,
so I can win the job without competing on price alone.
CONFIDENCE-IN-FILES (anxiety-driven):
When a customer uploads or designs their own artwork,
I want to know it will actually print correctly,
so I can avoid reprints, refunds, and embarrassing mistakes.Reusable template:
JOB STORY TEMPLATE
When [trigger — specific situation, time, who's involved],
I want to [motivation — what progress, solution-agnostic],
so I can [outcome — the better life / what I get back / how I'm seen].
QUALITY CHECK:
[ ] No persona, no demographics — situation only
[ ] No feature names in "I want to" (say the progress, not the UI)
[ ] "So I can" is an outcome/emotion, not a feature
[ ] Sourced from a real interview quote where possible8. Enumerating Print-Flow-360’s candidate jobs (and picking the wedge)
Pull the candidate jobs together and rate them on frequency (how often the struggle hits), pain (how much it hurts), push strength (how likely it triggers a switch), and product fit (how well your current product does it). Score 1–5; this is a hypothesis to validate in interviews, then re-rank with ODI (§10).
| Candidate job | Functional core | Freq | Pain | Push | Product fit | Notes |
|---|---|---|---|---|---|---|
| Stop losing nights to manual quoting | Instant accurate self-serve pricing | 5 | 5 | 5 | 4 | Sharpest wedge — frequent, painful, measurable, your calculator nails it |
| Stop being the unpaid designer | Customer self-designs print-ready art | 4 | 4 | 4 | 4 | Strong + differentiating (design studio). Anxiety: “will it print right” |
| Let customers order + pay online without me | Self-serve storefront + checkout | 5 | 4 | 4 | 4 | Core; gated by Stripe/Razorpay regions (SAM) |
| Look as legit as the franchise | Premium branded storefront | 4 | 3 | 3 | 5 | Strong emotional/social pull; weak standalone push |
| Win/keep B2B accounts | B2B portal, pay-on-account, approvals | 3 | 4 | 4 | 4 | High-value, lower frequency; great for larger ICP segment |
| Get jobs through production reliably | Production spine, preflight, fulfillment | 5 | 5 | 3 | 2 | High pain but weak product fit (gaps) — don’t lead here yet |
Decision: Lead the company narrative with “stop losing nights to manual quoting + let customers order online” (combine #1 and #3 — they’re the same Sunday-night scene). Use “stop being the unpaid designer” as the differentiation hook (the design studio is hard to copy). Hold B2B as the expansion/upsell job for the bigger-shop segment. Treat the production/preflight job as anxiety to neutralize, not a headline — because product fit is weak (PLATFORM_GAP). This directly sharpens GTM_01 positioning.
9. Job mapping — the universal 8 steps (find the gaps that lose deals)
Theory (Ulwick / Bettencourt). Analysis of hundreds of jobs found that any functional job decomposes into some or all of 8 universal steps, solution-agnostic, in roughly this order:
- Define — figure out goals / what’s needed to do the job.
- Locate — gather the inputs/information needed.
- Prepare — set up / organize the environment before doing the job.
- Confirm — verify everything is ready and correct before executing.
- Execute — do the core job.
- Monitor — track progress / that it’s going right.
- Modify — adjust/correct as needed.
- Conclude — finish, close out, reflect.
Mapping the whole job (not just the part your product touches) reveals where customers struggle today and where you’re strong vs. weak.
Applied — job map for “Sell a custom print order online” (the shop owner’s job):
| Step | What the shop needs to get done | Current way (Wix+email) | Print-Flow-360 today | Gap / force |
|---|---|---|---|---|
| 1. Define | Decide what products to sell online & how priced | Ad hoc; in Maria’s head | Product types, options, price calculator | Strong (Pull) |
| 2. Locate | Get artwork, specs, customer details into one place | Email attachments, phone | Storefront forms, custom fields, design studio | Strong (Pull) |
| 3. Prepare | Configure the product/price so a customer can order | Manual quote per request | Admin product + pricing setup | Anxiety: setup effort → done-for-you onboarding |
| 4. Confirm | Make sure the order is correct & print-ready before producing | Manual eyeballing, back-and-forth emails | Proof step exists; preflight/CMYK immature | WEAK — top anxiety. PLATFORM_GAP item #1 |
| 5. Execute | Take the order + payment | Deposit + invoice by hand | Storefront checkout + Stripe/Razorpay | Strong (Pull) |
| 6. Monitor | Track order/job status | Spreadsheet | Order + job workflow | OK |
| 7. Modify | Handle changes, partial shipments, reprints | Manual | Partial fulfillment immature | WEAK — PLATFORM_GAP item #2 |
| 8. Conclude | Deliver + notify + tracking + close out | Manual emails, no tracking | Carrier/tracking integration missing | WEAK — PLATFORM_GAP item #3 |
The strategic read: Your product is strong on the front half of the job (Define→Execute = sell online) and weak on the back half (Confirm/Modify/Conclude = produce + fulfill reliably). That’s fine and on-strategy — GTM_01’s category is “online storefront + design studio,” NOT “print MIS.” But the Confirm step (preflight) generates the loudest anxiety in the buying decision, so it punches above its weight in deals even though it’s not your headline job. Prioritize Confirm (preflight/proof confidence) over Conclude (tracking) because anxiety blocks the sale; tracking is a post-sale satisfaction issue you can phase in. Feed this ranking into PLATFORM_GAP_ASSESSMENT.
10. Desired outcomes + opportunity scoring (ODI) — what to build next, by the numbers
Theory. Once you know the job and its map, you express success as desired-outcome statements — solution-free, measurable success metrics customers use to judge any solution. Ulwick’s required structure:
[direction of improvement] + [unit of measure / metric] + [object of control] + [contextual clarifier]
e.g. "Minimize the | time it takes to | produce an accurate price | when a customer requests a custom job."Each statement is rated by customers on importance and current satisfaction (with whatever they use today). Then the opportunity algorithm:
Opportunity = Importance + max(Importance − Satisfaction, 0)The intentional design point: importance is double-weighted (it’s Importance + the gap, not (Importance + Satisfaction) / 2). The max(…, 0) floor means an over-served outcome (Satisfaction > Importance) is never scored below its importance — over-service simply earns no extra opportunity, it doesn’t go negative.
Two ways to put it on a 0–20 scale — pick one and stay consistent:
- Ulwick’s canonical method: survey on a 1–10 scale, report Importance and Satisfaction as the percentage of respondents who rated 9 or 10 expressed as a number out of 10 (e.g. 70% → 7.0). Opportunity then runs 0–20.
- Top-2-box operationalization (used in the worked example below): survey on a 1–5 scale, take the % choosing 4 or 5 (top-2-box), divide by 10 to land on 0–10. Same formula, same 0–20 range. This is a legitimate, lighter-weight variant — just don’t mix the two within one study.
Rough thresholds (Strategyn convention):
- > 15: extremely underserved — ripe, rare.
- 12–15: underserved — strong opportunity, prioritize.
- 10–12: appropriately served.
- < 10: overserved — don’t invest (and consider doing less).
Survey question wording (copy/paste — top-2-box variant):
For each statement, two questions, 1–5 scale.
IMPORTANCE:
"How important is it to you that you can [outcome statement]?"
1 = Not at all important … 5 = Extremely important
(Top-2-box = % choosing 4 or 5)
SATISFACTION (with how you do this TODAY):
"How satisfied are you with your CURRENT ability to [outcome statement]?"
1 = Not at all satisfied … 5 = Extremely satisfied
(Top-2-box = % choosing 4 or 5)
Importance score = (importance top-2-box %) ÷ 10 → 0–10
Satisfaction score = (satisfaction top-2-box %) ÷ 10 → 0–10
Opportunity = Importance + MAX(Importance − Satisfaction, 0) → 0–20Worked example — desired outcomes for the quoting/ordering job (illustrative numbers; replace with your survey):
| # | Desired-outcome statement | Imp % (T2B) | Imp (÷10) | Sat % (T2B) | Sat (÷10) | Opportunity | Read |
|---|---|---|---|---|---|---|---|
| O1 | Minimize the time to give a customer an accurate price for a custom job | 90% | 9.0 | 25% | 2.5 | 9.0 + (9.0−2.5) = 15.5 | Extremely underserved → headline |
| O2 | Minimize the likelihood that uploaded artwork prints incorrectly | 88% | 8.8 | 30% | 3.0 | 8.8 + 5.8 = 14.6 | Underserved → preflight (anxiety) |
| O3 | Minimize the time customers spend placing a repeat order | 70% | 7.0 | 35% | 3.5 | 7.0 + 3.5 = 10.5 | Appropriately served |
| O4 | Increase the number of orders that come in without me touching them | 85% | 8.5 | 20% | 2.0 | 8.5 + 6.5 = 15.0 | Extremely underserved → self-serve |
| O5 | Minimize the time to set up a new product for online sale | 80% | 8.0 | 45% | 4.5 | 8.0 + 3.5 = 11.5 | Appropriately served (but watch anxiety) |
| O6 | Minimize the likelihood my store looks unprofessional online | 75% | 7.5 | 55% | 5.5 | 7.5 + 2.0 = 9.5 | Slightly overserved — don’t over-invest in theme polish |
| O7 | Minimize the time to know a shipment’s delivery status | 60% | 6.0 | 50% | 5.0 | 6.0 + 1.0 = 7.0 | Overserved-ish → defer tracking |
The read for your roadmap: O1 (instant accurate quoting), O4 (hands-off orders), and O2 (files print right) are the underserved trio. O1/O4 you already do well → make them the marketing spearhead (you win on a real, measured gap). O2 is underserved AND you’re weak → #1 build priority (and it doubles as anxiety-removal in §5). O6 (looks professional) has high satisfaction → Wix/templates already make shops feel “okay enough” there — don’t burn roadmap on more theme polish, just don’t be worse than the incumbent. O7 (tracking) scores low-opportunity → confirms deferring it (matches §9).
Reusable ODI worksheet (spreadsheet skeleton):
COLUMNS:
A: Outcome # B: Outcome statement C: Job step (1-8)
D: Imp T2B % E: Sat T2B %
F: Importance = D/10
G: Satisfaction = E/10
H: Opportunity = F + MAX(F - G, 0)
I: Tier = IF(H>15,"Extreme",IF(H>=12,"Underserved",IF(H>=10,"Served","Overserved")))
J: Our product fit (1-5)
K: Action = build-priority where H is HIGH and J is LOW (underserved & we're weak);
marketing-spearhead where H is HIGH and J is HIGH (underserved & we're strong)
ONE ROW PER OUTCOME. Sort by H descending to rank opportunity.
Then segment two views:
• "H high AND J low" → build next (e.g. O2 preflight)
• "H high AND J high" → market hard (e.g. O1 quoting, O4 hands-off orders)
SAMPLE N: aim for 30–50 survey responses per segment for directional reads at
pre-PMF (not statistically tight, but enough to rank). Run separately for
solo-shop vs 3–30-staff segments — opportunities differ (see §6 patterns).11. Turning jobs into messaging, onboarding, and roadmap
JTBD isn’t a deck you write once — it rewires three operating systems:
A) Messaging (homepage, ads, sales). Mirror the push and promise the progress, in their words.
| Asset | Job-driven version |
|---|---|
| Hero headline | ”Stop quoting at 10pm. Let your customers price, design, and order online — themselves.” |
| Subhead | ”A branded online store + design studio for print & sign shops. Customers get instant prices and print-ready files; you get your evenings back.” |
| Three proof points | (1) Instant accurate pricing [O1] · (2) Customers design print-ready art [unpaid-designer job] · (3) Orders + payment, hands-off [O4] |
| Anxiety-busters (above the fold or FAQ) | “We set up your first products with you.” “Your files print right.” “Keep your phone number — this adds to how you sell, it doesn’t replace you.” |
B) Onboarding milestones (feed CONVERSION_FUNNEL). Time-to-value = seeing the job done once. Define the three “aha” milestones as job completions, not feature tours:
ONBOARDING MILESTONES (job-completion based)
M1 "First correct price" → owner sets up ONE product and sees the calculator
return a price they'd actually charge. (job: quoting)
M2 "First shareable storefront link" → owner has a branded URL they can paste
to a real customer right now. (jobs: look-legit + self-serve)
M3 "First hands-off order" → a real or test customer places + pays for an order
with NO email/phone touch from the owner. (job: stop touching every order)
Activation = reached M3. Everything in setup should drive toward M3 fast.
Kill any onboarding step that doesn't move toward M1–M3.C) Roadmap prioritization. Rank with the ODI table (§10) cross-referenced to the job map (§9): build underserved outcomes where you’re weak first (O2 preflight / Confirm), defend underserved outcomes where you’re strong with reliability + marketing (O1/O4), and stop investing in overserved outcomes (O6 theme polish, O7 tracking for now). This gives you a defensible, customer-grounded answer to “what next” that isn’t loudest-customer-wins.
Cheap validation / first moves (this week)
- Recruit 5 switch interviews this week. Post in 2–3 print/sign-shop Facebook groups + r/printing + a LinkedIn note to anyone who recently mentioned going online: “15-min chat + $50 gift card — recently started (or tried) selling/quoting online?” Use the §6 guide verbatim. Target the GTM_01 ICP.
- Do 1 “concierge job-done” test. Find one friendly shop, manually set up their top 3 products in Print-Flow-360 for them, hand them a storefront link, and watch them react. Did you remove the §5 anxiety? What did they say when they saw their own store? That’s a $0 PMF signal.
- Write your job story library (1 hour). Use the §7 template to draft the 5 candidate jobs; after 3 interviews, rewrite each in the shop owner’s actual words. The words that make them lean in become your homepage.
- Stand up a ~10-question ODI micro-survey (Google Forms). Use the §10 wording on the 7 outcomes; post in the same groups offering results back. Even 20–30 responses will tell you whether O1/O2/O4 really top the list before you spend a sprint.
- Rewrite your hero section using the §11A job-driven copy and A/B it against the current feature-led version. Pre-PMF, your homepage is your cheapest experiment.
- Re-rank the PLATFORM_GAP backlog against the §9 job map + §10 opportunity scores. Confirm preflight (Confirm step) outranks tracking (Conclude step) for now, and document why in that doc.
Cross-references
GTM_01_ICP_AND_POSITIONING_2026-06-15.md— the “Maria” persona and category claim; this doc supplies the job she’s hiring for. Use GTM_01’s ICP as the interview recruiting filter.GTM_03_WIN_LOSS_AND_CHURN_INTERVIEWS_2026-06-16.md— switch interviews of losses and churns extend §5–§6; the Four Forces explain why deals are lost (anxiety/habit won).GTM_04_PRICING_RESEARCH_METHODS_2026-06-16.md— the value you charge for is the job done; ODI underserved outcomes (§10) tell you which jobs justify which tier.GTM_05_COMPETITIVE_INTELLIGENCE_2026-06-16.md— define competitors as “anything that does the job today” (§1), including Wix + email + spreadsheets, not just web-to-print SaaS.GTM_06_TAM_SAM_SOM_MODELING_2026-06-16.md— the job + Stripe/Razorpay gating define which shops can actually hire you (SAM); job patterns (§6) define the SOM beachhead.CONVERSION_FUNNEL_RESEARCH_2026-06-15.md— the §11B job-completion milestones (M1–M3) are the activation events for the funnel.PLATFORM_GAP_ASSESSMENT_2026-06-07.md— re-prioritized by the job map (§9) and opportunity scores (§10): Confirm/preflight before Conclude/tracking.PRICING_RETENTION_REFERRALS_STRATEGY_2026-06-15.md— retention = continuing to do the job; the “what still annoys you” answers (§6 wrap) are your expansion roadmap.