Brand & Operations Build

What you walk away with

A working operational environment, in three layers.

At the end of month 3, you own all of it — built, documented, and handed over.

Layer 1

The brand layer
- Voice spec — lexicon, tone register, volume dial per surface.
- Visual identity — palette tokens, type tokens, logo system, photography direction, layout grid.
- Brand book — versioned, audit-tracked, queryable; for your team and for AI agents at once.
- Microcopy stress tests — voice under pressure: crisis comms, escalation, decline letters.
Layer 2

The operations layer
- Content workflow — editorial calendar, production, review, and publish cadence wired into your stack.
- AI agent personas — designed, deployed, integrated into your CMS, design tools, email, and Slack.
- Dashboards — what’s running, what’s flagged, what needs your judgment; visible to founder and team.
- Audit trail — every brand decision documented with rationale; queryable in seconds.
Layer 3

The team layer
- Onboarding plan — your team trained on the voice spec, visual tokens, agent SOPs, and audit workflow.
- Skill-transfer milestones — at months 1, 2, and 3 your team operates progressively more of the system. A deliverable, not a bonus.
- Escalation protocol — when work surfaces to you, to your team, to RTSN; documented and tested.

How the three months run

Sequenced, gated, three months.

Month 1 — Strategy + brand foundation

Kickoff and research deepen the Discovery diagnostic with macro, industry, competitor, and positioning analysis. Then the brand-voice work — lexicon, tone register, volume dial, microcopy stress tests. The month closes at the gate where you sign off the verbal identity.
Month 2 — Visual + content systems

Visual identity — palette, typography, logo system, photography direction — proposed, reviewed, locked. Then the content workflow and editorial cadence, designed with your team, with the first 30 days of content drafted for sign-off.
Month 3 — Operations + agent build + handover

AI agent personas designed, deployed, and integrated into your stack — each with its own SOP, validation criteria, and escalation thresholds. Then handover: your team trained, dashboards live, audit trail running, escalation protocol tested.

Your team’s role

What your team does — and does not — do.

Your team does

Joins kickoff and two to three working sessions per gate.
Reviews and signs off at each gate — sign-off is meaningful, not rubber-stamp.
Provides input on voice, visual, and content drafts — their judgment shapes the work.
Onboards onto the system in month 3 — about 6–10 hours per team member.

Your team does not

Manage RTSN day to day — we run on our cadence and surface decisions when they need you.
Coordinate between disciplines — we handle verbal, visual, and content coordination internally.
Build the operating system themselves — that’s our job; theirs is to be informed and review-capable.

Prerequisites

A diagnostic, ours or an equivalent.

You need a Discovery Workshop diagnostic, or an equivalent diagnostic we can audit at kickoff. “Equivalent” means:

A documented assessment of current brand and operations state.
A sequenced roadmap with milestones and success criteria.
Enough specificity that we can scope a three-month build against it without re-doing the diagnostic.

If you have an equivalent diagnostic, we audit it during the Build proposal phase. If it meets the bar, we proceed. If it doesn’t, we tell you what’s missing and recommend Discovery first. We don’t say no often — but we say no when the input isn’t there.

Fit

Who the Build is for.

This is for

Founder-led businesses — solo founder through about 25 staff, Singapore-anchored.
Brand and operations already diagnosed — by the Discovery Workshop or an equivalent.
A founder and team ready to commit three months of substantive attention.
A founder ready to install operational infrastructure, not just a brand refresh.

This is not for

Brand-refresh-only buyers — we don’t sell brand without the operations layer.
Founders without bandwidth for three months — the work is collaborative.
Companies needing enterprise procurement or regulated-industry certification beyond standard SG SMB compliance.

Frequently asked

Build questions.

Can I do Build without Partnership afterwards?: Yes. Build is a complete engagement on its own — you walk away with a working operational environment your team can run. Many clients take Build and self-operate. Partnership is for clients who want RTSN continuously alongside the team.
What if my scope changes mid-Build?: We have a documented change protocol. Small adjustments are absorbed within scope. Substantive changes trigger a written amendment with adjusted price and timeline — no surprise invoices.
What is the deliverable acceptance gate?: Each gate has a documented acceptance checklist signed at kickoff. You sign off when the checklist passes. We don’t ship without your sign-off; you don’t get billed for the milestone without it.
Do you guarantee the brand work will succeed commercially?: No. We deliver a working brand and operational system. The commercial outcome depends on factors beyond what we control. We don’t promise revenue uplift — we promise a system that won’t drift on you.
Can my existing brand or operations work be incorporated?: Yes. Build doesn’t start from zero — Discovery surfaces what to preserve, what to retire, what to evolve. Your existing good work becomes part of the system; your existing drift gets corrected.

Launch pricing

The SGD 25,000 rate is launch pricing — locked through the end of 2026 in exchange for permission to publish your case study. From January 2027, list pricing applies. More on the founding-customer arrangement

The working system, in three months.

Discovery Workshop first Already have a diagnostic? Email Kenny

Fixed price · four gates · your team in the room. After Build, the Partnership keeps it running — see the Partnership tier