DNN / BRAND VOICE / v1.0

We speak like we build.

Applies to everything we publish on behalf of Dinnartec: landing pages, subpages, SaaS products, email, social, support, proposals, NAVI output to customers, and AI agents inside product interfaces.

Evidence over poetry/Clear over clever/Confident without theatre
01WHO / TONE OF CHARACTER

Identity. Who we are when we speak.

Dinnartec speaks like a builder who also teaches. Someone who already did the work and can explain it without ceremony or empty jargon.

Attributes. No half measures.

Irreverent.

We are not afraid of the category or its rituals.

Expert.

We know what we are doing, and it shows.

Warm.

We talk like people, not like a company.

Casual.

No verbal suits, no protocol.

Emphatic.

We state things. We do not float.

Raw.

We prefer direct over polished.

Human.

Instrumental when needed, but never robotic.

Optimistic.

Building is an act of faith. The voice should show it.

Productive tensions

These pairs are not contradictions. They are the texture. If a Dinnartec text only carries one side, the voice is incomplete.

Irreverent, but respectful.

We say what we think. We do not disrespect people.

Expert, but teacherly.

We know the field. We explain it with patience, not condescension.

Close, but not overfamiliar.

Direct address, yes. Fake intimacy, no.

Raw, but precise.

Direct does not mean careless.

If Dinnartec were a type of text

A story with timeline and detail. Or a board/canvas where every piece is placed with intent. Never a flyer, never a corporate brochure, never a consultancy white paper.

References

Sounds like where we want to land
  • Vercel. Technical, precise, mono-forward, developer-first, no filler.
  • X. Lean, irreverent, unapologetic.
  • Apple. Declarative, spacious, confident without theatre.
We do not want to sound like this
  • Traditional consultancy. Promises too much, says too little, hides in abstraction.
  • Microsoft corporate. Heavy, formal, full of hedging.
  • Law firm. Distant, covered, written to avoid saying anything.
02CONSTANT / ACROSS ALL SURFACES

Voice. What does not change.

Voice is the set of traits that stays constant in every context. Tone changes. Voice does not.

Three signature lines

UseLine
Primary heroWe build AI-native software.
Secondary lineSoftware that works for you.
Institutional sloganInnovating the future, improving the present.

Three tests for voice

Before publishing any piece, ask:

Test / 01
Concrete promise or just poetry?

If we cannot prove it, we do not say it.

Test / 02
Can someone outside the category understand it?

If the sentence needs a glossary, it is broken.

Test / 03
Does it sound like Dinnartec or like "a company"?

If any SaaS could sign it, rewrite it.

Default subject
"We" + "you", always.

We build, make, ship. The reader is "you".

03VARIANT / BY SURFACE

Tone. What changes by context.

Voice stays the same. Pressure changes. This table decides.

SurfaceRegisterExample
Hero / primary marketingDeclarative, brief, closed.We build AI-native software.
Vertical subpagesMixed-weight, line with a finish.Open research and experimentation.
Technical error / 404Direct, no blame theatre.Nothing lives here. You took the wrong turn.
Confirmation / successConcrete, with a number.We got your message. You will hear back in under 24h.
First-time SaaS onboardingWelcoming without syrup.Welcome to [product]. Here you manage [what].
Transactional emailFunctional, no ceremony.Here is your purchase receipt.
Support / broken stateAcknowledge + plan, no loose apology.We understand the issue. Here is what we are doing.
Sales / B2B proposalsSame voice as the landing, with more numbers.Same voice. The data changes, not the register.
SocialNever marketer-ish. Observation, statement, thread, dry joke.Adapt the format. Keep the voice.
Slack / internalSame tone. Shorter length.No "good morning team." Get to the point.
04WORDS / DEFAULTS / TRAPS

Vocabulary.

Vocabulary carries posture. These are the words that keep the system sharp, and the words that make it generic.

Use

We build / We ship / We test / It works / When it works / Engagement / Brick / Build / Ship / Live / Ready / Evidence / Scope / Operation / State / Coordinate / AI-native / Agent / Operator / Ecosystem / Innovative / Leader

Avoid

cutting-edge / game-changing / seamless / seamless experience / revolutionary / transformative / synergistic / holistic / disruption / disruptive / solution (= product) / empower / maximize / optimize as marketing filler / best-in-class / take your business to the cloud / next level / the future of X

Trap rewrites

TrapRewrite
We take your business to the cloud.Your operation, in production, this week.
A custom solution.Software that adapts to how you work.
We empower your team.Your team operates less. It does more.
We innovate for you.We build for you.
05OPERATIONAL / STYLE

Writing rules.

Concrete rules: casing, punctuation, emoji, dates, length.

Rule / 01 / Casing

Sentence case in headlines, titles, paragraphs, and prose buttons.

Uppercase is reserved for DS chrome: eyebrows, badges, foot strips. It is visual structure, not voice.

Rule / 02 / Punctuation
  • Final period in headlines when the sentence closes.
  • Oxford comma: yes.
  • Em dash (U+2014): no. Replace with a period, colon, or comma.
  • Quotes: straight quotes.
  • Separator: metadata only, never prose.
Rule / 03 / Emoji

Zero. Never. In any channel.

Product, marketing, social, internal Slack, proposals, support. None. DS glyphs are UI, not emoji.

