Landscape architects · CRM
Keep each brief, site visit and fee proposal in one record with a next step.
A CRM for a garden design practice is a single record of every brief, with the site, the contact, the visit date, the drawings promised and the fee stage. GullySales sets up the fields and the follow-up dates, in a tool your team will keep up to date.
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 landscape architects
- Lead generation for garden design practices
- Follow-up systems for garden design practices
- SEO for garden design practices
- Local SEO for garden design practices
- Social media marketing for garden design practices
- Content marketing for garden design practices
- Buyer persona for garden design practices
- WhatsApp marketing for garden design practices
Sales and marketing for landscape architects, the overview.
Last updated 14 Nov 2026.
For landscape architects
Where it usually goes wrong, and what we would do.
“A brief lives in three places”
The developer's call is in a notebook, the villa owner's message is on WhatsApp and the architect's introduction is in an email. When the principal is on site, nobody can say where each brief stands.
“The proposal stage is where briefs fade”
Drawings were promised and a fee proposal was sent, then the client went silent. Without a date to follow up, the proposal sits unanswered, and the practice assumes the client chose someone else.
“Relationships with architects are not recorded”
Which architect sent which brief, and when you last showed them a finished site, lives in memory. When a team member leaves, the relationship records leave with them.
“Maintenance contracts have end dates nobody tracks”
An upkeep contract that lapses is a client you can lose without noticing. Without a recorded end date, the renewal conversation starts when the owner raises it.
What we do
What we deliver for landscape architects.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
Record fields that fit your work
Site type, size, stage of the building, referrer, visit date, drawings promised, fee proposal date and outcome.
Result: Every brief is stored the same way.
Stages from brief to maintenance
A pipeline from enquiry to site visit, proposal, agreement, supervision and upkeep contract.
Result: You can see where each brief is stuck.
Referrer tracking
Each architect, developer contact and nursery linked to the briefs they sent and the dates you last met.
Result: You know who to thank, show a project to or call.
Contract end dates
Upkeep contracts logged with start and end dates and a prompt before each end.
Result: The renewal conversation is yours to open.
Team habits
A short written routine for who updates the record and when, with a check on records left unchanged.
Result: The record stays true after the first busy fortnight.
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
Keep each brief, site visit and fee proposal in one record with a next step.
- Site type, size and stage
- Entered at the first call by the partner or coordinator, so the proposal is built on the real conditions.
- Decision-maker and influencer
- The developer, architect or committee member and the person who recommended you, noted so the proposal reaches both.
- Fee proposal and date
- Amount and scope sent, with the date, entered by whoever sent it, so no proposal waits without a reply.
- Source of the brief
- An architect, past client, project page or site board, chosen from a list, so you see which source pays.
- Next step and owner
- A site visit, a revised scope or a call, with the name of the person responsible, so each brief has a date.
Who it is for
This is written for these landscape architects.
- Landscape architects for apartment and township developers
- Practices designing podium gardens and clubhouse courts
- Landscape architects for villas and farmhouses
- Campus, school and institutional landscape architects
- Resort and hospitality landscape designers
- Public park, street and urban landscape architects
- Terrace garden and vertical garden specialists
- Landscape architects who also execute and maintain
Before you decide
When this may not be the right fit.
- You handle a few briefs a quarter and a notebook already works, so a tool would add typing.
- Nobody will enter notes after a site visit, so the record would be empty where it matters.
- You want the tool to find briefs, but a CRM only records the ones you have.
Before you decide
Agree the work. Know how to judge it.
CRM for garden design practices: 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 landscape architects. Anything missing is noted in the written scope, with who will supply it.
- All the places briefs are written
- Bring phones, notebooks, email folders, drawing registers and any sheets the team uses. We need to see where briefs live to bring them into one record, and which of those places each person will not give up. If some sit only in personal phones, the load is partial and the pipeline view will understate the true number of live briefs.
- A list of current live briefs
- Every brief you are still working on should be listed with its site, contact and stage. A rough sheet is enough. If the list is missing, the CRM opens empty, and for a few weeks it will not show the pipeline you actually carry.
- Agreement on one person to own the record
- One person in the practice must be responsible for keeping stages current and for reminding others. It may be a coordinator or a partner. Without a named owner, entries lapse within weeks, and the tool becomes another place where information is lost.
- Your rule for when a brief is lost
- State when a brief is moved to lost: no reply after a set number of follow-ups, a decline in writing, or a project cancelled. A clear rule keeps the pipeline honest. Without it, old briefs clutter the view and the counts at each stage mean little.
- Contract copies for upkeep clients
- End dates and renewal terms come from the signed contracts. Scanned copies are enough. Where contracts are missing, we leave the end date blank and mark the client for a call, so that no renewal is assumed that cannot be found on paper.
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
Trace one brief from first call to fee
We follow a recent brief through your practice with you, noting each place it was written down: a phone, a notebook, a proposal file, a payment sheet, a drawing register. We then pick a second brief that was lost and trace it the same way, to see where it slipped. You tell us who touched it at each stage. This gives us the real journey of a brief, and the points where it has gone missing before.
- 2
Name the stages from brief to upkeep
Together we write stages that fit your work: first enquiry, site visit, concept, proposal sent, agreement, supervision, handover and upkeep. You decide where a brief stops being active and where it is lost. The stages are limited in number so your team can remember them without opening the tool.
- 3
Choose the fields each record must hold
We list the facts a brief needs: site type, plot or podium, contact, referring architect, visit date, drawings promised, fee stage, expected decision date and the planting season the work is aimed at. You cross out any field your team will not fill, and we mark the three that must never be empty. Fewer fields kept up to date beat a long form left blank.
- 4
Set up the tool and load old briefs
We build the stages and fields in a tool your team will use, and load the briefs of the last year from your lists. You check the first twenty records against the originals. Any record that is wrong is corrected before the rest are loaded.
- 5
Add referrers and contract end dates
Architects and developers who send you work are recorded as referrers, linked to each brief they sent. Upkeep contracts get an end date and a reminder. You tell us which architects send you the best briefs, and we mark them so that a quiet relationship is visible and not forgotten.
- 6
Hold a review of the record with the team
After the team has used the record on live briefs, we sit with them and compare it with the start, asking each person which field was a nuisance and which saved a call. You and we look for briefs with no next step, stages that are skipped and fields left empty. The tool is then adjusted to how the practice truly works.
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.
Which CRM tool should we use?
Is a CRM too much for a small practice?
Can the CRM show which source pays?
Is a CRM too much for a small practice?
Can the CRM hold drawings and proposals?
Who sees the fee details?
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 landscape architects
Related work to consider.
Closest to this: leads and follow-up
Also for landscape architects
Or start from the overview: sales and marketing for landscape 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.