Skip to content

Field Notes

Lessons from the work, not the brochure.

Notes from inside real implementations: what we mapped, what surprised us, and what we learned only after the systems went live. No predictions, no generic AI takes.

Many identical-looking signal lines arriving from the left, converging at a single triage node, then leaving sorted into prioritized channels of different weights: undifferentiated requests being triaged and routed.

Field Notes · June 6, 2026

The maintenance request isn't the problem. The triage is.

Every maintenance request arrives marked urgent. Inside the property management companies we built for, the real job was never the repair. It was triage: deciding which requests are real, who owns them, and in what order.

Read the note
A flow of signal lines moving left to right, with several branching off into a separate parked, idle cluster: work pulled out of the flow and waiting on something outside the firm.

Field Notes · June 6, 2026

The work wasn't accounting. It was waiting.

Map an accounting firm as a system of queues and one of them is missing from every tool the firm owns, the queue that sets the pace. After building automation inside several firms, the constraint was almost never the accounting. It was the waiting.
Many tangled signal lines on the left resolving into a single calm, uninterrupted line on the right: scattered front-desk attention becoming focused.

Field Notes · June 5, 2026

What automating the dental front desk actually taught us

Inside the dental practices we built for, the front desk was never short on hands. It was short on uninterrupted attention, and almost everything we learned about automating it started from that one correction.