By Ritchie Clapson CEng MIStructE, propertyCEO
A friend of mine had an old light industrial building that he no longer needed and wanted to do something with it. He knew an architect and asked them to see whether there was scope to develop the building. Several months and £10,000 later, the architect produced a set of drawings. The existing building would be demolished to make way for three 2-bed flats and a studio. There would be granite worktops and gold taps, plus they’d even included one of those fancy electric turntable things that allowed cars to be parked in tight spaces. The architect’s bill was £10,000. Another £10,000 would see them move to the next stage.
My friend gave me a call for advice.
I explained that the plans were impressive. But …
· the market for studio flats in the area was non-existent (the architect had simply been trying to make use of some left-over space) and my friend could be left with a final flat that he couldn’t sell.
· the building was situated in what could only be described as a less-than-desirable part of town – not a ghetto, but certainly not somewhere you’d find granite worktops and gold taps or fancy parking turntables
· I had strong doubts that the plans would get planning consent as the new building was out of character with the street scene, particularly the row of listed cottages next door over which it would loom.
I agreed to help him develop it, and we did something completely different. Instead of demolishing it, we converted it to residential use under permitted development which neatly sidestepped most of the planning issues. Then we built five entry-level one-bed flats, which our estate agent said would sell much quicker than two-beds or studios. And because permitted development doesn’t carry a parking requirement, we didn’t need to install a fancy turntable, which gave us a lot more space. And there wasn’t a granite worktop or gold tap in sight.
My friend’s mistake wasn’t going to a bad architect—as I said, the plans were impressive—but he went to the wrong architect (one who specialised in high-end luxury homes) and he failed to give the architect a proper brief.
If you have a small-scale property project in mind, here are a few tips to help you find the right architect for you and how to get the best from them:
Make sure you set a design brief
Any architect is going to want to know what to design. Do your due diligence to determine what will sell well and who your end customer is. Talking to local estate agents will give you a great steer here, as will looking at what has been built recently in the area. The more specific you are, the less margin for error your architect will have, and you should be able to get a great design at the first attempt.
Pick an architect with relevant experience
It’s the horses for courses argument. You want to find someone with plenty of experience working on the type of project you will be building. Whether you’re tackling a development project or simply building an extension, it pays to go with an architect who’s familiar with the species. Ask to see some past projects similar to your brief.
Have a beauty parade
Don’t pick the first architect you come across that can do the job. Make sure you’ve at least three in the frame, and then make sure you go and see them all in person. Get quotes from each of them. If it’s a practice instead of a one-person operation, be sure to speak to the person with whom you’ll be working.
Ask about freebies
There will be times when you want to call your architect to discuss an in-principle idea. It happens all the time. You’ve just seen a great little opportunity but want to know if such-and-such is feasible. You want your architect to take ten minutes out to have a quick look and give a non-binding opinion. What you don’t want is for your architect to say, ‘that will cost £500, please send me a written design brief, and I’ll get back to you in a month’. So, check this out BEFORE you appoint your architect, but make it clear that you’d fully respect a fair usage policy when it comes to freebies.
Get referrals and testimonials
Ask around to see who comes recommended. Speak to contractors and project managers to see who they would recommend. All architects look the part on their websites, but the proof of the pudding will come from talking to their previous clients. Ask to speak to a client who has had a completed project and one that is ongoing. You’re looking to establish how responsive the architect has been, how easy to deal with, and how well they have interacted with the contractor and the rest of the team. Also, ask whether there have been any design errors and how they were rectified.
Learn how to block plan
When considering a potential development opportunity, a key question right off the bat is ‘how many units can I build on this site?’. If you have to ask your architect every time you look at a deal, it will soon get expensive and time-consuming. Instead, learn the art of block planning yourself, and then compare your ideas with the architect once you know the deal is worth taking to the next stage. Challenge your architect to do a better job than you have – after all, they’re supposed to be the experts.
Have a reserve list
Not only may you be encountering a variety of projects that might suit different architects, but you’ve also got no way of knowing whether your first-choice practice will be available when a deal comes along. It’s always sensible to know who your backup B Team will be, not just for architecture but also for every other member of your professional team.
My final piece of advice involves how you work with your architect once they’re appointed. Having worked on hundreds of projects over the years, I’ve often encountered situations where a project hits an unexpected bump in the road that suddenly needs to be dealt with or accommodated. The default solution for many professionals, architects included, is to accept that there will be some additional work involved or some extra cost added to the project. The problem is that they’re not paying for it, but you are. In these situations, I usually like to get my design team into a huddle and tell them there’s no more money to throw at the problem. So, instead, they’ll need to come up with an alternative solution that circumvents the issue but doesn’t cost me any more money. Whether they save the money from elsewhere, I don’t mind. But they need to come up with something.
Is it always possible? Not every time. But because the default thinking is to get the developer to pay, these people aren’t usually put in a position where they need to devise something more creative when it comes to problem-solving. And the reality is that they can often be rather good at it, particularly when they do it together.