danielslater.dev — Brand Strategy

Produced 2026-07-17 by a multi-agent workflow: 5 Sonnet research legs (solo-vs-studio trust dynamics, person-vs-studio naming, brand architecture, trust signals & tone, ocean-identity risk) → 1 Opus synthesis (3 directions) → 3 Opus adversarial critiques (conservative-buyer role-play, operator economics, differentiation/coherence) → reconciliation with Daniel across 5 interview rounds. Companion to BUSINESS-MODEL.md (settled the same day; this doc inherits its Repaint-lead offer, ICP-A/B/C, and channel sequencing). Raw outputs: session scratchpad research-result.json, directions.md, critique-*.md.

THE SETTLED STRATEGY IN ONE PARAGRAPH

One brand — danielslater.dev — a branded house with a benefit-led, matter-of-fact homepage ("Your website should be making you money"), Daniel present as a quiet trust signal but never the headline. Repaint is the one named, fixed-price SKU (promoted toward the hero once arm's-length international references exist). The ocean identity stays bold on the landing as a craft demo, calm everywhere conservative buyers read — with the Berlein clinical register surfaced early as proof of range. White-label runs on a fork: named-partner credit where negotiable (Bree), NDA-first invisibility via a dormant neutral entity where required (cold agencies). Trust is sold with structure, not promises: quantified case studies, milestones/escrow for first-time international clients, an explicitly-stated free-look → paid-audit ladder.

🔒 SETTLED 2026-07-24 — Decision #2 is overturned. The paragraph above is now HISTORY on the naming and domain question; everything else in it still stands.

Daniel: "change danielslater.dev to be my personal website and it's going to be powered by my agency." So:

• leachie.com = the commercial brand. The agency, the Repaint funnel, the therapist campaign, all paid traffic. This is the big-migration answer to the reconsideration's Q1, not the bolt-on one.
• danielslater.dev = Daniel's personal site, with a quiet "powered by Leachie" sign-off, business enquiries handed on to the studio, and the site itself listed as one of Leachie's examples.
• Name: "Leachie" — not "Leachie Dev", not "Leachie Studio".
• Identity: the lychee fruit, not the gecko the name comes from. Mark locked 2026-07-24 (the Cradle) — see leachie-rebrand/brand/LOCKED/. The ocean identity stays with the personal site and is retired from the commercial brand.
• The one brand / don't fragment the visibility budget finding is knowingly overridden: the personal site is not something Daniel needs to market, which is the exact condition the counter-case set for this being acceptable (see line ~255).

Full write-up: leachie-rebrand/LEACHIE-BRAND.md and leachie-rebrand/ALIGN.md (🔒 SETTLED BY DANIEL, at the top). The OPEN RECONSIDERATION section at the end of this doc is kept as the reasoning that led here — read it as resolved, not open.

DANIEL'S DECISIONS (interview rounds, 2026-07-17)

POSITIONING & MESSAGING

Hero (settled copy direction, register locked, wording may polish):

Your website should be making you money. Modern, fast rebuilds and AI assistants for practices and growing stores — sites that convert, assistants that answer around the clock, automation that kills the admin. One fixed price, and you own everything.

[WhatsApp] [See the work] built by Daniel Slater · Cape Town

Messaging hierarchy (what a first-time visitor learns, in order):

1. What this does for your business — revenue, bookings, after-hours coverage, less admin. AI named as the means, never hyped as the category (both markets show AI-fatigue; SA buyers need plain-language education, not AI persuasion).
2. Proof by named local case with numbers — Berlein (health), Aerias (e-comm), quantified. Berlein's calm clinical register shown early with the explicit line: "my site is the showreel; this is the register I ship for a practice."
3. You're not trapped — continuity block: for non-technical buyers this leads with "a person on the other end, month-to-month" (Care Plan); code/account ownership and written handover as the supporting detail (that ordering matters — code-ownership only reassures technical buyers).

Tone: quiet craftsman, matter-of-fact. Short declaratives, outcomes over adjectives, prices stated plainly, zero tech-stack talk (standing rule), zero AI hype. Sample register:

• WhatsApp first reply: "Hi [name] — Daniel here. Send me your site link and I'll tell you straight what's worth keeping — free, two minutes. If you want the full map with your own numbers, that's the Signal Audit (R3,500, credited to any build). No obligation either way." ← note the ladder is stated explicitly; the free look and the paid audit must never ambush each other (critique cross-cutting #2).

BRAND ARCHITECTURE

• Branded house. One identity for all four offers (high-confidence research: solo B2B providers should never fragment the visibility budget). No offer gets its own brand. No studio rename — no evidence a studio name buys a solo higher rates, and switching cost off the settled domain/identity is pure loss.
• "Repaint" is the one named SKU — its own page, fixed scope, fixed price, before/after module. It is a page under the brand, not a second identity. The most memorable asset in the review ("Repaint — fixed price, see the before and after" is what buyers repeat). Other packages (Signal Audit, Chat Agent, Care Plan…) are plain service pages using the BUSINESS-MODEL.md ladder names.
• Sequencing: benefit-led hero now (Q1–Q2, serves the warm SA pipeline); promote Repaint toward the hero when ≥2 arm's-length INTL references exist (~Q3, when the Upwork leg activates). Product-first-now was killed by all three critics: right skin, wrong quarter.
• dingese = dormant legal/invoicing wrapper only. Never on the site. Completed lazily (CIPC/FICA is real admin + possible legal fee — budget it in the week a white-label contract or INTL invoice actually needs it).
• Killed options, for the record: studio-name rebrand; house-of-brands; "The Bench" (agency-engine-as-brand — subordinated both payable Q1 buyers, stripped the uncopyable assets in its own lead channel, fought the named-partner preference); person-led headline (Daniel's steer: customer-first).

TRUST-SIGNAL STACKS (per ICP, order matters)

ICP-A — SA health/wellness practice (ignition):

1. Named local case + quantified outcome (Berlein) 2. Professional touches (daniel@danielslater.dev, written SOW, stated response habit) 3. Continuity: person-on- retainer, month-to-month, then ownership/handover 4. POPIA-aware data handling (cheap SA differentiator — few small competitors mention it). WhatsApp click-to-chat above the form. ZAR, 50% deposit / Net 7–14 stated plainly. Omit: platform badges, certs, INTL logos.

ICP-B — UK/EU/US e-commerce SMB (Q3 ramp):

1. Live inspectable before/after + numbers (Aerias) 2. Fixed transparent price
2. Structure, not promises: milestones or platform escrow as a feature, stated comms cadence in their timezone 4. Direct-maker access/speed 5. Soft risk-reversal. GDPR instead of POPIA. USD/GBP display. Disarm the offshore pattern-match explicitly — a burned UK buyer sees "remote Cape Town solo" as the silhouette that burned him; escrow/milestones + cadence is what converts him, not assurances. Known gap: both anchor cases are friendlies (Berlein via Alexa, Aerias via Bree) — n=1-arm's-length. Use the paid Signal Audit as the trust-bridge and the machine for manufacturing the first arm's-length reference (low-stakes $250 trial where the buyer watches Daniel work before the big cheque).

ICP-C — UK/EU boutique agency (durable engine): Sold off-site entirely: turnaround reliability, comms cadence, NDA-comfort, no-solicit, request-gated private portfolio. Public site carries at most one discreet line ("I also take on white-label overflow for agencies — ask."). The agency one-pager is built just-in-time for a named agency conversation, never on spec. Cape Town framed to agencies as cost + UK-timezone-overlap advantage.

OCEAN-IDENTITY DEPLOYMENT MAP

Identity itself is settled (llandudno, 2026-07-14 rebrand — see site memory). This maps where it carries weight:

Mandatory engineering, not polish: prefers-reduced-motion support; fast/skippable load path; measure hero LCP/TTI on a representative UK connection and SA mobile data (unmeasured as of 2026-07-17 — a mid-range Android on SA data bouncing before the Berlein contrast line is the concrete failure mode for the exact ignition buyer). Optional, zero-cost: one short "why the ocean" founder aside somewhere in the funnel (not the hero) to convert the aesthetic into intentional story for buyers who engage.

FIRST-90-DAYS BRAND TASKS (~12–16h, competes with Q1 substrate hours — not additive)

1. Homepage: benefit-led hero copy + small name line + CTA order (WhatsApp first for SA) — 3–4h
2. Berlein case study with quantified outcome — 3–4h (blocked on Alexa's number — ask early, it gates the anchor asset)
3. Aerias before/after with numbers (feeds Repaint page + later INTL tilt) — 2–3h (blocked on metric)
4. Repaint SKU page: scope, fixed price, what's-not-included, soft risk-reversal block — 2–3h
5. Continuity/ownership policy page + intake form with hospitality-decline line — 2h
6. Domain email live + minimal signature — 1h
7. Bree conversation: co-credit wording + aerias case clearance — ~0h + relationship time

Deferred on triggers: agency one-pager (first named agency conversation); dingese completion (first contract that needs it); Repaint-to-hero promotion (≥2 arm's-length INTL references); voice-offer brand surface (per BUSINESS-MODEL, only if ≥2 paying leads).

FALSIFIABLE ASSUMPTIONS / CHECKPOINTS

1. The warm SA well yields ≥1 qualified quote/month in Q1 (BUSINESS-MODEL M1 KPI). If dry in 4 weeks → the SA-benefit-led surface is pointed at a thin market; pull the Upwork/INTL tilt (Repaint-forward, escrow-first) forward from Q3.
2. A genuinely impressive Berlein metric exists and clears. If the number is thin, the anchor collapses to "we built this" (testimonial tier) — re-lead ICP-A stack with professional-touches + continuity and push harder for an arm's-length case via Signal Audit.
3. The benefit-led hero out-converts a person-led one for warm referrals. Untested — Daniel's taste call against the critics' person-led default. If warm referrals stall at the site step (referred people don't make contact), test re-adding a person-forward block above the fold before touching anything else.
4. Cold agencies actually require invisibility (med-confidence norm, zero cold relationships yet). If the first real agency is happy co-crediting, the fork simplifies to named-everywhere and dingese stays dormant indefinitely.

OPEN RESOLVED RECONSIDERATION (raised 2026-07-20 · settled 2026-07-24) — agency name "Leachie" + danielslater.dev as personal site

🔒 RESOLVED IN FAVOUR OF THIS ALTERNATIVE. Daniel chose it on 2026-07-24 — see the banner at the top of this doc for the settled shape. The four "open questions before this could settle" are answered as: Q1 leachie.com carries the funnel (the big-migration option) · Q2 the name is "Leachie" · Q3 dingese is untouched — Leachie is a brand, not the legal wrapper, and the dormant-neutral-entity fork still stands · Q4 neither gecko nor ocean: the identity is the lychee fruit, and the ocean identity stays with the personal site. Everything below is kept as the reasoning that produced the decision.

Original status when written: thinking out loud, nothing settled. This reopened Decision #2 (branded house on danielslater.dev; a studio rename was a killed option — see BRAND ARCHITECTURE).

The thought (Daniel, 2026-07-20): he owns leachie.com and is considering naming the agency "Leachie Dev" (or similar), keeping danielslater.dev as his personal CV / portfolio site.

What actually changes

• Two surfaces, split jobs: Leachie(.com) = the commercial agency brand (Repaint funnel, client-facing, white-label); danielslater.dev = the person (CV, portfolio, "who's behind it").
• The commercial brand stops being Daniel's own name → it reads more like a studio/team, not a solo freelancer.

Why it might be good

• Kills the "remote solo" pattern-match BUSINESS-MODEL flags for ICP-B/C (the burned-UK- buyer silhouette; agencies preferring a studio). A studio name is a cheap way to read as "a team."
• Clean commercial/personal split — better for white-label, for keeping the Nsuna day job separate, and for eventually selling/handing off a brand that isn't your legal name.
• Could be the "neutral entity" the white-label fork already needs (Decision #14 / dingese): Leachie = the arms-length / cold-agency face, danielslater.dev = the warm/named funnel. That reconciles the idea with the settled fork instead of fighting it.
• danielslater.dev-as-CV has immediate use — it's exactly what you'd point an employer at (see biz/career-opportunities.md: the xneelo/bank leads).
• The name fits Daniel's signature. A leachie is the New Caledonian giant gecko (Rhacodactylus leachianus) — the biggest gecko, nocturnal, an adhesive climber. Ready-made hooks that line up with the existing site: nocturnal "works while you sleep" (ties straight to the night-shift printed-slip hook family + "AI that answers around the clock"), sticks/holds (retention/reliability), punches above its weight (small shop, big delivery). A gecko mascot/animated background is a natural sibling to the surfers/ starlings/runners tiny-agents template. (These hooks are my associations, raw material — not decided.)

Why the settled strategy argued against it (counter-case, from the 2026-07-17 research)

• High-confidence finding that solo B2B providers should not fragment the visibility budget — two brands = two things to build recognition for on a solo's tiny budget.
• No evidence a studio name buys a solo higher rates.
• Switching cost is real — every site/funnel asset built so far lives on danielslater.dev; moving means migrating the Repaint funnel and rebuilding SEO/word-of-mouth equity.
• Current positioning leans on Daniel's name as the quiet trust signal ("built by Daniel Slater, Cape Town"); a studio brand removes the human from the commercial front (recoverable with a visible "by Daniel Slater" line, but no longer the default).
• Nuance: the research killed a studio rename that replaces danielslater.dev. Daniel's version keeps both, split by purpose — which softens the fragmentation objection only if danielslater.dev-as-CV is not something he needs to actively market.

Open questions before this could settle

1. Which domain carries the Repaint funnel / paid traffic — does leachie.com become the primary commercial site (big migration), or does danielslater.dev stay the funnel and Leachie start life as only the white-label/neutral face (small, additive)? This question determines whether this is a rebrand or a bolt-on — decide it first.
2. Exact name — "Leachie Dev" / "Leachie" / "Leachie Studio"? (Dev vs Studio shifts the solo-vs-team read.)
3. Relationship to dingese — does Leachie replace the half-registered "dingese" as the trading/legal wrapper, or is it just a brand over it?
4. Gecko identity vs the llandudno/ocean identity — replace, or coexist? The ocean identity is settled and heavily built; a gecko brand is a second visual system, not a tweak.

Process note (not an outcome): this is Daniel's taste + positioning call. Cheapest first move is to answer Q1 — funnel-moves vs Leachie-as-neutral-face — because everything else (migration effort, visual system, name form) hangs off it.