Symmetry in Practice
Four clients. Seventeen systems. One operating picture.
Every business we support runs on tools that don't talk to each other - a CRM here, invoicing there, marketing in a third place, mail in two more. Symmetry connects them into a single hub and turns the combined picture into boards their teams actually work from: stages, swimlanes, owners, and a daily digest. Four engagements show the same pattern at four very different shapes.
The pattern behind every board
Whatever the tools, the machinery is the same five moves - which is why a new system, or a new client, never means starting over.
- 01
Connect
Each tool becomes a connection - API, mailbox, or webhook. Credentials vaulted, sync monitored.
- 02
Normalize
Every record lands in one hub in one shape, whatever system it came from.
- 03
Route
Data-driven rules read each record and place it - no hand-sorting, no hardcoding.
- 04
Board
Stages and swimlanes materialize as working boards - advanced by hand or by the source system itself.
- 05
Report
One daily digest per client: tiles, trends, and an AI insight over the whole picture.
Case study · 01
A UX research consultancy
UX research & quantitative usability consulting
This firm produces a steady stream of expert content - articles, carousels, newsletters, videos - planned in an Airtable dashboard, sent through Mailchimp, and amplified on LinkedIn. What none of those tools offered was a way to manage the operation: where each piece stood, what was due, and how content effort connected to business development.
Before
Content status lived in Airtable fields, campaign results in Mailchimp, engagement on LinkedIn - three tabs, no deadlines enforced, and no sales pipeline at all.
With Symmetry
One content board with per-stage turnaround clocks, format swimlanes, and a sales board - Symmetry itself became the CRM they didn't have.
The connected stack
- Airtable content dashboard
- Mailchimp email marketing
- LinkedIn social
- Symmetry hub + CRM
The boards
Pipeline · Content
Every piece flows the same stages; format is the swimlane, not a separate list.
- Idea
- Draft
- Review
- Approved
- Scheduled
- Carousel
- Newsletter
- Video
- LinkedIn Article
- Testimonial
- Product Post
Pipeline · Sales
The CRM they now run entirely inside Symmetry.
- Identified
- Outreach
- Engaged
- Meeting Booked
- Proposal Sent
- Contract
- Won
Content pieces sync from the Airtable base and ride the board with real turnaround targets on each stage; Mailchimp and LinkedIn results flow into the same metrics library, so the digest reads content operations and marketing performance as one story.
- 7,900+ Mailchimp records normalized into the hub
- 12 content stages & formats managed on one board
- 2 pipelines - Content and Sales - from one hub
Case study · 02
A psychological testing practice
Healthcare · psychological evaluation and testing
This practice evaluates children and adults, and most of its new patients arrive by fax: referrals from physicians and other providers, mixed in with records requests, authorizations and charts sent after the fact. When Symmetry started running its operations it had one location. It has two today, with a third on the way - and every new site has been a configuration change, not a new back office.
Before
One fax line, read by hand. A referral that mentioned records looked like a records request, so new-patient work sat in the wrong queue - and the phone, the website chat, the EHR and two inboxes each held a different part of the same inquiry.
With Symmetry
Every fax is read, sorted and routed before a person opens it. Referrals, calls, chats and website bookings all land on one opportunity board, placed at the right location by what the record says. Real-time KPIs and a daily digest show the whole practice every morning, by location.
The connected stack
- Telzio fax, phone & voicemail
- IntakeQ EHR & booking
- GoHighLevel CRM & website chat
- Gmail a mailbox per location
- OnceHub consult bookings
- Symmetry hub
The boards
Pipeline · Opportunities
Every door feeds one board: a faxed referral enters at Inquiry, a website booking or inquiry email at Outreach. How the patient was reached is a tag, never a guess.
- Inquiry
- Outreach
- Schedule
- Won
Queue · Faxes
Read and sorted by AI; referrals skip the strip and go straight to the pipeline.
- Referrals
- Record Requests
- Authorizations
- Medical Records
- Unclassified
Each fax is OCR'd inside the hub - pages that arrive upside down or sideways are turned and read again - and sorted by AI into the practice's own categories. The sorting learned the practice's own edge cases: an order block makes a fax a referral even when it mentions records, and a summary-of-care packet is the chart that follows a referral, not a new one. When the second location opened, its rules, strips and outreach templates were cloned from the first, and because both sites share one fax number, each record is placed by what it says rather than where it arrived.
Every connection feeds the KPI library in real time: fax, email and voicemail volume by category, inquiries by front door, outreach and scheduling through the board, and won results by offer. The daily digest is built from the cards the practice chose, so leadership reads one page each morning instead of five systems. SLA clocks are ready on every queue; the practice started without targets and can put one on any queue the day it wants a turnaround held.
Faxes, voicemails and intake records carry protected health information, so HIPAA compliance is built into how the work runs rather than added as paperwork. Fax text is read by OCR inside the hub. The AI that sorts it runs on Microsoft Azure AI Foundry under Microsoft’s business associate agreement, and the job fails closed: if Foundry is not configured, the fax is left for a person rather than sent to any model without a BAA. Voicemails are transcribed by Azure Speech under the same agreement. Every record access is written to a tamper-evident audit ledger that names whose record was touched, so an accounting of disclosures can be answered patient by patient, and the practice’s data stays in its own scope, never pooled with another client and never used to train models.
- 1 → 2 locations since Symmetry started, a third underway
- 9 fax categories, read and routed before anyone opens one
- 4 front doors - fax, phone, chat, booking - feeding one board
- 1 daily digest with real-time KPIs, by location
Case study · 03
A media & creative agency
Media & creative services
This agency ran on two systems that never met: leads and nurture campaigns in GoHighLevel, contracts and invoicing in 17hats. Knowing where any one prospect stood meant checking both - and nothing tied a booked consultation to the contract that followed it.
Before
Two sources of truth for one relationship. A lead in GoHighLevel and a contract in 17hats were the same client, but no system knew it.
With Symmetry
One sales board spanning both systems - and the stages advance automatically from GoHighLevel's own pipeline, so the board is always current without anyone updating it.
The connected stack
- GoHighLevel CRM & funnels
- 17hats contracts & invoicing
- Airtable contact mirror
- Slack updates
- Symmetry hub
The board
Pipeline · Sales
Source-driven: GoHighLevel stage changes move the cards.
- New Lead
- Warm Lead Nurture
- Consultation Booked
- Booked
- Long-Term Nurture
Contacts resolve to one person across both systems, so the card for a lead carries their 17hats history beside their GoHighLevel activity. The board mirrors the CRM's own stages rather than inventing a second workflow - Symmetry's rule engine reads the source's pipeline data and keeps the board honest on every sync.
- 1,700+ 17hats records unified with CRM activity
- 5 sales stages, advanced by the source system
- 1 view of each client across lead, contract, and invoice
Case study · 04
A boutique services team
High-touch client services
This team runs a personal, high-touch business across five everyday tools: client conversation split between Gmail and Outlook, bookings and payments in HoneyBook, the marketing list in FloDesk, team chatter in Slack. Nothing was wrong with any single tool - the cost was the switching, and the absence of any combined picture.
Before
Five tabs to answer one question: who is this client, what have we promised them, and what's happening this week?
With Symmetry
Both mailboxes, bookings, and the subscriber list normalize into one hub - one record per person, one daily digest over all of it.
The connected stack
- Gmail communications
- Outlook communications
- HoneyBook bookings & invoicing
- FloDesk email marketing
- Slack team
- Symmetry hub
Every inbound conversation - whichever mailbox it lands in - files against the same person in the hub, beside their HoneyBook bookings and FloDesk subscription. The same rule engine that powers the larger clients' boards stands ready as their workflow grows: when a stage model earns its keep, it seeds as a board, not a rebuild.
- 5 systems consolidated into one hub
- 2 mail providers reading as one conversation stream
- 400+ marketing subscribers joined to client records
Different tools. Same machinery.
A testing practice's fax line, a research firm's content engine, a media company's split CRM, a boutique team's five-tab day - the same five moves connected each of them. Boards materialize from data-driven rules, stages move by hand or by the source system, and one digest reads the whole operation. The next system a client adopts is a connection, not a migration.
Book a Discovery Call