Fixed quote after a free call

Client approvals and change orders with a clear record

Design stages, finish selections and change requests wait on client decisions buried in email threads, and small extras add up without a record. We build a workflow that sends each stage or selection with a clear approval request, chases decisions that block the programme, logs change requests, routes them to the designer to price and gets the client's signed approval before extra work begins. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why approvals and scope creep stall design projects

A project stalls when the client has not approved the concept, the tile or the revised layout, and the order or contractor is waiting. Approval often lives in a reply-all at 11pm that nobody can find later.

Scope creep is the other side. A client asks for one more room, a different staircase or an extra site visit, and without a change order the additional fee is hard to raise and easy to dispute. ARB guidance in the UK expects changes to terms to be recorded in writing.

What we build

What our approvals and change order workflow includes

Stage approval requests

Each stage issue or selection sent with what is being approved, what happens next and a one-click approve or comment.

Decision chasers

Polite reminders for decisions that block the programme, with the designer told when a date is at risk.

Change request log

Client requests captured from email or the portal into a log with description, stage and status.

Priced change orders

The designer prices each change; the client signs a change order before work starts.

Approval record

Every approval and change order filed against the project with date, version and who approved.

Fee tracking link

Approved change orders added to the fee in Monograph, BQE CORE, Programa or your accounting tool.

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

    Stage issued

    The designer issues a stage package or selection for approval.

  2. 02 Automated

    Approval requested

    The client gets a clear request and reminders until they decide.

  3. 03 Automated

    Change logged

    Any change request is logged and sent to the designer.

  4. 04 Studio manager review

    Designer prices

    The designer or studio manager prices the change and prepares the order.

  5. 05 Principal or lead designer decides

    Design and fee decisions

    Design responses and fees for changes are decided by the lead designer or principal.

How it behaves

How approvals and change orders behave

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

What the client sees

  • A clear request saying what to approve and why it matters now
  • One-click approve or comment
  • A simple change order to sign before extra work

What the studio sees

  • Outstanding approvals by project
  • A change log with prices and status
  • A filed record of every decision

What the automation does

  • Sends requests and chases blocking decisions
  • Logs changes and collects signatures
  • Updates the fee when a change order is signed

Edge cases and fallbacks

Client approves by email reply
Captured into the record with the email attached.
Two decision makers disagree
The request stays open and the designer is notified.
Change request with no fee impact
Logged as nil-cost with the designer's note.
Portal or e-signature outage
Requests are resent by email and logged manually.

Architecture

Approvals and change orders at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Stage issue Drawings, boards Change request Email or portal n8n workflow Requests, chasers Client Approve or comment Lead designer Prices changes Change order Signed Approval record Versions, dates
  • Input
  • Logic and services
  • Output
  • People
  • Data

How it flows

  1. 1 Stage packages and change requests enter the workflow.
  2. 2 Clients get clear approval requests and reminders; change requests go to the designer.
  3. 3 The designer prices each change and the client signs a change order.
  4. 4 Every approval and change order is filed with version and date.

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.

Client approvals & change order automation project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Stages, current approval habits, change process and tools.

  2. 02

    Design

    2 to 3 days

    Approval templates, chaser timing, change order form and record format.

  3. 03

    Build

    1 to 2 weeks

    Requests, chasers, change log, change orders and fee link.

  4. 04

    Shadow run

    About 1 week

    Run on one live project with the designer checking every message.

  5. 05

    Launch

    1 to 2 days

    Roll out to active projects.

  6. 06

    Support

    Ongoing

    Template changes and new stage types.

What it runs on

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

n8n DocuSign or PandaDoc Programa, Studio Designer or Houzz Pro client portal Monograph or BQE CORE Google Drive, Dropbox or SharePoint Slack or Microsoft Teams

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

    Stages, templates and change process.

    $200 – $400

  • Build

    Requests, chasers, change log and orders.

    $500 – $1,300

  • Integrations

    Portal, e-signature, files and fee tool.

    $150 – $400

  • Testing and shadow run

    One live project run.

    $100 – $250

  • Launch and training

    Rollout and walkthrough.

    $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. E-signature, portal and n8n costs are billed to you directly.

Monthly running costs you pay directly

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

  • E-signature: DocuSign, PandaDoc or your platform's signing at the vendor's plan.
  • n8n: Free self-hosted Community edition, 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: changes recorded in writing

ARB guidance expects changes to the initial terms to be documented in writing; signed change orders provide that record.

Source: arb.org.uk

E-signature validity

Electronic signatures are generally recognised in the EU under eIDAS; your adviser confirms what suits each document.

Source: eur-lex.europa.eu

EU and UK: client data

Approval records and home photos are personal data and are stored with contracted processors.

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

Client approvals & change order automation questions, answered.

A written record of a change to agreed scope, with its effect on fee, budget or timing, signed by the client before the extra work starts. The workflow logs requests and collects signatures.

Yes, both for changes to the architect's own services and, separately, for construction contract changes. We automate the studio's own approvals and fee changes; construction contract changes follow the contract administrator's process.

No. If Programa, Studio Designer or Houzz Pro handles approvals, we connect to it and add chasers and records around it.

Reminders only go for decisions that block the programme, and they explain what is waiting on the client.

It flags unsigned changes on the project and in the weekly summary. Whether to proceed is the principal's decision.

Average days to client approval per stage, number of change requests, share signed before work and additional fees recovered.

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