Zero Click San Francisco

San Francisco briefing for the zero-click market.

A hands-on session for teams building agent workflows and answer-engine scorecards.

Planned Field Room

San Francisco focuses on the sources, prompts, and workflows shaping local AI answers.

How do supervised agents turn answer evidence into approved work without becoming black-box automation?

Request invite

December 2026Planned

San Francisco market scope

Product, growth, data, and engineering teams building the first agent workflows for answer operations.

Agent templates

briefs, source plans, schema fixes, PR targets, and answer review workflows

Runtime controls

inputs, nodes, reviewer gates, artifacts, exports, and proof linkage

Data handoff

analytics, warehouse, CRM, CMS, Slack, and API boundaries for scoped events

AgendaWorking room

01 AI answer behavior

Review how prompt families, engines, regions, and competitors change answer state.

02 Source strategy

Map the owned, earned, partner, retail, publisher, and community pages that AI systems trust.

03 Agent workflow design

Translate gaps into supervised briefs, source plans, technical fixes, PR targets, and owner queues.

04 Measurement and proof

Define what moved, what is inferred, what remains unknown, and what the next review inspects.

OutputsTakeaways

Answer-market map

Prompt families, engine behavior, competitors, citations, source classes, and open risks.

Action backlog

Owner-ready source, content, PR, technical, and commerce work with expected answer movement.

Proof cadence

What can be measured now, what remains inferred, and how the next review runs.

Pilot scope

One market, one competitor set, one answer map, and a decision on whether to operate monthly.

Room ReadinessPlanned status

Planning window

Date, city, and theme are directional until venue, attendee list, and final agenda are confirmed.

planned

Attendee fit

Best for operators with active prompt, source, answer-risk, agent-workflow, or proof questions.

fit

Evidence policy

Use public, anonymized, or customer-approved examples only; no private customer material in the room.

governed

Pilot path

The most useful output is a scoped Pilot Map, not a generic networking recap.

pilot

Room Protocol4 steps

01 Pre-read

Share the market question, prompt families, source classes, and proof caveats before the room opens.

02 Live map

Build a shared answer-market map with engines, sources, risks, owners, and unknowns visible.

03 Work queue

Translate findings into page, source, PR, commerce, technical, or agent-run work packets.

04 Closeout

Leave with a proof cadence, pilot scope, and decisions on what remains unclaimed.

Operating ObjectsBriefing packet

Prompt Graph

briefs, source plans, schema fixes, PR targets, and answer review workflows

signal

Source Map

inputs, nodes, reviewer gates, artifacts, exports, and proof linkage

source

Risk Ledger

analytics, warehouse, CRM, CMS, Slack, and API boundaries for scoped events

risk

Pilot Map

market boundary, owner queue, proof cadence, and next-cycle decision

pilot

GuardrailsHonest planning

Planned field room

Dates are planning windows until the attendee list, venue, and agenda are confirmed.

Sample evidence

Example surfaces are product demonstrations, not claims about attendee data or customer outcomes.

Attribution caveat

Crawler events, referrals, and answer deltas are discussed with confidence labels and caveats.

Human approval

Agent workflows produce drafts and recommendations; customer owners approve publication or external action.

Start with the map

Start with one market map.

Request the pilot