Models · engagement
Six models we work in
Engagement shape is chosen after the brief read — not before. Each model below names duration, studio presence and what you receive in the vault bundle. Amounts and retainers are agreed in a written proposal; nothing on this site states fees.
Advisory day
A single structured day on Ann Siang or your floor: brief read, spine sketch, channel questions captured in writing. You leave with a one-page summary and a list of open items — suited to leadership teams testing fit before a longer engagement.
Planning sprint
Two concentrated weeks: stakeholder interviews, market read, campaign spine draft and channel map circulated for comment. Scope, deliverables and studio contact are agreed in writing before day one.
Campaign build
Six to ten weeks from approved spine through proof production: creative direction, channel briefs, content system draft and launch calendar. Weekly proof sessions on the long desk; approvals logged in the ledger.
Embedded retainer
A strategist and art director pair hold a studio seat with your marketing team for a quarter or longer. They attend your stand-ups, maintain the spine, route proofs and keep comms cadence visible — without replacing your in-house lead.
Launch period
Focused support from pre-launch through go-live and two weeks after: daily check-ins, asset routing, stakeholder memos and a post-launch review document. Built for product launches and major programme roll-outs.
Documentation handover
Final two weeks of an engagement dedicated to vault bundle assembly: indexed spine, creative standards, channel map, content system and launch archive formatted for your wiki and agency partners.
Choosing a model
Advisory day suits leadership teams testing fit. Planning sprint and campaign build cover most new programmes. Embedded retainer fits marketing teams who need ongoing spine maintenance. Launch period is booked against a fixed go-live date. Documentation handover closes engagements where your team will operate the system independently.
Models can sequence: advisory day, then planning sprint, then campaign build, then handover. We document the path in the first written scope so procurement and finance see the full arc.
Model codes M-01 through M-06 appear on written scopes only — not as SKUs. Duration, studio presence and vault bundle contents are listed in the proposal you receive after a brief read.
Sequencing is common: advisory day, planning sprint, campaign build, documentation handover. Procurement teams see the full arc in the first scope document so finance is not surprised by a second proposal mid-quarter.
M-06 documentation handover is often underestimated. Two dedicated weeks produce indexed vault bundles: spine PDF, creative standards, channel map, content system, launch archive formatted for wiki import.
M-05 launch period includes post-launch review prompts scheduled before go-live. Your team receives questions to ask sales and support, not a celebration deck.
M-04 embedded retainer assigns named strategist and art director seats. They attend your stand-ups during critical weeks; they do not replace your marketing lead or buy media.
M-03 campaign build assumes spine approval before proof production. Week three is not for rewriting strategy — it is for making work that matches the signed hierarchy.
M-02 planning sprint ends with circulated channel map and creative direction notes. Comment period is dated; silence after the date is treated as approval to proceed to build.
M-01 advisory day compresses intake into one structured session on Ann Siang or your floor. Summary arrives within forty-eight hours with open items listed for your owners.
Written scopes name the model code, duration, participants, deliverables and confidentiality clause. Amounts appear only in private proposals, never on this site.
Transition from M-03 to M-06 is common when your team will operate the system alone after launch. We schedule handover weeks before go-live, not after fatigue sets in.
Embedded retainer M-04 includes quarterly vault audit: spine still accurate, channel map still matches product, creative standards still followed by partners.
Planning sprint outputs are versioned v0.1, v0.2 — not mystery Google Docs with anonymous edits overnight.
Chinatown district