Case Study

Case Study: Interior Design Studio CRM & Workflow

We built a connected set of automations for a residential architecture and interior design studio: a CRM pipeline, client intake with discovery booking, fee proposals and terms with e-signature, stage approvals and change orders, and FF&E procurement tracking. The principal now spends discovery calls on projects that fit, every decision has a written record and clients get a weekly view of their orders.

Practice type
Residential architecture and full-service interior design
Team involved
Principal, lead designers, studio manager, procurement coordinator
Systems connected
Studio platform, CRM, e-signature, accounting, email, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Enquiries came from the website, Houzz, Instagram and builders, and lived in three inboxes. The principal took discovery calls for projects far outside the studio's area and budget.

Fee proposals took an evening each and follow-up was irregular. Some projects started before terms were signed.

Client approvals sat in email threads, and small extra requests were rarely priced or signed.

Procurement ran on a spreadsheet beside the studio platform, and clients emailed weekly to ask where their furniture was.

Goals

What the project had to change

  • One pipeline with every enquiry and its source.
  • Discovery calls only for projects that fit the brief.
  • Every project started on signed terms, with a retainer paid.
  • Every stage approval and change order recorded in writing.
  • Every FF&E item tracked from approval to delivery, with clients updated weekly.

What we built

What we built, as one connected system.

01

Studio CRM pipeline

We connected the website, Houzz and social messages and referral emails to one pipeline with stages from enquiry to active project, follow-up tasks and a monthly source report.

Service details
02

Client intake and discovery booking

A short questionnaire scores each enquiry against the studio brief, sends courteous declines the principal approved and lets good fits book a discovery call.

Service details
03

Fee proposals and terms

Drafts assembled from the studio's own templates after each call, edited by the principal, sent for e-signature, followed up and converted to a retainer invoice and project on signature.

Service details
04

Approvals and change orders

Stage packages and selections go out with clear approval requests and chasers; change requests are priced by the designer and signed before work starts.

Service details
05

FF&E procurement tracking

Approved selections become purchase orders and deposit requests; vendor acknowledgements and ship dates are chased and logged, delays alert the designer and clients get a weekly update.

Service details

Architecture

How the studio's workflows connect

Enquiries Web, Houzz, social Studio platform Projects, items Vendor emails Acks, shipping n8n Five workflows AI steps Drafts, parsing CRM and records Deals, approvals Sign and invoice DocuSign, Xero Studio manager Lists, chasers Principal Fees, design Log and reports Monthly summary
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 Enquiries, the studio platform and vendor emails feed one n8n instance.
  2. 2 Five workflows update the CRM and records, send documents for signature and invoices, and use AI to draft and parse.
  3. 3 The studio manager works one set of lists; the principal edits proposals and prices changes.
  4. 4 Every step is logged, with a monthly summary of the agreed measures.

How it behaves

How the system behaves day to day

What each person sees and what runs in the background, including what happens when something goes wrong.

What clients see

  • A prompt reply and a short questionnaire after enquiring
  • A clear proposal soon after the discovery call
  • Simple approval requests and change orders
  • A weekly update on their orders

What the studio sees

  • One pipeline, one approvals list and one procurement view
  • Drafts to edit instead of blank pages
  • Delay alerts before they hit install dates

What the automation does

  • Captures, scores, drafts, sends and chases on schedule
  • Files every approval and change order
  • Logs every step and alerts the studio manager on failures

Edge cases and fallbacks

A valued referral partner sends a project
Routed to the principal whatever the score.
A client approves by email reply
Captured into the approval record with the email attached.
A vendor acknowledgement shows a new price
Flagged to the coordinator before payment.
Terms signed but retainer unpaid
Reminder sent; the project waits for the principal's decision.
n8n or the studio platform is unavailable
Actions queue and retry, and the studio manager gets an alert.

Integrations

What we connected

All integrations

Programa

Interior design project management

Schedules, selections and invoices.

Through Programa's Xero integration; any direct API access confirmed per project.

HubSpot

CRM

Contacts, deals, pipeline stages and tasks.

HubSpot CRM REST API.

Xero

Accounting

Invoices, contacts and payments.

Xero Accounting API.

DocuSign

E-signature

Proposals, terms and change orders sent and tracked.

