Sitescribe
An SMS-first, voice-to-field-management writer for small trade shops: a worker texts a number, speaks an update, and it lands in the shop's field-service system with a geo-tagged photo attached — no app to install.
A worker on the roof has one hand on a ladder and a phone in the other. The update that matters — demo done on the third floor, water damage at the northwest corner, two more days needed — never makes it into the shop's field-service system, because logging it means opening an app, finding the work order, and typing on a jobsite. So it gets shouted to the foreman, or it gets lost, and the office reconstructs the day from memory. The structured record the back office needs and the friction the field will tolerate are at war, and the field always wins.
The owner or operations lead of a 10-100 employee trade shop or small general contractor already running on a field-service platform — the person who pays for that system and personally absorbs the cost of a field that won't feed it data.
Field workers won't install apps while the back office needs structured data; an SMS-and-voice writer resolves an adoption-versus-data conflict that SMS, voice AI, and field-service software each leave unresolved on their own.
Five-of-five model consensus that the underlying voice stack is now commodity, an April 2026 open-source release validating no-app SMS distribution, and a platform incumbent's board-level AI move starting a 12-18 month clock on the single-platform portion of the wedge.
It was unbuildable until the voice stack commoditized in 2026; with that done, the defensible work shifts to trade vocabulary and the cross-platform writer layer.
A genuine adoption-versus-data tension that no single existing part resolves alone, sitting on a voice stack that only commoditized in 2026, with a structural blindspot the incumbents can't close and an external open-source proof that the no-app distribution pattern works now.
Defensibility has to be earned in vocabulary depth and the cross-platform router, not in the technology itself; the integration surface for v1 is wide and largely uncatalogued; and write-access to some field-service systems may be partner-gated, which would strain the core loop.
Genesis doesn't invent in isolation — Sitescribe shares architecture with, or powers, these ideas.
Discussion
No comments yet — be the first to weigh in.