AI for Architecture Practices in York
York architecture practices sit in a city where almost any project of size lives inside a conservation area, a designation that shapes the brief before the first sketch goes on paper. Practices we talk to work out of studios off Micklegate, in converted offices around Stonegate and the Minster, and in newer space at Monks Cross and along the A1237 ring road. The book is a mix of conservation work in the city walls, residential extensions across Clifton, Heworth and Bishopthorpe, education projects for the University of York, and small commercial work tied into the science park out at Heslington. Partners still draw. Associates still run planning. Technologists still own the Revit standards. What goes missing is the partner's afternoon, lost to a fee proposal written from scratch for the fiftieth time, or a heritage statement that takes three days to assemble because the policy references and the pre-app correspondence sit in five different places. AI earns its keep here by taking the production admin off the technologists and the associates, without going anywhere near the design judgement.
How we help architecture practices in York
Fee proposals that reuse what the practice already knows
A fee proposal for a RIBA stages one to four extension on a Clifton terrace is the same scoping conversation the practice has had fifty times. The partner still writes it from scratch, because the last proposal sits on somebody's laptop in a format nobody is going to go hunting for at four o'clock on a Tuesday. Three or four hours disappear before the draft is ready to send, and the client has gone quiet while they wait. Repeat it across the partner group and the practice is quietly funding a full-time role in proposal writing that nobody ever hired.
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 laid out by RIBA stage, fee structured the way the practice has always structured fees, assumptions written in the house voice, timeline pitched against the last three projects of similar shape. The partner signs it off after whatever edits they want. The judgement stays with the partner. What gets taken off the Tuesday afternoon is the retyping and the hunting.
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 the firm ended up sending more proposals a month rather than fewer because the partners had stopped being the bottleneck. The architecture version is smaller in volume and higher in craft, but the shape of the win is the same. Proposals go out the same day the brief lands. Clients stop chasing.
Heritage statements assembled in hours, not three days
A full submission for a conservation area extension within the city walls or a listed building consent on a Stonegate frontage is a three-day job if somebody does it properly. Design and access statement, heritage statement, pre-app correspondence with the City of York Council conservation officer, planning history for the address, policy references from the local plan, all pulled into a coherent document a planning officer can read in one pass. On a good week the practice gets to it. On a bad week the submission slips by a fortnight because the associate running it is closing a tender package for a different job.
We build a drafter that sits on top of the practice's own archive of submitted statements, the City of York local plan PDFs and the pre-app notes, and produces a starting draft from the site address and a short brief. Policy references pulled correctly. Heritage context written against the 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. What was a three-day assembly job becomes a half-day review, and the practice stops losing Fridays to document wrangling.
Drawing register reconciliation without the Friday stand-off
On a typical live project the drawing register is the thing that quietly gets 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 an 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 matches which revision of the architectural plans.
We set up a light layer that reads the drawings out of Revit or BIM 360, the RFIs out of the contractor's system and the markups out of the QS's email, and keeps the drawing register and the information release schedule in sync automatically. It flags mismatches before the issue pack gets packaged, and it drafts the cover letter in the format the practice has always used. The project architect still signs off every issue. What gets taken off the Friday evening is the reconciliation, which is nobody's idea of 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 back 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 up the road in the north east
We are based just up the road in the north east, which makes York a straight run down the A19 or the East Coast Main Line. The practices we meet in York tend to be partner-led, somewhere between three and twenty people, and the partners have been through enough BIM rollouts and software procurement cycles to be properly sceptical of anything that promises transformation. Conservation officer correspondence, listed building consents and the constraints of working inside the city walls shape the working week in a way that does not show up in a Leeds or a Manchester practice. What we do is quieter than the usual AI pitch. We pick one specific piece of production admin, take it off the associates and the technologists, and put the numbers on the table before we suggest the next thing. The design judgement stays with the partners.
Common questions from York 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 already paying for. We make it do more of the work.
Is this going to touch the design itself?
No. We stay off the design side of the practice on purpose. The partners keep the design judgement. The associates keep the planning calls. The 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, information release schedules. The creative work of the practice is not ours to touch, and we do not want it.
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. Most architecture practices we talk to are rightly cautious about this, particularly where listed building work or sensitive residential commissions are involved. We walk you through exactly what it 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 of work come later, once trust has been earned and the first one 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 good associates are hard enough to hold on to without anyone losing them on purpose.
Run an architecture practice in York?
Fifteen minutes from you, and a detailed written report back within twenty-four hours. No sales call required.