Summary
A five-trade home-services brand in the Detroit metro, formed by consolidating two longstanding businesses under a new name, needed a content system that knew who it was before it wrote a word. I provisioned it as a full tenant of my Article Factory: an isolated project, a deployed dashboard and a complete brand-setup context layer. One command, about fifteen minutes, no performance data yet.
A new name with forty years behind it
The brand covers HVAC, plumbing, electrical, appliance repair and commercial refrigeration across the Detroit metro. It was formed by bringing two established trade businesses, one dating to 1984, under one name, with more than forty years of combined experience and a 4.9 out of 5 rating across 48 reviews.
It competes against national chains, single-trade shops and the lead platforms that sell the same homeowner to five contractors at once. A generic content pipeline would have written for none of that.
What provisioning creates
One command creates the tenant. It adds the client record to the shared database under per-tenant isolation, runs a brand-setup research pass, and deploys a live dashboard on the client’s own subdomain. The result here was its own hosting project, a working dashboard, and the context layer the Factory reads before every article.
The context layer
- Company profile. The two legacy businesses, the consolidation, the five trades, the service area, the proof points it can claim.
- Audience personas. Emergency Ellen, whose furnace died in January; Maintenance Mike, who schedules ahead; Project Paula, planning a renovation; and B2B property managers with portfolios to keep running.
- Customer voice. How real customers describe the problems, from reviews and calls.
- Writing guidelines. Tone, structure, what the brand never says.
- CTA library and lead-magnet library. Approved calls to action by funnel stage, and the offers an article can point to.
- Content inventory and operator directives. What already exists and how the operator should run this tenant.
Who the business is not for
The context layer also names the segments the brand should not write for: pure-price shoppers, buyers looking for a personality-led brand, and DIY purists. That list keeps the Factory from drafting articles that attract the wrong reader and dilute the pages that book.
Where it stands
The tenant, the dashboard and the context layer are live and verifiable in the repository and the artifact store. There is no Search Console, analytics or CRM series for this client yet. The build is the deliverable; production starts when the first keyword list is approved.
At a glance
- The niche: Five-trade home services, Detroit metro, a new brand over two legacy businesses.
- The problem: A generic content pipeline can’t write for a consolidated trade brand competing with chains, specialists and lead platforms.
- What was built: A full Article Factory tenant: isolated project, deployed dashboard, and an eight-file context layer including four personas and three not-for segments.
- Implementation: One provisioning command, about fifteen minutes; brand-setup research pass; dashboard deployed to the client’s subdomain.
- Results: Tenant live and verifiable. No performance data yet.
- Built with: my Article Factory.
