Inkwork · capability folio

Six disciplines, one hanging index

Scene: mid-morning on Kelantan Road, the folio clips are set out beside the long table. Problem: the brief lists six needs but the organisation only has language for two. Method: read each need as a folio entry with its own mark. Deliverable: six written scopes you can approve independently or as a set.

f.01

Brand narrative

The brief says the company helps teams work better together, but the website opens with a feature list and the deck opens with funding history. Narrative work here names the story arc that connects origin, present work and near-term intent — written so a product marketer can reuse paragraphs without rewriting the spine each quarter.

Arrives: A founder's letter, three competitor homepages, an internal strategy memo.

Handed back in writing: Narrative frame document with story arc, scene notes and forbidden constructions.

f.02

Message hierarchy

Every surface argues it is primary. The homepage headline, the app store line and the sales one-pager each claim centre stage. Hierarchy work decides what must be understood first, what supports that understanding, and what belongs only in detailed material.

Arrives: Live site copy, sales deck, onboarding emails, support macros.

Handed back in writing: Hierarchy map with primary, secondary and supporting messages marked for reuse.

f.03

Campaign architecture

Channels multiply faster than messages settle. Architecture work maps what each surface is responsible for — without pretending every post carries the same weight. The output is a plain-language plan others can execute.

Arrives: Channel list from client team, prior campaign retrospectives (qualitative), brand constraints.

Handed back in writing: Architecture document with channel roles, sequencing notes and handover points.

f.04

Art direction

Visual work begins before language settles and photographs drift from the narrative. Art direction here ties scenes to the hierarchy — what should be shown, what should never appear, how crop and light support the sentence order.

Arrives: Existing brand imagery, location constraints, production partner capabilities.

Handed back in writing: Art-direction brief with scene list, crop rules and reference plates.

f.05

Copy craft

Drafts arrive polished on the surface but uneven under reading aloud. Copy craft is line-by-line work against the hierarchy — headlines, subheads, body, calls to action — checked the way a proof reader checks registration.

Arrives: Draft copy from internal teams or partner agencies.

Handed back in writing: Proof pages with marked revisions and reuse guidance.

f.06

Production supervision

Launch week compresses decisions. Supervision work names who signs what, in which order, before anything publishes — a schedule the room can follow when timelines tighten.

Arrives: Launch timeline, stakeholder list, legal or compliance review points.

Handed back in writing: Production supervision schedule with sign-off matrix and daily check notes.

Type

Specimens before sentences run

Type specimens in the room remind us that letterforms carry tone before words arrive. Copy craft and art direction share this wall until hierarchy is agreed.

Close-up of a marked-up page with pencil and margin notes — Marked page · copy craft pass

Each folio entry stands alone; together they form a campaign season.

Working notes on brand narrative

Brand narrative is the discipline clients confuse with rebranding. Rebranding swaps visuals; narrative names the story your organisation tells about itself across every surface. On Kelantan Road, narrative work begins by laying origin story, present capability, and near-term intent side by side — then marking where they contradict.

The f.01 folio usually needs a founder or CEO in the first session, not because they must approve tone, but because origin language often lives only in their head. We write the arc as three acts with scene notes: what the reader should understand at each act, and which sentences currently violate that understanding.

When narrative dries, the forbidden-constructions margin is as important as the spine itself. Teams reference it when agencies propose taglines that sound fresh but undo months of hierarchy work.

Working notes on message hierarchy

Hierarchy work answers a single question: if someone reads only one line on each surface, what must they carry away? Most organisations fail here because every channel owner treats their headline as primary. The f.02 folio maps primary, secondary, and supporting messages with reuse rules — which lines may appear on product pages, which belong only in sales decks, which must never appear in social posts.

We test hierarchy by reading surfaces aloud in order of customer journey, not org chart. A homepage line that works in isolation but collapses when followed by onboarding email copy has failed the test — and the failure is marked, not debated.

Hierarchy maps stay pinned beside the long table until art direction begins. Visual teams receive them before mood boards, not after.

Working notes on campaign architecture

Architecture work begins when channels multiply faster than messages settle. The f.03 folio assigns each surface a plain-language role: what it teaches, what it reminds, what it asks. Media partners receive this as instructions, not interpretive briefs — reducing the gap between strategy slides and channel execution.

Sequencing matters as much as roles. Some surfaces must lead; others follow once understanding exists. We map handover points — where one channel passes the reader to the next — so launch weeks do not compress decisions that needed separate drying time.

Architecture maps are revised only through folio addenda. Verbal channel pivots during stand-ups are noted as conversation, not consent.

Working notes on art direction

Art direction here is not a mood film. The f.04 brief lists photographable scenes tied to hierarchy — what should appear in frame, what must never appear, how crop and light support sentence order. Abstract mood references are allowed only after scenes are named.

We work from location constraints and production partner capabilities, not from stock libraries alone. A scene list that cannot be photographed in Singapore within budget is rewritten before copy craft begins — not after launch assets are due.

Reference plates hang beside type specimens until hierarchy dries. Direction that arrives before language settles is marked wet and returned to the rack.

Working notes on copy craft

Copy craft is line-by-line work against the hierarchy — headlines, subheads, body, calls to action — checked the way a proof reader checks registration. The f.05 folio produces proof pages with marked revisions, not polished final ads pretending to be drafts.

We read copy aloud in the room. Sentences that look balanced on screen often fail when spoken — rhythm reveals where hierarchy wobbles. Stakeholders listen without editing for the first pass; marks come on the second.

Reuse guidance accompanies every proof page: which sentences belong on which surfaces, which must stay unique, which are forbidden even as variants.

Working notes on production supervision

Supervision is the discipline most teams underestimate. The f.06 schedule names who signs what, in which order, before anything publishes — a matrix the room follows when timelines tighten. Verbal approval is noted as conversation, not consent.

Daily check sheets during launch run list surfaces due, surfaces signed, surfaces blocked — with reasons written in plain language. Post-launch readouts capture what held against hierarchy and what drifted, so the next season begins with documented debt rather than anecdote.

Production partners receive the sign-off matrix at kickoff. Surprises in launch week usually mean supervision was skipped, not that the creative was wrong.

Find us

AdBloom Haven Pte. Ltd.
31 Kelantan Road, #03-01
Singapore 208706

+65 6208 5714

Maps load when you accept Maps cookies or choose Accept all. You can change this anytime from Manage cookies.