AI for Architecture Practices in Glasgow
Glasgow architecture practices carry a project mix that reflects the breadth of the city's built environment. Studios in Finnieston, the Merchant City and around the Clydeside regeneration zones deal with commercial refurbishment, heritage work on the Victorian tenement and warehouse stock, and the large-scale residential and mixed-use commissions that flow from Glasgow City Council's housing programme. The Mackintosh buildings and the Category A-listed stock around Blythswood Hill generate a steady flow of listed building consent work that demands detailed heritage submissions. University of Glasgow and NHS Greater Glasgow capital programmes provide another layer of institutional project work. Partners still draw. Associates still run planning. Technologists still own the Revit standards. The production paperwork underneath all of that is where the week goes. Fee proposals rewritten from scratch. Planning statements that need three days to assemble. Drawing registers that slip behind every time a project hits a tender deadline.
How we help architecture practices in Glasgow
Fee proposals that reuse what the practice already knows
A fee proposal for a RIBA stages one to four commission on a Finnieston commercial conversion or a Category A listed building in the Merchant City is the same scoping exercise the practice has done many times. The partner still writes it from scratch because the last comparable proposal is in a folder that nobody opens during the working day. Three or four hours disappear before the draft is ready to send, and by then the client is starting to wonder whether the inquiry landed with the right person. Across the partner group the practice is sustaining the equivalent of a part-time role in proposal writing that nobody planned for.
We wire up a tool that reads the practice's past proposals, past fee agreements and past stage packages, and drafts a starting fee proposal from a short brief the partner types in. Scope by RIBA stage, fees structured the way the practice has always structured them, 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 evenings back.
Planning statements assembled in hours, not three days
A full planning submission for a Category A or B listed building in Glasgow, or a conservation area consent in one of the tenement districts, is a serious document job. Design and access statement, historic environment statement, pre-application correspondence, planning history for the address, policy references from the Glasgow City Development Plan and Historic Environment Scotland guidance: all assembled into one coherent document the planning officer can read in one pass. On a good week the associate gets to it. On a bad week the submission slips because the same associate is closing a tender package for an NHS Greater Glasgow commission.
We build a drafter that sits on top of the practice's own archive of submitted statements, the Glasgow local plan PDFs and the pre-app notes, and produces a starting draft from the site address and a brief. Policy references checked against the current plans. Heritage context written against the practice's own archive. Design and access language in the voice the practice has always used. The associate reviews and edits before it goes near the planning portal. A three-day assembly becomes a half-day review.
Drawing register reconciliation without the Friday stand-off
On any live Glasgow 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 because nobody has a free hour to reconcile the spreadsheet. By Friday the issue pack is going out and somebody is still working out which revision of the M and E drawings corresponds to 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. What gets removed is the Friday evening reconciliation, which was never architecture.
“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, an easy run up the M74 from Glasgow, and happy to come up for a meeting when the work is worth it. The Glasgow practices we talk to tend to be partner-led, between four and twenty people, and the partners have been through enough BIM rollouts and Historic Environment Scotland cycles to be properly sceptical of anything that promises transformation. Listed building consents in the Merchant City, conservation area work in the tenement districts, NHS Greater Glasgow capital programmes: the planning pressures are specific and the tolerance for vague software claims is low. What we do is pick one 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 Glasgow 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. Glasgow practices doing listed building and Category A heritage work carry sensitive site data and client NDAs. 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 work comes later, once trust has been earned and the first piece 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 are genuinely hard to hold on to in a competitive city without anyone losing them deliberately.
Run an architecture practice in Glasgow?
Fifteen minutes from you, and a detailed written report back within twenty-four hours. No sales call required.