BecomingIQ · Specialist Line

Westbrook Landscape Group · Plant Specialist · v0 demo · Goodmark Nursery

Sales-Call Demo Flow · D6

Plant Specialist v0 · Demo Briefing

A 5-minute call: 30-second hook, 2-minute walk, 2-minute close. Operator-side voice — Westbrook queries Goodmark, every spec attribute cited, every claim auditable. Roadmap visible on the surface. Crew doesn’t wait on Dan’s callback.

Status

v0 build complete · all 6 deliverables shipped · Surface A openable

Demo-Ready · Show on becomingiq.com

32

Plant SKUs · calibrated

4

Authority tiers

4

Agent positions

~15 hrs

Per additional grower

Contents

  1. Pre-call setup
  2. The 30-second hook
  3. The 2-minute walk · 3 moves
  4. The close moment
  5. Objection handling · 8 anticipated
  6. Cross-demo continuity with Vendor
  7. Posture notes (do not abandon)
  8. Failure modes · catch yourself
  9. Sample queries cheat sheet
  10. The build behind the demo
  11. Pattern membership · roadmap
  12. Scope · what v0 does not promise
01

Pre-call setup

60 seconds before connect

Deploy URL pattern

Cold demo surface-a-plant-lookup.html (local) or becomingiq.com/_demo/plant-specialist

Per-prospect becomingiq.com/{slug}/plant-specialist/ via proto skill

Surface preload

Open Surface A. Sample chips visible: Redpointe Red Maple · Karl Foerster · Swamp White Oak · Winterberry Holly. Zoom 110-125% for screen-share. Keep sample-queries.md in a second tab for failure-mode beats.

02

The 30-second hook

Lead with this
Setup

Frame the demo in one sentence.

5 sec
Demo host Quick demo. This is Plant Specialist. Drop a plant name. Comes back with the spec — every line cited — and your grower’s current availability. Watch.
Move

Click Redpointe Red Maple. Let it render. Silence helps.

15 sec

Point at the spec card top line: scientific name + cultivar + trademark + patent stack.

Land

Name what came back.

10 sec
Demo host Redpointe Red Maple. Acer rubrum ‘Frank Jr.’, trademark Redpointe, patent PP16769. Zone 4 through 9. Forty-five by thirty mature. JFS breeder cited. Morton Arboretum cited. Missouri Botanical Garden cited. Below — Goodmark has it in three calipers, list price published, last refreshed eight days ago. Your crew doesn’t wait on Dan’s callback.
03

The 2-minute walk · 3 moves

~120 sec total
Move 1

Cite-by-cite drill

40 sec

Click the citation tier-tag on the hardiness zone line.

Demo host Watch this. Every line on the spec card has a citation. Tier 1 — Morton Arboretum, USDA, land-grant universities. Tier 2 — extension services. Tier 3 — trade pubs. Tier 4 — grower-confirmed, that’s Dan. The agent never writes a plant fact it can’t cite. Public LLMs hallucinate plant facts — wrong zone for a cultivar, wrong dig window. This doesn’t. The evidence layer is the ground truth. If the layer doesn’t carry it, the field stays empty.
Move 2

The dioecious gotcha

40 sec

Click Winterberry Holly. Point at dioecious: true right at the top of the spec card.

Demo host Right at the top — dioecious: true. Male pollinator required. ‘Jim Dandy’ or ‘Southern Gentleman’ for most female cultivars. If a contractor plants only the female and doesn’t know — they get no berries in February. Public LLM might not surface that until the customer’s already in trouble. This agent surfaces it every time, because it’s in the evidence layer. The wedge isn’t ‘agent knows plants generically.’ It’s Goodmark’s calibrated layer, with Dan’s register, instantly.
Move 3

The roadmap affordance

40 sec

Point at the Alternative Finder · designed for next build card below the sourcing card. Mandatory beat · Amendment E

Demo host See this card down here — ‘designed for next build.’ That’s Position 4’s Alternative Finder. When the first plant isn’t available — say Goodmark is out of #15 Redpointe — the agent will surface alternatives that hold the design intent. Operator picks which alt holds. Agent doesn’t recommend; it surfaces the trade-offs. That’s the v0.1 build. v0 covers plant-name spec + sourcing — exactly what your crews ask all day. Alternative Finder ships next.
04

The close moment

~60 sec

Pivot to extension

Demo host This is one grower’s calibrated layer. Goodmark’s. Westbrook works with Wilson, Fiore, Midwest Ground Covers, others. Each one gets the same shape — same schema, same standards framework, same agent crew — via the extension methodology. About 85 hours for the first install; 15 hours per grower after that. Your operator’s full preferred-grower picture, calibrated.

