Three companies, five locations, one brand
Four legacy food businesses, three registrars, three hosts, and two customer bases with nothing in common.
Four legacy food businesses were consolidating into one brand family — a USDA processing plant, a meat company, a ranch and market, and a market and barbecue.
Each had grown its own way: its own domain across three registrars, its own host, its own social accounts, its own way of taking payment. Two customer bases with almost nothing in common — 6,000 producers who drop animals, and 3,100 retail and delivery subscribers. Individually each business worked. Together they were a tangle, and nobody had asked whether any of the tools talked.
How we untangled it.
Brand first, because the naming decision gates everything downstream — then the namespace, then the stack, then the communications.
The part that mattered most was the sequencing of the transition itself. A rebrand email from a corporate entity is exactly the wrong instrument for a producer who has driven the same forty-five minutes for fifteen years. So every processing message went out signed by the person those customers actually know, and the most sensitive group heard first.
What was built.
A brand and a namespace. Purpose, values, mission, voice, logo, typography, iconography, palette, and an art direction guide. Then every entity mapped to a final name and URL, with market research, trademark availability review, and a registrar analysis — three registrars and three hosts collapsed into a single domain strategy the merged brand owned outright instead of renting in six places.
A tech-selection framework, not a vendor opinion. Six e-commerce platforms, three POS systems, and three email platforms scored on the same grid — native fit, integration depth, learning curve, and true annual cost including credit-card processing rather than sticker price — with a plain-English verdict per platform.
A segmentation model that made personalization possible. 9,100 contacts split by relationship — producer, retail, e-commerce — and by location, then wired to mass SMS capability configured and tested before a single message went out.
A single content operating system. One database replaced scattered docs and threads: 25 approval-ready assets across 7 channels covering 6 location-and-segment combinations, plus roughly 20 reusable templates. Every piece tracked by phase, entity, location, channel, subject line, status, and approval date, so a message could not go out unapproved and nothing landed in the wrong inbox.
Plus staff enablement — talking-point cards, an internal FAQ, and role-play sessions — because the first person a customer asks about the new sign is whoever is behind the counter.
What changed.
Jolt Co delivered the foundation: the brand, the namespace, the platform decision, the segmentation model, and the transition communications, with success targets defined before launch rather than after — retention, response rate, sentiment, and staff confidence.
This page ends there deliberately. The measured outcomes against those targets, and the final stack cost before and after, sit with the client and have not been reported back. We would rather show the work than borrow a number.
Brand system · platform scoring framework · mass SMS · Notion content database