Questions

A work track begins with brief intake: your team sends context on the company, audience and existing material. The assigned lead maps that input against the track you selected — T-01 through T-06 — and schedules a working session within the declared cadence. At the positioning stage, we draft a positioning framework and audience map for cross-check before release. The narrative stage produces a message hierarchy and narrative arc your in-house team can carry. Channel architecture follows: roles per channel, sequencing and a production schedule tied to review cadence. Each stage ends with a deliverable per stage — documents, not decks — and a review loop before the next gate opens. The brief runs the work; the bench does not rely on memory. Standing advisory on T-06 keeps the system wired to its track after handover.

Send whatever exists: brand guidelines, prior campaigns, site copy, research summaries and stakeholder notes. We work from material on the bench rather than blank screens. Name the audience, the market and which track the brief most resembles. The assigned lead replies with a proposed cadence and first working session date.

Brief intake is an email thread or call — never a form on this site. You write to [email protected] with context. We read, assign a lead and return a short note on scope shape and cadence. No figures are requested at intake. Scope is agreed in writing before production begins.

A working session is structured time on the bench: stakeholders present, the assigned lead facilitates, outputs are captured in shared documents. Sessions run to a declared cadence — weekly, monthly or per campaign gate. Notes are issued within one business day.

We read copy aloud, map proof points against the message hierarchy and cross-check before release with the core team. Channel-specific variants are drafted only after the master narrative is stable. The goal is a system that does not rely on memory.

Channel architecture assigns roles: which channel carries which message, in what order, at what frequency. We document sequencing in the spec sheet format — track, cadence, deliverables, lead — so your team can run rollout across the region without renegotiating basics each week.

Each track has an assigned lead named at intake. That lead owns the production schedule, review cadence and handover. Escalation routes through the same person unless you request a change in writing.

Material moves through agreed folders and email threads. We do not operate a client portal on this site. Files are versioned with mono date stamps in filenames. Final packages are delivered in formats your team can edit.

We build asset libraries, guidelines and editorial calendars your team maintains. Advisory on T-06 covers standing review cadence after major tracks close. The workshop supplements — it does not replace — your internal marketing function.

Mon–Fri 09:30–18:30 SGT at 12 Gopeng Street, Icon @ Tanjong Pagar. Email received outside hours is queued for the next working day. Regional teams may request sessions aligned to their timezone where feasible.

Email you send is processed under our privacy notice. We keep correspondence only as long as needed for the track and statutory requirements. See privacy.php for PDPA rights and contact details.

After intake, the assigned lead issues a scope note listing track, cadence, deliverables per stage and review gates. Changes require a written addendum. Commercial terms are discussed separately — never on this website.