The decision in one sentence

Earn the switch.
Own the coffee job.

A complete coffee-selling product: reviewed facts, beautiful buying, six subscription models, loyalty, and the next customer visit. Validate its commercial foundation with a scoped $99 offer.

Explore the full product vision ↗See the merchant pitch ↗

01 / An observable job, not a category fantasy

Start where coffee changes
and subscriptions already matter.

Established Shopify roasters and specialist multi-roaster retailers. A real upcoming launch, seasonal lot change, or club selection gives us a task to observe.

24,960Active identities with strong coffee language

5,990Broad roasting-language screen

5,820Strong coffee + roasting language

2,606Specialty + coffee + roasting language

1,073Coffee + roasting + recent product + subscription detection

268Local theme + coffee language

Screening, not TAM. 1,385,355 source rows processed; identity deduplication and exported-status filtering. 197 stratified candidates and 60 negative controls audited. Signals do not establish active orders, reachable buyers, or paid demand.

Methodology & verified counts ↗

Warm start ≠ whole market

634 specialty stores meet the task-oriented intersection. 353 Krown-vendor coffee identities are potential distribution signals; relationships and theme versions need checking.

Two buyers to separate

Own-brand roasters launch their own lots. Multi-roaster retailers curate other roasters’ inventory. Test their sourcing and rotation jobs independently.

$1M requires reach

842 paying stores at $99/month exceed $1M gross ARR. That is ~14% of the broad roasting screen before disqualification. This is arithmetic, not a penetration forecast.

02 / One catalog. One complete task.

The demonstration is the
second coffee launch.

Approved coffee information flows through one consistent buying experience. When the lot changes, the merchant can see and resolve the consequences before customers receive the next bag.

01 / REVIEW

Trust the facts.

Source evidence, conflicts, missing values, and existing field mappings. No invented tasting scores.

02 / PRESENT

Tell one story.

Shared cards, PDP facts, finder, and purchase options read the approved coffee object.

03 / ENROLL

Make a clear promise.

Same coffee or roaster’s choice. Real variants, grind, size, cadence, and recurring price.

04 / CONTINUE

Ship the right coffee.

Physical variant mapping, consent, stock, price, and engine confirmation before a lot change.

Interactive / merchant

Review a coffee source ↗

Resolve a conflict and update the shared preview.

Interactive / merchant

Configure a real offer ↗

Explore model, eligibility, options, and next-lot rules.

Interactive / shopper

Build the next delivery ↗

Choose, edit, and review an illustrative subscription.

Standalone prototypes with sample state. Current Polaris components in admin; existing Coffeetale assets in customer previews.

The flagship product / broader than the first pilot

Six ways to buy.
More reasons to return.

The complete experience includes a coffee workspace, storefront and discovery, subscription studio, loyalty, customer journeys, and design freedom. A smaller release is a sequence—not the product ceiling.

01 / Compact purchase

The daily refill ↗

Known coffee, grind, size, bags, and cadence.

02 / Editorial comparison

The roaster’s club ↗

Choose a tier and let the roaster curate each cycle.

03 / Selection grid + tray

Build a box ↗

Multiple coffees, quantities, grind, limits, and progress.

04 / Guided discovery

Personalized coffee ↗

Taste and brew preferences with hard decaf constraints.

05 / Gift composer

Give coffee ↗

Recipient, message, duration, start, and entitlement.

06 / Consumption calculator

Coffee for the team ↗

Team size, cups, bag formats, and editable cadence.

Configure the six-model studio ↗Compare distinct real-world references ↗

Loyalty is a first-class module

Buy 5 eligible bags.
Earn a €10 next-order reward.

The customer sees meaningful progress; the merchant sets the earning unit, eligibility, reward, redemption, and refund rules. Per-bag earning differs from per-order earning. Subscription renewal eligibility must be explicit.

A separate “buy 5 drinks, sixth free” café program is a future POS workflow. It does not share an assumed identity or ledger with online beans.

Try earning, redemption & refunds ↗

Coffee rewards / local fixture

The next bag
comes with progress.

✓✓✓✓5

4 / 5 stamps

Buy 5 eligible 250 g bags, earn a €10 reward for your next order.

