Symphony Core at a Glance
Your first twenty minutes. What the company is, what it sells, what it is trying to do, and which system holds what. Read this before anything that assumes you already know.
1. What the company is
Symphony Core is a marketing operations company for small service businesses. Not an agency that makes ads and bills for them: we install and run the system a small business would otherwise have to assemble from six tools and nobody to watch it.
The product is sold as the Intelligent Marketing OS, and the pitch is that it is turnkey in about 30 days and tailored to the trade, rather than a generic stack the owner has to configure.
What it covers:
| Lead capture and routing | Every enquiry lands somewhere and goes to someone |
| Multi-channel follow-up | SMS, email, voice and social, automated |
| Reputation | Review requests and review responses, run on a schedule |
| Websites | Built to convert, not to win design awards |
| SEO and analytics | Found locally, and measured |
| AI automation | The parts that do not need a person |
Pricing is a flat monthly subscription, month to month, no long-term contract. Every feature is on every plan — the tiers differ by seats, contacts, credits and support, not by capability. The current tiers and prices are in Symphony Core Company Info; read them there rather than from memory, because they change and that page is the one that is right.
2. Who we are for
Service businesses at roughly $100K–$2M in annual revenue. Home services — HVAC, plumbing, electrical, landscaping, cleaning — plus real estate and professional services.
The client we are built for is losing leads to slow response, drowning in manual follow-up, or wants the marketing to keep running while they do the actual work. The disqualifiers matter at least as much as the fit, and they are in the SC Ideal Customer Profile.
3. What the company is trying to do
Two goals. Everything anyone here works on should trace to one of them.
| Goal | What it means day to day | |
|---|---|---|
| G1 | Revenue — grow collecting monthly recurring revenue and finish the year cash-flow positive | "Collecting" is the operative word: money actually arriving on an active subscription, not a signed proposal |
| G2 | Delegation — build the workflows so the company runs with minimal founder time in routine delivery | Every role here exists to take something off the founder's desk permanently, not to help with it |
G2 is why most roles exist, including every new one. A task that gets done but leaves the founder in the loop has not met it. The targets and the live numbers behind both goals are held separately; the direction is what matters for the work.
4. Which system holds what
The common mistake in the first week is putting something in the wrong place and assuming it is filed. It is not.
| System | What lives there | How you get in |
|---|---|---|
The platform — app.symphonycore.com | Contacts, conversations, pipelines, calendars, campaigns. Client and prospect records both. This is GoHighLevel, white-labelled as Symphony Core; clients only ever hear the Symphony Core name | Your own user, scoped to what your role needs |
This wiki — team.symphonycore.com | Every SOP, standard, script and rule sheet. The only place they are correct | Browser, behind sign-in |
| ClickUp | Tasks and assignment. Who is doing what, and the state of it | Only roles whose work is ticket-driven |
| Google Drive | Working files, worksheets, exports, anything binary. Your own shared folder is here | Your folder is shared with you directly |
| Slack | Day-to-day conversation. Decisions get written down elsewhere afterwards | Invite per channel |
Two rules that save the most time. The wiki is the source of truth — when a copy of a document somewhere disagrees with the wiki, the wiki wins, and the copy is the thing to fix. And passwords never travel in writing: not email, not chat, not a document. Credentials are held in 1Password and shared another way. A written request for your password is wrong no matter who sent it.
5. Where to go next
Your role has its own reading path, in order, in the Contractor Onboarding Reading Lists. Find your section and work down it; the order is deliberate in the roles where it matters.
How the team is organised and who owns what is in Team Structure. How we work together day to day — hours, responsiveness, escalation — is in Team Ways of Working.
Related Documents
- Symphony Core Company Info — the detail behind every number on this page
- SC Ideal Customer Profile — who we serve, and who we decline
- Team Ways of Working — how we operate together
- Team Structure — roles and ownership
- Contractor Onboarding Reading Lists — your role's reading path
Document History
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-10-27 | Symphony Core Systems Team | Initial version. Written because the Inside Sales reading path opened on company context that was not reachable: sc-goals.md and the company-info quick reference are repo-only, and a contractor with wiki access and no repo access met the compliance rules before anything had described the business. This page carries the orientation without the revenue targets and live-numbers pointers that keep sc-goals.md internal |