Practical CRM setup for a solo landscaper

How we work: This guide uses current public documentation and does not claim hands-on testing unless stated. Some links may later become affiliate links, at no added cost to you. Rankings are independent of commissions.

The smallest useful CRM for a solo landscaper has three linked records—client, property, and opportunity—and one operating rule: every open opportunity has a next action with a due date. Start there. A complicated automation cannot rescue a list that does not show who needs a reply today.

This is a desk-researched setup guide, not a product test. We checked the linked Jobber, Yardbook, and National Association of Landscape Professionals documentation on August 8, 2026. The field list, pipeline, and review routine below are a vendor-neutral operating design. They are not claims that we ran a landscaping company or measured a sales lift.

What should a solo landscaper build first?

Build the CRM in the order below. This ranking puts record quality before automation because reminders are only useful when they point to the right customer, property, and decision.

This setup is narrower than our landscaping CRM software comparison. Use that guide to choose a product. Use this one to configure the process after choosing it.

Which CRM records and fields are actually necessary?

Do not make one contact record carry every fact. Jobber’s current data model illustrates the useful separation: requests, quotes, jobs, and invoices attach to a client, while properties are the physical work locations belonging to that client. Its property documentation allows one client to have multiple properties. Yardbook’s customer-management documentation also covers customers with multiple properties.

The following is a practical minimum field dictionary. “Required at” means the point at which the record cannot move forward without the field; it does not mean every intake form must ask every question.

Store an estimated lawn area, budget, or desired start date only when it changes qualification or estimating. A prospect’s rough area is not a substitute for a field measurement. Avoid copying the same gate code into client notes, property notes, a quote, and a task; duplicates become contradictory. Keep sensitive access information only where it is needed, restrict who can see it, and do not expose it in client-facing templates.

Yardbook calls custom fields “Extension Columns” and, in the documentation checked August 8, 2026, allows them on customer or property objects. The published limit is 10 text, 5 number, and 5 yes/no fields per object. That is enough for a lean setup, but it is also a reason to define fields before creating them.

What six pipeline stages keep sales work visible?

Use a stage only when it changes the next action. “Interested,” “warm,” and “talked to” may describe a feeling, but they do not tell a solo owner what to do.

Close non-active opportunities into one of three outcomes:

• Not a fit: outside the service area, service not offered, timing impossible, or another written qualification rule failed.
• Lost: the prospect made a decision and did not buy. Record the reason only when it is known; “unknown” is more honest than a guess.
• Nurture: the prospect explicitly wants a later conversation. A nurture record needs a real future date, not an indefinite parking lot.

Jobber’s current request statuses are product-specific, so they do not map one-for-one to this pipeline. Its documentation does support the underlying flow: requests can be created by customers or internally, move to an assessment, and convert to a quote or job. Configure the nearest equivalent in the chosen system and preserve the exit rules.

How should calls, forms, email, and social messages enter one queue?

Every inquiry needs the same minimum capture, regardless of channel:

1. identify the person and service property;
2. record at least one valid reply channel and the relevant permission;
3. summarize the requested service in plain language;
4. record the actual source rather than defaulting everything to “website”;
5. set the stage to New inquiry; and
6. create the next action and due date before leaving the record.

A web form can create the record directly. Jobber’s request documentation, checked August 8, 2026, says forms can collect contact details, job information, images, measurements, and lead source. It also allows staff to create the same type of request for phone, email, or in-person inquiries. The important design is not the form builder; it is that every channel reaches the same review queue.

For a solo operator answering calls between jobs, use a short internal intake form or saved template rather than free-form notes. Do not ask the prospect to complete an estimating questionnaire before confirming that the property and service fit. Collect the smallest amount needed for the next decision, then add detail during qualification or assessment.

If an answering service or AI receptionist creates records, test the handoff with the safeguards in our AI phone answering guide. A transcript is not a qualified opportunity until the address, requested service, contact method, and next action are correct.

When should information be a field, tag, or note?

Use a field when the value must be complete, filtered, handed to another workflow, or reported consistently. Use a tag for optional grouping. Use a note for context that does not belong in a controlled list.

Examples:

• Lead source, pipeline stage, and next-action date are fields.
• service:mowing, service:irrigation, or zone:north can be tags.
• “Customer asked whether the maple can remain untouched during cleanup” is a dated note tied to the relevant property or opportunity.

