Research coverage.
5,036 of 35,673 conversations processed.
The percentage tracks extraction coverage. Classification, evidence review and the business assessment are still in progress.
Discovery leads under challenge.
The leads below are screening hypotheses, not finalists. Each needs distinct buyers, recurring work, payment evidence and a gap in existing solutions. See the source-based screening report.
No evidence-backed shortlist yet.
Historical frequency alone cannot establish a business. We will distinguish theme defects, documentation gaps and one-time changes from recurring merchant work worth paying to solve.
Generic AI store builders, support chatbots and service agencies are not default recommendations. Image production remains outside the preferred direction.
Keep checkout reachable by keyboard.
A recent merchant reports a purchase-blocking keyboard problem in the cart. Support attributes it to a wholesale app replacing the checkout button; that diagnosis and a completed repair remain unverified.
Developer guidance, an app advertising attribution, and manual testing services address parts of this work; exact fit remains unverified. Accessible purchasing can remain valuable as storefront creation gets cheaper, but recurring failures and a separately paying buyer are unproved.
Source evidence, current alternatives and disconfirmation
Collect trade information; request a product quote.
Two historical requests concern adding tax and trade fields to an account form, and hiding selected product prices so shoppers can ask for a quote. They establish distinct setup needs, with no recurring paid gap yet.
Native forms, B2B draft orders and quotation apps overlap parts of these jobs. Capturing a tax ID does not verify it; a reported Shop the Look display limitation does not establish failure of quotation software as a category.
Source evidence, alternatives and the next disconfirmation
Separate the operating job from page setup.
Accurate product information and receiving inquiries remain useful when storefronts become cheaper to create. These cases establish setup friction, with no recurring paid gap yet.
Display product facts correctly
Custom nutritional icons encounter a character-handle mismatch; a later dynamic-source field loses formatting. Typed metafields overlap the basic display job. Suggested fixes are not confirmed outcomes.
Receive inquiries on partner pages
The request is contact-form placement. Shopify documents a reusable contact template; partner routing, lead attribution and ongoing operations are not evidenced.
Source evidence, native overlap and disconfirmation
Waiting for stock is different from taking a preorder.
One merchant asks for tag-dependent restock alerts or preorder checkout, and explicitly asks about custom integration fees. Another wants a “Coming Soon” page that cannot proceed to checkout.
The fee inquiry is a request for a service. No accepted quote, completed payment or recurring product budget is established.
Test the policy before proposing a product.
Klaviyo documents product-tag targeting and a restriction when products remain purchasable without stock. Shopify supports preorders through apps. Exact combined behavior remains untested; no new business is selected.
Evidence, current alternatives and the smallest test
Keep product information specific.
Three different requests concern shopper inputs, product-specific information and catalog filters. Native metafields and Search & Discovery overlap substantially. The cases do not establish one recurring paid data operation.
Source scope, native capabilities and the next disconfirmation
Keep order instructions intact.
One merchant reports three truncated order notes. Their purpose, operational consequence, cause and resolution remain unknown. Native capture exists; a recurring paid gap is unproved.
Source scope, native controls and disconfirmation
Clear unwanted catalog tags.
One historical request asks how to remove accumulated product tags. Current native bulk controls overlap directly; repeated cleanup failures and a separate software budget are unproved.
Source scope, native controls and disconfirmation
Charge for content access.
One historical presale question asks about monthly access to recipes. The proposed consumer price is not an app budget. Billing and content-gating tools already overlap; no recurring merchant burden or failed installed alternative is established.
Source scope, current alternatives and disconfirmation
Identify where a signup came from.
One historical request asks to distinguish signup sources. A separate case asks where emails are stored. Existing Shopify capabilities overlap, and the records do not establish recurring paid demand.
Source evidence, alternatives and disconfirmation
A price still needs the right scope.
An accepted EUR 750 theme-service amount remains outside this investigation’s venture scope. A separate Nutri-Score display case is reported solved after configuration changes. Neither establishes a recurring budget for a new product.
Source evidence and outcome boundaries
Keep the promotion tied to the intended purchase.
One merchant wants a bundle discount confined to the bundle shopping flow and reports a code-based workaround. Promotion eligibility could outlast cheap storefront creation, but recurring burden and an independent budget remain unproved.
Fast Bundle documents the core eligibility rule. Exact store fit is untested; no residual paid gap or finalist is established.
Source evidence, current alternatives and the smallest further test
Choose the contents; keep the transaction records.
Two older requests concern shopper-built gift packs and transaction exports. These are separate jobs. Neither establishes a recent, persistent gap or an independent budget.
Product-grid bundle apps and native transaction exports overlap substantially. Exact merchant fit remains untested; no finalist is selected.
Source evidence, current alternatives and disconfirmation
Stock availability needs a precise promise.
One merchant reports stock appearing available across two Shopify stores connected to NetSuite despite different quantities. The cause, recurring loss and independent budget remain unproved.
Pickup availability can include transfers, and existing connectors advertise location mapping and inventory sync. These are checks to make before proposing another product; they do not establish what caused this report. No finalist is selected.
Source evidence, current alternatives and the smallest disconfirmation test
Rental stock needs dates, not just quantities.
One merchant asks for rental inventory and scheduling. Allocating finite stock across dates could remain useful when storefront creation becomes cheap, but the source establishes no booking losses, repeated failures or separate budget.
Existing rental apps advertise substantial overlap, including date-based capacity, calendars and returns. A native-feature request does not establish willingness to buy another app. No finalist is selected.
Source evidence, current alternatives and the smallest disconfirmation test
Choose an offer, not just a country.
One merchant wants US shoppers to choose a domestic range or a wider international catalogue with different prices and shipping. Another wants store stock visible while online orders ship from a warehouse. These are separate jobs; recurring loss and an independent budget remain unproved.
Native products, markets and shipping rules overlap substantially. The next test must preserve the chosen offer through checkout. New market-shipping features have limited availability; exact store fit is untested.
Evidence, native alternatives and disconfirmation · How Taylor’s completed reading changes the screen
Preorders and kit choices need an exact gap.
Two older requests concern preorder-specific communication and choosing patterns within a fixed three-item kit. A recent bundle-app failure and appointment timeout are separate incidents; they do not establish persistence of those earlier jobs.
Shopify and existing apps overlap both workflows. Exact fit, recurring consequences and an independently paying buyer remain unproved. No finalist is earned.
Source evidence and current alternatives
Verify a tracking failure before proposing another tool.
One merchant reports that Meta receives events while its browser helper does not show the pixel as expected. Campaign harm is predicted; the proposed extra setup expense is not a completed payment or recurring budget.
Shopify diagnostics and existing pixel apps overlap generic setup work. A durable measurement job is plausible, but repeated failures, measurable consequences and an independent paying buyer remain unproved.
Source evidence and current alternatives
Changing product facts need a clearer paid gap.
One merchant explicitly says manufacture and best-before dates change frequently for each product. That is a continuing data-change job;its cost and independently paid value remain unknown.
A separate food-menu context asks for variant information and clearer delivery choices. Native bulk editing,variant collections,unit pricing and existing description apps overlap these requests. No finalist is earned.
Source evidence and current alternatives
Size and stock must agree.
A second source context reports inaccurate size-and-stock filtering. The shopping job could outlast cheap storefront creation,but the exact cause, recurring consequence and independently paid gap remain unproved. Native filtering overlaps substantially.
Allergen-icon setup,sibling-product display and one-time theme repair are separate contexts. Store-host mentions remain unverified identity candidates.
Evidence and current alternatives · Identity limits
What do side-cart recommendations produce?
One merchant asks for recommendation statistics. The continuing measurement job is plausible; recurring work, a paying buyer and a paid gap remain unproved. Existing reports overlap, while exact cart interaction coverage is untested.
Evidence and limitations · Source screen
Product facts outlast themes. Paid demand remains unproved.
Catalog size is not recurrence
A 2023 conversation asks for distinct nutrition and ingredient data across a stated 700-product catalog. A 2025 conversation asks to reuse attribute icons and labels instead of entering the same values repeatedly. A July 2026 case adds structured nutrition values and icons driven by product fields. These are three support contexts, not verified independent buyers.
The later collection-card display failure was resolved. Shared-entry reuse was not confirmed; neither case establishes recurring maintenance cost or a separate budget.
Existing tools raise the bar
Shopify documents reusable metaobject entries, product references and bulk metafield editing. Ablestar advertises bulk and recurring edits. Exact case fit has not been tested.
A catalog-data job could survive cheap storefront generation, but native setup or an existing app may be enough. No new finalist is promoted. A historical popup defect remains a counterexample, not an assurance venture.
Read source evidence and counterexamples · Six dated official capability checks · Why contact IDs are not buyer counts
Useful beyond the theme business?
The new venture must retain paid value if themes and manual storefront development become marginal. This is a stress scenario, not a forecast. Theme updates and customization continuity are excluded; the remaining leads are not promoted by elimination.
| Family | Job that could remain | Missing proof | Decision |
|---|---|---|---|
| Location-specific fulfillment | Accurately promise stock and assortment for a chosen fulfillment route. | Same repeated failure across buyers, measured consequence, named incumbent attempts and separate budget. | Unvalidated discovery lead. |
| Category specifications and comparisons | Help shoppers compare relevant product attributes. | Recurring catalog work beyond a one-time display setup; current inexpensive apps overlap. | Low-priority screening lead. |
| Theme update and code continuity | Value depends on theme maintenance. | Outside the user's strategic scope, regardless of observed support volume. | Excluded from new-venture ranking. |
Support demand is not willingness to pay. No new business finalist, paid buyer count or archive-wide no-go finding is established. Read the provisional business assessment. The prior update matrix is retained as historical existing-business research.
The alternatives are getting stronger.
These are advertised capabilities checked against official documentation. No product was installed or tested on a customer store. Catalog-data requests now receive the same incumbent challenge; variant presentation and event calendars remain downgraded screening leads. Theme-dependent work is excluded.
| Screening lead | Existing alternative | Still unproven |
|---|---|---|
| Location-aware shopping | Inventric advertises location filtering and cart validation. | A recurring routing or maintenance problem that survives correct configuration. |
| Category comparisons | Compareder advertises category metafields. | Repeated data-maintenance burden and a separate budget. |
| Update and testing assurance — excluded | Shoptest advertises scheduled journey checks; SimGym assesses live and draft themes. | Historical comparison only. Theme continuity and relabeled assurance ventures are outside the user’s scope. |
| Collection-aware variants | Shopify variant-level collections and existing apps. | An independent recurring merchant job beyond theme presentation, with a separately paying buyer. |
| Multi-business events calendar | Cowlendar documents combined service calendars; Events Calendar supports filtered views of shared event lists. | Repeated operational work, an unmet acceptance case and a separate budget. |
Further source checks of translation, supplier-file onboarding and multi-value product filters found substantial native and app overlap. Accelerated checkout introduces a distinct path to test for required inputs; no new finalist was added. See the source screening and counterexamples.
Further broad discovery: B2B setup, event-calendar selection and holiday processing notices are durable-job possibilities, but current platform/app capabilities overlap the observed requests. A VIP launch layout and an unused paid-app refund are counterexamples to treating setup or billed months as recurring value. Five complete contexts and 20 published anchors received independent review and principal adjudication; no new finalist was added. Read the evidence and incumbent constraints.
Support requests establish problems to investigate, not willingness to purchase. Read the capability limits and source review.
Wave 47 is checkpointed: 96 new conversations independently reviewed; 15 corrected. Six classification records cover nine issues. Current checkpoint.
Durable jobs still need a paid gap.
A historical request combines warranty registration, unique-code validation and invoice uploads. Dealer enquiries and retained submissions are separate tasks. These could outlast theme sales, but current Forms and warranty apps overlap, and no recurring independent budget is established.
One recent merchant wants location details without stock-controlled pickup. Two license tickets repeat one reported purchase episode; they do not establish two buyers. Theme-license recovery remains excluded.
Four complete contexts and eleven published anchors independently reviewed. Selected discovery evidence, not population prevalence. Read the screening note and official alternatives.
A request is a starting point.
A product-sibling question faces native and app overlap. A three-zone charge, tax and coupon workflow is too underspecified to define a product. A pickup-readiness complaint ends with support reporting the expected times, without customer confirmation. A delivery-widget diagnosis remains disputed.
Four complete contexts and twelve published anchors received independent review and principal adjudication. No recurring independent budget or new finalist is established.
Read the source screen and six official capability checks.
Durable jobs, with configuration counterexamples.
Three recent conversations, thirteen published anchors and six current primary sources. These are selected contexts, not verified buyers or a prevalence estimate.
Gift recipient details
A floral merchant wants clearer delivery wording and separate purchaser and recipient details. The activity is ongoing, but the exact checkout setup, completed outcome and independent budget remain unknown. Current Shopify address and wording controls overlap ordinary setup; case fit is untested.
Resolved cases constrain the gap
A missing collection was reportedly fixed through Markets/catalog configuration. A video bug was confirmed fixed. A separate cart complaint led to activation of a built-in variant setting, with later shopper success unverified. Many shopper emails can come from one configuration incident.
No new finalist is earned. The jobs could survive theme decline; these cases do not establish a separately paid recurring gap. Read the source screen and current alternatives.
Existing app use narrows the gap.
Four fully fetched text contexts and 21 selected published anchors. Referenced catalog and campaign visuals were unavailable. These are selected conversations, not verified buyers or population rates.
Inventory and holiday pickup
A bakery reports using a paid inventory app and an existing pickup scheduler; the scheduler’s payment status is unknown. It asks about compatibility before buying a theme. CR advertises dates, cutoff controls and collection-specific pickup rules. No incumbent failure or budget for another product is demonstrated.
Product content and outcomes
One merchant receives native metafield guidance for unique product content and an acknowledged presentation review. Hands-on implementation and the requested hover behavior remain unconfirmed. An old attribution question faces current native reporting alternatives; a checkout incident ends with a support-claimed theme fix.
No new finalist is earned. The jobs could survive cheaper storefront generation, but independently paid recurring value after existing alternatives remains unproved. Read the source screen, limits and seven official capability checks.
A useful job still needs an unmet paid gap.
Four complete text contexts and 13 published anchors. Two opened in 2026; two are historical controls. These are selected contexts, not verified buyers or population rates.
Variants without duplicate catalogs
One merchant wants separate variant cards across several collections while avoiding duplicate product records. Shopify now documents variant-level collections, which does not guarantee separate storefront cards. Stamp advertises separate cards from $12/month. No failed incumbent trial or new-product budget is shown.
Structured customer enquiries
An equipment merchant asks for an image and VIN/serial-number field. Native Shopify Forms supports text fields and a file upload. Separate shared-content and missing-email requests do not establish a recurring intake problem. Existing theme spending does not transfer to another product.
No additional finalist is earned. Both jobs could survive cheaper storefront generation; independent recurring paid value remains unproved. Read the source screen and five official capability checks.
Recoverability can matter beyond themes.
One March 2026 conversation, four published anchors and four official sources. A discovery lead, with no supported finalist.
An accidental deletion
A merchant reports deleting a metafield and its values and asks for a dated export. The field's resource type, loss extent and recovery outcome are unknown. A theme purchase is not a backup-software budget.
Protection has existing alternatives
Shopify distinguishes definition-only deletion from deletion with values. Rewind and Metafields Guru overlap backup and recovery workflows. Continuous protection could justify recurring value even for rare accidents, but this case proves neither a separate budget nor an unmet gap.
Theme-continuity ventures remain excluded. No restoration, installation or customer contact occurred. Read the source screen, limits and four official sources.
An ongoing job can already be served.
Three distinct source contexts and nine published anchors. No independently paid recurring gap is established.
Bundle documents and inventory
A November 2025 merchant values automated component-stock synchronization already supplied by Shopify Bundles, but reports confusing invoices and order confirmations. The job survives cheap storefront generation. A question about developer help is not paid intent.
Shopify documents grouped order confirmations and invoices from December 2024. Exact single-item display, template history and installed fit remain unknown. Official notification scope.
Controls against an easy conclusion
A December 2022 selected-store purchase-control request was confirmed solved with existing documentation. An October 2025 wine-field setup question received metafield guidance but no confirmed implementation. These are different contexts, with no verified buyer count.
The next local test is repeated document-specific operational cost after native and app configuration, with an accountable buyer and separate budget. A generic bundle-display app is held; a notification-maintenance service does not become a theme-continuity workaround.
Read the evidence limits and four official sources
Recurring work can already be automated.
Four selected conversations, 17 published anchors and seven official sources. Distinct jobs, with no supported finalist.
A changing catalog
An October 2026 merchant reports over 100 new products per month and roughly 300 active beers. Its automated spreadsheet upload already saves time. Unnamed bundle and filter apps are in use, with payment status unobserved. Native metafield imports and existing fixed-price box builders overlap the requests; exact fit remains untested.
Configuration and format controls
A separate merchant confirms nutrition data now pulls correctly, then reports empty blocks and raw HTML from a third-party feed. Another asks for category-specific filter visibility and later reports a mobile-menu freeze. These are separate functions and outcomes, not a common paid market.
Product information can matter beyond themes. Repeated manual rework, measured residual cost, an independently paying buyer and recurring value beyond existing automation are still unproved. A theme-block or generated-layout problem does not justify a renamed continuity venture. Read the source limits and current alternatives.
Which item blocks pickup?
One November 2025 request and three distinct recent controls. No supported finalist.
A precise cart question
A merchant describes a mixed-location cart example and asks shoppers to see which item is unavailable where. This is an anticipated scenario, with no documented failed order, recurring incident, measured loss or separate budget. Three presentation changes in the same ticket do not add buyers or resolve that cart request.
The platform has moved
Shopify added transfers from several locations in March 2026. A Plus/Enterprise test drive identifies unpickable items; existing apps advertise cart inventory or pickup selection from about $10/month. Exact mixed-cart fit has not been tested. These are capabilities and listed prices, not merchant spend.
Fulfillable-cart decisions can matter beyond themes. Recurring residual work and independently paid value after native configuration remain unproved. Per-product size guides, allergen icon rendering and theme accessibility due diligence are separate controls. Theme continuity or a renamed assurance service remains excluded. Read the source limits, six official sources and smallest further test.
A second lens on
the app business.
Collected text reading and independent synthesis complete.
960 public HTML pages captured. 961 of 961 available text documents fully read by the source-reading pipeline.
What this adds
Published arguments about platform risk, durable merchant jobs, narrow customers, retained value, pricing and distribution. The full corpus includes app essays, consumer operations, trackers, tools and ad-to-page examples.
How it enters the research
Taylor’s writing supplies a perspective and hypotheses. Its examples and benchmarks stay attributed to him; they do not increase Krown merchant counts or establish willingness to pay. Current platform capabilities still require primary verification.
Read the sourced assessment and coverage · Apply the completed synthesis · Original writing
External-source snapshot: pending. Collection scope: sitemap and reachable public text; robots respected. Images and arbitrary interactive states were not inspected.
A million in ARR
has to add up.
These are transparent scenario assumptions, not observed willingness to pay. Setup fees and annual prepayment timing do not increase ARR.
The current commercial ledger contains 119 source-scoped observations across 100 conversations and 179 overlapping issue-label assignments. They are not independently verified transactions, buyers or a new-product subscription budget. Shared theme purchases and conditional refunds remain scoped to the existing contract. Theme-dependent ventures remain excluded. Read the current scoped summary.
Starts at zero customers. Constant monthly paid additions; churn applies to the opening customer base. No expansion revenue. Actual conversion, margins and founder workload remain unvalidated.
The existing audience is an advantage.
It is not a growth engine by itself.
The supplied populations—42,000 historical users, about 10,000 active users and over 100,000 trials—overlap. Reachability and marketing eligibility are unverified.
10,000 delivered × 25% opens × 5% click-to-open × 2% conversion × $99/month.
10,000 delivered × 5% click-through × 2% conversion × $99/month.
What would make
this worth building?
A small product Ruben can build and operate, with a continuing customer outcome and an acquisition path beyond Krown.
Repeated work, across real buyers.
Separate conversation counts, issue instances and distinct stores. A long support thread is not repeated demand.
Current pain and evidence of spending.
Old requests establish history. Recent unresolved or costly work establishes relevance. Frustration alone does not establish payment intent.
A gap that survives the alternatives.
Check current Shopify capabilities, existing apps and internal automation. Require paid value that survives cheap storefront generation and declining theme sales.
A test that can disprove the idea.
Define interviews, paid validation, retention evidence and kill criteria. “Do not build yet” remains a valid outcome.
App compatibility is not a paid gap by itself.
A prospective combination
A February 2026 collaborator wants store controls and stock badges while Zapiet handles pickup and delivery. The client has not bought the theme. Claimed future client applicability is not observed repeated failure or multiple verified buyers.
The vendor already overlaps
Zapiet documents inventory integration and stock-display widgets, with plan and functional limits. Exact fit is untested. Accurate fulfillment can outlast themes; theme-specific adaptation remains excluded. No independent recurring budget or finalist is established.
Four selected source contexts, twelve published anchors and five official sources. Three layout, video and currency contexts are separate controls. Evidence, alternatives and disconfirmation test.
Generated blocks do not establish a recurring paid job.
Two content questions
One developer wants product-specific tasting content; another merchant wants empty AI-generated blocks hidden. Native dynamic sources overlap, while the exact generated-block behavior is untested. No recurring burden or independent budget is established.
Keep the controls separate
A WhatsApp review app already serves review collection; its theme integration remains unconfirmed. Another merchant reports checkout fixed with a small code edit. Theme-dependent repair stays excluded. One actual AI-block user is not a theme-collapse forecast.
Four selected recent contexts, twelve published anchors and four official sources. No installation, outreach or finalist. Evidence, incumbent overlap and disconfirmation.
Address language and pickup intent need separate proof.
Checkout addresses
One merchant requests English address autofill for Japanese postal codes. Existing validation and post-order transliteration overlap, but do not prove the exact checkout fit. Recurring loss and an independent budget remain unknown.
Pickup selection
Another merchant wants the chosen store kept primary. Support says the default theme already does this; no clean-copy result is shown. A separate translation episode was solved with existing settings. These are leads and controls, not finalists.
Three selected contexts, seven published anchors and seven official sources. No installed trial or outreach. Evidence and disconfirmation.
A pickup-time request faces existing scheduling tools.
Choose a collection time
One prospective merchant asks for shopper-selected pickup times. This job can outlast themes, but no configured result, recurring failure or separate budget is evidenced. Current Zapiet documentation directly overlaps scheduling; exact installed fit remains untested.
Resolved cases matter
Two other conversations include explicit customer confirmation of integration fixes. Payment-widget wording is not willingness to pay, and app use is not proof of spend. A variant-launch request shows ongoing commerce, with no demonstrated recurring software cost.
Four selected contexts, ten published anchors and three official sources. Separate jobs and outcomes, not one market or four verified buyers. Evidence, current alternatives and limits.
Recurring abuse needs a gap beyond native protection.
Daily newsletter submissions
One merchant reports dozens of fraudulent footer signups each day over a month. Native CAPTCHA was reportedly enabled but ineffective there. Current hCaptcha and double opt-in overlap; a correctly configured current-store result and independent budget remain unknown.
Keep consequences and controls distinct
Another merchant reports a lawsuit and accessibility changes; the proceeding is unverified. Theme-update continuity remains excluded. A confirmed low-stock revision let a different merchant remove an app, with no proof of prior spend or a remaining paid gap.
Further historical sources report newsletter abuse and CAPTCHA signup friction. No observed subscriber loss or separate budget is established.
The original six contexts remain separate; the linked report adds two historical controls. Separate jobs, not a combined market or six verified buyers. Evidence, alternatives and disconfirmation.
Show shoppers a variant they can actually buy.
One specific shopping job
A June 2026 source asks for color and size to coexist on the same variant, that matching variant to be available, and filter counts to agree with purchasable results. This could matter after storefront creation becomes cheap.
The paid gap is unproved
Current native filtering, new variant collections and existing apps need an exact behavior test. One stated theme purchase is shared across three requirements; recurrence, measured consequences and an independent product budget remain unknown.
One selected context, seven published anchors and four opened official sources. No installed trial or finalist. Evidence and disconfirmation.
Location inventory and order instructions still need a paid gap.
Separate operational reports
A historical multi-store merchant reports shoppers seeing stock from another state. Another reports cart instructions disappearing before checkout and says the suggested steps did not work. Neither establishes repeated paid work or a current common defect.
Keep setup controls visible
Native pickup and note capabilities overlap parts of these jobs. A delivery badge and a larger bundle section remain configuration requests. Fulfillment and instruction handoff can outlast themes; an independently paying buyer and reason to subscribe remain unproved.
Evidence, alternatives and disconfirmation test. No finalist is selected.
Discount the checkout choice a merchant prefers.
Two historical requests ask for a bank-deposit discount and a pickup discount. Current apps advertise overlapping capabilities. A paid theme update in one conversation establishes no budget for discount software; repeated costly work and an independently paying buyer remain unproved.
Source scope, alternatives and disconfirmation. No finalist is selected.
Separate color pages need consistent stock.
One historical merchant wants distinct color pages, swatch navigation and bundles without stock-number trouble. Current grouping and inventory tools overlap parts of the job; their combined fit is untested. Repeated costly work and an independently paying operator remain unproved.
Source scope, alternatives and next research step. No finalist is selected.
What this research can establish.
Scope, snapshot and source limitations
Cutoff: 23 October 2026, 20:14:39 UTC. Both accessible inboxes and all statuses are inventoried. Full text is fetched through the thread endpoint; attachment contents are excluded. Help Scout is live, so bodies reflect retrieval time. Deleted and inaccessible records cannot be inferred. Source counts can change during collection.
Sampling and quality gates
The initial calibration sample selects a reproducibly random page from each Themes year and includes the small Apps inbox. This clustered sample is not a representative prevalence estimate. Independent held-out review must measure substantive-need precision and recall before scaling extraction. Long, multilingual, attachment-dependent and no-issue cases require additional review.
Privacy, local storage and model processing
Raw source responses stay in private local storage. The pipeline redacts selected text before account-hosted model analysis. Earlier waves found missed credential formats in earlier inputs; detected derived copies were scrubbed and normalization was revised. Prior model transmission cannot be undone. See the privacy correction below. Models still run remotely; local storage does not make inference offline. Ticket text is untrusted evidence. No customer messages or source changes are authorized.
Sources and reproducibility
Coverage comes from local SQLite records and immutable source responses. See the method and run manifest below for current counts, unresolved gaps and the next resumable action. API behavior was checked against Help Scout’s conversation documentation, thread documentation and rate-limit documentation on 23 October 2026.