Brand / Tone and voice
Tone and voice
NTWRK sounds like an operator who has read the data, says what it shows, shows the scene where it matters, and stops. Drafted by the NTWRK Content Editor from canon v2 and live copy. Approved in v1.0.
01The voice in one line
An operator who has read the data, says what it shows, shows the scene where it matters, and stops.
Register: operator-grade, dry, high-EQ. Australian in sensibility: direct, practical, sceptical of hype. Contractions are house style.
02Voice principles
| Principle | Why |
|---|---|
| Plain over clever. Say it the way you’d say it to a CFO. | The buyer has to repeat it to a board. Clever doesn’t survive the retelling. |
| Evidence over adjectives. A count with its denominator beats a claim. | A count can be checked. “Robust” can’t. |
| Show the scene. Put a person, a place or a moment next to the number. | A scene is how a number gets remembered. |
| The reader is the subject. Open on “your”, the problem or the finding. | Never open on “We”, “Our” or “NTWRK”. |
| Declarative over hedged. State it once, then state the limit once. | Caveat soup reads as fear. One clean limit reads as honesty. |
| Quiet confidence over hype. | No superlatives, no urgency, no countdowns. |
| Credit before critique. | A reader who feels caught stops reading. |
| End on the reader’s problem. | A competence close is a pitch with the ask removed. |
| Ownership lands somewhere. | Site and sales copy say what the client keeps. Editorial says it where true. |
03Do and don’t, from real NTWRK copy
Each “don’t” is a real line from the site. Each “do” uses only facts already on the site. Headings: 3 to 7 words, under about 45 characters, concrete, two beats, never explaining (“The log said fine.” · “Two of thirty-three.”).
Name the systems, don’t summarise them
Do
Your customer data sits in the CRM, the email tool, the analytics account, the warehouse and a spreadsheet someone guards.
Already live on the customer intelligence page. Reuse the scenes the site has.
Live: customer intelligence page
Don’t
Your customer data is spread across systems.
Live: Home, entry points
Make the exit a moment
Do
Plan the exit before you sign. The supplier’s last day is the test. Someone inside the business has to open the logic, approve a change and keep the work running the next morning.
Same facts, set on a particular day.
Content Editor rewrite
Don’t
Your next supplier decision should include the exit. A useful system needs an owner inside the business.
Live: Home, 04
Count the parts, let the reader choose
Do
Eight parts. The use case picks which.
The heading carries both facts on the page.
Content Editor rewrite
Don’t
What a working build can include.
Live: Home, 03
Cut the numbered three
Do
At renewal, the vendor knows what is embedded in its platform. The customer finds out when it starts counting the cost of leaving.
Lead with the sharpest consequence.
Content Editor rewrite
Don’t
That has three consequences. First, … Second, … Third, renewal negotiations become asymmetric.
A numbered three reads like a slide and is a slopscan tell.
Live: Field note No. 04
Keep the scene that’s working
Keep
It is the one someone says when renewal arrives: ‘We could leave, but it would be too hard.’
A moment and a line someone actually says. The standard for every opening.
Live: Field note No. 04
Don’t close on what we build
Do
End on the note’s own last line, then the standard subscribe block and nothing more.
Content Editor rule
Don’t
… is what NTWRK builds: the definitions, the model and the record of why. … The leaving test is where every conversation starts.
A competence close.
Live: Field note close band
Private insight pages: open on credit, drop the gotcha
Say what is working before what is not. State what the data cannot show once, without the jab. Speak as “we”, never “I”. No real lines from private pages appear in this book: it is public.
July Home copy worth bringing back
| Line | Why |
|---|---|
| “Stop at day 30 and the four outputs are handed over, documented.” | A plain statement of the handover. |
| “From 10 December 2026, privacy policies must disclose certain automated decisions.” | A bounded, dated claim. Use the corrected form in house rule 15: covered organisations, decisions that could significantly affect someone, kinds not reasons. |
Don’t revive
| Line | Why |
|---|---|
| “The intelligence you rent was never yours to keep.” | It contradicts renting models and platforms on merit. Moved here by Wes, 8 Oct 2026 (thesis audit C11). |
| “OWNED. NO RENT.” | The 23 Sep audit bounded “no rent”. |
04Words we use, words we avoid
| Use | Notes |
|---|---|
| intelligence you own | The category line is “AI-native intelligence you own.” Prefer “intelligence” to “capability”. |
| first-party, AI-native | Hyphenated, lower case mid-sentence. |
| customer intelligence, operating intelligence | The two doors. Lower case in running copy. |
| the decision logic, the data record, the workflow, the documentation | The four things a client keeps, always in this order (house rule 14). |
| Book a call | The one primary CTA wording, on every button (R5). “Scope the 30-day POC” is retired as a CTA. “30-day proof” is the only noun form. Avoid “POC” and “proof of concept” in copy. |
| Approved, 13 Oct 2026 A 30-day proof on one decision. / First engagement: a 30-day proof on one decision. | CTA lead-in, APPROVED by Wes, 13 Oct 2026: the short form under each Book a call button, the full form once per page in the close band. The footer keeps “Starts with a 30-day proof.” |
| Build to Keep | The publication. No hyphens. |
| How we work | The nav label and the page, /how-we-work/ (R6, #135). Never “How it works”, “Method” or “Ownership” as a label. |
| trace, see why each decision was made | People trace a decision or see why it was made. A system records decisions; it never “explains” them (house rule 13). |
| each decision | Never “the decisions that matter”. |
| delivery dock, prep bench, the plate Delivery dock bronze Prep bench silver The plate gold | The main public labels for the data tiers. Bronze, silver and gold appear only as small tags beside them. |
| Trading Manager | The role in the Example Co. retail trade meeting example. |
| Example Co., Example Shire | Synthetic business and council examples, tagged illustrative. |
| field note, Field Note 06 | |
| NTWRK | Always capitals in text. The wordmark is ntwrk/. |
| customers | Never “users” when we mean customers. |
| supplier | For third parties. “Vendor” for the market, never for us. |
| complaint | A one or two star review. Define once per piece. |
| listing, network, store, venue | Concrete nouns from the data. |
Avoid
transformunlockleverageutilizeseamlessrobustsuperchargesynergycutting-edgerevolutionarygame-changerempowerelevateholisticparamountfurthermoremoreoverdelvesolutionsbest-in-classworld-classAI-powerednext-generationend-to-end (filler)tenantusers (for customers)platform (for us)vendor (for us)AI transformationdigital transformationAI adoptionfuture of workcopilot (as our noun)10xAI agencynavigate (filler)transformativethis changes everythingit is important to notein today’s rapidly evolving landscapefive ways leaders canBuild-to-KeepAgree?Thoughts?
| Also avoid | Notes |
|---|---|
| “Explain” for a system’s decisions | “a system that explains its decisions”, “a smaller surface to explain”. A person or a vendor explaining their approach is fine. |
| Storage vendor names | (cloud providers, data platforms) in public copy, figures, captions, alt text, decks or field notes. No logos. Wes can name options in conversation. |
| “Scope the 30-day POC” | As a button or link label. |
05House rules
- No em dashes or en dashes. Full stop, comma, colon, or “to” for ranges (“2 June to 9 September 2026”).
- No “rather than”. Field Note 06 and Issue 04 cleared at zero; zero is the standard.
- No “we”, “our” or “us” in field notes or newsletter issues. See the surface table.
- No client names in public content beyond the clients already cleared on the site. Field notes and newsletters name no business. Networks are lettered, or given a category only with Wes’s clearance, and get no counts that could identify them.
- Never end on a pitch. Check the last two sentences.
- Staff names are always masked, even in quoted reviews: keep the first letter and the length (
T********). - Signature devices at most once per page.
- No rule-of-three lists used only to sound authoritative.
- Label the evidence: fact, interpretation, inference, opinion or recommendation.
- Run slopscan and read every hit. Zero unearned hits.
- “Own the layer that decides.” Allowed only in the newsletter, the close of the Own the record field note, the one LinkedIn post and Wes’s spoken answers. Never on Home, About, the nav, or any meta or OG text.
- No prices. No figure, range or placeholder anywhere public. Where price comes up: “Pricing is set in the proposal after scoping.”
- The trace rule. Copy promises that people can trace a decision or see why each decision was made. It never says a system “explains” decisions.
- Ownership order. Ownership means the decision logic, not where the data sits. Where the four owned items appear, decision logic comes first, then the data record, the workflow and the documentation. Where ownership is introduced, the zero-copy concession goes first, word for word: “Some platforms can now leave your data in your warehouse, which is good. The question is where your identity rules, segments and agents live.” Approved placements: the
/how-we-work/owns section and the Home panel only. Never on About. Once per page. - Retired claims and on-hold stats.Retired: rent-back lines (“copy your data into their store and rent it back”, “The intelligence you rent was never yours to keep.”, “OWNED. NO RENT.”); “Systems you own can explain their decisions. Systems you rent explain nothing the day you leave.”; any claim that a business must explain each customer’s outcome (APP 1.7 to 1.9 asks for kinds of information and kinds of decisions, not reasons); owned systems as “compliant by default”; AI costs rising or tripling; rip and replace; owning as cheaper; “The direction is no longer in question.”On hold until sourced. The on-hold figures are listed in the internal voice.md.The December line, when used: covered organisations, decisions that could significantly affect someone, kinds of information and kinds of decisions, the vendor point, and “a privacy lawyer signs off the policy”. Source: Wes’s APP 1.7 position doc, 8 Oct 2026.
06en-AU conventions
| Topic | Rule |
|---|---|
| Spelling | Australian: organisation, behaviour, prioritise, analyse, centre, sceptical, judgement, licence (noun), license (verb). program vs programme: “program” is the house spelling, confirmed in the 8 Oct 2026 audit and applied site-wide (PR #139). |
| Dates | “20 July 2026” in copy. Short form “Tue 13 Oct” in tables and subject lines. Ranges with “to”. Periods anchored: “in the 12 months to 9 September 2026”. Every figure carries its capture date. |
| Times | 24-hour with zone: “10:00 AEDT”. |
| Numbers | Words for one to nine, numerals from 10; spell out a number that starts a sentence. Thousands take a comma (1,389); round with “about”. Denominator on first use. Hyphenate compound adjectives (“30-day proof”, “five-star review”); the site writes “one and two star reviews” unhyphenated for now. |
| Percentages | 57.8%: numeral, no space, one decimal in data copy. |
| Currency | No code, Australian dollars assumed. “A$” only beside another currency. No prices: no figure, range or placeholder anywhere public (house rule 12). Illustrative “50% of 160”, a count with its denominator, not a fee. |
| Quotes | Double curly quotes, as on the site. |
07How the voice shifts by surface
| Surface | Who speaks | Pronoun | The ask |
|---|---|---|---|
| Site | NTWRK | “we” allowed; claims open on “you” | Yes. One primary CTA (“Book a call”) and one form per page. The lead-in under the button is approved by Wes, 13 Oct 2026 (section 4, Use). |
| Field notes | NTWRK (Wes’s ruling, 15 Sep 2026) | No we/our/us; NTWRK in third person | None in the body; standard subscribe block |
| Newsletter | NTWRK. From: “Build to Keep from NTWRK” | No we/our/us | None; footer added at send |
| Private insight pages | NTWRK, to one named client | “we”, never “I” (decided 5 Oct 2026) | One clear next step, no pressure lines. |
| Sales | NTWRK | we | Yes; NTWRK holds every ask |
| Wes’s channels | Wes | I, never we/our/us | Never, including no competence close |
08Pre-publish check
No dashes, no “rather than”, no banned words. No we/our/us where the surface table bans it, and no claim opening on “We”, “Our” or “NTWRK”. No unmasked staff name and no uncleared client. Every number has a denominator and a date. The opening is a scene or a finding. At least one heading is a kicker. The last two sentences leave the reader holding their own problem. slopscan run, every hit read. No price, no retired claim or on-hold stat, no storage vendor name, no system that “explains”. The four owned items run logic first, and the position line appears only where house rule 11 allows.
09Canon examples
Do
We build AI-native intelligence, and you own it.
Canon v2
Don’t
We leverage cutting-edge AI to unlock seamless, transformative customer experiences.
Five banned words in one sentence.
Canon v2 (before)
Do
We ship software. Fast, reliable, yours.
Canon v2
Don’t
We ship software — fast, reliable, yours.
Em dash.
Canon v2 (before)