Keep the tag vocabulary short. Jobber’s documentation says tags can filter and segment clients but do not appear in its mobile app. Yardbook’s Tag Manager supports filtering and bulk changes. Those details show why a tag should not carry a safety-critical instruction or be assumed visible in every field view.

Do not use a single “VIP” tag to encode payment history, property access, service level, and communication style. The meaning cannot be audited. If a value changes what work is promised, give it a named field or attach it to the accepted scope.

What should happen every day?

The daily habit is small: update the opportunity immediately after each meaningful interaction. Record what changed, move the stage only when its exit condition is met, and replace the completed action with the next one.

At the start of the workday, filter for:

• next actions due or overdue;
• New inquiry records with no acknowledgment;
• assessments completed but still sitting in Assessment booked;
• estimates due but not sent; and
• accepted work that has not reached the schedule.

At the end of the workday, check phone, email, web, and social inboxes for inquiries that never became records. This is a reconciliation step, not a second pipeline.

What is the 25-minute weekly CRM maintenance routine?

Block one 25-minute review at the same time each week. The duration is a starting operating policy, not a measured industry benchmark. If the review regularly takes longer, fix the intake or update step that creates the cleanup.

Minutes 0–5: resolve identity and ownership errors

Merge or flag duplicate people and properties using the product’s supported process. Check that each opportunity belongs to the correct service address. Be cautious with destructive cleanup: Jobber’s current help page says client profiles cannot be merged, and its property page warns that deleting a property also deletes associated quotes and jobs. Archive when retention is appropriate; do not use deletion as routine tidying.

Minutes 5–10: clear the action exceptions

Filter open opportunities missing a next action or due date. Fix every one. Then work through overdue actions from oldest to newest. A stale record must receive a new agreed action, close with a known outcome, or move to Nurture with a real future date.

Minutes 10–15: inspect estimates and handoffs

Check that every sent estimate has a follow-up date. Check that every Won opportunity became scheduled work with the accepted scope, correct property, billing contact, and promised timing. The sales pipeline should not become a shadow schedule.

Minutes 15–20: close dead work honestly

Review opportunities with no recent activity. Do not leave them open to make the pipeline look larger. Use Lost, Not a fit, or Nurture, and record a reason only when the prospect supplied one or an explicit qualification rule applied.

Minutes 20–25: review one week of evidence

Count new inquiries, estimates sent, wins, and closed outcomes by source. Also count open opportunities missing a next action; the target for that control is zero. Do not copy a close-rate benchmark from another company. Build a baseline from the company’s own consistent stages and definitions.

NALP’s current CRM reporting supports this emphasis on process. Landscape companies interviewed for its guide described using tasks for follow-ups, tracking lead sources, and connecting lead, estimate, and invoice steps. NALP’s sales-process example also stresses mapping who responds, qualifies, follows up, and schedules the next meeting. Those are operating examples, not proof that another company’s response target or close rate will transfer to a solo business.

How can the setup be tested without risking customer data?

We did not test vendor accounts for this article. Before importing live customers, create synthetic records that exercise the model:

1. one homeowner with one property and one mowing inquiry;
2. one property manager with two service addresses;
3. one person requesting two services that should close separately;
4. one duplicate inquiry from a second channel;
5. one property outside the service area;
6. one estimate that moves to Won and becomes a scheduled job;
7. one declined estimate with an unknown reason; and
8. one Nurture opportunity with a future action.

Confirm that filters find missing and overdue actions, one client’s properties stay separate, a won scope reaches the schedule, and closed work disappears from the active queue without losing history. Export the required records and open the files outside the CRM. If the system cannot return usable client, property, opportunity, note, quote, and outcome data, document that limitation before relying on it.

Our software stack audit template helps identify the source of truth and export owner before several tools begin editing the same customer data. If cost is the constraint, compare the available starting points in the free landscaping software guide instead of building the process around a subscription the business may not keep.

What is the final setup recommendation?

Start with the three-record model, the six active stages, and the next-action rule. Run it manually until one weekly review can explain every open opportunity. Add tags only for useful segments, and add automation only after the manual trigger and stop condition are stable.

The CRM is working when the owner can answer four questions without searching texts, email, and memory: Who asked for work? At which property? What decision is pending? What happens next, and when? Everything else is optional until it improves one of those answers.