The 8-Stage Workflow That Runs Our Studio

Every creative studio eventually hits the same wall: work is coming in, projects are moving, but nothing feels tracked. A lead goes cold because nobody followed up. A revision round turns into five because approval was never formally captured. A project "ends" but files are still being requested three weeks later.

The fix isn't more tools. It's a shared definition of where every project actually is at any given moment. At Hyperfantasy, we run everything through eight stages — from the first moment someone hears about us to the day we hand over the final files. Here's how it works, and why each stage earns its place.

Stage 1: Marketing

Everything starts before the client even knows they're a client. Marketing is the stage where awareness is built and relevant leads are attracted — portfolio updates, content, outreach, referrals. The keyword is relevant: the goal isn't reach for its own sake, but attracting the kind of client the studio is actually built to serve.

What we track here is simple: where leads come from. Every channel gets tagged, so over time we know which efforts convert into real work and which are just noise. A studio that doesn't know its lead sources is guessing with its marketing budget — whether that budget is money or hours.

The stage is done when a prospect takes a real action: they reach out, fill a form, or reply to outreach. That moment moves them forward.

Stage 2: Enquiry

An enquiry is a raw signal, not a deal. Someone wants something — but we don't yet know what, how big, or whether it fits. This stage exists to qualify: capture the client's information, understand the need in their own words, and decide whether this is a conversation worth continuing.

Every enquiry gets a status — new, replied, qualified — so nothing silently rots in an inbox. Speed matters here more than polish. A same-day reply with two clarifying questions beats a perfect proposal sent a week late.

The stage is done when the enquiry is either qualified (real need, plausible fit) or respectfully closed.

Stage 3: Deal

This is where a conversation becomes a commitment. Scope gets defined, a proposal goes out, pricing is put on the table, and terms are agreed. It's also where discipline pays off: deal value, expected closing date, and win/lose outcomes are all recorded — including the losses. Lost deals are data. If you keep losing on price, or on timeline, or to the same competitor, you want to see that pattern, not just feel it.

Not every project needs the full ceremony. Small or repeat work can close on an email confirmation; larger projects, anything involving IP transfer, or engagements running longer than a few weeks get a proper agreement. The point is that the decision about which path to take is deliberate, not accidental.

The stage is done when the client says yes in writing and the commercial terms are locked.

Stage 4: Project Management

The deal is signed — now the real work gets structured. This stage is the operational backbone: tasks are broken down, milestones are set, timelines are drawn, and responsibilities are assigned. Discovery and research live here too, as the opening phase of the project rather than a separate stage. In practice, discovery is project work — separating it just adds ceremony without adding clarity.

This is also where expectations get their final calibration. The client learns the rhythm: when they'll see work, how feedback rounds function, and what's expected from their side. Most project pain traces back to this stage being rushed.

The stage is done when there's an agreed plan the client has seen — milestones, timeline, and what happens at each checkpoint.

Stage 5: Approval

Approval is a gate, not a vibe. Deliverables are presented in versions, feedback is consolidated, and sign-off is captured explicitly — a recorded yes, not an assumed one. This is the first of two points in the workflow where the studio principal personally steps in as the final checkpoint, because approvals are where scope either holds or quietly dissolves.

Revision rounds are counted against what was agreed in the deal. That's not bureaucracy; it's what keeps a two-round agreement from becoming a seven-round marathon that nobody remembers agreeing to.

The stage is done when the client has formally signed off on the design direction and deliverables.

Stage 6: Development

Approved designs become working products. Each deliverable gets its own task list, progress is tracked as a percentage rather than a feeling, and every output is linked to its file — no "which version is the latest?" archaeology at the end.

The critical discipline here is fidelity to what was approved. Development is not a second design phase. When implementation reveals a genuine problem with the approved design — it happens — the change goes back through a lightweight approval loop rather than being silently improvised into the build.

The stage is done when the build matches the approved scope and is ready for structured testing.

Stage 7: QC

Quality control gets its own stage because "we'll test as we go" is how bugs reach clients. Work runs through a defined checklist; issues get logged and tracked to resolution; the revision counter keeps everyone honest about how many passes it took.

QC is also the stage most likely to send work backward — a failed check returns the item to Development. That's the system working, not failing. A workflow that only moves forward is a workflow that ships problems.

The stage is done when the checklist passes clean and open issues are resolved or explicitly accepted.

Stage 8: Handover

The finish line — and the stage most studios fumble. Handover is treated as its own deliverable: final files organized and transferred, documentation prepared, credentials passed over, and a handover checklist walked through together with the client. The principal steps in personally here for the second time, because the last interaction is the one clients remember.

A clean handover does two jobs. It protects the studio — a signed acceptance means "done" is a fact, not an opinion. And it sets up the future: warranty terms are stated, and the relationship transitions gracefully instead of just stopping. The best source of the next project is a client whose last project ended well.

The stage is done when acceptance is signed, everything is transferred, and the project record is closed.

Why Eight, and Not Five or Twelve

The number itself isn't sacred — the boundaries are. Each stage ends with something verifiable: a qualified lead, a signed deal, an approved design, a passed checklist, a signed acceptance. If you can't tell whether a stage is finished, it isn't a stage; it's a mood.

Three things make this workflow hold up in practice. It's honest about non-linearity — work moves backward from QC to Development, deals stall and revive, and the system allows it instead of pretending otherwise. It puts human judgment where it matters most — at Approval and Handover — instead of spreading thin attention across everything. And it produces a paper trail as a side effect: by the time a project closes, the proposal, agreement, sign-offs, and acceptance already exist, because they were each the exit ticket of a stage.

A pipeline like this won't make the work itself better. But it makes the work visible — and visible work is work you can actually improve.