Fixed quote after a free call

CRM for architects and interior designers, set up around how studios win work

Design studios win work through referrals, contractors, Houzz and Instagram enquiries, website forms and repeat clients, and most track it in an inbox. We set up one pipeline in the CRM you have, whether that is HoneyBook, Dubsado, Monograph, BQE CORE, Programa or HubSpot, feed every source into it, automate follow-up tasks, hand signed projects to your project tool without retyping and send a monthly report on where good projects come from. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why design studios lose track of good enquiries

Architecture and interior design leads are few and valuable, and they arrive slowly: a referral from a builder, a message on Instagram, an enquiry through Houzz, a past client starting a second home. Each lands in a different inbox and is easy to forget during a busy design week.

Principals rarely know how many enquiries came in, how many became discovery calls, how many proposals were sent and which sources produce the projects worth having. Without that, marketing spend and referral relationships are run on gut feel.

What we build

What our CRM for architects and interior designers includes

Every source in one pipeline

Website forms, Houzz and social messages, referral partner emails and calls feed one pipeline with the source recorded.

Studio-specific stages

Enquiry, qualified, discovery call, site visit, fee proposal sent, terms signed, active project and completed, matched to your process.

Follow-up tasks

Tasks and due dates for the principal or studio manager so no enquiry or proposal sits untouched.

Project hand-off

When terms are signed, the client, fee and scope move into Monograph, BQE CORE, Programa or your project tool through its API or connector.

Referral partner tracking

Contractors, builders and past clients who refer work are tagged, so you can thank them and see who sends the right projects.

Monthly pipeline report

Enquiries, calls, proposals, signed projects and fee value by source and project type.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Enquiry arrives

    A form, message, referral or call creates or updates a contact in the CRM.

  2. 02 Automated

    Acknowledged

    The prospective client gets an approved reply and next step.

  3. 03 Automated

    Stages move

    Bookings, proposals and signatures move the deal automatically.

  4. 04 Studio manager review

    Studio manager follows up

    The studio manager works tasks and keeps notes current.

  5. 05 Principal or lead designer decides

    Project accepted

    Whether to take on a project, and on what fee and scope, is decided by the principal.

How it behaves

How the studio CRM pipeline behaves

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

What the client sees

  • A prompt, personal acknowledgement after they enquire
  • A clear next step: a short questionnaire or a call
  • No repeated questions once the project starts

What the studio sees

  • One pipeline with every enquiry and its stage
  • Follow-up tasks with due dates
  • Signed projects appearing in the project tool

What the automation does

  • Captures and merges enquiries from every source
  • Moves stages from bookings, proposals and signatures
  • Builds the monthly source report

Edge cases and fallbacks

Past client starts a new project
Matched to the existing contact and flagged as repeat work.
Enquiry from a contractor on behalf of a client
Recorded with the contractor as referral partner and the client as contact.
Project tool has no API for a field
The hand-off creates what it can and sends the studio manager a short task list.
CRM or Zapier outage
Enquiries are queued and retried, and the studio manager gets an alert.

Architecture

A CRM pipeline for a design studio at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Website forms Enquiries Houzz and social Messages Referrals Builders, clients n8n Capture and dedupe Studio CRM Pipeline stages Studio manager Tasks, notes Project tool Signed projects Monthly report By source
  • Input
  • Logic and services
  • Data
  • People
  • Output

How it flows

  1. 1 Enquiries arrive from the website, Houzz, social messages and referral partners.
  2. 2 n8n captures each one, merges duplicates and updates the CRM pipeline.
  3. 3 The studio manager works follow-up tasks; signed projects move to the project tool.
  4. 4 A monthly report shows enquiries, proposals and signed fees by source.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

CRM for architects & interior designers project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Enquiry sources, current tracking, CRM and project tools, stages and reporting needs.

  2. 02

    Design

    2 to 3 days

    Stage definitions, field mapping, hand-off rules and consent fields.

  3. 03

    Build

    1 to 2 weeks

    Source capture, pipeline automation, tasks, project hand-off and report.

  4. 04

    Shadow run

    About 1 week

    Enquiries flow into the pipeline while the studio keeps its old process, and we compare.

  5. 05

    Launch

    1 to 2 days

    Switch over and train the principal and studio manager.

  6. 06

    Support

    Ongoing

    New sources, stage changes and reporting tweaks.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n HoneyBook or Dubsado through Zapier Monograph API and webhooks BQE CORE API HubSpot CRM API Gmail or Microsoft 365

Cost estimate

What it costs, line by line.

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

    Sources, stages, field mapping and reporting.

    $200 – $400

  • Build

    Capture, merging, stages, tasks and hand-off.

    $500 – $1,300

  • Integrations

    CRM, project tool, email and forms.

    $150 – $400

  • Testing and shadow run

    Side-by-side with your current tracking.

    $100 – $250

  • Launch and training

    Switch-over and studio training.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. CRM and project tool subscriptions, Zapier or n8n are billed to you directly. A two-way project-tool sync may need a second workflow.

Monthly running costs you pay directly

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

  • CRM and project tool: Each vendor's own plan.
  • Zapier or n8n: Your Zapier plan where a product connects only through Zapier; n8n self-hosted free or n8n Cloud from about €20 a month (Starter, billed annually).

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

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

UK: written terms before work

ARB guidance says architects meet the standard by giving clients written terms of engagement before work starts and recording changes in writing; the pipeline will not mark a project active without signed terms.

Source: arb.org.uk

UK: marketing emails

PECR requires consent, or the soft opt-in conditions, for marketing by electronic mail, with a way to refuse in every message.

Source: www.legislation.gov.uk

EU and UK: processors under contract

CRM and automation vendors that hold client data act as processors and need a written contract.

Source: gdpr-info.eu

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.

FAQ

CRM for architects & interior designers questions, answered.

If you already use HoneyBook, Dubsado, Houzz Pro, Programa or Studio Designer, its built-in client tools are often enough once automated. Studios that want a separate sales pipeline often choose HubSpot. We help you decide based on how you win work.

Practice platforms such as Monograph and BQE CORE include pipeline and project accounting, and both publish APIs. Larger practices sometimes run a CRM such as HubSpot alongside. We connect whichever you choose.

HoneyBook connects to Zapier on its Essential and Premium plans, with triggers such as a new client or a paid invoice. We use those connections, and n8n where needed, to link the rest of your studio.

No. The CRM handles enquiries to signed terms, then hands the project to your project tool so nothing is retyped.

Yes. Referral partners are tagged on each enquiry, and the monthly report shows which partners send signed projects so you can thank them properly.

Enquiries by source, time to first reply, discovery calls, proposals sent, proposals accepted, average fee and referral partner contribution.

Free 20-minute call

Want this 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