Know where the project stands and what happens next.

Project map

One path. Six approval points.

1. 01

   Before quoting

   Intake and current-state review

   We review existing assets and channels to identify the constraint that deserves attention first.

   OUTPUTCurrent-state summary and three priorities

   Terra11

   • Review the current website, social page or sales channel.
   • Audit representative content and visual assets.
   • Identify three priorities using practical criteria.

   Client

   • Share current links and 3–5 representative files.
   • Explain the goal, deadline and expected budget.
   ✓ Approval pointBoth sides agree on the problem to solve before choosing a visual direction.
2. 02

   About 30 minutes

   Consultation and scope

   A general request becomes countable deliverables, a schedule and clear responsibilities.

   OUTPUTQuote, scope, timeline and approval points

   Terra11

   • Explain the review in plain language.
   • Offer no more than two suitable options.
   • Write deliverables, timing and two revision rounds.

   Client

   • Confirm the priority and decision maker.
   • Choose a realistic option and review exclusions.
   ✓ Approval pointScope, schedule and terms are confirmed in writing.
3. 03

   After 50% deposit

   Onboarding and approved brief

   Source content, access and approval criteria are organised before production begins.

   OUTPUTApproved brief and input checklist

   Terra11

   • Provide a focused briefing form.
   • Create a shared folder and file structure.
   • Confirm the brief as the single source of truth.

   Client

   • Supply source assets on time.
   • Verify product facts, pricing and rights.
   • Assign one person to consolidate feedback.
   ✓ Approval pointThe approved brief defines the problem; new requests are rescoping items.
4. 04

   Before scaling

   Creative direction and key sample

   A representative design is produced first so the solution can be evaluated in context.

   OUTPUTApproved direction and key sample

   Terra11

   • Build the visual language and hierarchy.
   • Create one to three representative samples.
   • Explain design decisions against the brief.

   Client

   • Review content, direction and usability.
   • Return one consolidated set of comments.
   ✓ Approval pointThe key sample is approved before the full system is produced.
5. 05

   As quoted

   Production, revision and QC

   The approved direction is expanded, reviewed and checked before handoff.

   OUTPUTComplete and quality-checked design set

   Terra11

   • Produce all scoped items.
   • Manage up to two revision rounds.
   • Check copy, colour, dimensions, CTA and file naming.

   Client

   • Reply on schedule with consolidated notes.
   • Approve the final preview before export.
   ✓ Approval pointRevisions improve the approved solution; changing the goal changes the scope.
6. 06

   Post-delivery support

   Handoff, guidance and follow-up

   Files arrive organised, with guidance on where and how to use them.

   OUTPUTOrganised files, guide and follow-up plan

   Terra11

   • Organise folders by channel and purpose.
   • Deliver source files when scoped.
   • Provide a short guide and follow-up where relevant.

   Client

   • Confirm file access and completeness.
   • Store a backup and share real usage feedback.
   ✓ Approval pointHandoff confirmation records delivered files and the support period.