The ask · three options

Demo host Want to see this with your data? Three options. One: tell me your top three preferred growers and one of them gets the v0 evidence-layer treatment as your first install. Two: skip ahead and show me what plant-spec questions your crews ask all day — we calibrate to that. Three: do nothing, see if I haven’t bothered you again in 30 days.

The 85-hour promise

Demo host First grower install runs about 85 hours over two-to-three weeks. That includes the calibration call with your grower owner — Dan equivalent. Schema-first, evidence-layer build, ANSI Z60.2 alignment, citation discipline per attribute. After that, your other growers come in at ~15 hours each. No signup, no portal, no contract until you’ve seen one in your hand.
05

Objection handling

8 anticipated · ranked by likelihood
Objection Likelihood Response
O1 · “Can’t I just Google this?” High Public answers don’t know your grower’s specific calibers, dig windows, or Dan’s calibration on Beech Leaf Disease or ALB in your region. The wedge is Goodmark’s plants, against Goodmark’s availability, with Goodmark’s register — not generic plant knowledge.
O2 · “Does it have all 399 SKUs?” High 32 today — the seed records, fully calibrated and citation-grade. Extension methodology documents how we reach 399. ~85 hours for first install; ~15 hours per additional grower. Calibrated depth on what your crews actually spec, expanding as gaps surface.
O3 · “What about daily availability changes?” Medium Today: dated xlsx refresh — freshness signal flags rows > 30 days old. v0.1 path is live-feed integration (cron or API). Typically discussed during the Dan calibration call. Not load-bearing for v0; meaningful for v0.1.
O4 · “Is it just an LLM with a system prompt?” High No. Authority-disciplined retrieval against a citation-traceable knowledge layer. Public LLMs hallucinate plant facts — wrong zones, wrong dig windows, made-up patent numbers. This agent reads the evidence layer or doesn’t write the attribute. Grounded retrieval, not smarter generation.
O5 · “What if a plant isn’t in the layer?” Medium Agent says so honestly. Click Hostas:
“This plant isn’t in Goodmark’s current calibrated knowledge layer. Want Goodmark’s availability listings, or escalate to Dan?”
Two follow-up paths. Honesty over coverage.
O6 · “Does Dan have to maintain this?” Medium Methodology covers ongoing maintenance — it’s not Dan’s role to populate fields. First calibration captures his register and microclimate notes. After that, extension is a documented process. Dan’s time is the constraint we’re relieving, not the constraint we’re multiplying.
O7 · “What about Wilson, Fiore, MGC?” High Extension methodology covers them at ~15 hours per grower after the first install. v0 is Goodmark-only by scope — clean wedge, validate the pattern. Multi-grower extension is v0.1, named on the demo as the next build.
O8 · “Where does this run?” Low Demo runs at becomingiq.com/_demo/plant-specialist; production deploys per your install practice (operator dashboard, crew-side app, or grower portal). v0 is operator-side: your crew queries your grower. v0.1+ supports posture-toggle when grower-side becomes the answer for your shop.
06

Cross-demo continuity with Vendor

When both walked together

Demo sequence (Vendor → Plant)

  1. Open with Vendor Surface C. “Westbrook just got a quote from Lurvey. Watch what comes back.”
  2. Land the rep-quote sanity check. +8% above operator’s own basis on the sample Lurvey quote.
  3. Pivot to Plant Specialist Surface A. “Same Westbrook. Now their designer is specifying a Redpointe Red Maple for that DuPage residential job. Watch the read.”
  4. Land the spec + sourcing two-stack. Redpointe full citation stack + Goodmark availability.
  5. Name the pattern. “Both specialists ride the same family architecture. Operator over slow-moving catalog joined to fast-moving live-state signal. Operator-deference posture — agent surfaces, operator decides. Each grower or vendor calibration takes ~15 hours after the first install.”

What stays consistent

Same operator (Westbrook). Same family posture (operator-vs-self anchor · intelligence ON existing relationships · passive reads, not recommendations). Same authority discipline (different substrates, same trust mechanic). Same Chicagoland regional spine.

What distinguishes

Vendor’s wedge: intra-vendor pricing intelligence + rep-quote sanity check — the “your rep is quoting ~$150 high” beat. Plant’s wedge: spec + sourcing two-stack on preferred grower with citation-grade authority — the “your crew doesn’t wait on Dan’s callback” beat. Different surfaces: Vendor’s Surface C is quote-drop; Plant’s Surface A is name-lookup.

07

Posture notes

