CRM for Architects: Tracking Leads to Appointments

Why architecture practices need a CRM

A CRM for architects is a single record of every enquiry, fee proposal and client relationship, with a stage and a value attached to each. Its job is to show the practice what work is likely to arrive, when, and whether the team will be free to do it.

In many practices business development lives in directors' inboxes and memories. An enquiry arrives, a fee proposal goes out, and nobody records whether it was chased, why it was lost or what fee the client eventually accepted elsewhere. Each director has a partial view, and the practice as a whole has none.

That gap costs money in three ways. Proposals go unchased because nobody owns the follow-up. Resourcing decisions are made without knowing that two large appointments may land in the same month. And fee levels drift, because nobody can see which fees won and which lost. A CRM does not need to be complicated to fix all three. It needs a short list of stages, a few required fields and a weekly habit of keeping it current.

Pipeline stages that fit how architects win work

Five stages are enough for most practices: enquiry, qualify, fee proposal, negotiation, and won or lost. Each stage should have a clear entry test so that two people would put the same opportunity in the same place.

Qualify before you price

The qualify stage is the one most practices skip, and it is where most wasted proposal time comes from. Before writing a fee proposal, confirm four things: the client has a realistic budget, the site and brief are real, the programme is achievable, and you know who decides. A short qualification call often saves days of fee proposal work on a job that was never going to proceed.

Lost is a stage too

Close opportunities as lost when the client chooses someone else, goes quiet for an agreed period or shelves the project. A pipeline full of proposals nobody has heard about for six months makes the forecast look better than it is.

Value the pipeline by probability

A probability-weighted pipeline multiplies each opportunity's fee by the chance of winning it at its current stage. The total is a more realistic view of future fee income than the sum of every proposal sent.

Set a probability for each stage, then refine it from your own results once you have a year of data. The figures below are illustrative starting points; your own win rates will differ.

Enquiry

4 opportunities worth £120,000 in fees, weighted at 10%, gives £12,000.

Qualify

3 opportunities worth £150,000, weighted at 25%, gives £37,500.

Fee proposal

3 opportunities worth £180,000, weighted at 40%, gives £72,000.

Negotiation

2 opportunities worth £90,000, weighted at 70%, gives £63,000.

Total

£540,000 of fees in the pipeline, with a weighted value of £184,500.

The weighted figure is a planning number, not a promise. No single opportunity will pay out at 40% of its fee; it will be won or lost. Across a dozen or more opportunities, though, the weighted total is a reasonable guide to the fee income the practice can plan around, and comparing it month to month shows whether business development is keeping pace with delivery.

The unweighted pipeline tells you how busy directors have been. The weighted pipeline tells you how busy the practice is likely to be.

Link the pipeline to future resourcing

A fee in the pipeline is also a block of hours the practice will need to staff. Converting likely wins into hours, by month, shows whether the practice will need to hire, free people up or chase more work.

If each fee proposal is priced from hours by stage, the hours are already known. Divide the fee by a blended rate when they are not. For example, an illustrative £60,000 appointment at a blended £75 per hour is 800 hours. Spread over a 16-week Stage 2 and 3 programme, that is 50 hours a week, or about 1.3 full-time people at 37.5 hours each.

A simple rule works for most practices: show opportunities at negotiation stage as tentative allocations in the resource plan, and opportunities at fee proposal stage as a total of hours that might be needed. Our guide to resource planning for architecture practices covers how to build the plan itself.

What to record, and the win/loss review

Record the few fields that let you forecast and learn, and nothing else. A CRM that asks for twenty fields per enquiry will not be kept up to date.

• ✓Client, contact and how the enquiry reached you: referral, repeat client, website, framework or competition.
• ✓Project type, location, construction budget and the RIBA stages in scope.
• ✓Fee by stage, the hours and team behind it, and the fee basis quoted.
• ✓Pipeline stage, owner, next action and its date.
• ✓Expected decision date and expected start date.
• ✓Outcome, and for losses, the reason and the winning fee if the client will share it.

Review wins and losses every quarter

Once a quarter, look at every opportunity that closed. Calculate the win rate as proposals won divided by proposals decided, so an illustrative 4 wins from 12 decided proposals is a 33% win rate. Then look for patterns: which sources convert, which project types you lose on price, and whether fee levels on won work were high enough to deliver at a margin. Our guide to fee proposal templates covers how to structure the proposal itself.

Ask lost clients a short, polite question about why. Many will answer, and a handful of honest replies is worth more than any amount of guessing.

Questions practices ask

Short answers to the questions UK practices ask most often about CRM and business development.

Do architects need a CRM?

Any practice with more than one person bringing in work benefits from one. A CRM gives the practice a shared record of enquiries, fee proposals and outcomes, so follow-ups happen, future workload is visible and fee decisions are based on what actually won.

What pipeline stages should an architecture practice use?

Five stages suit most practices: enquiry, qualify, fee proposal, negotiation, and won or lost. Give each stage a clear entry test, such as a confirmed budget and decision-maker before an opportunity counts as qualified.

How do you calculate a weighted pipeline?

Multiply each opportunity's fee by the probability of winning it at its current stage, then add the results. For example, a £50,000 fee proposal weighted at 40% contributes £20,000. Set the probabilities from your own historical win rates once you have enough data.

Can we use a general CRM like HubSpot or Salesforce?

Yes, and many practices do. The limitation is that general CRMs do not know about RIBA stages, hours budgets or resourcing, so the fee and team behind a deal usually has to be rebuilt in a separate system once the job is won.

How should we record why we lost a fee proposal?

Use a short fixed list of reasons, such as fee, programme, experience, relationship or project cancelled, plus a free-text note. A fixed list makes the quarterly review possible; the note keeps the detail.

Where Avoice fits

In Avoice the CRM and the project are the same record, so the fee and team behind a deal carry straight into delivery.

In Avoice Clients and CRM, each deal is priced by stage, team and hours, and that price becomes the fee in the proposal. When the deal is won, the project is created with its stages, fees and hours budget already filled in, ready for timesheets to roll up against. People and staffing then shows how the new hours sit against the team's capacity and allocation across live projects.

To see a deal turn into a staffed, budgeted project, book a demo.