Fixed quote after a free call

An architect or interior design website that wins the right enquiries

We design and build an image-led portfolio website for architects and interior designers that loads fast on phones, presents projects as proper case pages, explains services and process clearly, carries local SEO and feeds enquiries into your intake questionnaire and CRM. Projects typically cost $5,000 to $12,000 and take six to ten weeks.

The problem

Why design studio websites underperform

Design studios are judged on their portfolio, yet many sites use huge uncompressed images that crawl on mobile, show projects as galleries with no story, and hide what the studio actually does and where.

Publishing client homes also needs care: permission from the client and the photographer, no identifying addresses and credits where due.

What we build

What our architect and interior design websites include

Project case pages

Brief, approach and outcome with photography, written with you, instead of an unlabelled gallery.

Service and area pages

What you do (new builds, extensions, renovations, full-service interiors) and where, built on real projects.

Fast, image-led design

Responsive WebP or AVIF images, lazy loading and a layout that lets the work speak.

Permission tracking

A record of client and photographer permission for each project before it goes live.

Intake form

The website form feeds the intake questionnaire, CRM and discovery booking.

Local SEO basics

Schema markup, consistent contact details, Search Console and a technical audit before launch.

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

    Visitor arrives

    A prospective client finds the studio through search, Houzz or social.

  2. 02 Automated

    Work explained

    Project and service pages show what you do and how.

  3. 03 Automated

    Enquiry sent

    The intake form sends the enquiry into qualification and the CRM.

  4. 04 Studio manager review

    Studio updates

    The studio adds projects once permissions are recorded.

  5. 05 Principal or lead designer decides

    Publishing approved

    The principal approves every project page and confirms permissions before publishing.

How it behaves

How the portfolio website behaves

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

What the visitor sees

  • Fast, beautiful project pages on any device
  • Clear services, process and areas
  • A short intake form or booking link

What the studio sees

  • Enquiries arriving pre-qualified in the CRM
  • Simple screens to add projects
  • Permission records per project

What the automation does

  • Optimises images on upload
  • Routes enquiries into intake
  • Keeps schema and sitemap current

Edge cases and fallbacks

Project without recorded permission
Kept in draft until permission is recorded.
Old URLs from the previous site
Redirected to the matching new page.
Workflow outage
Enquiries are stored and emailed to the studio.

Architecture

A design studio portfolio website at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Search and social Google, Houzz Portfolio site Fast, image-led Project pages Case stories Intake form Qualifying fields Workflows Intake, CRM Principal Discovery call
  • Input
  • Logic and services
  • Output
  • People

How it flows

  1. 1 Prospective clients arrive from search, Houzz and social.
  2. 2 Project and service pages show the work and the process.
  3. 3 The intake form sends enquiries into qualification and the CRM.
  4. 4 The principal takes the discovery call and approves every project page before publishing.

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.

Architect & interior design portfolio website project plan

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    About 1 week

    Current site, positioning, services, areas and project selection.

  2. 02

    Content and design

    About 2 weeks

    Page plan, project stories, design and permission records.

  3. 03

    Build

    2 to 4 weeks

    Pages, image pipeline, intake form, schema and workflow links.

  4. 04

    Test

    About 1 week

    Speed, accessibility, forms, redirects and SEO audit.

  5. 05

    Launch

    2 to 3 days

    Go live, update Google Business Profile and Houzz links, submit the sitemap.

  6. 06

    Support

    Ongoing

    Optional monthly care for new projects and updates.

What it runs on

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

Laravel or WordPress Tailwind CSS Responsive WebP and AVIF images Schema.org LocalBusiness markup PageSpeed Insights and Search Console n8n for form routing

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 audit

    Current site, positioning and project selection.

    $500 – $1,000

  • Content and design

    Page plan, project stories and design.

    $1,200 – $3,000

  • Build

    Pages, image pipeline, form and schema.

    $2,300 – $5,800

  • Integrations

    Intake, CRM, analytics and Search Console.

    $500 – $1,200

  • Testing and launch

    Speed, accessibility, redirects and launch.

    $500 – $1,000

  • Total project estimate

    $5,000 – $12,000

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Photography is not included. Hosting and domain 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.

  • Hosting and domain: Billed by your hosting provider and registrar.

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.

Accessibility

WCAG 2.2 is the W3C accessibility standard; we test contrast, keyboard use and alt text before launch.

Source: www.w3.org

Honest reviews

The FTC rule bans fake or bought reviews and testimonials; testimonial sections use genuine, permitted quotes only.

Source: www.ftc.gov

EU: AI disclosure if you add chat

An AI assistant on the site must tell visitors they are interacting with AI from 2 August 2026.

Source: artificialintelligenceact.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

Architect & interior design portfolio website questions, answered.

Fast, image-led pages, projects told as stories, clear services and areas, an easy enquiry route and solid technical SEO. Beautiful but slow sites lose mobile visitors.

We build on proven layouts but design for your brand and work; templated sites tend to look like everyone else's.

Yes. Projects, images and text are editable, with image optimisation handled automatically.

Responsive WebP or AVIF versions at several widths, served by device, with originals kept off the page.

Each project has a permission record for the client and photographer before it can be published.

Enquiries by page and source, discovery calls booked from the site and Search Console impressions for service and project pages.

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