03 / SECTION
PROJECTS
&DELIVERABLES
41
articles
Briefs, timelines, revisions, file delivery, hand-off, scope changes, and project lifecycle.
41 articles
How many revisions are included?
Two consolidated rounds per deliverable. A round is one written feedback document returned within five business days.
Who owns the final work and intellectual property?
Full IP transfers to you on final payment. No license-back, no studio-rights-to-display without explicit permission.
Do I get source files? What about working files?
Yes, on final payment. Includes editable design files, project files, source code, and stems. Stored in a single archive.
How archived projects can be reopened
How old work is retrieved, reviewed, and quoted when a client returns months later.
What is included in post-launch support
The difference between bug fixes, launch support, content updates, and new feature requests.
How project boards are organised
How tasks, files, decisions, approvals, and questions are separated so nothing disappears.
What happens if we miss a feedback deadline
How missed client feedback windows affect the schedule and how to restart cleanly.
Can you add deliverables mid-project
How additional pages, scenes, cuts, screens, or tracks are handled without derailing the original work.
How game concept deliverables are structured
What a pitch deck, mechanics sheet, art direction board, and prototype note usually include.
How music production reviews work
How demos, arrangement notes, mix checks, and stems are handled.
How video edit reviews work
How selects, rough cuts, fine cuts, colour, sound, and export approvals are sequenced.
How animation reviews work
How motion drafts, timing notes, frame comments, and final renders are reviewed.
How version control works for websites and apps
How commits, review deployments, branches, and release notes are used on technical projects.
How file naming works
The naming system used for drafts, exports, source files, and final handover archives.
How content delays affect timelines
Why missing copy, footage, product data, or references can pause a project even when production is ready.
How copywriting fits into a project
When copy is edited, rewritten, structured, or left to the client.
What if I do not have brand assets yet
How projects proceed when logo, copy, photos, and brand rules are incomplete or absent.
Can you work from an existing brand guide
How existing brand rules are absorbed into web, motion, video, app, and illustration work.
How client approvals are recorded
Why approvals need to be written and how they protect both sides from memory drift.
What happens during a launch window
How launch windows are planned for sites, apps, campaigns, video premieres, and public announcements.
How handover is checked
The final checklist used before files, credentials, exports, and deployment notes leave the studio.
How source files are delivered
What source means for websites, apps, artwork, video, audio, and motion work.
What happens if stakeholders disagree
How conflicting feedback is resolved through a single decision owner and written trade-offs.
How revisions are counted
What counts as one consolidated round and how scattered comments are grouped.
How to give useful technical feedback
How to report app, website, dashboard, or integration issues in a way that can be reproduced.
How to give useful design feedback
How to write feedback that moves the work forward without becoming contradictory or vague.
How do I give feedback that actually moves the work forward?
Consolidated, written, specific. One document per round. Reference frame numbers, page sections, or timestamps.
How milestone reviews work
What a milestone review includes, how feedback is collected, and when the next phase starts.
What belongs in the first kickoff call
A checklist for turning a signed scope into a moving project without wasting the first week.
What if I am not happy with the work?
Two paths: fix it under the revisions clause, or escalate to a written quality review. Refunds are not offered in place of corrections.
Can I edit the work myself after delivery?
Yes — that is the point of source files. Hand-off includes a written guide for the most common edits in your stack.
Do you handle emergencies and production-critical issues?
For active and recently-shipped projects, yes — within defined limits. For unrelated emergencies on third-party work, no.
How are scope changes handled mid-project?
Through a written change order. The original quote does not move silently. Small adjustments are absorbed; substantive changes are quoted.
What support do I get after the project ships?
14 days of included bug-fix and question support. After that, continuity blocks or a fresh project.
What does project hand-off look like?
A 30-minute hand-off call, a written hand-off document, all source files, and a 14-day post-launch support window.
Who is my point of contact during the project?
A single project lead from kick-off to hand-off. The studio principal is available for escalation.
What happens if my project goes on hold?
Holds are agreed in writing. Up to 14 days is free. Beyond that, a hold fee preserves your slot and team.
How do you handle projects with multiple stakeholders?
One decision-maker per project, named on the proposal. Internal politics do not become our process.
Do you handle multi-language or localised projects?
Yes for web and app. Translations supplied by you or your translator; we handle layout, typography, RTL, and locale variants.
Do you run a project post-mortem after launch?
Yes, for any project over six weeks. 45-minute call, shared document of what went well, what did not, and what we would change.
How long do you archive past projects?
Final deliverables archived 7 years. Working files purged after 12 months unless you contract retention. Retrieval is free in the first year, billed after.