DocuSign eSignature REST API and Connect webhooks.

Calendly

Scheduling

Discovery calls and site visits booked from real availability.

Calendly API and webhooks.

Gmail and Microsoft 365

Email and calendars

Enquiries, vendor acknowledgements and client updates.

Google and Microsoft APIs.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We sat with the principal, studio manager and coordinator, mapped enquiry to install and agreed the studio brief and data flows.

  2. 02

    Design and access

    Week 2

    Pipeline stages, questionnaire, proposal templates from the studio's own clauses, approval and change order formats, and access to every tool.

  3. 03

    Sprint 1: CRM pipeline

    Week 3

    Built capture and stages and shadow-ran against the inboxes; demo and sign-off.

  4. 04

    Sprint 2: intake

    Week 4

    The pipeline went live. Built the questionnaire, scoring, declines and booking.

  5. 05

    Sprint 3: proposals

    Week 5

    Intake went live. Built draft assembly, e-signature, follow-ups and retainer invoices.

  6. 06

    Sprint 4: approvals

    Week 6

    Proposals went live. Built approval requests, chasers and change orders.

  7. 07

    Sprint 5: procurement

    Week 7

    Approvals went live on active projects. Built POs, deposits, vendor chasers and client updates.

  8. 08

    UAT and handover

    Week 8

    The studio ran acceptance tests on every workflow; we switched everything on, handed over the run book and trained the team.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Captures enquiries and keeps the pipeline current
  • Sends the questionnaire, scores fit and books calls
  • Assembles proposal drafts and chases signatures
  • Sends approval requests and change orders
  • Drafts POs and chases vendors for dates

The team does

  • Review borderline enquiries
  • Check and place purchase orders
  • Follow up on stalled approvals personally
  • Confirm vendor prices and dates

Principal or lead designer decides

  • Decides which projects to take
  • Sets fees, scope and terms
  • Prices change orders and makes design decisions
  • Chooses substitutes for discontinued items

Compliance handled

Privacy, consent and safety, built in.

Written terms before work

Projects only open on signed terms, matching ARB guidance in the UK.

Source: arb.org.uk

Changes recorded in writing

Every change order is signed and filed before extra work.

Source: arb.org.uk

Consumer cancellation rights

For UK consumer clients, the workflow records any express request to start work in the cancellation period.

Source: www.legislation.gov.uk

Processors under contract

Every tool holding client data is covered by a processor agreement.

Source: gdpr-info.eu

No automated project decisions

Scores only sort; the principal decides which projects to take.

Source: gdpr-info.eu

Outcomes

What changed for the practice

  • Every enquiry lands in one pipeline with its source and a next step.
  • The principal spends discovery calls on projects that fit the brief.
  • Proposals go out soon after each call, and projects start on signed terms.
  • Every approval and change order has a written record.
  • Clients get a weekly order update, and delays reach the designer before install day.

What we track

The measures the practice watches.

Enquiry response

Time to first reply and share of enquiries qualified.

Proposal velocity

Days from discovery call to proposal and to signature.

Approval speed

Average days to client approval per stage.

Change control

Share of changes signed before work and additional fees recovered.

Procurement health

Items without acknowledgement, delayed items and install dates moved.

Cost estimate

What a project like this costs

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Process mapping, data flows, templates and the backlog for all five workflows.

    $1,000 – $2,000

  • CRM pipeline module

    Capture, stages, tasks and source report.

    $700 – $1,600

  • Intake module

    Questionnaire, scoring, declines and booking.

    $500 – $1,300

  • Proposal module

    Draft assembly, e-signature, follow-ups and retainer.

    $700 – $1,700

  • Approvals module

    Approval requests, chasers and change orders.

    $800 – $2,000

  • Procurement module

    POs, deposits, vendor chasers and client updates.

    $800 – $2,000

  • Integrations

    Studio platform, CRM, e-signature and accounting.

    $200 – $400

  • Testing, UAT and launch

    QA, user acceptance testing, launch and training.

    $300 – $1,500

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every studio gets its own fixed quote after a free call.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • Studio software: Studio platform, CRM, e-signature and accounting at each vendor's plan.
  • AI usage: Pay-per-use model fees, usually small at studio volumes.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Free 20-minute call

Want this built for your architects & interior designer?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call