Services for architects and interior designers

CRM and studio automation for architects and interior designers who would rather be designing

Make It Flow delivers automated business solutions for architecture practices and interior design studios: a CRM that tracks every enquiry to a signed appointment, enquiries qualified before a principal gives up an afternoon, fee proposals and terms followed up properly, client approvals and change orders with a clear record, FF&E procurement tracked from order to install, and an AI assistant that answers prospective clients from your approved wording. Principals and lead designers keep every design, fee and scope decision.

Your studio software stays the record

Projects, fees, time and schedules live in Monograph, BQE CORE, Programa, Studio Designer, HoneyBook or whatever you use. We connect through their APIs, accounting links or Zapier, and you own every workflow.

Designers decide, software reminds

Automation sorts enquiries, drafts proposals from your templates and chases approvals. Fees, scope, design and every client-facing judgement stay with the principal or lead designer.

A written record by default

Terms, approvals and change orders are sent, signed and filed automatically, which supports written-terms duties such as the UK ARB guidance and makes extra fees easier to agree.

Services

Studio automation for design practices, service by service.

Each one is a focused project with a fixed quote, a written plan and a handover you own.
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 bookin... How we built it

Case Study

Case Study: Interior Design Studio CRM & Workflow

Read the full case study

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.

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

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.

Platform integrations

The software you already use, connected.

Practice systems, CRMs, phones, payments and reviews, connected through documented APIs, webhooks, n8n and custom code.
All integrations

Monograph

Practice management (architecture)

Pipeline, projects, phases and fees for hand-off and change orders.

Monograph API and webhooks, confirmed per project.

BQE CORE

Practice management and accounting

Clients, projects, fees and invoices.

BQE CORE REST API with OAuth 2.0.

Programa

Interior design project management

Schedules, selections and invoices.

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

Studio Designer

Interior design management and accounting

Proposals, purchase orders and invoices.

Connection method confirmed per project.

Houzz Pro

Design business software

Leads, proposals and client portal activity.

Connection method confirmed per project.

HoneyBook

Client management

New clients, projects, meetings and payments as workflow triggers.

HoneyBook's Zapier integration on its Essential and Premium plans.

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.

Tech we work with

Any language, any stack.

Make It Flow delivers automated business solutions: workflows, integrations, AI assistants and the apps around them. Our team works in whatever language and stack fits the job and the systems you already run.

Automation

n8nWebhooksREST and GraphQL APIsScheduled jobs and queues

Backend

PythonPHP and LaravelNode.js and TypeScriptJava

Data

SQL (MySQL, PostgreSQL)Google Sheets and AirtableData sync and ETLReporting dashboards

Frontend and mobile

JavaScript and TypeScriptTailwind CSSJava and Kotlin for AndroidBrowser extensions

AI

Claude, Gemini and OpenAI modelsRetrieval on your own documentsModel Context Protocol (MCP)Evaluation sets

Cloud and DevOps

DockerLinux serversGitHub ActionsMonitoring and backups

FAQ

Automation for architects and interior designers answered.

The admin around the design: enquiry qualification, discovery call booking, fee proposal follow-up, terms and signatures, stage approvals, change orders, purchase orders, delivery tracking, invoicing reminders and review requests. Design work and client judgement stay human.

Many studios already have one inside their project tool: HoneyBook, Dubsado, Houzz Pro, Programa or Studio Designer for interiors, Monograph or BQE CORE for architecture. Others use HubSpot. We usually automate what you have rather than add another system.

Our fixed quotes start at $1,000 to $2,500 per workflow, $2,500 to $7,500 for an AI assistant and $5,000 to $12,000 for a portfolio website. A connected set of five workflows typically lands between $5,000 and $12,500. Software subscriptions are billed to you directly by each vendor.

For admin, yes, with care. We use AI to sort enquiries, summarise threads and draft messages for review, never to produce design decisions, and we keep client drawings out of AI tools unless you approve the vendor and terms.

Yes. We work remotely with practices worldwide and design for local rules: UK ARB guidance on written terms, consumer cancellation rights in the UK and EU, GDPR and UK GDPR, and TCPA rules for texting in the US.

A single workflow usually goes live in three to five weeks. A connected set is delivered in one-week Scrum sprints, one workflow at a time, in about eight weeks.

Free 20-minute call

Tell us where the studio week disappears

Book a free 20-minute call. We will look at your enquiries, proposals, approvals and procurement, tell you honestly what is worth automating and give you a fixed quote if it is.

Book a free 20-minute call