AI for Architecture Practices in Edinburgh
Edinburgh architecture practices work in one of the most rigorously conserved urban environments in Britain. Practices with studios in Leith, the New Town and the Southside carry a portfolio that typically mixes listed building consents, World Heritage Site applications and conservation area conditions alongside the university capital programmes, NHS Lothian estate work and social housing commissions that provide a more regular project rhythm. The Scottish Government's planning framework adds its own distinct policy layer on top of Historic Environment Scotland's consent requirements. Partners still draw. Associates still run planning. Technologists still own the Revit standards. The paperwork underneath all of it is where time disappears. Fee proposals drafted from scratch on Tuesday evenings because nobody goes hunting for the previous one. Planning statements that take three days to assemble. Drawing registers that fall behind every time a project hits a busy week.
How we help architecture practices in Edinburgh
Fee proposals that reuse what the practice already knows
A fee proposal for RIBA stages one to four on a New Town tenement refurbishment, a Leith commercial conversion or a university capital project is a scoping exercise the practice has done many times before. The partner still writes it from scratch because the last proposal is in a folder on somebody's laptop that nobody opens mid-week. Three or four hours go before the draft is ready to send, and meanwhile the client has started to wonder if the enquiry was registered. Across the partner group the practice is quietly sustaining the equivalent of a part-time proposal-writing role that was never in the budget.
We wire up a tool that reads the practice's past proposals, fee agreements and stage packages, and drafts a starting fee proposal from a brief the partner types in. Scope by RIBA stage, fees in the structure the practice has always used, assumptions in the house voice, timeline calibrated against the last three comparable projects. The partner reviews and edits before anything goes out. The judgement stays with the partner. The hunting and the retyping go.
A twenty-five-person professional services firm we work with took proposal time from four or five hours to under one using a very similar set-up, and ended up sending more proposals per month because the partners stopped being the bottleneck. The architecture version runs at lower volume and higher craft, but the shape of the win holds. Proposals go out the same day the brief lands. Partners get their Tuesday evenings back.
Planning statements assembled in hours, not three days
A full planning submission for a listed building in Edinburgh's New Town, or a consent application within the World Heritage Site buffer zone, is a serious piece of document work. Design and access statement, historic environment statement, pre-application correspondence, planning history for the address, policy references from the City of Edinburgh Local Development Plan and the relevant Historic Environment Scotland guidance: all assembled into one coherent document. On a good week the associate running the project manages it. On a bad week the submission slips a fortnight because the same associate is closing a tender package for an NHS Lothian commission.
We build a drafter that sits on top of the practice's own archive of submitted statements, the local plan PDFs and the pre-app notes, and produces a starting draft from the site address and a short brief. Policy references checked and pulled from the current plans. Historic environment context written against the practice's own archive of previous submissions. Design and access language in the voice the practice has always used. The associate reviews and edits before anything goes to the council. A three-day assembly becomes a half-day review, and Fridays stop being swallowed by document production.
Drawing register reconciliation without the Friday stand-off
On a live Edinburgh project the drawing register is what quietly falls behind. The technologist issues drawings to the contractor, the QS marks up comments, the architect issues a revision, and the information release schedule lags by a week because nobody has a free hour to update the spreadsheet. By Friday the issue pack is going out and somebody is still reconciling which revision of the structural drawings matches which revision of the architectural set.
We set up a light layer that reads drawings out of Revit or BIM 360, RFIs out of the contractor's system and markups out of the QS's email, and keeps the drawing register and information release schedule in sync automatically. It flags mismatches before the issue pack is packaged and drafts the cover letter in the format the practice has always used. The project architect still signs off every issue. The Friday evening reconciliation drops out of the picture entirely.
“The partners had stopped dreading the admin side of winning new business. That felt like the real result.”
One problem at a time
We work on one problem at a time. No transformation programmes, no glossy strategy decks, no retainer signed before you have seen anything running. The first conversation is a free AI Opportunity Report. Fifteen minutes on the phone, and within twenty-four hours you get a written report that picks two or three places where AI would pay for itself quickly in your practice, with honest estimates of what it would cost and how long it would take.
If one of the ideas looks worth doing, we talk about doing it. If none of them do, the report is yours to keep. No sales call, no pressure to move faster than you want to.
We are based just across the border in the north east
We are based just across the border in the north east, about ninety minutes down the A1 from Edinburgh, which in practice means we are happy to come up for a meeting when it matters. The Edinburgh practices we work with tend to be partner-led, somewhere between four and twenty people, and the partners have been through enough BIM rollouts and Historic Environment Scotland consent cycles to be properly sceptical of anything that arrives promising transformation. Conservation conditions in the New Town, World Heritage Site applications, Leith waterfront consents, university capital programmes: the planning pressures are specific and the tolerance for vague software claims is low. What we do is pick one precise piece of production admin, take it off the associates and the technologists, and put the numbers on the table before we suggest anything else.
Common questions from Edinburgh architecture practices
What kind of AI tools do you actually use?
Whatever fits the job. We are tool-agnostic and we do not resell anything, so nothing gets recommended because a vendor is paying us to push it. For architecture practices it usually ends up being document extraction over past submissions and proposals, workflow platforms like Make or n8n for the plumbing between systems, bespoke wrappers around Claude or GPT for the language-heavy work, and integrations with Revit, ArchiCAD, BIM 360 and whatever project admin software you already run. We do not replace software you are paying for.
Is this going to touch the design itself?
No. We stay off the design side of the practice on purpose. Partners keep the design judgement. Associates keep the planning calls. Technologists keep the Revit standards. What we build sits around the design, on the production paperwork that was already getting done on a Friday night. Proposals, planning statements, drawing registers, specifications. The creative work of the practice is not ours to touch.
Is it safe to use AI with client project data?
Yes, when it is set up properly. We only use deployment patterns where your project data stays under your own control and is never used to train an external model. Edinburgh practices doing World Heritage Site and listed building work carry historically sensitive data and client confidentiality obligations. We walk you through exactly what the data flow looks like for each specific tool in the free report rather than asking you to take our word for it.
How long does a typical project take?
The first piece of work normally runs two to six weeks, from the first conversation to something actually running inside your practice. We keep the first project small on purpose so you see a result quickly and can decide for yourself whether we are worth having back for the next one. Bigger or more ambitious pieces come later, once trust has been earned and the first thing has paid for itself.
Will this replace our technologists or our associates?
No. Every practice we have worked with has ended up with the same team doing more of the architecture they came into the profession to do and less of the production paperwork they did not. The goal is to take the Friday evening assembly off the associates and the technologists, not to shrink the practice. Good technologists and associates are difficult enough to retain in a city like Edinburgh without anyone losing them deliberately.
Run an architecture practice in Edinburgh?
Fifteen minutes from you, and a detailed written report back within twenty-four hours. No sales call required.