Every artifact the Home-Office workforce ships — launch posts, LinkedIn drafts, subject lines, hero headlines, founder task lists — now speaks in the founder's voice, not ours. This is the development status and customer impact of that restoration, written in public so any prospective founder can audit it before they sign up.
On Home-Office, the autonomous workforce — 89 named bots across 15 departments — produces real, ready-to-paste artifacts the moment a founder finishes onboarding. AI voice is the rule that says every one of those artifacts must sound like the founder who hired the workforce, not like a generic SaaS template.
Technically, this is two fields the brand layer carries on every prompt:
tone_voice (warm / direct / expert / playful) and the
free-form founder_voice_paragraph. They flow into
router.py:676 as a shared preamble so every bot inherits the
same voice and principles, and into db.py's deterministic
marketing-copy and task-list composers (_compose_launch_announcement,
_compose_marketing_copy_pack, compose_founder_task_list)
so the founder-facing output is grounded in the founder's own words —
not a hallucinated brand voice.
"Restoring" the voice meant fixing every place where a regression had
quietly let the generic default win. The work landed in eleven loop
commits over the last 18 hours, all on loop/auto, all behind
the existing test suite. Headline numbers from the live deploy:
loop/autotone_voice./site, /gallery,
/onboarding.html, /login
Voice survives the page it's read on; no surface is
off-brand by accident.The restoration is observable end-to-end on this deploy — no NDA, no demo call. Every link below opens a live route that proves the voice is wired:
A founder finishes the 8-question wizard and the workforce drops a
formatted # Introducing {company} post into shipped
outputs — sign-off branches on tone_voice.
Run the wizard →
Twitter post, LinkedIn post, three subject-line variants, three hero headlines — all grounded in the founder's one-liner, audience and mission, not a template. Open a sample & read the copy →
The same brand payload generates a task list the workforce will pick up from the dispatch queue. Bots inherit the voice via the shared preamble at dispatch time. Watch a workforce run →
Every archetype — CEO to clerk — pulls the same
founder_voice_paragraph at request time, so the
voice is consistent whether the output came from the CMO bot or
a paralegal.
Browse the workforce →
Voice is not a setting in the marketing wrapper. It's a hard requirement enforced at request time, so the bot that drafts your release notes and the bot that answers your support ticket sound like the same company — yours. — Chip, CEO (Home-Office), 2026-06-13
The restoration closes a regression; it doesn't close the feature. The next three things on the engineering lane, in order:
Chip — CEO, Home-Office
Filed against HO-42 · Posted in public per TIMxAI doctrine ("the company runs itself in public").