Do not abandon
  • Operator-deference is the anchor. Never say “you should plant X instead.” Agent surfaces; operator decides. The only forward-looking surfacing is the Alternative Finder roadmap affordance — framed as “designed for next build,” not “instead try this plant.”
  • Authority discipline is non-negotiable. Citations on every spec attribute. “Drop the citation chips” isn’t a feature request — it’s an erosion. The citation chips are the wedge.
  • Operator-side voice (Amendment D), not grower-side. Westbrook queries Goodmark. “Dan-is-not-the-bottleneck” is told from the operator’s side. Never say “Goodmark deploys this for their customers” in v0 demo.
  • Goodmark only in v0 (Amendment B). No Wilson / Fiore / MGC / Lurvey plant data. Multi-grower is the v0.1 promise.
  • Lurvey is out of Plant Specialist scope entirely (Amendment A · retail). Lurvey may appear in Vendor demo; Plant Specialist does not query Lurvey rows.
  • Synthetic operator is upfront. “Westbrook is synthetic, built to demo against” lands before any prospect asks. The Goodmark evidence layer is real (32 records, real Tier 1-4 citations); only the operator wrapper is synthetic.
  • Roadmap affordance is mandatory, not optional (Amendment E). Alternative Finder · designed for next build appears on Surface A and is pointed to during Move 3 of the 2-minute walk. Skipping it leaves prospects thinking Position 4 is unfinished rather than scoped.
  • Methodology vs Installation layer separation in talk. “Methodology is portable, installation is per-grower.” Don’t say “the agent is portable” (vague) or “we’d rebuild it” (false).
08

Failure modes · catch yourself

5 common drift patterns
If you say… Catch and reframe as
“The agent recommends planting Acer rubrum because it tolerates compacted soils” “The agent surfaces that Acer rubrum tolerates compacted soils, cited to Morton Arboretum. Your designer decides if that matches the job spec.”
“Goodmark deploys this for their customers” “Westbrook’s crew queries Goodmark — Westbrook’s preferred grower. v0 is operator-side. Grower-side deployment is documented but not in v0 demo.”
“The agent knows about Redpointe Red Maple from training data” “The agent reads the evidence-layer record for Redpointe — the same authority-disciplined source Morton Arboretum’s citation would point you to. If the layer didn’t carry it, the agent wouldn’t say it.”
“Want me to find an alternative if Goodmark is out of stock?” “Alternative Finder is v0.1 — designed for next build. v0 covers plant-name spec + sourcing. The roadmap affordance shows where that lands.”
“The agent works across all your growers — Wilson, Fiore, MGC, Goodmark” “v0 is Goodmark-only. Extension methodology brings in Wilson, Fiore, MGC at ~15 hrs per grower. v0.1 promise; not v0 capability.”
09

Sample queries cheat sheet

Rehearse before demo

Redpointe Red Maple

Lead query · richest record · trademark + cultivar + patent stack

“JFS introduction. Patent-protected. Morton Arboretum cited the hardiness zones, the breeder cited the genetics, Missouri Botanical Garden cited the cultural needs. Three calipers in stock, list price published.”

Karl Foerster Feather Reed Grass

Perennial Plant of the Year 2001 · awards field · perennial category

“Perennial Plant of the Year 2001. Plant Association called it 21 years ago and it’s still the bones of half the DuPage commercial plantings.”

Swamp White Oak

Illinois native · EAB-replacement narrative · rain-garden landscape use

“Illinois native — three citations to back it. Tolerates compacted urban clay. Note flags it as a Morton Arboretum-recommended EAB replacement.”

Winterberry Holly

Dioecious gotcha · operator-must-know surfacing

“Dioecious flag is the saver. Without the male pollinator, the female cultivar doesn’t fruit. Public LLM might miss it until the customer’s already in trouble in February.”

Accolade® Elm

Morton Arboretum bred · high DED resistance · regional pride

“Bred by Morton Arboretum — twenty minutes from Westbrook’s shop. Vase form, classic American elm silhouette, high DED resistance.”

Hostas

No-match deference state · honesty-over-coverage demo beat

“No matching record. Agent says ‘Goodmark’s calibrated layer doesn’t carry this — want the availability listing OR escalate to Dan?’ Operator-deference posture in action.”

10

The build behind the demo

D2 crew · D4 data flow

Agent crew · 4 positions (Hook B+ recalibrated)

Position 1

Plant Catalog Reader

Reads materials_catalog Goodmark-scoped. Match strategy ladder: scientific exact → fuzzy → common → trademark. Returns ALL matched rows; no “best” pick.

Position 2

Availability Reader

Extracts supplier_info + size_options + import_metadata. Emits sourcing rows sorted by size. Freshness warning if last_updated > 30 days.

Position 3

Intent Matcher

