Named
The agent mentioned you. It may never open your page.
Seed narrative · Agentic selection infrastructure
A flight recorder for buyer agents. Replay the task. See who survived, who got picked, and where the agent gave up. Selection share and completion are the scoreboard.
Synap1e is working on Picked. Pre-product; the system below is proposed.
01The problem
GEO measures the answer. A delegated buyer task keeps going: shortlist, verify, book, buy. A brand can clear the first three states and still lose at the fourth.
The agent mentioned you. It may never open your page.
Your page supplied evidence. That evidence may favor someone else.
You fit the task. Now the agent has to finish it.
A gate, a missing fact, a broken handoff. The agent leaves or switches.
ChatGPT named tracked brands in 33.3% of a MarketScale B2B sample and cited them in 12.8%. Overall mention rate was 26.4%; citation rate, 17.1%. These are answer metrics from Jul 7–Oct 5, 2026, not purchase outcomes.[2]
In Broadcastwell’s 860 B2B answers, vendor-authored pages accounted for 77.4% of citations among the top 100 cited domains. The category leader appeared in 80% of its category’s answers; 35% of companies were named in zero. One engine, Jul 18–23, 2026; not a market-wide census.[3]
02The proposed product
One delegated task across ChatGPT agent mode, Claude computer use, Gemini agentic tasks, and Perplexity Comet. Log the observable retrieval set, applied criteria, selection, and abandonment. Access to hidden model reasoning is not assumed.
Canonical jobs with hard constraints and a definition of done. Reuse the job across brands; otherwise every replay becomes bespoke consulting.
“Payroll for a 40-person company, multi-state, demo this week.”
“Book a pediatric dentist in Round Rock this week who sees a 20-month-old.”
“Find a carry-on under $180 that fits a Tesla Model Y frunk.”
Same task, four agents. They do not behave the same. Record each system’s visible path instead of averaging away its failure.
Working replay hypotheses from the seed brief, not Picked benchmarks or guaranteed behavior.
Who was retrieved? Who survived evaluation? Who was selected? Show which constraint flipped the decision, with the page or cited evidence attached.
Selection share: share of eligible canonical replays that choose the brand. Completion: share that reach the task’s definition of done. Neither is live buyer volume.
Cookie wall. Login gate. Stock that disagrees with the page. Missing constraint. Contradicted claim. Missing from retrieval. Give the failure a reason code, then a specific patch.
A feed field, suitability block, booking endpoint, or fact correction. A patch is a testable recommendation, not a promised lift.
Canonical task / PAYROLL-040
Definition of doneA valid demo request submitted with a confirmation. No real submission has been made.
Agent mode / illustrative trace
Selected you at #4Decision flipped on: suitable coverage.
Computer use / illustrative trace
Lost on a contradicted claimCLAIM_CONFLICTPatch: reconcile the coverage fact.
Agentic task / illustrative trace
Abandoned the demoLOGIN_GATEPatch: an actionable demo endpoint.
Comet / illustrative trace
Shortlisted; did not transactNaming a shortlist did not complete the job.
Abandon / elimination reasons
CLAIM_CONFLICTCoverage contradicted → correct the fact on the page and in independent listings.LOGIN_GATEDemo scheduling blocked → expose a usable booking endpoint.Illustrative task-set selection share
A separate, invented task-set summary, not calculated from the four displayed traces. Neither figure is a Picked customer result or an external benchmark.
COOKIE_WALLCritical facts blocked by consent UI → make the suitability block readable before nonessential cookie choices.
LOGIN_GATERequired action hidden behind an account → expose a supported booking endpoint and clear handoff.
STOCK_MISMATCHAvailability conflicts with the page → correct stock and availability in the feed field.
MISSING_CONSTRAINTFit cannot be established → publish the exact qualifying fact in a suitability block.
CLAIM_CONFLICTIndependent evidence disagrees → make a fact correction across the page, feed, and third-party record.
NOT_RETRIEVEDNo candidate-set entry → fix the relevant feed field or discoverable category suitability evidence, then rerun.
Suitability content: selection 11.4% without, 30.8% with, 2.7x at comparable rank. Correcting a wrong prior about the brand: 13.9% → 27.5%, about 2.0x. These are study observations, not promised Picked outcomes.[1]
Agents drew on prior brand beliefs in 81.6% of commands, checked 3.4 independent sources per claim, and eliminated candidates in 27.9% of conflicting-claim cases in the reported sample. The product must retain evidence, not infer an invisible thought process.[1]
The category boundary
Profound, Peec, Scrunch, and Ahrefs Brand Radar already sell the visibility answer: “were you named?” Picked’s proposed question is what happened after the buyer delegated a task.[9]
| Dimension | GEO visibility platforms | Picked / proposed |
|---|---|---|
| Unit of work | Prompt panels and generated answers | Canonical buyer task with constraints and a definition of done |
| Data | Mentions, citations, answer position, sentiment | Observable action traces, candidate survival, selection, abandoned steps |
| Scoreboard | Were you named, and how often? | Selection share and task completion on a controlled replay set |
| Recommended work | Visibility and content recommendations | A reason code tied to a feed field, suitability block, endpoint, or fact |
| Proof of value | Movement in the answer panel | The same task rerun after a patch, with a changed selection or completion outcome |
This is a funded category, not an empty market: Profound raised a $96M Series C at a $1B valuation in February 2026 and reported 700+ enterprise customers in that announcement. Its capital is a distribution risk for Picked, not evidence of demand for this exact product.[8]
03The wedge
Payroll and HR first, until the trace is undeniable. Comparable constraints, visible claims, and a demo endpoint. Do not boil the ocean.
First / B2B software
10.8%[1]
Q3 2026 category agentic share. Build one payroll/HR task library, sell repeated measurement, and require a before/after rerun.
Second option / Ecommerce catalogs
12.3%[1]
Q3 2026 category agentic share. SKU constraints, stock disagreement, feed diffs, and competitor switches. Enter only after the first category works.
Second option / Bookable local
7.4%[1]
Q3 2026 consumer and local services share. Suitability and real appointment availability. An alternative second vertical, not a parallel launch.
The largest share is not automatically the best wedge. Travel booking was 14.6% in Q3 2026; the first market remains B2B software. These category shares are First Page Sage estimates, not Picked’s serviceable market.[1]
Timing signal, not TAM: under 5% of sites optimized for agent traffic, Digidop domain audit, May 2026, via Similarweb. After OpenAI’s Jul 10, 2026 model update, about two-thirds of ChatGPT Shopping recommendations came from merchant feeds rather than crawled pages, according to Profound’s analysis cited by Verlua in Sep 2026; these were monitored prompts, not purchases.[5][6]
Commerce context ≠ Picked TAM. McKinsey, Oct 17, 2025: U.S. B2C agentic commerce $900B–$1T by 2030, global goods $3–5T. Includes AI-shaped purchases, not only agent-completed checkout. Excludes services and B2B.[7]
04Intended model / not live pricing
Charge for a repeatable selection diagnostic, not a dashboard full of names. These are proposed plans; no subscriptions, signed partners, or revenue are claimed.
Discounted
Intended research arrangement
$1,500
/ brand / month · intended
$4,000
/ month · intended
Custom
Intended private deployment scope
Gross margin only works if a category task library is reused across brands. Replay cost is not known yet. Measure runtime, retries, and human review before treating these prices as viable.
The intended moat
A First Page Sage study, Oct 2, 2026, covered 4,213 commercial prompts and 657 agentic tasks. Schema’s recommendation lift fell to 0.4 points after controlling for authority. Clarity of offering doubled recommendation rate, then leveled off. On agentic tasks, suitability and information consistency outweighed schema; this was a vendor-led study, not proof of Picked’s advantage.[4]
Permissioned, versioned paths from retrieval to a completed or abandoned task. Evidence accumulates through repeated runs; none has been accumulated by Picked yet.
Reusable jobs, constraint hierarchies, and definitions of done. A library that captures payroll buyers’ actual constraints is harder to copy than a markup checklist.
Trace → reason code → change → rerun. Keep the task and environment comparable, and record failures as well as wins. Causality still needs disciplined evaluation.
What we will not claim: no proprietary OpenAI or Google logs, no access to private chain of thought, and no platform partnership. Picked would record what its own authorized replay can observe.
05The investor question
The opportunity is a decision record that helps a brand change an outcome. The burden of proof is a successful patch and rerun, not the size of agentic commerce.
First-party selection reports could compress the category. Picked would need independent cross-agent evidence and a useful patch loop; neither is proven.
Agent UIs change monthly. Harness maintenance, task validity, and permissioned access are ongoing costs, not a one-time integration.
If category tasks do not reuse, runtime and human review can consume the subscription. The first library must prove cost reuse as well as selection movement.
Suggested / not committed
$2.5–4M
seed
A proposed financing range. No round, investor commitment, customer traction, or signed design partner is claimed.
Why this could be fundable
Build a reliable harness for the same buyer job across agents. Start with payroll and HR. Show that a recommended change moves selection share on a controlled rerun. Then learn whether buyers will pay to repeat the measurement.
Agent browser runtime · Eval harness · First B2B task library · Recruitment of 15 design partners as a target, not existing relationships.
Proof to raise against: selection share moved on a rerun after a recommended patch.
| Window | Build | Evidence to earn |
|---|---|---|
| 0–4 months | Harness for two agents and 50 payroll/HR tasks. | Stable, reviewable traces for the same task; measure replay cost. |
| 4–9 months | Four agents, abandon taxonomy, ten design partners, first before/after. | Partners are a recruitment target. Show selection share movement after a patch. |
| 9–14 months | Second vertical and self-serve Team plan. | Choose ecommerce catalogs or bookable local; prove task reuse before broadening. |
| 14–18 months | API, private task sets, renewal on selection share. | Customers renew for decision evidence, not additional mention charts. |
Research windows matter. These are dated industry studies and projections, not Picked traction. The console is an illustrative product sketch. Agent-specific replay behavior is a hypothesis to test. The pricing, financing, and roadmap are proposed.