Residential architects · CRM
Keep every plot, family and proposal in one place so no enquiry goes quiet.
A CRM for a residential architect is a record of each enquiry, the plot, the family members who decide and what was last said. GullySales sets up a simple one that fits a small practice and teaches the team to keep it current.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Also for residential architects
- Lead generation for residential architects
- Follow-up systems for residential architects
- SEO for residential architects
- Local SEO for residential architects
- Social media marketing for residential architects
- Content marketing for residential architects
- Buyer persona for residential architects
- WhatsApp marketing for residential architects
Sales and marketing for residential architects, the overview.
Last updated 14 Nov 2026.
For residential architects
Where it usually goes wrong, and what we would do.
“A house takes a long time and memory fails”
Between first enquiry, site visit, fee note, silence and eventual signing, months pass. A partner remembers one family and loses another. A shared record holds the plot, the budget discussed and the next call due.
“Spreadsheets split across phones”
The enquiry sits in one partner's WhatsApp, the proposal in another's laptop. When that person is on site, nobody can answer the family. A single shared record means anyone in the practice can pick up the conversation.
“Past clients are your referral list”
A finished house leads to neighbours' questions two years later. A record of every completed project, with the family's contact and handover date, lets you stay in touch and see which past clients sent others.
What we do
What we deliver for residential architects.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Simple pipeline for enquiry to signed project
Stages such as enquiry, site visit, fee note sent, family discussing and signed, with a named owner at each.
Result: Every enquiry sits in a stage with a person responsible.
Family and plot record
Fields for plot size, location, budget range, who decides and what each asked.
Result: You never ask the same question twice.
Source and referrer tagging
A field for who or what sent each enquiry, from engineer to Instagram.
Result: Source reports are drawn from the record.
Past-client list
Completed projects with handover date, review status and referrals received.
Result: You can see whom to contact and whom to thank.
Team training
A short walk-through for partners and coordinators on what to record after each call.
Result: The team uses the record on real enquiries.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
These are the fields a house enquiry record needs.
- Plot size, facing and location
- Entered at the first call. It lets you see at a glance which proposals suit the houses you have drawn.
- Family members who decide
- Names and roles recorded after the first meeting. Tells you who must be present before a fee note is discussed.
- Budget range stated
- As the family gave it, with the date. Compared later with the brief, it shows where an expectation changed.
- Stage of the proposal
- Enquiry, plot visit, brief, fee note sent, discussion, signed or declined. The principal updates it after each contact.
- Referrer
- Who sent the family, entered on the first call. It tells you whom to thank, and keeps referral sources visible.
- Reason for no
- A short pick list plus a line in the family's words. After enough such notes you can see what stops proposals.
Who it is for
This is written for these residential architects.
- Independent architects designing individual houses on owned plots
- Practices working on gated-community villas and farmhouses
- Architects for apartment renovation and home redesign
- Studios specialising in compact urban houses on 20 by 30 and 30 by 40 sites
- Architects who take on vernacular and sustainable homes
- Design-and-build practices that also supervise construction
- Architects serving non-resident Indian families building at home
- Small practices that work with a single partner and one site engineer
Before you decide
When this may not be the right fit.
- You take two or three houses a year and a notebook already holds everything you need.
- Your team does not update records, and a CRM would hold last month's picture only.
- You plan to store clients' title documents in a general system with open access.
Before you decide
Agree the work. Know how to judge it.
CRM for residential architects: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from residential architects. Anything missing is noted in the written scope, with who will supply it.
- Every place enquiries are written now
- Bring the diaries, the sheets, the phone notes and the inbox folders. Enquiries are scattered across them. Without a full sweep, the new record starts incomplete and the team keeps its old habits. Phones matter here, because plot photographs and quick questions arrive by message and never reach the diary.
- A list of open proposals and their stage
- The record starts with live cases. Bring the families who have a fee note or a proposal and have not replied. If none are written down, we collect them from the team's memory, which takes longer and is less certain. Add the date of the last contact, since the first reminders are set from it.
- The past-client list with contact details
- Past clients are your referral list, and the record should keep them. Bring names and the year each house was completed. Where contact details are old, we mark them for the team to confirm. Include the date each house was handed over, because a past client may be ready for an extension or a second house some years later.
- Say who may see fee details
- Fee notes are sensitive in a practice with several people. Only you can say who may see them. If you leave it open, we default to the narrowest view and ask you to widen it.
- A person who will keep it current
- A record decays if no one owns it. Name the person, even if it is a junior member. Without one, the system fills for a month and then fades, and families fall back into the diary. Give them time in the studio for it, as an unscheduled task is the first to be dropped on a busy site-visit day.
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Follow one signed project from first call
We pick a recent project and trace it with you: the first call, the site visit, the proposal, the fee note, the signing. You say where information was kept and where it was lost. This shows what the record must hold and what the studio already does well on paper. We also ask what you wished you had known at the second meeting, because that is the first field the record must hold.
- 2
List the stages and the facts for each family
We write the stages from first contact to signed project and the facts to be kept: plot, location, budget, who decides, who referred and what was last said. You choose the stage names in your own words. The list is kept short enough for a busy studio to use. Where a family has several decision-makers, the record has room for each name and role, since the person who calls is rarely the only one who decides.
- 3
Choose the tool and set up the pipeline
We compare a simple sheet and a free or low-cost CRM against your habits and pick what the studio will actually open. We set up the stages, the source list and the referrer register. You decide who sees fee details. We choose a tool your team can open on a phone at a plot visit, because a record that waits for the office desk is filled in from memory.
- 4
Load the live enquiries and test them
We enter the open enquiries and run test entries from the website, a message and a call. The person who handles enquiries works with us. We check that reminders fire, that duplicates are flagged and that the record opens on a phone.
- 5
Train the team on their own cases
We train in the studio with real families, so that notes are written the way people speak. You set the expectation that a family not in the record does not exist. Questions from the team change the fields before final setup. Each person practises entering a visit note straight after a site visit, since that is when the detail is fresh and when a note is likely to be lost.
- 6
Switch over and assign ownership
On the day agreed the diaries stop and the CRM is the record. You name who owns the data, who holds the logins and what happens when a team member leaves. We read the first proposals against the record and correct what is missing.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Do we need paid software?
What if the team does not update it?
Should past clients stay in the CRM?
Should the CRM record the fee we quoted?
Can the CRM store drawings and proposals?
What about enquiries that come through a builder or a relative?
How long is the contract?
How soon will we see results?
Who will actually do the work?
What do you need from us?
More for residential architects
Related work to consider.
Closest to this: leads and follow-up
Also for residential architects
Or start from the overview: sales and marketing for residential architects.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.