Open the merchant program controls →

Loyalty route: provider widget, custom interface, or narrow owned ledger?

Appstle’s $10–$30 researched widget tiers are a cost baseline. The custom Coffeetale interface needs separate API access with unpublished pricing. Smile API was researched at $999/month; Rivo requires a higher tier. Price/access economics may justify estimating a narrow owned ledger, including stable customer identity, duplicate events, refunds, and redemption correctness. Desired UI and delivered integration are separate decisions.

Provider evidence · Full loyalty specification

Full vision / engineering-only sensitivity800 / 1,200 / 1,600 h

Discussion scenarios only: $48k / $72k / $96k at $60/hour, excluding design, support, services, and other costs. These are not estimates.

At 25 engineering hours/week32 / 48 / 64 weeks

Capacity arithmetic for the broader vision. The $26–41k initial-app allowance below excludes all six production models and an owned loyalty engine.

Operational product / validate with design partners

Subscriptions and rewards need an operational plan.

Work with real club and recurring-box operators before implementing advanced allocation rules. The six-model studio shows hypotheses. It does not validate selection windows, no-response defaults, reservation timing, or shortage policy.

Observe two different workflows.

Recruit a curated-club roaster and a merchant running a customer-built recurring box. Watch a normal cycle, a stockout, a late edit, and a failed payment. Compare redacted inventory, due cycles, customer terms, and the actual allocation sheet.

Design-partner discovery plan ↗

Separate four operational decisions.

Accept new signups. Plan existing deliveries. Protect stock through a real mechanism. Resolve shortages under the customer’s agreed terms. A visual builder cannot decide these policies on the merchant’s behalf.

Try the planning workspace ↗

01 / RECONCILE

Stock + source events

Shopify availability, due cycles, issued rewards, and timestamps. Exclude orders already represented in committed stock.

02 / PLAN

Keep demand classes visible

Scheduled obligations, unmapped club demand, issued rewards, and uncertain future earning. Never substitute zero for unknown.

03 / ALERT

Send a useful review request

Variant, location, cutoff, gap, affected offers, and a human owner. Internal operational alerts differ from marketing nudges.

04 / CONFIRM

Review before an operation

Recheck stock and permission; use an authorized provider route. Pending is not confirmed. Forecasts never charge customers.

Planning arithmetic / one 250 g physical variant100 − 60 − 10 = 30

Available bags minus not-yet-ordered renewal bags and a separate buffer. Existing committed orders are already excluded from Shopify available. Fifteen two-bag first deliveries is a planning upper bound, not guaranteed subscription capacity.

Physical rewards / separate assumptions8 issued · 12 near

At 50% issued redemption and 25% combined near-threshold earning/redemption, allow 4 + 3 bags: 23 remain in the scenario. A €10 voucher has no specific SKU demand. Issued rewards survive stockout.

Start with historical replay, shadow forecasts, and useful alerts. Add assisted operations, then narrow automation only after merchant rules and provider behavior pass together. Estimate demand visibility, allocation, concurrency, and operational alerts separately from shopper layouts.

Explore stock shock & alert previews ↗Backend flow, records & acceptance cases ↗

03 / A replacement-worthy product

The incumbent is often
already good.

A polished card or cheap import is easy to substitute. Our case must survive a comparison with the merchant’s best existing workflow and actual invoices.

Alternative	What is already credible	What Coffee Kit must prove
Coffeefy / CoffeeRx	Free coffee presentation / advertised $14.99 finder	The connected, repeated job justifies more than an attractive block.
Andeo / Curobi	Coffee matching and coffee clubs/boxes	Better catalog-to-purchase-to-next-lot execution in the actual use case.
Recharge / Seal / Appstle	Established subscription operations; Recharge documents rotation.	Correct, simpler coffee changes or an economically better owned route.
Shopify native + current tools	Free subscription baseline, existing theme and AI tooling	Less work and more reliable outcomes than a competent native setup.
Full Krown Studio suite	A broader companion suite at a proposed $99; existing distribution	A more specific repeat job. Preserve Studio as the alternative; avoid building both now.

