Symphony Core Brand Voice
This document defines how Symphony Core sounds and writes across all communications. It combines voice/tone guidelines with writing standards and channel formatting into a single reference.
Part 1: Brand Voice Profile (Template Format)
This section follows the standard Brand Voice Template used for all client brand boards.
Business Info
- Brand Name: Symphony Core
- Type of Business: Systems as a Service -- marketing automation for small businesses
- Company Website: https://symphonycore.com
Location and Contact Info
- Company Email: contact@symphonycore.com
- Phone Number: +1 (475) 244-9646
- Company Address: Connecticut, USA
- Business Hours: Monday-Friday, 9 AM - 5 PM ET
Brand Communication and Personality
- Tone of Voice: Expert but approachable, practical but engaging, confident but not arrogant. 60% conversational, 70% simple language, 55% expert authority.
Brand Identity and Market Positioning
- Target Audience: Service businesses ($100K-$2M revenue) in home services, real estate, and professional services across the US (Tier 1), India (Tier 2), and other WhatsApp-first markets (Tier 3) -- owner-operators or marketing decision-makers with 2-50 employees who need marketing systems but lack time or technical skills. See
sc-ideal-customer-profile.mdfor full criteria andsc-buyer-personas.mdfor individual-level personas. - Customer Pain Points: Missing leads after hours, juggling too many disconnected tools, no visibility into what marketing works, manual processes that steal time from serving customers.
- Brand Promise: Complete marketing systems, fully operational, within 30 days.
- Brand Values: Clarity, Fairness, Results, Simplicity, Transparency.
- What does your brand do?: Make marketing simple through automation and stress-free systems that let business owners focus on running their business -- delivered globally through our hybrid US/India operating model.
- What makes you better than competitors?: Done-for-you systems (not DIY software), 30-day implementation (not months), flat pricing (not variable), ongoing operation included (not just setup).
- Unique Selling Proposition: Systems as a Service -- enterprise-grade marketing automation designed for small business reality. One integrated platform replaces 5-10 tools, operational in 30 days.
- Risks of Inaction: Every week without a system is leads walking away. Competitors with automation capture the prospects you miss. Manual processes don't scale.
- Call to Action: Book a free demo at https://symphonycore.com/schedule-my-demo/. CTAs always point at the root domain, never the
go.subdomain
Part 2: Extended Voice & Tone Guidelines
1. The "We Are X, But Not Y" Framework
Our voice is defined by what we are AND what we consciously avoid:
| We Are | But NOT |
|---|---|
| Expert | Intimidating |
| Practical | Boring |
| Empowering | Patronizing |
| Clear | Simplistic |
| Collaborative | Dependent |
| Confident | Arrogant |
| Direct | Harsh |
| Professional | Corporate |
| Friendly | Unprofessional |
| Results-focused | Salesy |
Voice in Action
Expert, but NOT intimidating:
- Yes: "With 20+ years in technology, we've seen what works and what doesn't"
- No: "Our proprietary methodologies leverage enterprise-grade architecture"
Practical, but NOT boring:
- Yes: "Your system captures leads at 2 AM when you're asleep. They get a response. You get the business."
- No: "The system responds to leads automatically during off-hours"
Empowering, but NOT patronizing:
- Yes: "You know your business. We know systems. Together, we build something that works."
- No: "Don't worry--we'll handle the complicated stuff so you don't have to think about it"
Clear, but NOT simplistic:
- Yes: "Marketing automation combines CRM, email, texting, and scheduling into one system that works without manual effort"
- No: "It's like magic--your marketing just happens!"
Confident, but NOT arrogant:
- Yes: "We've refined this process over dozens of implementations. It works."
- No: "We're the best in the market and no one else can match what we do"
2. Voice Spectrum
| Dimension | Scale Position | How It Shows Up |
|---|---|---|
| Formal ↔ Conversational | 60% Conversational | Professional base with approachable warmth |
| Technical ↔ Simple | 70% Simple | Explain complex ideas in plain language |
| Urgent ↔ Calm | 50% Balanced | Acknowledge urgency without creating panic |
| Optimistic ↔ Realistic | 60% Realistic | Hope grounded in pragmatism |
| Serious ↔ Playful | 35% Playful | Professional first, with moments of wit |
| Expert ↔ Humble | 55% Expert | Lead with expertise, stay open to learning |
| Bold ↔ Reserved | 60% Bold | Confident claims backed by evidence |
3. Tone by Scenario
While our voice stays consistent, tone shifts based on purpose, audience, emotional state, and platform.
| Scenario | Tone | Voice Shift | Example |
|---|---|---|---|
| Sales/Demo | Confident + Value-focused | More assertive, outcome-oriented | "Here's exactly how this generates qualified leads for businesses like yours" |
| Educational Content | Clear + Encouraging | More patient, detailed | "Let's break down how marketing automation actually works--no jargon" |
| Customer Success Story | Enthusiastic + Warm | More celebratory | "When Mike implemented his system, everything changed. Here's what happened..." |
| Support/Help Article | Supportive + Practical | More instructional, patient | "Here's exactly how to solve this, step by step" |
| Problem/Issue Communication | Accountable + Solution-oriented | More direct, action-focused | "We identified an issue. Here's what happened and what we're doing about it" |
| Email Marketing | Helpful + Benefit-focused | More conversational | "Quick question: How many leads did you miss last week?" |
| Social Media | Engaging + Valuable | More casual, punchy | "Your competitors are answering calls at 10 PM. Are you?" |
| Legal/Policy | Professional + Clear | More formal, precise | "Your data remains your property. We don't sell or share client information." |
Tone by Persona
| Persona | Tone Adjustment |
|---|---|
| Home Services (Mike) | More direct, less theory. "Here's how it works" over "Here's why it matters" |
| Real Estate (Sarah) | More relational, lifestyle-aware. Acknowledge the hustle, offer relief |
| Professional Services (David) | More formal, reputation-conscious. Sophisticated language, professional references |
4. Vocabulary
Words to Embrace
| Word/Phrase | Why We Use It |
|---|---|
| Results | We're outcome-focused, not activity-focused |
| Systems | Our core offering--complete systems, not tools |
| Orchestrate | Better than "manage"--implies sophisticated coordination |
| Automate/Automation | Core capability, explains the value |
| Proven | We back claims with evidence |
| Qualified leads | Specificity matters--not just "leads" |
| 30 days | Our implementation promise--concrete and differentiating |
| Flat pricing | Transparency differentiator |
| Customers | Not "users"--we serve people, not metrics |
| Small businesses | Our audience--say it directly |
| Working system | Emphasizes operational, not just delivered |
| Measurable | Everything should be quantifiable |
Words to Avoid
| Word/Phrase | Why We Avoid It | Use Instead |
|---|---|---|
| Synergy/Leverage | Corporate jargon, meaningless | "Works together" / "Use" |
| Cutting-edge | Vague, unsubstantiated | Specific capability |
| Best-in-class | Unprovable claim | Specific differentiator |
| Industry-leading | Empty superlative | Concrete evidence |
| Revolutionary | Overused, sounds salesy | "Different approach" |
| Easy | Sounds condescending | "Simple" or "straightforward" |
| Paradigm shift | Buzzword | Just describe the change |
| Users | Impersonal | "Customers" or "clients" |
| Solution (alone) | Vague | Specific: "system," "approach," "service" |
| Basically | Sounds like oversimplifying | Just explain clearly |
| Obviously | Can sound condescending | Remove or explain why it matters |
| Game-changer | Overused | Describe the specific impact |
Phrases That Sound Like Us
- "Here's exactly how this works"
- "Let's be specific about results"
- "Your system captures leads while you sleep"
- "30 days to a working system"
- "Results, not dashboards"
- "We build it. It runs. You focus on your business."
- "Systems that work without you"
- "Flat pricing, no surprises"
- "We're not software. We're not an agency. We're Systems as a Service."
Phrases That Don't Sound Like Us
- "We leverage best-in-class solutions"
- "Our revolutionary platform disrupts the industry"
- "Unlock your potential with our proven framework"
- "Don't miss this opportunity!"
- "Act now before it's too late"
- "We basically handle everything for you"
- "Trust us--it's easy"
5. Grammar & Style
Punctuation
| Element | Preference | Example |
|---|---|---|
| Oxford comma | Yes | "Leads, nurturing, and conversion" |
| Em dashes | Avoid in client comms and email. Use a comma, period, or parenthetical instead. Permitted sparingly in marketing copy for structural emphasis, never as a dramatic pause. See email-writing-style. | Use "One system, not five" not "One system--not five" |
Double hyphens (--) | Never, anywhere, including internal docs. A double hyphen is just an em dash substitute and reads the same. Replace it with a comma, colon, period, or parenthetical (a semicolon is also fine in internal docs). | Use "One system, not five" not "One system -- not five" |
| Contractions | Yes, for warmth | "We're" not "We are" |
| Exclamation marks | Sparingly (max 1 per section) | Reserve for genuine enthusiasm |
| Ellipses | Avoid | Don't trail off... |
| ALL CAPS | Never in body copy | Use bold instead |
| Semicolons | Avoid in marketing copy | Break into separate sentences |
| Colons | Use to introduce lists | "Our services include:" |
Capitalization
| Element | Style |
|---|---|
| Headlines | Title Case (Capitalize Major Words) |
| Subheadings | Title Case |
| Button text | Title Case ("Get Started", "Learn More") |
| Product names | As trademarked ("Systems as a Service") |
| All caps | Never in body copy |
Sentence Structure
| Preference | Guidance |
|---|---|
| Voice | Active by default ("We build systems" not "Systems are built") |
| Length | Vary--mix short punchy sentences with longer explanatory ones |
| First person | Use sparingly in marketing (brand voice, not personal opinion) |
| First person singular ("I") | Use when the sender is personally taking an action (e.g., "I have routed this", "I will reply by Friday"). Reserve "we" for things the company does collectively. Personal ownership reads as more accountable in 1:1 client comms. |
| Second person | Use freely--speak directly to customers ("you," "your") |
| Questions | Rhetorical questions sparingly--don't overuse |
Numbers & Data
| Situation | Style | Example |
|---|---|---|
| Numbers 1-9 | Spell out | "three leads," "five tools" |
| Numbers 10+ | Numerals | "30 days," "15 hours" |
| Percentages | Numerals + % | "67% of leads" |
| Money | $ + numerals | "$500," "$2,000" |
| Time/Duration | Numerals | "30 days," "24/7" |
| Start of sentence | Spell out | "Thirty days to a working system" |
Formatting Standards
Headers:
- H1: Page/article title (one per page)
- H2: Major sections (3-5 per long article)
- H3: Subsections (as needed)
- H4-H6: Rarely used (for complex documents only)
Lists:
- Bullets for 3+ parallel items, scannable information, feature lists
- Numbers for sequential steps, ranked information, process flows
Links:
- CTA links: Clear action ("Learn how it works")
- Reference links: Descriptive ("See our case study")
- Avoid: "Click here," generic text
6. DOs and DON'Ts
General Communication
| DO | DON'T |
|---|---|
| Lead with outcomes, then explain how | Dive into features first |
| Use specific examples from real businesses | Speak in generalities |
| Acknowledge the complexity they face | Oversimplify their challenges |
| Write short paragraphs (2-3 sentences) | Write dense, academic prose |
| Use headers and white space | Long blocks without visual breaks |
| Speak to business impact | Focus on software features |
| Invite questions and dialogue | Talk AT them |
| Use numbers and proof | Make unsupported claims |
| Show understanding of constraints | Assume unlimited time/budget |
| Tell stories backed by data | Choose only one approach |
Sales & Marketing
| DO | DON'T |
|---|---|
| Ask questions before positioning | Pitch immediately |
| Reference their specific situation | Use generic scripts |
| Be transparent about pricing | Create mystery around costs |
| Explain limitations honestly | Overpromise capabilities |
| Follow up helpfully | Follow up aggressively |
| Let results speak | Oversell with adjectives |
Support & Service
| DO | DON'T |
|---|---|
| Acknowledge their frustration | Dismiss their concerns |
| Lead with severity and impact in client terms (e.g., "not urgent", "won't affect your search ranking") | Lead with technical field names, error codes, or platform jargon |
| Provide clear next steps | Leave them uncertain |
| Take ownership of issues | Blame other factors |
| Follow up to confirm resolution | Assume it's fixed |
| Be proactive about potential problems | Wait for them to discover issues |
| Give support@symphonycore.com as the only contact in shareable material | Name an individual as an escalation contact ("For escalations, ask for Rohit") — never in client- or partner-facing material unless explicitly requested for that artifact |
Translating technical notices for clients. When forwarding or responding to a third-party technical alert (Google Search Console, SEO plugin warning, hosting alert), the client reply should answer four questions in order: (1) is it urgent? (2) what is the real-world impact on their business? (3) what is being done about it and by whom? (4) what, if anything, do they need to do? Skip the technical detail (field names, error codes, schemas) unless the client explicitly asks. Source the technical detail in the internal ticket, not the client email.
Part 3: Channel Formatting Standards
7. Blog Posts
| Element | Standard |
|---|---|
| Title | Problem statement or outcome promise |
| Meta description | 150-160 characters, include primary keyword |
| Length | 1,500-2,500 words for comprehensive coverage |
| H2 headers | 3-5 throughout article |
| Examples | 2-3 industry-specific examples |
| CTA | Specific invitation in conclusion |
| Internal links | 2-3 relevant posts |
Blog Structure:
- Hook (first paragraph): State the problem or promise
- Context: Why this matters to the reader
- Solution/Content: Main value of the article
- Examples: Real-world applications
- Conclusion: Summary + clear CTA
Tone: Educational + Encouraging (60% conversational, 70% simple)
8. LinkedIn Posts
| Element | Standard |
|---|---|
| Length | 100-300 words |
| Opening | Hook with insight or question (first line visible) |
| Line breaks | Every 1-2 sentences for readability |
| Hashtags | 3-5 relevant ones |
| CTA | Soft invite to engage |
LinkedIn Structure:
[Hook - first line visible before "see more"]
[Main insight or observation]
[Supporting point or example]
[Takeaway or question]
#Hashtag1 #Hashtag2 #Hashtag3
Tone: Professional + Approachable (65% conversational)
Content Mix:
- 70% Educational/Value
- 20% Company/Culture
- 10% Promotional
9. Email Marketing
| Element | Standard |
|---|---|
| Subject line | 40-50 characters, benefit or pain point |
| Preview text | Extend subject line value |
| Body length | 150-200 words |
| Paragraphs | 2-3 lines maximum |
| CTAs | 1 main CTA per email |
| P.S. | Optional, for secondary offer |
Email Structure:
- Subject: Benefit or specific pain point
- Opening: Problem acknowledgment or question
- Bridge: "Here's what's possible..."
- Value: One main point + proof
- CTA: Single clear action
- P.S. (optional): Secondary offer or personal touch
Subject Line Formulas:
- Pain-focused: "The leads you're missing this week"
- Outcome-focused: "How contractors capture 3x more leads"
- Question: "What happens when a lead calls after hours?"
- Specific number: "One system. Every lead. 30 days."
Tone: Direct + Valuable (70% conversational)
9a. Client Correspondence (1:1 Email)
Section 9 above covers campaign email. This covers the other kind: a real message to a named client, prospect or partner. The standards are different, and the failure mode is different.
Operational detail lives in .claude/working-rules.md § email-writing-style. What follows is the voice principle behind it.
The principle: the email is a pointer, not a container.
A client email has one job: say the thing, point at the material, ask for at most one action. Length almost never comes from saying too much about the subject. It comes from two habits:
- Restating what the attachment already says. If a pack, proposal or document is attached, it carries the detail. Repeating a date or a list in the body does not make the reader more likely to act on it; it makes the email longer and the document look optional.
- Managing the relationship out loud. Opening by praising how the client handled something, admitting fault that changes nothing, or granting permission to decline a request you just made. All three feel considerate to write and read as padding, or worse, as uncertainty.
Cut on sight
| Pattern | Example | Why it goes |
|---|---|---|
| Relational preamble | "Thank you for saying it plainly. Ending something well is harder than starting it." | Warmth comes from doing the work well, not from saying warm things |
| Restated detail | A dates block reproducing what the attached document leads with | The email should point at the document, not compete with it |
| Self-reproach | "I should have spotted that sooner" | Invites re-litigation, gives the reader nothing to act on |
| Post-ask retreat | "If you would rather not, that is completely fine" | Undercuts the ask and reads as anxiety about having made it |
| Unverified standard advice | Telling a client to export data they do not have | Noise at best, false at worst. Check their actual state first |
The test. Read the draft and ask of every paragraph: does this tell them something they cannot get from the attachment, or ask them to do something? If neither, it is padding, however well written.
Professional and short are the same edit. Where a client email reads as unprofessional, the cause is usually not word choice. It is the writer being present in the email more than the subject is.
10. Website, Social Media & Sales
Website Copy
| Page Type | Focus |
|---|---|
| Homepage | Outcome-focused headline, social proof, clear CTA |
| About | Story, values, trust signals |
| Services | Problem -> Solution -> Proof |
| Landing pages | Single focus, conversion-optimized |
| Blog | Educational value, SEO-optimized |
Copy Principles:
- Headlines: Outcome over features
- Subheadlines: Clarify the promise
- Body: Problem -> Solution -> Proof -> CTA
- CTAs: Action-oriented ("Get a Demo," "See How It Works")
Tone: Confident + Helpful (55% conversational)
Social Media (Facebook/Instagram)
| Element | Standard |
|---|---|
| Length | 1-3 sentences |
| Visual | Required (image or video) |
| Video length | 15-60 seconds |
| Hashtags | 3-5 relevant ones |
| Emojis | Sparingly (0-2) |
Tone: Engaging + Valuable (70% conversational)
Sales Collateral
| Element | Standard |
|---|---|
| Lead with | Biggest outcome/benefit |
| Proof | Specific case studies or results |
| Objections | Address common concerns |
| Next steps | Clear path forward |
Tone: Confident + Evidence-based (50% conversational)
Customer Support/Help
| Element | Standard |
|---|---|
| Structure | Problem -> Solution -> Related resources |
| Language | Customer terms, not technical jargon |
| Visuals | Screenshots/video where helpful |
| Multiple paths | Docs, video, live chat options |
Tone: Patient + Helpful (75% conversational)
11. SEO Writing Guidelines
Keyword Integration
| Location | Guidance |
|---|---|
| Title/H1 | Include primary keyword naturally |
| First paragraph | Primary keyword in first 100 words |
| H2 headers | Include secondary keywords |
| Body | 1-2% keyword density (natural usage) |
| Meta description | Primary keyword + CTA |
| URL | Primary keyword, hyphens between words |
SEO Content Checklist
- Primary keyword in title and H1
- Meta description 150-160 characters with keyword
- Keyword in first paragraph
- 2-3 internal links to related content
- 1-2 external links to authoritative sources
- Alt text for all images
- Headers break up content every 300 words
- Minimum 1,000 words for ranking content
Part 4: Content Templates
Blog Post Template
# [Outcome-Focused Title with Primary Keyword]
[Hook: 1-2 sentences addressing the problem]
[Context: Why this matters to the reader]
## [H2: First Major Section]
[Content with examples and specifics]
## [H2: Second Major Section]
[Content with data or case study]
## [H2: Third Major Section]
[Actionable advice]
## Key Takeaways
- Point 1
- Point 2
- Point 3
## Ready to [Desired Action]?
[CTA paragraph with link]
Email Template
Subject: [Benefit or pain point - 40-50 chars]
[First name],
[Hook: Question or problem statement]
[Bridge: Here's what's possible...]
[Value: One main point + evidence]
[CTA: Clear next step button/link]
[Signature]
P.S. [Optional secondary offer]
LinkedIn Post Template
[Hook - first line that stops the scroll]
[Main insight - 2-3 sentences]
[Supporting point or example]
[Takeaway or question to drive engagement]
#Hashtag1 #Hashtag2 #Hashtag3
Content Types Quick Reference
| Type | Length | Tone | Primary Goal |
|---|---|---|---|
| Blog post | 1,500-2,500 words | Educational | Inform + establish expertise |
| LinkedIn post | 100-300 words | Professional | Engage + build thought leadership |
| 150-200 words | Direct | Drive specific action | |
| Website copy | Varies | Confident | Convert + inform |
| Social media | 1-3 sentences | Engaging | Connect + provide value |
| Case study | 500-1,000 words | Evidence-based | Prove results |
| Help article | 300-500 words | Patient | Solve problem |
Quality Checklist
Before publishing any content, verify:
Voice Alignment
- Sounds like Symphony Core (not generic or corporate)
- Expert but not intimidating
- Clear but not oversimplified
- Confident but not arrogant
- Matches intended channel tone
Clarity & Structure
- Main message is clear within first paragraph
- Jargon is avoided or explained
- Specific claims have evidence
- Active voice is used
- Short paragraphs (2-3 sentences)
- Headers break up content
- One main CTA per piece
- Easy to scan
Audience Fit
- Appropriate for the target persona
- Addresses their pain points
- Uses language they'd use
- Respects their intelligence
Technical
- Spelling and grammar checked
- Links work correctly
- Formatting displays properly
- Mobile-friendly
- Meta data complete (titles, descriptions)
Examples: Good vs. Not Us
Homepage Headline
Good (On-brand):
"Marketing systems that generate leads while you run your business"
Not Us:
"Revolutionary AI-Powered Marketing Solutions for Modern Businesses"
Why: The first is specific, outcome-focused, and speaks to our audience. The second is vague, buzzword-laden, and could be anyone.
Value Proposition
Good (On-brand):
"Stop missing calls. Start closing jobs. Your marketing system captures and follows up with every lead, even when you're on the job site."
Not Us:
"Our comprehensive lead management platform leverages cutting-edge technology to optimize your customer acquisition funnel."
Why: The first speaks to a real problem in real language. The second is corporate speak that says nothing specific.
Email Subject Line
Good (On-brand):
"The leads you missed last week"
Not Us:
"Don't miss out on this game-changing opportunity!"
Why: The first is specific, relevant, and creates curiosity. The second is generic urgency that sounds spammy.
Related Documents
- SC Customer & Market Canon Index - Canon entry point
- SC Brand Foundation - Values that drive our voice
- SC Market Positioning - What we say and how we differ
- SC Ideal Customer Profile - Account-level audience criteria
- SC Buyer Personas - Individual-level personas (4 across US + India)
- SC Market Segmentation - Vertical × geography grid
- SC Marketing Blurbs - Approved company descriptions
- SC Design Kit - Visual standards
- SC client profile - SEO identity values; this doc remains the canon source for tone of voice and point of view
Revision history
| Date | Version | Change | Author |
|---|---|---|---|
| (pre-2026-02) | 1.0 | Initial brand voice and writing standards. | Symphony Core Systems Team |
| 2026-02-25 | 2.0 | Merged sc-content-style-guide.md into this document. Writing standards, channel guidelines, SEO guidelines, and content templates added as Sections 7-11. | Symphony Core Systems Team |
| 2026-05-20 | 2.1 | De-CT'd Target Audience (now: US Tier 1 + India Tier 2 + Tier 3) and "What does your brand do?" (mission synced to sc-brand-foundation.md v2.0 + hybrid US/India delivery framing). Office address at Southbury retained as legitimate location reference. Related Documents expanded to cover canon entry point + new ICP / personas v2.0 / segmentation docs + SearchAtlas BV. Closes follow-up flagged in sc-customer-canon-index.md v1.0 §5. | Rohit Anand |
| 2026-05-29 | 2.2 | Three additions surfaced from the Kraneworks/Michelle Google Search Console reply: (1) reconciled em-dash guidance with the email-writing-style working rule (avoid in client comms); (2) added "First person singular (I)" sentence-structure rule for personal ownership of actions in 1:1 client comms; (3) added Support & Service "Lead with severity and impact in client terms" DO + a new "Translating technical notices for clients" subsection covering the four-question framework. | Rohit Anand |
| 2026-06-08 | 2.3 | Added an explicit Punctuation rule banning the double-hyphen (--) everywhere, including internal docs (it is an em dash substitute and reads the same). Surfaced from the CDM hiring-doc review. | Rohit Anand |
| 2026-08-19 | 2.4 | Added section 9a, Client Correspondence (1:1 Email). Section 9 covered campaign email only, leaving the more common case with no voice guidance at all in this document. Surfaced when Rohit cut a drafted client closure email roughly in half: every cut removed either detail the attached pack already carried, or the writer managing the relationship out loud. Records the pointer-not-container principle and a cut-on-sight table. | Rohit Anand |
| 2026-08-30 | 2.5 | Company Address changed from the Southbury street address to the "Connecticut, USA" locality line. The Southbury office was vacated August 2026; client-facing marketing now carries locality only (no street address). The Branford PMB remains legal/corporate-only. | Rohit Anand |
| 2026-10-09 | 2.6 | Call to Action moved from go.symphonycore.com/schedule-my-demo to the root domain, symphonycore.com/schedule-my-demo/. CTAs always point at the root domain. | Rohit Anand |
Every piece of content should pass the "Is this Symphony Core?" test. If it could have been written by any company, it's not on-brand. Our voice is our differentiation as much as our product is.