Chip-first bid walkthrough that works on the phone

One question, one answer chip

Prompts ask; chips answer. Prefer trade words: job, footprint, remodel, rough-in. Avoid software words like configure, select an option, or let AI pick.

Keep chip labels short enough for one line on a folded outer screen (~18 characters). Long chips stack and slow a gloved thumb.

Local craft before cloud round-trips

On-device rules for takeoff, quote checks, and schedule shifts keep the walkthrough alive in basements, steel buildings, and trucks. Frame local as a benefit — right here on the phone — never as degraded mode.

When a request falls outside deterministic rules, say it needs a person, not that the model failed.

Carry site, client, and notes into the PDF

The proposal the client receives must show the same site address, client name, scope notes, and trade lines the estimator just walked. Generic demo language is a field UX bug, not a content polish issue.

Site photos attach to the bid and print in the PDF; videos stay on the bid record with a playable link from bid detail.

Ask TBC entry that does not break the job

Put Ask TBC where the estimator already is: bid generator and bid detail. Pass the current project name, client, site, divisions, and notes so the walkthrough starts mid-job instead of from a blank greeting.

Greeting lock (craft voice): On-site bid walkthrough. Tap a chip and I'll build the proposal from your numbers — right here on the phone.

Seven-minute check still applies

Before shipping a chip flow, run the existing seven-minute glare-and-glove test on the crew’s own device. If chips miss under glare or gloves, fix the tap targets before adding more features.