Landscape architects · Website
Build a site that shows the size, the type and the problem solved on every project.
A website for a garden design practice is where a developer, an architect or a homeowner checks your work after an introduction or a search. GullySales works on project pages by site type, a clear scope of design, supervision and upkeep, and an enquiry form that asks the right things.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What website means
A website is the page a customer lands on after searching, clicking an advert or scanning a code, and it decides whether they call or leave. GullySales builds and maintains sites that load quickly, explain the offer plainly and make the enquiry form or phone number easy to find.
Also for landscape architects
- SEO for garden design practices
- Local SEO for garden design practices
- Lead generation for garden design practices
- Social media marketing for garden design practices
- Content marketing for garden design practices
- Buyer persona for garden design practices
- CRM for garden design practices
- Follow-up systems 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.
“Beautiful borders do not show the work”
A gallery of plants proves taste, but a developer wants the site size, the level changes and the constraint you solved. Without them, the site reads as a nursery catalogue.
“Visitors arrive from a phone”
A villa owner opens the site on a phone beside the bare plot. Heavy image galleries that load slowly or overflow the screen lose them before they reach a project.
“Scope is unclear”
Visitors cannot tell whether you only draw, or also supervise, plant and maintain. A page that separates those four services stops the price-per-square-foot comparison before it starts.
“A project brief form that is too short or too long”
A form that asks only for a name gives you nothing to prepare with. One that asks for a full brief puts people off. A short form with site type, size, location and stage works.
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.
Project pages by site type
Pages for podium gardens, township open space, villas, farmhouses and terraces, each with size, levels, palette and the problem solved.
Result: A visitor finds a site like their own.
Scope page
A plain page separating design fee, supervision visits, planting contractor and upkeep contract.
Result: Visitors see four separate items and not one lump price.
Mature-garden photographs
Pictures of finished gardens revisited later, each marked with the age of the planting.
Result: The site shows what the planting becomes.
Phone-first build
Pages designed for a phone first, with images sized to load without delay.
Result: The site reads comfortably on the device most visitors use.
Brief form and callback
A short form for site type, size, location and stage, plus a callback option.
Result: Enquiries arrive with enough detail to prepare the first call.
How the result is measured
- Page load time
- Bounce rate
- Enquiries from the website
Recorded as a baseline before work starts, so every later report has an honest comparison.
Pages to build
Show the size, the type and the problem solved on every project.
- Project page with site facts
- Site area, type, role of the practice and the problem solved, so a developer sees the scale of the work.
- Mature work
- Photographs of gardens after a few seasons with the age stated, so the site shows what the plan becomes.
- How we work
- The stages from site visit to supervision, with drawings delivered at each, so the fee is understood.
- Site types we take
- A page listing villas, podiums, campuses and parks, with the kind of brief the practice prefers.
- Start a brief
- A short form asking for site type, size, stage and location, which feeds the record.
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 have no photographs of finished sites, and the site would show only plants.
- Nobody will update projects after launch, so the site would show old work.
- Clients have not agreed to be shown, and publishing their gardens could expose a private home.
Before you decide
Agree the work. Know how to judge it.
Website for garden design practices: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the pages that support a buying decision and the actions visitors must complete. Keep examples of failed forms, unclear product information, and questions your team answers repeatedly.
Make the scope clear
Agree the page list, content ownership, integrations, and who controls the domain and hosting. Include redirects and existing search traffic in a redesign brief, before changing addresses.
Check the work in use
Complete a real enquiry journey on a phone and a laptop. Check that the confirmation appears, the enquiry reaches the right person, and tracking records the action once.
Know when to change course
If visitors can enquire but the team does not follow up, start with the sales handover. A larger website will not resolve that delay.
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.
- Login to the domain and hosting
- The site moves only when someone with authority can change the domain settings. Bring the registrar and hosting logins, or the name of the person who holds them, and the email address the domain was registered with. If they are lost, recovery comes first and the launch date depends on it.
- A shortlist of projects with clearances
- Each project on the site needs the client's agreement to be shown. A message from the client is acceptable. Projects without clearance are described by type only, and the site starts with fewer named gardens than you hoped.
- Photographs of gardens at a few years
- Mature planting is what a visitor trusts. Bring the original files, not messaging copies, with a line on which garden and which year each belongs to. If only handover photographs are available, the project pages carry a note about their age and we arrange a visit before launch.
- Your scope of work in your own words
- Say what the practice does at concept, detail, supervision and upkeep, and what it leaves to others, such as the nursery supply or the irrigation contractor. A page of notes is enough. Without it, the scope page repeats generic wording and the same confusion over three bills returns.
- A decision on who answers the form
- Someone must read every brief that arrives from the site and reply, including the ones sent late at night or from an architect's office. Name that person and a substitute, and say which of you replies to architects. If the form lands in an unattended inbox, the best-looking site will lose briefs to slow replies.
How it works
How the website 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
Read the site as an architect would
We open your current site on a phone and on a laptop, as a developer's team or an architect would after an introduction, and we try the form and the phone number as a stranger. You tell us what you wish they saw. We note which projects are hard to find, which pages carry no scope of work and where a visitor would leave.
- 2
Agree which projects to show
From your project list, you choose the gardens that belong on the site and mark the ones that cannot be named, including any that a developer's contract keeps private. We group them by site type. The choice is yours, since only you know which clients agreed, which gardens have matured and which show the work you want next.
- 3
Sketch the pages from site type to scope
We draw the sitemap: a page per site type, a scope page that separates design, supervision and upkeep, a page for architects and developers, and a short page on how a first visit works. You review the sketch before any page is built. Changes at this stage cost nothing, and changes after the build cost a good deal of time.
- 4
Write the scope page and project pages
We draft each project page with the plot, the problem, the planting and how the garden looks now, then the scope page that says what the practice does at each stage. You correct facts and approve every sentence. Photographs are matched to the text and labelled with the age of the planting.
- 5
Build the brief form, test it on phones
We design the enquiry form with the questions your intake needs, a callback option and a place to attach a plot photograph or a drawing. You and your coordinator fill it in as a client would, and we check that the answers land in the brief record with the source filled in and the attachment opening on a phone. The pages are tested on small screens first.
- 6
Compare enquiries with the old site
At the start we record the enquiries the old site brought and the share that reached a visit, with the pages each visitor opened before writing. After launch we compare, page by page, and look at which project pages were opened before an enquiry. You decide which pages to deepen, and what to add.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales process design, at stage 1, prospecting and lead generation. The audit comes before it, and sales management keeps it running.
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 · you are here
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3
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.
Can the practice keep its old site, or must it be rebuilt?
Which projects should go on the site?
Who owns the site and its content?
Which projects should go on the site?
Will the new site replace the one we have now?
Who owns the site and what happens if we part ways?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for landscape architects
Related work to consider.
Closest to this: search and visibility
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.