Rule / 04 / Numbers and dates
  • Money: use the symbol. $3,000/month.
  • Spanish dates: short English month, May 1, 2026.
  • English dates: day-first numeric, 01/05/2026.
  • Real counts always. If it is 2, say 2.
Rule / 05 / Length
  • Headline: max 10 words.
  • Lead / paragraph: 4-6 lines.
  • Button / CTA: 1 word ideal, 2 max.
  • General sentence: short. If it can be cut, cut it.
Rule / 06 / Global English

Neutral, global English.

Avoid local slang, forced idioms, and region-specific jokes. The line should read clearly from Bogota to London to Singapore.

06ADAPTATION / NOT TRANSLATION

Bilingual. ES to EN.

English is not a 1:1 translation. It adapts the rhythm while keeping Dinnartec voice and tone.

ESEN adaptation
Construimos software AI-native.We build AI-native software.
Construimos software que trabaja para ti.Software that works for you.
Lo que probamos sale como codigo. No como promesa.What we ship is code. Not promise.
Publicamos cuando funciona. No antes.We ship when it works. Not before.
Tecnologia con proposito.Technology with purpose.

Operating rule. If an ES line only works because of rhythm or double meaning, rewrite it in EN. Do not translate it literally. Same in reverse.

07PROPER NOUNS / KEBAB SLUGS

Product naming.

Internal products are proper nouns and keep their written form in every context.

Display in proseInternal slug
NAVInavi
Brickendbrickend
Real Estatereal-estate
Fitnessfitness
ElPlanEs (client)elplanes
Never

Real-Estate / RealEstate / realEstate / REAL ESTATE in prose / Navi mixed case

08WORKED / CONCRETE

Examples. Do and don't.

Concrete pairs. When in doubt, find the closest pair and decide from there.

Headlines

Do
We build software like an essay.
Don't
The revolution in enterprise software.
Do
Technology with purpose.
Don't
Innovative technology solutions.
Do
Software that organizes, automates, and helps you operate less.
Don't
We empower your team with technology.
Do
Open research and experimentation.
Don't
The future of technology research.
Do
We ship when it works. Not before.
Don't
Cutting-edge launches every week.

Errors and states

ContextDinnartecNot Dinnartec
404Nothing lives here. You took the wrong turn.Oops! Something went wrong.
Form sentWe got your message. You will hear back in under 24h.Thank you for contacting us! We will get back to you soon.
MaintenanceTomorrow, 05/05/2026, between 02:00 and 04:00, [product] will be unavailable. Come back after.We are improving your experience. Sorry for the inconvenience.
Failed paymentThe payment did not go through. Check your method and try again.There was a problem processing your payment. Please try again later.
OnboardingWelcome to Real Estate. Here you manage inventory, clients, and contracts.Hi! We are so happy to have you. Start your journey here.

Same input, Dinnartec version

Prompt / Promote that Brickend is now on npm

Brickend is now on npm.

bun install -g brickend and start building.

14 bricks, 7 templates. Open source as of today.

Prompt / Announce scheduled maintenance

Tomorrow, 05/05/2026, between 02:00 and 04:00, Real Estate will be unavailable.

Scheduled maintenance. Back at 04:00.

Prompt / Announce a Senior Dev opening

We are looking for a Senior Dev who knows how to build, not just write code.

Stack: TypeScript, Next.js, Postgres. Remote from LatAm.

Apply at hello@dinnartec.com.

09AI COMPLIANCE / SAME VOICE

NAVI and AI agents.

NAVI writes like Dinnartec. Same voice, same tone, same rules. It does not sound like a generic AI assistant.

Rules for customer-facing output

Rule / 01
Identity.

"I" when NAVI operates, "we" when it speaks for Dinnartec. Never "as a language model..."

Rule / 02
Conciseness.

Maximum 4-6 lines per block. Same rule as humans.

Rule / 03
No theatre.

It does not announce what it is about to do. It does the work and delivers.

Rule / 04
States.

If it is processing, say what it is processing. If done, say what it found. If failed, say what failed and what comes next.

Rule / 05
No-list applies.

Never cutting-edge, innovative, seamless. Not even in generated suggestions.

Rule / 06
No emoji.

Never. DS glyphs only live in UI.

Compliance checklist

Before showing output to the user:

  • 01Does it sound like Dinnartec or generic ChatGPT?
  • 02Is there a word from the no-list?
  • 03Are there emoji?
  • 04Does it open with "Hi!" or "Welcome!" when it does not need to?
  • 05Does it apologize without a reason?
  • 06Does it promise something it cannot prove?
  • 07Is it sentence case, not Title Case?
  • 08Does it go past 6 lines without need?
  • 09Does it use an em dash?

If any item lights up, rewrite before shipping.

10ABSOLUTE / NO EXCEPTIONS

Hard no-list.

Absolute rules. No exceptions. If output breaks one, rewrite it before publishing.

  1. 01No emoji. In any channel, in any context.
  2. 02No em dash (U+2014). Replace with a period, colon, or comma.
  3. 03No regionalisms. Global-neutral English always.
  4. 04No words from the NO list.
  5. 05No marketing exclamations ("Incredible!", "Last chance!").
  6. 06No vague promises. If we cannot prove it, we do not say it.
  7. 07No "as a language model..." or any robotic equivalent.
  8. 08No excessive apologies. Acknowledge and move.
  9. 09No direct 1:1 copy between ES and EN. Always adapt.
  10. 10No "marketing voice" in social, sales decks, onboarding, or support.