4.0 Who we're writing for
The most important rule on this page
We're writing for mortgage brokers, insurance agents, dealership owners, home services operators, solar installers, fintech sales leads, and tour operators.
We are not writing for software buyers. We are not writing for startup people. We are not writing for engineers.
These readers have been in business for 20 years. They've been pitched a million products. They have sharp BS detectors. They want plain English, real numbers, real customers, and respect for their time.
4.1 The vibe, in five words
If a draft doesn't feel like all five of these, it's probably off-brand.
Confident
We know how lead conversion actually works. No hedging, no fluff.
Clear
Plain words, short sentences. Every paragraph earns its place.
Friendly
We're in this with the reader. Warm, not saccharine.
Grounded
Real examples, real numbers. We don't float above the problem.
Sharp
Opinions have edges. Clever beats cute. Every time.
4.2 Do & don't
Quick reference for what to reach for, and what to refuse.
Do
- Speak like a smart friend who's seen this exact problem before.
- Lead with the outcome. “More leads closed” beats “cutting-edge AI.”
- Name the pain in the reader's words before you prescribe.
- Show one concrete example where a principle lands.
- Use the tagline in full: “Building AI Magic — One Block at a Time.”
- Default to short sentences. Long paragraphs earn their length.
- Use specific industry language. Mortgage brokers say “rate,” “LO,” “pre-qual.” Insurance agents say “carrier,” “renewal.” Auto says “trade-in.” Match it.
- Treat the reader as already an expert. They know speed-to-lead matters — don't define it.
Don't
- Don't stack jargon (“AI-powered lead intelligence platform”).
- Don't hedge with “just,” “simply,” or “literally.”
- Don't promise revolutions. Promise the next 30 days.
- Don't describe the product without describing what it fixes.
- Don't use “utilize” when “use” does the same work.
- Don't write anything a real human wouldn't say out loud.
- Don't say “AI-powered.” We are AI. Stating it is filler.
- Don't paint us into a service corner. We're product-first; services are a useful option.
4.3 Eight messaging principles
The shape of an on-brand sentence. Each one paired with a side-by-side off-brand vs on-brand example.
Eight principles that actually ship.
If a draft doesn't line up with one of these, it probably shouldn't go out.
Diagnose before you prescribe.
Name what's broken in the reader's world before you explain how we fix it. Prescription without diagnosis reads as a sales pitch. Diagnosis reads as expertise.
Lead with outcomes, not features.
Features only mean something once the outcome lands. Always pair “what it does” with “what you get because of it.”
Pressure + relief.
Name the pain honestly. Then offer the release. Never only pressure. Never only relief.
Show, don't just tell.
Proof beats adjectives. A concrete number, a customer quote, a before / after — all land harder than any claim.
Expert friend, not salesperson.
Write like you'd explain it to a friend who asked for help. Not a deck. Not a landing page. A friend.
Subheads stay scannable.
Hero subs: 12–22 words. Section subs: 10–20. If a sub doesn't fit, it's doing two jobs. Cut it down to one.
Specifics over adjectives. Always.
Every claim ships with proof. A number, a customer name, a real outcome. Naked claims read as fog.
Sales-led describes how you buy, not how you run.
MagicBlocks is product-first with services available. Bigger teams often run it themselves. Smaller teams typically take onboarding services. Both are valid customers. Never paint MagicBlocks as service-only or self-serve only.
4.4 Banned words
The software-sales cliché hall of fame. These words don't add information — they add noise. Prefer the plain version every time.
Banned
- revolutionary
- cutting-edge
- game-changing
- world-class
- best-in-class
- seamless
- synergy / synergies
- unleash
- empower
- robust
- disruptive
- innovative
- transformative
- scalable
- leverage (verb)
- utilize
- just
- simply
- literally
- obviously
- solution
- stack
- API
- endpoint
- real-time
- orchestration
- JSON-driven
- deploy / deployment
- multi-prompt architecture
- state machine
- CDP-native
- Guardian compliance layer
- production-grade (without specific proof)
- enterprise-grade
- AI-powered (as a feature claim)
- operator (when overused)
4.5 Tech jargon → plain English
When you catch yourself reaching for the left column, switch to the right.
4.6 Words we love
The vocabulary that actually describes what MagicBlocks does — the funnel, the reply, the human moment, the operator's day.
Words we love
- Lead
- Conversation
- Qualify
- Nurture
- Convert
- Momentum
- Respond
- Reply
- Human
- Reliable
- Every time
- In minutes
- Playbook
- Pipeline
- Speed-to-lead
- Funnel
- Leak
- Booked
- Closed
- Reps
- The team
- In production
- Day one
- By Monday
- Real customers
- Battle-tested
4.7 Anatomy & notes
A few operating rules that keep the voice consistent across channels.
- The tagline is always written with the em dash — not a hyphen, not a colon: “Building AI Magic — One Block at a Time.”
- We use sentence case for headings. Title Case reads as a press release.
- Numbers are always numerals (“60 seconds”, not “sixty seconds”) except at the very start of a sentence.
- Product names take a capital M + B: MagicBlocks, never “Magic Blocks” or “magic blocks”.
- Never position MagicBlocks as a remedy for legal liability or lawsuits. Saying “stop AI from getting you sued” implies legal protection we can't guarantee — and ironically increases legal risk. Frame the same point as operator rigor: “Won't say something that puts you in trouble” / “Built so the AI works inside your rules” / “Production-grade compliance discipline.”
- When in doubt: read the sentence aloud. If a real person wouldn't say it, neither should we.