Competitor capabilities/prices are public claims checked in the research, not integration test results. Studio portfolio counts come from supplied historical research and are not directly comparable to this market screen.

Competitor evidence & review signals ↗

The moat is maintained correctness.

Accurate field and variant mappings. Eligible recommendations. Consistent rendering. A safe second change with low assistance. Krown’s design and distribution help us enter; sustained reliability earns retention.

Data ownership is a feature. Approved public facts belong in merchant-owned Shopify fields. Agencies can render them independently. Evidence and private operational state stay private.

Prove the switch, one route at a time.

Presentation replacement → catalog and experience replacement → new-club enrollment → supported contract migration. Each is a different scope and cost.

Replacing a $39 quiz with $99 Coffee Kit while retaining all other providers raises the bill by $60. Time saved, paid preference, or actual retired spend must explain the difference.

04 / Architecture follows the customer promise

Own the coffee model.
Earn the right to own renewals.

Route A / first purchase

Enrollment over existing plans

Correct product, variant, and selling-plan choice. The existing engine owns renewal, portal, and contract changes.

Fastest test of the buying experience
No promise of automatic rotation
Provider spend remains visible

Test the complete task

Route B / test first

Deep Seal integration

Documented API/webhook access makes Seal a credible price baseline. Verify pre-charge coordination and failure behavior before committing.

Appstle partner route as fallback
Access and entitlements need proof
Provider controls its own contracts

$123.95 illustrative total / mo

Route C / serious alternative

A narrow owned engine

Shopify supplies payment primitives and a reference app. Coffee Kit still operates scheduling, recovery, portal, notices, and incidents.

One currency, domestic shipping
Fixed refill + one physical-lot club
Requires paid preference and capacity

Spike, estimate, then decide

Illustration: $99 Coffee Kit + $24.95 Seal, assuming subscription count fits the tier. At 500 monthly orders / $15,000 subscription revenue, researched Loop Pro and Skio Scale examples total $610.50 and $948 respectively; coverage differs.

Before charging

The actual physical SKU must resolve with the right size, grind, stock, and amount. A permanent club SKU with a new label does not solve inventory.

Before changing

Same-coffee subscriptions need the applicable customer choice. Roaster’s choice stays within agreed terms. A taste match is not contract consent.

Before release

Pass stock, retry, duplicate event, cancellation, price, failed-payment, revoked-access, and refund cases. Pending confirmation must never read “applied.”

All routes, costs, migration boundaries & lifecycle cases ↗

The product boundary

A complete experience.
A disciplined scope.

Build and own

Source-backed review, mapping, and audit
Shared coffee experience configuration
Eligibility and approved coffee transitions
One supported subscription route

Integrate with care

Shopify price, inventory, checkout, and payment primitives
One tested marketing event/template handoff
Existing loyalty ledger and customer permissions
Native or selected pickup workflow

Use the foundation

Coffeetale cards, facts, finder, and brew-guide patterns
Current Polaris admin components
One selected external theme/version
Merchant-owned fields and a plain agency renderer

Later, if evidence earns it

Wishlist and cross-device saved coffees
Editorial events and QR-to-finder entry
Complex gifts, arbitrary bundles, and POS
Broad write API, own loyalty, or campaign tooling

AI proposes facts; merchants approve them. Test 100 representative sources with a holdout. Initial HTML and consistent product data support discoverability; they do not guarantee AI citations or rankings.

Data, AI, ownership & agency contracts ↗

05 / Price the work that repeats

$99 is the hypothesis.
Support is the sensitivity.

Explore contribution after platform-fee assumptions, $5/store infrastructure, and recurring support at $30/hour. These are planning scenarios, not a forecast.

Paying stores 100Support minutes / store / month 30 minFee scenarioOtherwise-unallocated fixed costs / month

Exclude support from fixed costs if it is already charged here. Onboarding, acquisition, tax, provider fees, and owned-engine costs are excluded.

Contribution / store / month

$61.28

Gross annual recurring revenue: $118,800
Recurring support workload: 50 hours/mo
Monthly contribution: $6,128
After selected fixed costs: −$8,872
Break-even paying stores: 245

Confirm Krown’s fee eligibility and aggregate lifetime threshold. Actual fee rules and adjustments differ from a simple additive sensitivity.

