Brand Voice Framework - Tone & Messaging Guide

Discovery notes

Your four samples pull in two directions. The homepage and pricing lines ("empowering", "synergistically", "unlock your full potential", "enterprise-grade") sound like generic SaaS marketing copy — not your voice. The founder's own Slack description ("where's my stuff at, across every client") and even the error message's plain first half ("something went a little sideways") are closer to how you actually described the product. Pattern: your unedited language is plain, practitioner-first, and slightly self-deprecating; your published copy has drifted into borrowed SaaS-speak, likely from templates or committee-editing. The voice guide below is built from the founder language and stated values, not the homepage/pricing copy — those two are flagged for rewrite, not used as source material.

Voice Attributes

Plain-spoken

What it means: We describe what the product does the way a developer would explain it to a friend, not the way a pitch deck would.
DO: Use the words your own founder used ("where's my stuff at"); say the function, skip the abstraction.
DON'T: Reach for "streamline," "synergistically," "unlock potential," "empower" — these appear nowhere in your actual founder language, only in the copy that reads as off-voice.
Examples: "See what's actually pending, across every client." / "One place. No status meetings."

Unhurried honesty

What it means: We tell people the real situation, including when something's broken, without manufactured cheerfulness.
DO: State what happened and what's being done, plainly.
DON'T: Add exclamation points or reassurance-performance ("Don't worry!") that reads as scripted rather than felt — this is also your stated anti-pattern (Monday/Asana's peppy tone).
Examples: "Something broke on our end. We're on it — status page has the latest."

Respect for their time

What it means: Directly reflects your stated value — no fake urgency, no dashboard theater.
DO: Lead with the useful information; cut copy that exists to sound impressive rather than inform.
DON'T: Use urgency language ("unlock now," "don't miss out") your audience has learned to distrust from bloated PM tools.
Examples: "Set up takes about ten minutes. That's it."

Tone Matrix (NN/g four dimensions)

Shift for error messages specifically: slightly more formal/reassuring than baseline (user is frustrated), but energy stays matter-of-fact — do not add exclamation points even here, since that's the exact pattern you're rejecting.

Messaging Hierarchy

Positioning: We help freelance developers stop losing time to status admin across clients, by giving them one plain view of what's pending — without the enterprise PM overhead they've already rejected.

Pillars: (1) One view across every client, no per-tool updating, (2) Built for solo/small teams, not scaled-down enterprise software, (3) Minutes to set up, not a rollout project.

Proof points: Not supplied — you haven't given me a real setup-time figure, user count, or specific before/after workflow number. I won't invent one. If you have real data (even "median setup: 8 minutes" from actual users), that's what goes here.

Apply — rewrites

Error message
Before: "Oops! Something went a little sideways. Don't worry, our team is on it!"
After: "Something broke on our end — we're on it. Status: [link]"
Maps to: Unhurried honesty (states the real situation, no manufactured cheer), Plain-spoken (cuts "oops"/exclamation performance).

Pricing line
Before: "Unlock your team's full potential with our enterprise-grade solution."
After: "Built for the way you actually work — solo or a few people, not a department."
Maps to: Plain-spoken (no "unlock potential" abstraction), Respect for their time (states the actual differentiator instead of a generic superlative).

Next steps

1. Pressure-test these 3 attributes against 5-10 more real samples (support replies, more Slack, a sales call transcript) — three samples is a workable start, not full discovery.
2. Get a real number for at least one proof point before this hierarchy goes into any external content.
3. Rewrite the homepage headline next — it's the biggest visible gap between stated voice and current copy.