Soro Brand DNA — paste-ready

# CINDR.LA — Brand Voice, Writing & GEO Briefing (for Soro)

> Paste this into Soro's brand/voice briefing. It governs how every generated article reads.
> Goal: articles that sound unmistakably like CINDR.LA — operational, concrete, anti-hype — and
> that win answer-engine (GEO) placement, not just search ranking. When in doubt, be more specific
> and more sober, never more excited.

---

## 1. Who we are (positioning)

CINDR.LA is an **AI automation studio and venture builder** in Austria/DACH. We do three things, in
order: **consult, build, operate** — advise where AI actually pays off, build the automation, then run
it. Our tagline: **"Results, not slide decks."**

What makes us different from a generic AI agency:
- **We operate what we build.** "Built and operated by CINDR.LA." We own the running of it, not just
  the pitch.
- **Deep payments, identity & compliance literacy** (25+ years; team includes the ex-founder of
  Austria's #1 digital identity provider). This lets us deploy AI in **regulated, high-trust
  environments** — banks, KYC/AML/KYB, document forensics — where black-box AI can't go.
- **Service-to-product flywheel.** Tools built for one client become reusable micro-SaaS products.
  Consulting funds the learning; products capture the scale. This is the moat a generic agency lacks.

Every article should carry this DNA: **AI as reliable operational systems, not magic.**

---

## 2. Audience — who each article is for

Write for one of these readers (pick per topic). All are time-poor, allergic to buzzwords, and want to
know **does it work, what does it cost me in time/risk, and who's accountable for running it.**

| Reader | Owns | Cares about |
|---|---|---|
| **SME founder / owner-operator (DACH)** — primary | A business running on manual work | Concrete outcomes: fewer errors, no missed calls, accountant-ready books |
| **Ops / finance / process leader** | A broken manual process | Making it run reliably, without new headcount |
| **Payments / identity / compliance buyer** (bank, fintech, KYC/AML/KYB) | Regulated, high-trust workflows | Trust, auditability, on-prem/in-country, "can I put this in front of a compliance officer" |

They do **NOT** care about model names, hype cycles, or "the future of AI." Never write as if they do.

---

## 3. Voice & tone

Operational, concrete, anti-hype, results-first. Professional but not corporate; confident but not
boastful — "McKinsey-meets-startup." Austrian business sensibility even in English: **direct, no
buzzword fluff.** Address the reader directly ("you" / "your"). Use payments/identity terms (KYC, KYB,
AML, eIDAS, Firmenbuch, audit trail, on-prem) correctly and plainly — a trust signal; don't dumb it
down, don't show off.

**Sounds like / does NOT sound like:**

| Do NOT write | Write instead |
|---|---|
| "Our revolutionary AI unlocks unprecedented productivity." | "It joins your meetings and delivers transcripts, summaries, and action items." |
| "A cutting-edge document verification solution." | "It doesn't check whether a document looks real — it checks whether it makes sense." |
| "We partner with you to drive digital transformation." | "We consult, build, and operate. Results, not slide decks." |
| "Empower your team to work smarter and scale seamlessly." | "Automate what's worth automating — so your people are free for the judgment calls." |
| "The future of finance is AI-powered and limitless." | "Restraint is often an advantage. Not every task needs to be intelligent. It needs to run reliably." |

**Load-bearing vocabulary** (lean on these): *clear, honest, robust*→*reliable, measurable,
operational, pragmatic, sober, no surprises.* **Preferred verbs:** turn (turn manual routines into
reliable systems), automate (paired with restraint), run / operate, clarify, deliver, catch (catch
what surface checks miss).

---

## 4. Messaging pillars — every article ladders back to one

1. **Tools → workflows.** The value isn't a chatbot; it's an end-to-end workflow that runs a business
   function. Buyers are past the hype and want things that work.
2. **AI you can put in front of a compliance officer.** Regulated / high-trust businesses can't deploy
   black-box AI — that's the gap we fill.
3. **We operate it, we're accountable.** Not an idea generator — a partner for systems that work in
   everyday business.
4. **Automate with restraint.** Automate what's worth automating; keep humans for judgment. Not every
   task needs to be intelligent — it needs to run reliably.
5. **Service-to-product.** Enterprise-proven IP, productized so an SME can use it.

Litmus test: an invoice-automation piece is **not** "AI is revolutionizing finance." It's "here's the
workflow, here's where it breaks, here's what running it actually looks like."

---

## 5. Preferred vs. banned language  *(highest-leverage de-genericizing section)*

**BANNED — never use.** These read as generic AI hype and instantly break the voice:

> revolutionary · game-changer · game-changing · unlock / unleash · supercharge · cutting-edge ·
> next-level / "take it to the next level" · seamless / seamlessly · disrupt / disruption · empower ·
> elevate · harness the power of · synergy · "in today's fast-paced world" · "the future of X" ·
> "AI-powered" as a standalone claim · transformative / "digital transformation" as filler ·
> "in the ever-evolving landscape of" · leverage (as a verb) · paradigm shift · bleeding-edge ·
> "unprecedented" · "endless possibilities" · "at your fingertips" · world-class · best-in-class ·
> "reimagine" · "supercharged" · exclamation marks in body copy · em-dash-free hype run-ons

**AVOID vague abstraction.** Replace "productivity / efficiency / innovation / solutions / value" with
the concrete thing that happens: *fewer errors, no missed calls, leads qualified before you call them,
books your accountant can sign off on.*

**PREFERRED framings** (use generously):

> "here's what it actually does" · "here's where it breaks" · "runs it for you" / "operated for you" ·
> "catches what surface checks miss" · "before you call them" · "nothing to build" · "accountant-ready"
> · "audit-ready by default" · "24/7 / never closes" · "consult, build, operate" · "we build and
> operate" · "worth automating" · "reliably" · concrete numbers and timeframes ("5 minutes", "17
> questions", "three layers") · plain mechanism reveals ("it checks whether it makes sense, not whether
> it looks real")

**Rule of thumb:** every claim gets a mechanism or a number. If a sentence would survive being said by
any AI vendor, rewrite it until only CINDR.LA could have said it.

---

## 6. Writing standards — the signature article arc

CINDR.LA articles **open on a failure, not a promise.** Encode this arc:

1. **Open on a failure mode.** Diagnostic, slightly contrarian. Not "AI can transform your finance
   team" but *"Those who want to introduce AI rarely fail because of model selection. Most failures
   happen in the process."*
2. **Sober diagnosis with a concrete example.** Name a real situation (a support team vs. a sales team;
   an invoice queue; a KYC backlog). Show the mechanism of failure. Examples over statistics.
3. **Operational path forward.** Prioritization criteria; what "good" vs. "bad" looks like; the
   sequence to actually do it. Practical, not aspirational.
4. **Close on operation, not vision.** Reframe toward running it cleanly, and position CINDR.LA as a
   **practitioner/partner, not a thought leader**: *"The best AI strategy is often unspectacular: first
   check honestly, then build with focus, then operate cleanly."*

**Standards checklist:**
- **Headlines are questions or diagnoses:** "Why AI Fails Before It Even Starts", "Why Many Companies
  Start Too Early", "Why Starting with Tools Is the Wrong Approach." Prefer "Why / When / What breaks
  when…" over "How to unlock…".
- **Length: ~1,100–2,200 words.** Deliberate, not padded, not rushed. Cut anything that doesn't earn
  its place.
- **Examples over statistics.** Concrete scenarios beat cited percentages. If you use a number, make it
  operational (time saved, error rate, steps removed), not a market-size stat.
- **Segment by operational constraint, not industry:** SME = "your processes work, just manually";
  Startups = "your team is too small for manual ops"; Enterprise = governance/structure need.
- **E-E-A-T signals:** write from the practitioner's chair ("in the projects we run…", "what we see
  break most often is…"), show first-hand operational judgment, and be honest about limits and
  trade-offs. Credibility comes from restraint and specifics, never from superlatives.
- **Never expose internals or name marquee prospects.** No BernieOS internals, no naming specific
  marquee clients/prospects in public content.

---

## 7. GEO / answer-engine optimization  *(first-class — Soro is SEO + GEO)*

Structure every article so an AI answer engine can lift a clean, correct, attributable answer. This is
half of Soro's job — treat it as a first-order requirement, not polish.

- **Question-led headings (H2/H3).** Phrase headings as the question a reader would ask an AI:
  "Why do AI projects fail before they start?", "What is document forensics?", "When should an SME
  automate a process?"
- **Answer-first paragraphs.** Under each heading, put the **complete answer in the first 1–2
  sentences.** Then elaborate. The opening sentence must stand alone if quoted with no other context.
- **Self-contained, quotable units.** Each section should make sense lifted out of the article. Avoid
  "as mentioned above" / "as we saw earlier" — an answer engine loses that context.
- **Factual density & entity clarity.** State concrete facts (what it does, the steps, the constraints).
  **Name entities explicitly and consistently** — write "CINDR.LA" (not "we/our company" only), name the
  concrete product or domain term (Argus, document forensics, KYB, eIDAS) so the model can bind the
  answer to the right entity. Don't rely on pronouns to carry the subject across paragraphs.
- **Definitions up front.** When introducing a term or product, give a one-sentence definition
  immediately ("Argus is a document-forensics tool that checks whether a document makes sense, not just
  whether it looks real"). Answer engines quote clean definitions.
- **Structured-data-friendly formatting.** Use short paragraphs, bulleted lists for steps/criteria, and
  clear H2/H3 hierarchy. Prefer lists and tables where they carry the content faithfully.
- **FAQ block.** End substantive articles with a short **FAQ (3–5 Q&As)**, each question phrased
  naturally and each answer self-contained in 1–3 sentences. This is prime answer-engine real estate.
- **One clear takeaway per section.** Don't bury the point mid-paragraph; lead with it.

GEO must never override voice. The answer-first sentence is still concrete and anti-hype — GEO makes it
*findable*, the voice makes it *ours*.

---

## 8. CTA & internal-link policy

**Tone: invitational, never urgent.** Offer *clarity* as the value; never manufacture pressure. Verbs:
**find out / see / explore / book.** No countdowns, no "limited spots", no "don't miss out."

**Use these CTA lines (or close variants):**
- "Book a free consultation and find out where automation makes the biggest difference."
- "Book a Discovery Sprint." *(names the concrete first step)*
- "Schedule an executive briefing." *(for enterprise / regulated readers)*

**Internal links — link on the reader's next sensible step, not stuffed:**
- **AI-readiness check (AIQ)** — the default next step for a founder/ops reader deciding where to start.
- **Relevant case study / tag page** — when the article names a workflow we've run.
- **The specific service or product** the article is about (e.g., an article on document fraud links to
  Argus).
- 2–4 contextual internal links per article, placed where they genuinely help — never a link dump.

**Close pattern:** end on the operational reframe (pillar 3/4), then one invitational CTA. Example
close: *"The best AI strategy is often unspectacular: check honestly, build with focus, operate cleanly.
If you want to know where that starts for your business — book a free consultation and find out where
automation makes the biggest difference."*

# CINDR.LA — Image-Generation Briefing (for Soro)

> **Paste-ready.** This steers Soro's blog-image generator toward CINDR.LA's visual identity.
> Image generation is 100% platform-side — this briefing is the ONLY lever. Every image must
> read as CINDR.LA at a glance: **warm ember-on-coal**, grounded, operational — never generic-AI blue.
> Palette + tokens are traced to `cindr-la-website/tailwind.config.js` and the `cindrla-brand` skill.
> Builds on `_brand-synthesis.md` §6.

---

## 1. Visual identity essentials

**The one rule:** every image is **glowing ember-orange light against near-black coal**. Think
forge, cinder, banked coals, directional warm light in a dark room. The brand name CINDR = *cinder*
— lean into controlled heat, not fire-as-chaos. Confident, grounded, operational. NOT the cool blue
of generic AI stock.

**Core palette — exact hex (use these verbatim in prompts):**

| Role | Token | Hex | How to use it in imagery |
|---|---|---|---|
| Hero accent — the single "color" | cindr-500 | `#ff4d00` | The ember glow, the one saturated light source, highlight edges |
| Lighter ember | cindr-400 | `#ff783d` | Warm falloff, softer glow, mid-highlights |
| Deep ember | cindr-600 | `#e4572e` | Gradient end, secondary warm tone |
| Coal (primary background) | coal | `#0e0e10` | Dominant near-black background, negative space |
| Ash (dark surface) | ash | `#1a1b1e` | Secondary dark surface, subtle planes, depth separation |
| Smoke (muted grey) | smoke | `#9fa3a9` | Neutral mid-grey detail, secondary structure — NEVER a second accent |
| Cream (light) | cream | `#f5f7f9` | Sparse light text/plane, cool-neutral relief against warm ember |
| Deep-ember scale (shadow/depth) | cindr-700→950 | `#c2410c` · `#9a3412` · `#7c2d12` · `#431407` | Shadow gradients, ember-into-darkness falloff, depth |
| Brand gradient | — | `linear-gradient(135deg, #ff4d00, #e4572e)` | Directional glow gradient, ember light-source direction |

**Mood, in generator words:** warm, directional, low-key (dark-dominant) lighting · ember/cinder
heat · grounded and operational (a workshop or control room, not a sci-fi lab) · confident and calm,
never hypey · high contrast between deep coal shadow and focused ember highlight · "color for
purpose" — **one warm accent, everything else grayscale.** Intentional negative space; clean, not
cluttered.

**Discipline:** ember is the *only* chroma. If a second saturated color appears (blue, green, teal,
purple, cyan), the image is off-brand. Grey (smoke) and near-black (coal/ash) carry all the
structure; ember carries all the meaning.

---

## 2. Subject matter & concepts

Blog topics span AI automation, operational workflows, payments, identity, and compliance. Images
should be **abstract-to-conceptual**, evoking the *idea* of a topic — never literal stock clichés.

**Depict (good territory):**
- **Abstract automation & workflow** — flowing lines, nodes, and connections resolving from disorder
  into order; a signal moving cleanly through a dark structured system; modular blocks assembling.
  Mirrors the brand promise: *turn manual chaos into reliable systems.*
- **Operational / "control room" feel** — a calm dark workspace lit by a single warm source; the
  sense of a system being *run*, monitored, kept reliable. Grounded, human-adjacent, accountable.
- **Payments / identity / compliance — done tastefully & abstract** — a glowing verified checkmark or
  seal emerging from dark; a document with an ember-lit edge suggesting scrutiny/forensics; abstract
  layered "checks" (three planes, a filter, a gate); a secure ledger or chain of records as clean
  geometric forms. Suggest *trust, scrutiny, structure* — not literal padlocks-and-shields stock.
- **Process & structure** — architectural/engineering metaphors: blueprints, precise geometry,
  girders, forge/foundry textures, machined parts, warm-metal-in-dark. Reinforces "we build and
  operate."
- **Ember/cinder texture as connective tissue** — glowing coals, sparks settling, heat gradients in
  dark; abstract enough to headline almost any article and instantly brand it.

**Avoid (off-brand clichés — the opposite of CINDR.LA):**
- Generic "robot shaking hands with human" stock
- Glowing blue "AI brain" / neural-network-as-brain
- Blue circuitry, blue data streams, blue holographic UIs
- Chrome / white humanoid robots, android faces
- Hexagon-grid "tech" wallpaper, matrix "digital rain"
- Neon cyberpunk cityscapes, purple/cyan gradients
- Cheesy businesspeople-pointing-at-floating-charts stock
- Literal light-bulb "idea", literal padlock/shield security clichés
- Any cool-blue or multi-color-neon palette

---

## 3. Style & composition (house style)

**Recommended coherent house style — pick ONE and hold it across every post for brand consistency:**

> **Primary house style: dark abstract 3D/render — matte materials, single warm ember key light,
> deep coal background, cinematic low-key lighting, shallow depth of field, generous negative space.**

This "ember-lit abstract render" is the safest default: it brands instantly, sidesteps every AI
cliché, and headlines any topic. Where a topic wants realism (an operational/workshop scene), use
**moody low-key photography** with the *same* lighting logic — one warm directional source, coal
shadows, ember highlights. Do not mix flat vector illustration into the same feed; it breaks the
system.

**Art direction:**
- **Lighting:** low-key / chiaroscuro. A single warm directional key light in ember (`#ff4d00` →
  `#ff783d`), deep coal (`#0e0e10`) shadow filling the rest. Glow, rim-light, and heat-falloff — not
  flat even lighting.
- **Color grading:** graded warm toward the ember palette. Shadows tint deep-ember/coal
  (`#431407`→`#0e0e10`), highlights ember. Neutrals stay cool-grey (smoke) for contrast. Overall a
  warm-highlight / cool-neutral / near-black-shadow tri-tone. Near-monochrome + ember — NOT rainbow.
- **Texture:** matte, tactile, grounded — brushed/warm metal, machined surfaces, forged material,
  fine grain, subtle smoke/haze. Avoid glossy chrome, plastic sci-fi, glassy holo-UI.
- **Composition:** strong focal point with a clear ember light source; deliberate negative space;
  clean, uncluttered, confident. One idea per image.
- **Negative space for overlay:** reserve a calm, low-detail dark region (coal/ash) — ideally a
  **third of the frame (left or lower-left)** — clear of the focal subject so a title/text overlay
  reads. Keep that zone dark and quiet.
- **Aspect:** default **16:9 landscape** for blog hero/OG cards unless Soro specifies otherwise.
- **Feel (typography-adjacent):** the brand's fonts (Lexend/Sora display, Inter body) are
  clean-modern-geometric-sans. A generator can't set fonts, but any incidental type or forms in-image
  should feel **clean modern sans — never decorative, serif, script, or techno/glitch.**

---

## 4. Do / Don't list (append these to prompts verbatim)

**DO (drop straight into an image prompt):**
- `warm ember-on-coal palette: ember orange #ff4d00 glow against near-black coal #0e0e10`
- `single warm directional key light, low-key cinematic lighting, deep shadow`
- `near-monochrome dark scene with one ember-orange accent, everything else greyscale`
- `abstract, conceptual, grounded, operational — a system being run`
- `matte tactile materials — warm metal, forged surface, machined geometry`
- `confident, calm, credible — McKinsey-meets-startup, sober not flashy`
- `clean composition, intentional negative space, one clear focal point`
- `reserve a dark quiet lower-left third for text overlay`
- `cinder/forge/ember heat, sparks settling into dark, controlled heat`
- `16:9 landscape, shallow depth of field`

**DON'T (negatives / avoid list):**
- `cool corporate blue, blue circuitry, blue data streams, teal/cyan/purple neon`
- `glowing blue AI brain, neural network brain, holographic UI`
- `robot shaking hands, chrome humanoid robot, android face`
- `hexagon-grid tech wallpaper, matrix digital rain, sci-fi cyberpunk city`
- `light-bulb idea, padlock/shield security cliché, businesspeople with floating charts`
- `hypey, flashy, futuristic sci-fi — no lens flares, no rainbow gradients`
- `cluttered, busy, over-detailed; multiple saturated colors`
- `flat vector cartoon mixed into the photographic/render feed`

**One-line phrasing swaps to keep the tone right:**
- warm ember-on-coal — NOT cool corporate blue
- confident, grounded, operational — NOT hypey sci-fi
- one ember accent on greyscale — NOT multi-color neon
- abstract & conceptual — NOT literal stock cliché
- matte forged texture — NOT glossy chrome

---

## 5. Alt-text convention

> In-repo alt-text implementation (the DE→EN sync pipeline) is a **separate follow-on** on the
> protected `cindr-la-website` repo. Here we only fix the *convention* Soro should generate to.

**Pattern:** one plain sentence, ≤ 125 characters, describing *what the image shows* first, then the
*concept* it represents. Lead with the concrete subject (screen-reader users hear this), weave in ONE
relevant article keyword naturally, and **do not** start with "Image of…" / "Picture of…" or stuff
keywords. Alt-text must **describe the image**, not merely repeat the article title (the current
title-mirroring behavior is exactly what to avoid).

- Descriptive-first · accessible · one natural keyword · no "image of" · no keyword stuffing · ≠ the H1.

**Examples:**
- Article on invoice automation →
  `Abstract ember-lit workflow lines resolving into an ordered invoice pipeline on a dark background.`
- Article on KYC/identity checks →
  `Glowing verification seal emerging from coal-black, evoking layered identity checks.`
- Article on AI failure modes / readiness →
  `A single ember light in a dark control room, suggesting an AI system being run reliably.`

---

## Ready-to-paste image style prompt (global directive)

> Use as Soro's global/style instruction when only a compact directive is accepted:

```
Style: warm ember-on-coal. A dark, abstract, conceptual scene — near-black coal background
(#0e0e10) with a single warm directional ember-orange key light (#ff4d00 into #ff783d) as the
only saturated color; all else greyscale (smoke #9fa3a9) and deep-ember shadow (#431407).
Low-key cinematic lighting, matte tactile materials (warm forged metal, machined geometry),
shallow depth of field, one clear focal point, generous intentional negative space with a
quiet dark lower-left third reserved for a text overlay. 16:9 landscape. Mood: grounded,
operational, confident, sober — a system being run, forge/cinder heat under control. Depict
abstract automation, workflow, and payments/identity/compliance motifs tastefully. STRICTLY
AVOID: cool corporate blue, blue circuitry or data streams, glowing blue AI brains, robot
handshakes, chrome humanoids, hexagon-grid tech wallpaper, cyberpunk neon, teal/purple/cyan,
lens flares, and generic hypey sci-fi. One ember accent on greyscale — never multi-color.
```