$594,000

Gross ARR at 500 stores. At 30 minutes per store, recurring support alone is 250 hours each month.

600-store ceiling

With 30 new stores/month and 5% monthly churn, the arithmetic long-run ceiling is 600. Growth requires retention as well as acquisition.

Engine cost is additional

The illustrative owned-engine model adds $39.20/store at 50 stores or $23.60 at 100. The measured spike must replace those assumptions.

Full economics, fee schedule, assumptions & merchant value ↗

06 / Three people. Explicit capacity.

A staged experiment,
with evidence at every gate.

The 12-week sequence is an experiment cadence. Production readiness, engineering availability, provider approval, and real renewal timing determine the calendar.

Weeks 1—2

Observe & compare

Six actual merchant tasks, current invoices, Seal lifecycle proof, and a bounded reference-app gap estimate.

Gate: a repeat job + plausible total price + technical route.

Weeks 3—4

Choose the slice

Field contract and one storefront path. 8–12 qualified candidates; five explicit $99 scoped acceptances.

Gate: commit to one supported route or narrow the proposition.

Weeks 5—8

Build & harden

Correct purchase behavior, measured onboarding, and lifecycle acceptance before any rotation release.

Gate: four useful activations when the slice is ready.

Weeks 9—12+

Observe repeat value

Second changes, support effort, and mature paid cohorts. Extend observation if renewals have not occurred.

Gate: three renewals + two paid stores outside Krown.

Discussion allowance / not an estimate$25,920–$40,980

Spike 32–48 developer hours; initial app 280–440 more; design 100–160; support 80–120. Rates $60/$45/$30, plus $300–$900 tools. Before owned engine or complex migration.

Protect the theme business13–20 engineering weeks

312–488 developer hours at 25 app hours/week, before approvals and scheduling delays. A production owned engine is additional work, not hidden inside the same date.

Developer

Data and purchase correctness, operational route, lifecycle tests, access, observability, and incidents.

Designer

Review and buying journeys, the shared visual system, reusable demos, and observed task completion.

Support / growth

Qualification, onboarding, documentation, cohort records, and second-change assistance. Founder owns go/no-go decisions.

Acquisition and commercial capacity

Start with 20–30 qualified Krown relationships, then two specialist agencies and selected external roasters. Reserve a proposed 22 commercial team-hours/week: support 12, design 6, developer/founder 4, separate from product engineering. Cap assisted onboardings at two/week and active pilots at 8–12. No outreach or ad spend has been initiated.

Switching assistance has a separate budget

A possible $750 one-time service for up to 500 simple contracts, one source/store/gateway/currency, is an internal hypothesis after a route is proven. The research scenario leaves $330 contribution before acquisition/fixed overhead; five extra technical hours nearly consume it. It is not a live offer or a promise of automatic migration.

What automation can responsibly do

Prepare source-backed previews, public-fact qualification, draft field maps and messages, summarize authorized research, and organize support evidence. Humans approve coffee facts and commercial promises. Developers retain payment, contract, and cutover authority.

07 / The next investment decision

What would change
our minds?

Do merchants pay for the complete task?

Five scoped $99 acceptances, four useful launches and second actions, then three paid renewals. Record declines and assistance; interest alone is insufficient.

Can a provider safely coordinate the next lot?

Same-scenario Seal proof versus an owned-engine estimate. If provider rotation already solves it cheaply, earn the fee elsewhere or repackage.

Can the merchant do the second change?

Measure corrections, elapsed work, and support minutes. Narrow configurations or separate services when the support burden breaks capacity.

Do they only value setup?

Consider a theme/sections/service business. A narrower $49 recurring offer is a separate test, not validation of the $99 proposition.

Does native or Studio win?

Keep reusable infrastructure and useful theme components. Stop an undifferentiated suite; preserve the full Studio comparison without building both in parallel.

No interviews, paid demand, provider lifecycle tests, extraction benchmark, production performance benchmark, or conversion uplift were established by this research.

The evidence behind the pitch

The full business and product plan

All decisions, assumptions, source links, tradeoffs, and handoff detail.

Read the full report ↗

The complete product