Normalizes plant identity (common · scientific · trademark · patent). ICNCP formatting. Capability-boundary routing hints (design_intent · multi_grower) without enforcing.

Position 4

Specification Surfacer

Reads evidence-layer record by scientific_name. Authority discipline: cited or omitted. Assembles spec_card + sourcing_card + citations + deference posture. Reshape from Alternative Finder per Amendment C.

Data flow · three flows

┌──────────────────────────────────────────────────────────┐ │ BUILD-TIME compile │ │ seed-database-v1.md ──▶ compile-seed-database.py │ │ ──▶ plants.json (32 records · 0 ✗)│ ├──────────────────────────────────────────────────────────┤ │ INGEST │ │ 4.28.26-Availability.xlsx ──▶ ingest-goodmark.ts │ │ ──▶ materials_catalog │ ├──────────────────────────────────────────────────────────┤ │ QUERY-TIME │ │ query ──▶ P3 Intent ──▶ P1 Catalog ──▶ P2 Availability │ │ └──▶ P4 Surfacer │ │ ──▶ plant-spec-response envelope │ │ ──▶ Surface A two-stack render │ └──────────────────────────────────────────────────────────┘

Methodology layer (portable)

Schemas (5) · agent-crew architecture · standards framework (4-tier authority) · extension methodology (~85hr first / ~15hr Nth) · citation propagation rules · deference templates. No grower-specific tokens.

Installation layer (Goodmark-specific)

Compiled plants.json (32 records) · materials_catalog Goodmark-scoped rows · Dan’s register in deference strings · Surface A’s embedded 12-plant demo subset.

Amendments locked at spec close (S3)

A Lurvey dropped from Plant Specialist v0 substrate (retail · permanent unless wholesale surfaces) B Goodmark-only v0 scope; multi-grower via extension methodology v0.1+ C Hook B+ lead surface (spec + sourcing two-stack); Position 4 reshape Alternative Finder → Specification Surfacer D Operator-side deployment posture for v0; Westbrook queries Goodmark; grower-side held in reserve E Alternative Finder roadmap-note affordance visible on demo (mandatory · “designed for next build”)

11

Pattern membership · roadmap

Family altitude

Pattern: interface-agent-over-evidence-layer

Plant Specialist v0 is Instance N of the pattern. Per the evidence-layer README, three current confirmations: Wilson’s Intelligence (production at wolfcouncil.com/wilson) · Plant Specialist (this build) · Unilock contractor blitz (verify source at use time). Candidate named capability class: Interface Agents.

Catalog-keeper graduation entry brief at _build-close/catalog-keeper-graduation-entry-2026-05-14.md — founder paste-and-confirm pending.

v0.1+ paths named (not built)

ALive Goodmark availability feedReplace dated xlsx with cron / API. ~10-20 hrs once. Trigger: Dan calibration call.
BWilson · Fiore · MGC extensionPer-grower evidence layer + ingest + scope mapping. ~15 hrs per grower after first install.
CMulti-grower cross-availabilityPosition 1 returns rows across growers; per-grower availability comparison. Depends on Path B.
DProject Intake capture handoffJob Measurement capture → Plant Specialist query auto-populate. ~10-20 hrs.
ESynthetic persona register variation2-3 demo personas with different registers (CLT/ISA · Master Gardener · retail).
FPosture toggleOperator-side ↔ grower-side framing on single surface. Earns answer via real demo runs.

Held-open at family altitude

Specialist Frame shared runtime shell — the “extract the common code” question. Held until N=3+ Specialists earn it (Vendor · Plant · Asset). Do not pre-resolve at N=2.

12

Scope · what v0 does NOT promise

Do not silently expand
  • Does not pitch the Specialist Frame shared-runtime-shell concept (held-open until N=3+ specialists)
  • Does not promise Alternative Finder behavior in v0 (Amendment C · v0.1+)
  • Does not promise multi-grower lookup in v0 (Amendment B · Goodmark-only)
  • Does not promise live-feed integration in v0 (xlsx refresh discipline; live feed is v0.1 Path A)
  • Does not promise design-intent matching (Hook A · v0.1+)
  • Does not promise RFQ line-item entry (Hook C · v0.1+)
  • Does not lead with grower-side framing (Amendment D · toggle is v0.1+)
  • Does not lead with the pattern-membership beat — reserved for sophisticated-buyer calls
  • Does not promise QB write-back · capture-handoff · purchase-history integration (Vendor’s surface)
  • Does not promise plant-decision recommendations (Constraint #1 · operator-deference is load-bearing)

If a prospect asks about any of the above: “Not yet · would that be useful?” Capture for downstream prioritization. Don’t commit.