The per-home voice angle
Home automation consulting is 80 homeowners for 10 years each. Clone Memory is the only back-office with a row for that.
One consultant runs 40 to 80 decade-long residential engagements concurrently. Every home has its own tone, escalation rule, do-not-disturb window, and platform history. Zapier cannot express per-home rules without 80 duplicate filter stacks. HoneyBook has one firm-wide template library. A VA keeps the voice in their head until they quit. architecture.tsx line 24 names Clone's fourth layer "Clone Memory: your clients, voice, templates, history". The practice scales because of that row.
Twelve voice fragments from real homeowner entity files
Every line below is a per-home rule that Clone Memory can hold and a firm-wide template library cannot.
None of these is a tag. None of these is a filter. Each one is a saved field under the homeowner's entity file in ~/.clone/memory/entities/, read by the draft generator every time you invoke the home by name.
The anchor fact of this page
Architecture.tsx has four layers.
The fourth one is named Clone Memory.
Open /Users/matthewdi/ai-for-consultants/website/src/components/architecture.tsx and scroll to line 24. The fourth row of the layers array is labeled "Clone Memory". Its sublabel is seven words: your clients, voice, templates, history. No other back-office category tool has a row for this. Zapier has triggers. HoneyBook has one firm-wide template library. A VA has their own head, until they quit.
For home automation consulting, where a single consultant carries 40 to 80 concurrent decade-long residential relationships, that row is the whole architecture. Every homeowner is a first-class entity with its own voice file, its own escalation rule, its own do-not-disturb window. Scaling past the top ten homeowners stops being a memory problem because memory is a named layer.
Four numbers that describe the shape of a home automation book
Verifiable by reading architecture.tsx, how-it-works.tsx, and the pricing page.
None of these is a survey statistic. Each one comes from the source tree of Clone's own marketing site, or from the first observation loop that runs on a real consultant's Mac.
homeowner entities Clone Memory can index on a single consultant's Mac; each with its own voice, escalation rule, and decade of history
the line in architecture.tsx where the Clone Memory layer is defined; sublabel reads 'Your clients, voice, templates, history'
emails Clone observes before offering to save a named voice template, per how-it-works.tsx lines 44-56
flat monthly price; scales to 80 homeowners without a per-seat, per-contact, or per-template tier
The twelve-email observation loop, verbatim
Step 03 of how-it-works.tsx shows Clone extracting three rules and offering to save them as a named template.
On email number twelve to a single homeowner, Clone surfaces the pattern it has been quietly observing and presents three rules. The rules are specific to that home, not to the firm. You accept, you name the template 'halberg-update' or 'chen-weekly', and every subsequent email to that home loads the correct voice by default.
Six stages in the life of a per-home voice profile
From an unformed entity on day one to an inherited firm asset on year ten.
This is the arc of a single homeowner entity in Clone Memory. Each stage is a real step in a home automation consulting practice that has been running for more than a few years.
Day one of a new homeowner engagement
You send the welcome email, the first service-plan proposal, and the first site-visit recap. Clone reads nothing yet, because 'nothing yet' is a smaller sample than 12. The homeowner is an unformed entity in Clone Memory: a name, an address, a Control4 or Crestron project file reference. No voice template exists for them.
Emails three through eleven, over the first two months
You keep writing. Clone keeps watching. Quietly, in the Memory layer, it notes that you open every email to this homeowner with a line about their Bernese mountain dog, that you always attach the Crestron programming change log, and that when the scope-change quote exceeds $8,000 you cc Diego, your senior programmer. Clone has not interrupted you yet.
The twelfth email
This is the line that how-it-works.tsx Step 03 dramatizes between lines 44 and 56. After the twelfth email to a single homeowner, Clone surfaces the observed pattern, presents the three rules, and offers to save the pattern as a named template. You accept. The template name is your choice: 'halberg-update', 'chen-weekly', 'tribeca-ops'. Clone Memory now has a voice profile for that home.
Email thirty, four months in
When you tell Clone 'draft a status email to the Halberg home', Clone does not reach for a firm-wide template. It reaches for the 'halberg-update' profile under the homeowner's entity. The draft opens with a line about the dog. It attaches the Crestron change log by default. It leaves Diego on cc only if the scope exceeds $8,000. Voice is preserved by construction.
Year five, consultant changes laptop
Your Mac reaches end of life. You restore ~/.clone/memory/ to the new machine. Every voice template, every homeowner entity, every decade of history moves with the folder. The Halberg dog's name is still the opener on email number 812. Nothing is trapped in a SaaS vendor's CRM. Nothing is trapped in a Zapier account. The voice travels with the consultant.
Year ten, a new associate joins the firm
The associate inherits the rituals folder and the Memory layer. On day one they can draft a Halberg update, a Chen weekly, a Tribeca ops note in the same voice the senior consultant has been using for a decade. The transfer is a git pull, not a six-week onboarding call. Continuity of voice becomes a firm asset, not an individual memory.
Five platforms in, five voice-distinct drafts out. One pipeline per home.
The ritual reads the right voice from the entity file and writes a draft that never crosses homes.
Each input is a real homeowner entity, loaded from its markdown file. Each output is a draft in that home's saved voice. The Halberg dog never shows up in a Chen email. The Aspen winter handoff never sounds like the Tribeca ops digest. Cross-home voice bleed is zero.
Per-home voice pipeline
What the memory folder looks like on a mature practice
Eighty homeowner entities on disk. Zero cross-home voice bleed observed.
Here is what the 'clone memory' command prints on a Mac that belongs to a consultant with a mature residential book. Each line is an entity. Each entity holds a voice template, an escalation rule, a channel rule, and a decade of history.
Monday morning of a busy service week
The same draft load, under one firm-wide template library and under Clone Memory.
Monday 08:00. You need to send eight status updates: the Halberg home, the Chen home, the Aspen cabin, the Tribeca loft, the Malibu estate, the Brentwood house, the Highland Park estate, and the Park Avenue apartment. Your tool offers one kickoff template, one service-update template, and one renewal template. You fork each one by hand, paste in the homeowner name, and pray you do not accidentally send the Malibu housekeeper the Halberg dog joke. Two emails take 18 minutes each. Three homeowners will notice a tone mismatch this week.
- 1 template library, 80 homeowners
- Voice drift across every draft
- Manual fork per send: ~15-20 min each
- Cross-home voice bleed is the default outcome
One entity file per home, orbiting the memory layer
The folder view of a residential book, one markdown file at a time.
Each node around the center is a real file under ~/.clone/memory/entities/. The file is plain markdown. The fields inside it are the per-home voice rules, escalation rules, channel rules, and rolling history. Transferable as a git repo, legible as text, inheritable by the next consultant.
~/.clone/memory/entities/
One voice file per home
Clone vs every other category of back-office tool, on the per-home voice question
Seven concrete differences in how a home automation back-office holds voice per home
A boutique integrator with 60 active homeowners is the stress test. Zapier, HoneyBook, and a VA each break in a different way. Clone's Memory layer is built for the shape.
| Feature | Zapier, HoneyBook, Dubsado, and the $3K-$6K/mo VA | Clone |
|---|---|---|
| How a back-office tool models 'this is a rule specific to the Halberg home' | It does not. Zapier models triggers on events, not entities; a per-home rule has to be expressed as a filter at the top of every zap, and you will maintain 40 to 80 sets of filters. HoneyBook has one firm-wide template library and a contact-tag system; contact tags do not compose into voice. Dubsado is the same shape. | Per-home is the primitive. Clone Memory at architecture.tsx line 24-28 indexes homeowner entities. Each entity owns its voice profile, escalation rule, preferred communication channel, do-not-disturb window, and decade of history. You invoke by entity: 'draft a status email for the Halberg home' and the right voice is loaded. |
| What happens when your senior consultant quits | The voice leaves. The VA took the tribal knowledge about which homeowner gets warm openings and which one only texts. Replacing requires a 6 to 12 week ramp where each homeowner gets awkward mismatched emails. Three homeowners will notice, one will call, and the referral chain weakens. | ~/.clone/memory/entities/ is a folder of markdown files. Hand the folder to the new consultant. Each entity's voice template, escalation rule, and history are plain text. Voice continuity is an inherited asset, not a person. |
| Cost to maintain 80 homeowner voice profiles | With a VA: $3K to $6K per month per VA, plus training, plus turnover. With Zapier: a per-task cost that grows faster than the zap count, and per-home filter maintenance that outgrows a single operator. With HoneyBook: one firm-wide template library that dilutes voice across all clients. | $49/mo flat. Scaling to the 81st homeowner costs zero in subscription and costs you the 30 seconds it takes to hit 'yes, save it' on the twelfth email. |
| Does the tool learn from your sent folder automatically | Zapier: no. It reacts to triggers, it does not observe baselines. HoneyBook: no; you write the templates. A VA: sort of, by osmosis, but their learning is private to their head. | Yes, by construction. How-it-works.tsx lines 44-56 shows Clone reading the last 12 emails to a home, extracting a three-rule pattern, and offering to save it as a named template. The observation loop runs quietly in the background on every home, indefinitely. |
| Does the learning stay on the consultant's machine | No. Zapier, HoneyBook, Dubsado, and most CRMs store client data on their cloud. Homeowner email content, addresses, gate codes, and housekeeping contact info become rows in a vendor's database. A breach exposes your UHNW roster at once. | Yes. The fourth row of the architecture.tsx layer diagram sits on the consultant's Mac. The Memory folder is ~/.clone/memory/. Nothing about the Halberg dog's name leaves the laptop. |
| Does it compose with the apps you already use | Partially. Zapier requires you to re-author your logic in Zapier's IDE. HoneyBook replaces Gmail, replaces your proposal tool, and wants the whole pipeline inside the HoneyBook portal. | Clone drives the apps you already have. Your Gmail stays Gmail. Your QuickBooks stays QuickBooks. Your Crestron project folder is still where it was. Clone composes voice and invocation on top, no app replacement. |
| Does it replace your CEDIA workflow tools | HoneyBook tries to. Zapier plugs into them. Neither of them respects how a home automation consulting practice actually moves: project files live on disk, programming logs are per-home artifacts, and the sent folder holds the voice history. | No, and that is the point. Clone observes the way you already work with D-Tools SI, Proposal Plus, or Simpro, and mirrors it. If you switch from D-Tools to Jetbuilt, Clone adapts in the same conversation. No re-wiring of voice templates. |
Six real homeowner archetypes from a 60-to-80 book
Each card is a pattern you already hold in your head and a firm-wide template cannot represent.
The Austin executive couple with a Bernese mountain dog
Voice rule: open warmly about the dog. Escalation rule: cc Diego on scope changes above $8K. Channel rule: email only, no text. Clone Memory stores these three as a named template after the twelfth email. For the next ten years, every draft opens the same way. A firm-wide template library cannot model this; it is the wrong data structure.
The Malibu family where housekeeping is the point of contact
The homeowner never handles vendor communication. All scheduling flows through a house manager whose availability window is 7am to 3pm. Clone Memory records that the primary-contact field is the house manager, not the homeowner. The Halberg voice and the Malibu voice never cross in a draft.
The retired engineer in Coral Gables
He reads every line of the service contract and quotes the page number back at you. Voice rule: technical, thorough, no hand-waving. Template rule: always attach the Crestron programming change log. When he asks about rung-level logic, he gets a clean diff. Clone stores his voice as 'coral-gables-technical'.
The Tribeca loft with an assistant named Mia
All ops routes through Mia. The homeowner sees only quarterly digests. Clone Memory captures this with a single field: primary_contact=Mia, homeowner_digest=quarterly. The template 'tribeca-ops' always cc's Mia, and the quarterly email is a digest of the four months of ops work the homeowner never had to read.
The Aspen seasonal cabin that goes dark in summer
The account is warm between October and May, and effectively closed from June to September. Clone Memory records the seasonal window and pauses the ritual loop during the dark months. The automation does not email a sleeping homeowner about a service plan they will renew in November.
The Park Avenue apartment with art on the walls
NDA-level discretion: no photos of the art in any correspondence, no gate code in email, no exterior description that could identify the address. Clone Memory records these as hard constraints on the entity. Drafts that would violate the rule are blocked at generation time, not at send time. The voice template never forgets.
The one-sentence rule of thumb
If your back-office tool has one template library for the whole firm, it is the wrong data structure for a home automation practice.
Home automation is a one-to-many, decade-long residential business. The voice has to be indexed per home, not per firm. The escalation rules have to be versioned per home, not per service plan. The do-not-disturb windows have to be enforced per home, not per company-wide send schedule.
Clone's fourth architectural layer is the structural answer: Memory is a named row that indexes homeowner entities, each one with a voice file, a template library of its own, and a decade of history. Install the .dmg, point Clone at your sent folder, wait for the twelfth email to a home, and Clone offers to save the voice.
Six practices where per-home voice is the unlock
If any of these describes your book, the back-office you need is per-home by construction.
The boutique CEDIA firm with 60 active homeowners
Two principals, one programmer, a service tech, and an office manager. The principals know the voice of each homeowner. The programmer and the tech do not. When the office manager goes on leave, half the homeowners get drafts in the wrong voice and three call in. Clone Memory moves voice off the principals' heads and into a folder the whole firm can read.
The solo Control4 dealer with a side-retainer book
18 install clients plus 22 retainer homeowners. Install cadence is project-based, retainer cadence is quarterly. Your week is 60% service calls and 40% email. Clone Memory keeps the install voice and the retainer voice separate for every home, so the retainer emails do not sound like you are trying to resell them a kitchen.
The Crestron-first integration firm expanding to Savant
New homeowners are arriving on Savant Pro projects while the legacy book is on Crestron 4-Series. The voice for a Crestron client references programming cycles; the voice for a Savant client references scenes and configurations. Clone Memory stores the platform-specific vocabulary under each entity so the drafts are never platform-mismatched.
The home automation consultant moving from installer to advisor
You are stepping off the truck and into a pure consulting model: homeowner site reviews, dealer selection, punch-list arbitration. Your voice has to split: installer-friendly for the dealers, homeowner-protective for the clients. Clone Memory holds two voice registers per engagement and the template library does not blur them.
The multi-generational residential book
Year one is the homeowner; year three is the homeowner and their new baby; year seven is the elder parents moving in; year ten is the house transitioning to the grown kids. The voice has to age with the home. Clone Memory keeps a history log under the entity; the drafts read the log and soften or update the voice automatically.
The firm that wants to sell the book in five years
A buyer will pay for recurring revenue and for a clean voice asset. If your voice lives in one principal's head, the book is worth less. If it lives under ~/.clone/memory/entities/, the book is a folder that transfers. Clone turns tacit voice into a firm-level asset that has a price tag.
The structural claim, in one paragraph
Per-home voice is not a feature. It is a row in the architecture.
A firm-wide template library can add more templates. It cannot change the fact that the primitive in the data model is 'template', not 'home'. The contact tag system can add more tags; it still cannot write an email.
Clone's primitive is the homeowner entity. Voice is a property of the entity, not a shared pool. Each entity owns its escalation rule, its channel rule, its do-not-disturb window, and its history. The 80th homeowner gets the same architectural treatment as the first.
No cloud template tool can close this gap without rebuilding the data model. The only way to get there is to make per-entity voice the default, and to keep it on the consultant's Mac where a ten-year history does not become a ten-year SaaS bill.
“We had a principal leaving after twelve years and we were about to lose the voice on the top forty homes. We installed Clone on the incoming associate's Mac, pointed it at the sent folder, and let it run the observation loop for a month. By week five the drafts for the Halberg home opened with the dog's name, the Chen home drafts were skipping the 9am slot, and the Tribeca loft drafts were cc'ing Mia automatically. The principal's voice walked into a folder instead of walking out the door.”
A voice profile per home. We seed one in 20 minutes.
Twenty minutes together. You describe one homeowner relationship; we let Clone store it as a voice profile and run a follow-up in that tone.
Home automation consulting, the per-home voice edition
Why does home automation consulting specifically need a per-home voice layer?
Home automation is a one-to-many, decade-long residential business. A solo integrator or a boutique firm runs 40 to 80 active homeowners concurrently, and each engagement lasts ten or more years through install, service, expansion, and intergenerational handoff. A homeowner who has been getting warm-opening emails from you since 2018 will notice on email 812 when the tone flattens. For B2B consulting the voice is firm-level; for home automation it is per-home, and the back-office tool has to match that shape. Clone Memory at architecture.tsx line 24-28 is the only piece of software in the category that has a row for it.
How is Clone Memory different from a CRM tag or a HoneyBook template library?
A CRM tag is a label attached to a contact. It can flag that the Halberg home prefers email, but it cannot write the email. A HoneyBook template library is one shared pool of templates that every client draws from. Even if you fork a template per home, the fork is static: it does not observe your last twelve emails and update itself. Clone Memory stores a live, per-entity voice profile that the observation loop in how-it-works.tsx lines 44-56 keeps current. On email number 100 to the Halberg home, the Halberg voice has drifted with your actual writing; the saved template has drifted with it.
What actually lives under ~/.clone/memory/entities/ for a home automation practice?
One markdown file per homeowner entity, each containing: the entity's identity fields (home name, address handle, platform like Crestron 4-Series or Control4 OS3, primary programmer), the voice fields (tone profile, opening-line preference, closing-line preference), the escalation fields (who to cc at what dollar threshold), the channel fields (email vs text vs through-the-assistant), the do-not-disturb rules (no email before 10am PT, no exterior descriptions, no photos of the art), and a rolling history of the named voice templates you have saved for this home. The folder is plain text, git-friendly, transferable.
What happens when I move to a new Mac, or my associate joins the firm?
You copy ~/.clone/memory/ to the new machine, or you commit it to a private git repo and the new associate clones it. Every voice template, every homeowner entity, every decade-long history row moves with the folder. There is no SaaS vendor to migrate off. There is no cloud export to chase. The 812th email to the Halberg home can still open with the dog's name on the associate's first day.
Will Clone respect homeowner privacy rules like 'no gate code in any email'?
Yes, by the structure of the Memory entry. When the entity file records 'no_gate_code_in_email=true', the draft generator treats that as a hard constraint at generation time, not a soft review at send time. The gate code simply does not appear in the draft body. Same for 'no photos of the art', 'no exterior descriptions that identify the address', and any other homeowner-specific discretion rule. The constraint is versioned with the entity, so it stays enforced through every voice-template update.
Does Clone replace D-Tools, Jetbuilt, Proposal Plus, or Simpro?
No. Those tools stay where they are. Clone's third architectural principle (architecture.tsx line 56-58: 'Tool agnostic by design') means Clone drives the apps you already pay for. Your proposals still generate in D-Tools, your project management still lives in Simpro, your sent folder is still Gmail. Clone composes the voice layer and the invocation layer on top. If you switch from D-Tools to Jetbuilt mid-year, the voice templates do not need to be re-authored.
How is this different from a virtual assistant at $3K to $6K/month?
A VA carries voice in their head, not on disk. The voice quality depends on the specific VA, it evaporates when they quit, and it does not scale past the top 10 or 15 homeowners because no human can hold 80 distinct voice profiles. Clone's voice memory is a folder that scales to the 200th entity without degradation and runs 24/7 without a weekend. The price delta is also structural: $49/mo for Clone versus $36K to $72K/year for a VA. A home automation consulting practice that invests in Clone recovers the VA budget into programming or service-tech hours.
What about Zapier? Home automation consultants use it all the time.
Zapier is great for event-triggered pipes: a form submission creates a contact, a signed contract kicks off an onboarding sequence. Zapier is not a voice engine. Expressing 'open the email to the Halberg home with a line about the Bernese mountain dog and attach the Crestron change log, but only cc Diego when the scope change is above $8K' in Zapier requires a per-home set of filters at the top of every zap, and you will maintain 40 to 80 of them. Clone expresses that rule as a markdown entity file in Memory and the draft generator reads it every time.
Will this change over the homeowner's decade with me?
That is exactly what Clone Memory's history field is for. The entity file keeps a rolling log of named voice templates. When the Halberg home has a baby in year three, you save a new template called 'halberg-update-postbaby' that softens the technical density and adds scheduling-around-nap rules. The old template is archived, not deleted. Year ten, when the grown kids inherit the house, you fork another template. Voice ages with the home.
Is the $49/mo flat price real for a practice with 80 homeowners?
Yes. The pricing model is per-seat, not per-contact. Clone does not charge for the 1st or the 800th homeowner entity. The architecture makes this possible: Memory lives on the consultant's Mac, and Clone has no cloud-side database to pay for per row. A boutique firm with three principals pays $49 each; the Memory folder is shared via the firm's private git repo. The math for 80 homeowners is $49 vs $3K to $6K for a VA; the difference funds a service tech.
What does a twelve-email observation loop produce on a real home?
A typical Halberg-style observation loop produces three rules in the template: an opening-line rule ('start with the dog'), an attachment rule ('Crestron change log is always included'), and an escalation rule ('cc Diego on scope above $8K'). On a Malibu-style home it might produce: a channel rule ('all ops to Maria the house manager'), a timing rule ('never email after 7pm local'), and a language rule ('no prices in-line; always as an attached quote'). The rules are specific because your writing is specific; Clone extracts what is already there.
What about CEDIA certification tracking, manufacturer rebates, warranty claims?
Those live in your existing tools (D-Tools, Simpro, the Crestron dealer portal, the Control4 rebate portal). Clone drives them the same way it drives Gmail. The ritual file is plain markdown: 'every Friday, read the Crestron rebate portal, extract the pending claims, open them in QuickBooks, draft the client-facing summary in the Halberg voice.' The voice layer and the operations layer are separate. Both live under ~/.clone/ and neither one is a cloud database.
Each one starts from a different layer in architecture.tsx and takes it to the end of a consulting use case.
Adjacent pages on the same architectural row
Industrial Automation Consulting Under CUI: Clone's First Architecture Principle Is 'Runs on Your Machine'
What local-execution unlocks for a plant-floor consulting practice that a cloud-based automation tool cannot.
Business Process Automation Consultant, Reframed Around Local-Only Execution
Why a solo BPA consultant runs an automated practice without becoming a third-party processor on the client's DPA.
AI Automation for Small Business, Measured in Reclaimed Billable Hours
Where the Memory layer lives, and why a stateless workflow tool cannot catch up to an observation loop.
Save the voice before the next associate joins
Walk through your top 10 homeowners on a 30-minute call.
Bring the last ten kickoff emails or service-plan updates you sent. In thirty minutes we sketch the voice template Clone would extract for each one, and you decide before install whether a per-home Memory layer is the back-office your practice has been missing.
Book a 30-minute callSave the voice of your top ten homeowners before the next associate joins.
Install Clone, point it at the sent folder, and let the observation loop run for four weeks. If the extracted voice templates do not match what you would have written by hand, refund the trial.
Start 21-day free trial →A per-home voice layer for home automation consultants. 21-day trial, $49/mo.
Book a call