Field notes

Journal

How a message becomes a job you can trust. Product thinking, not launch posts.

006

No. 006 · Operations

Field service requests start in chat, not in a job form

Most field tools start once a job form exists. The request already lives in WhatsApp, SMS, email, or a call. The hop after that is where jobs get lost.

Read the note

12 Aug 2026 · 10 min

Earlier notes

5 notes

005

AI drafts the field job. You still approve it.

The model can turn a sentence into fields. It does not create the job, assign a crew member, or invent a price. A person still lets the work through.

8 Aug 2026 · 11 min

004

When AI cannot answer, handoff is the product

When the latest message cannot be answered from your FAQs, hours, or catalog, software should hand the thread to a person, and say so. That is a feature.

28 Jul 2026 · 10 min

003

Field

Crew need the job record, not another inbox

A crew member on a driveway does not need another chat to babysit. They need the job record: site, window, checklist, photos, and a close the customer hears.

14 Jul 2026 · 10 min

002

Company

One field operations product, not a pack per trade

We do not ship an HVAC edition, a cleaning edition, or a property edition. The product is one path. The first conversation is still how your week runs.

30 Jun 2026 · 10 min

001

An AI with the wrong company's data is a leak

If the model can read the inbox, retrieval still has to stay inside your company. Another company's history is not extra context. It is a leak, full stop.

18 Jun 2026 · 10 min