The studio framework
Turn your way of working into a system other people can follow.
The strongest transition happens when four things evolve together: your commercial model, your project workflow, your operating systems and your team structure. Hiring before those are clear usually creates more questions instead of more capacity.
01ModelKnow what kind of studio you are building.
02SystemsMake delivery repeatable.
03PeopleGive work clear ownership.
04LeadershipMove founder time to higher-value decisions.
Chapter 01
01 · Decide what kind of studio you want to build
01Define whether you want a solo-led boutique studio, a small team or a larger practice.
02Choose the project types you want the studio to become known for.
03Set a realistic target for annual revenue and owner income.
04Decide how much of your own time you still want to spend designing.
05Define the level of service the studio should be able to deliver consistently.
06Use this vision to guide pricing, hiring and systems instead of growing randomly.
Chapter 02
02 · Separate yourself from the business
01List everything you currently do as the founder.
02Identify which tasks require your creative direction.
03Identify which tasks only require a documented process.
04Create a distinction between founder work, delivery work and admin work.
05Move information out of your memory and into shared systems.
06Build the business so clients are hiring the studio, not only your personal availability.
Chapter 03
03 · Standardise your services
01Define your core service packages.
02Write clear inclusions and exclusions.
03Set standard project phases.
04Create a consistent revision policy.
05Define payment milestones.
06Create add-on services for work that regularly sits outside scope.
07Review which services are commercially strong enough to keep.
Chapter 04
04 · Build a repeatable project workflow
01Create one standard sequence from enquiry to handover.
02Use the same project setup for similar jobs.
03Create templates for briefs, schedules, presentations and handovers.
04Define where files, notes, decisions and approvals live.
05Create a consistent naming system.
06Build stage-gates before work moves to the next phase.
Chapter 05
05 · Create studio SOPs
01Document onboarding.
02Document site survey and project setup.
03Document concept-development preparation.
04Document presentation creation.
05Document drawing QA.
06Document FF&E and specifications.
07Document procurement.
08Document invoicing and handover.
Chapter 06
06 · Build a studio operating system
01Choose one place for project management.
02Choose one place for financial visibility.
03Choose one place for client communication and approvals.
04Centralise calendars and deadlines.
05Keep contacts and suppliers accessible to the team.
06Reduce duplicate entry between tools.
07Create a weekly operating rhythm for project and studio reviews.
Chapter 07
07 · Know your numbers before you grow
01Track monthly revenue.
02Track direct project costs.
03Track overhead.
04Track owner compensation.
05Track gross and net profit.
06Track outstanding invoices.
07Track pipeline value.
08Know how much cash the studio needs to safely hire.
Chapter 08
08 · Build pricing that supports a team
01Price for the real cost of delivery.
02Include admin and management time.
03Include software, overhead and project risk.
04Protect a target margin.
05Create minimum project fees.
06Increase fees when the business model cannot support help.
07Separate procurement / markup revenue from design fees.
Chapter 09
09 · Create a capacity model
01Estimate available delivery hours per person.
02Separate delivery capacity from admin and management time.
03Estimate hours required by project type.
04Limit overlapping projects intentionally.
05Forecast upcoming project starts.
06Leave contingency for revisions and site issues.
07Use capacity to decide when to say no or hire.
Chapter 10
10 · Start delegating before hiring full-time
01Delegate repetitive admin.
02Delegate production tasks with clear briefs.
03Use specialist freelancers where the workload is irregular.
04Create feedback loops around deliverables.
05Keep ownership clear.
06Document recurring instructions so you stop re-explaining them.
07Measure whether delegation is actually creating founder capacity.
Chapter 11
11 · Make your first hire deliberate
01Hire to solve a specific bottleneck.
02Write the role around outcomes, not vague support.
03Define what the person owns.
04Define what still requires founder approval.
05Set a 30 / 60 / 90-day onboarding plan.
06Make sure you can afford the role through a slower period.
07Do not hire simply because you are temporarily busy.
Chapter 12
12 · Build a team structure
01Clarify who owns creative direction.
02Clarify who owns project coordination.
03Clarify who owns technical production.
04Clarify who owns procurement and supplier follow-up.
05Clarify who owns finance / invoicing admin.
06Create escalation paths for decisions.
07Keep role boundaries simple enough for a small team to follow.
Chapter 13
13 · Build a stronger client experience
01Create a clear onboarding sequence.
02Set expectations around communication.
03Use standard meeting rhythms.
04Keep approvals recorded.
05Send proactive updates.
06Make decisions easy for the client.
07Create a polished handover experience.
Chapter 14
14 · Create a predictable sales pipeline
01Track every qualified enquiry.
02Record lead source.
03Record expected project value.
04Track proposal status.
05Follow up consistently.
06Measure conversion rates.
07Keep marketing active even when projects are busy.
08Forecast future workload from the pipeline.
Chapter 15
15 · Build a studio brand, not just a personal brand
01Create a clear studio positioning.
02Build a portfolio around the work you want next.
03Keep messaging consistent across website, proposals and social media.
04Show the process and capability of the studio, not only the founder.
05Introduce team members visibly when appropriate.
06Create case studies that explain the studio's thinking.
07Make the brand feel bigger than one person's inbox.
Chapter 16
16 · Protect scope and quality as the team grows
01Use documented scopes.
02Record client approvals.
03Track revisions.
04Use QA checklists.
05Assign final review responsibility.
06Train the team on what counts as extra work.
07Price expanded scope before delivering it.
08Do not let growth reduce design quality.
Chapter 17
17 · Build management habits
01Review project status weekly.
02Review cash and invoices weekly.
03Review pipeline weekly.
04Review team workload weekly.
05Hold short, focused internal meetings.
06Resolve blockers quickly.
07Track recurring problems that should become new SOPs.
Chapter 18
18 · Reduce founder dependency
01Move project status out of private messages.
02Create shared access to supplier and contractor information.
03Document recurring decisions.
04Create standard approval rules.
05Train someone else to understand critical workflows.
06Let team members make decisions inside defined boundaries.
07Protect founder time for high-value work.
Chapter 19
19 · Know when the studio is actually working
01Projects are profitable after team costs.
02Deadlines are visible and mostly predictable.
03Clients know where to find information.
04Team members understand ownership.
05Founder time is no longer consumed by every task.
06Lead flow continues while the studio is busy.
07The studio can take on more work without immediately becoming chaotic.
Chapter 20
20 · Build your 90-day transition plan
01Days 1–30: define the studio model, services and bottlenecks.
02Days 1–30: centralise project and business information.
03Days 31–60: document workflows and standardise templates.
04Days 31–60: review pricing and profitability.
05Days 61–90: delegate one repeatable area of work.
06Days 61–90: define the first hiring trigger or next team role.
07Days 61–90: review what still depends too heavily on the founder.
Signs the transition is working
Your studio health check.
ProfitProject marginWork stays profitable after team cost.
CapacityFounder hoursLess delivery depends on you personally.
SystemsRepeatabilityProjects follow a known workflow.
TeamOwnershipPeople know what they own next.
Put it into action
Your first 90 days.
Days 1–30
Define.
Choose the studio model, tighten services, centralise information and identify the biggest areas still depending entirely on you.
Days 31–60
Systemise.
Document workflows, build templates, review pricing and move repeatable project information into one operating system.
Days 61–90
Delegate.
Hand off one clearly documented area of work, define the next team role and start managing the studio through visibility instead of memory.