Landscapt (CRM)

Estimates & the Budget Engine

How an estimate is built, how its numbers are actually calculated, and how it becomes a job.

Creating an estimate

On the Estimates list, Stage, Sales Rep and Service are multi-select checklists (Sales Rep also offers Unassigned; Stage includes Converted) and Client is a free-form search. Filters stack: each keeps its own value and an estimate must match all of them. The header counts what is showing (“X of N estimates” while filtered). The Won / Lost Reason column shows the reason given when an estimate was closed, and the estimate's header carries a “Won reason” or “Lost reason” badge.

  1. Go to CRM → Estimates → + New Estimate.
  2. Pick a client. Leads are labeled “(lead)” in the picker so you can tell them apart from active clients at a glance; inactive or cancelled clients don’t show up at all.
  3. Set the estimate date and a valid-until date — it defaults to 30 days out, but can be pushed further for a bid that needs more runway. The proposal page is honored through the end of that day (in your company’s time zone); see “Valid until” under the proposal link below.
  4. Assign a sales rep and, if needed, a Sale Type (new sale or renewal) — it decides which commission rate applies and flows through to the job and invoice.

From there you’re in the estimate detail view, where line items, direct costs, and the summary panel all live.

Estimate numbers count up on their own. To continue the numbering from another system, go to Settings → Accounting → Estimate Numbering, enter the number the next estimate should have and click Set number. It never goes below the highest estimate number already in use, existing estimates keep their numbers, and invoices are numbered separately.

Estimate Builder: drafting line-item text from a transcript

Tools → Estimate Builder is a small AI-assisted writing aid, separate from the estimate detail view itself. It takes a sales-visit transcript and turns it into draft line-item wording you copy into a real estimate — it does not create or touch any estimate record on its own.

  1. Upload a transcript file (.txt or .vtt) or paste transcript text directly. For a .vtt file, the tool automatically strips the WEBVTT header, speaker-id lines, and timestamp lines before showing you the cleaned text.
  2. Click Generate Proposal. The transcript is sent to an AI model that drafts professional, client-ready line-item descriptions — grouped by service type, with locations, quantities, and exclusions called out, and any ambiguous point (like whether weed killer was discussed) flagged inline for you to resolve.
  3. Click Copy to Clipboard and paste the wording into the appropriate line item on the actual estimate you’re building.
This is a text draft, not a finished estimate. The tool never sets pricing, never submits anything, and never creates or modifies an Estimate record — it only produces description text sitting in the browser tab until you manually copy it in. Always check scope, quantities, and pricing against what was actually measured/quoted before pasting it in, and resolve any clarification flags in the output first.

Stage vs. approval status

These are two separate fields on the estimate, and they get confused constantly because they both sound like “where is this at.” Stage tracks the sales process. Approval Status is a separate internal sign-off gate that sits on top of it.

StageWhat sets it
DraftDefault stage for a brand-new estimate. Still being built — line items and pricing are in flux. Drafts were never presented to a client, so Close Ratios and win-rate figures leave them out of both counts and amounts.
QuoteSet manually once the estimate is ready for internal review — the numbers are considered final pending sign-off.
SentSet when the estimate is actually delivered to the client (email, PDF, or the client portal). Blocked from actually going out if Approval Status is still Pending — see the callout below. The bulk Mark as Sent action on the estimates list skips any selected estimate whose approval is pending or denied, and says how many it skipped; open those and send from the estimate. A bulk stage change that is blocked for some estimates (for example one with active jobs or invoices) still applies to the rest and reports how many couldn’t be moved. Pipeline dashboards count Sent estimates as open pipeline alongside Draft and Quote.
AcceptedSet when the client accepts — in full or via a tiered/partial acceptance, whether you mark it in-app or the client accepts online through the proposal link. Once an estimate is Accepted, a Convert to Job button appears in its header; converting normally happens from here.
LostSet when the client declines — including a Decline in the client portal, which records the reason “Declined by client via portal” — or when an estimate is manually marked dead. Line items already marked “lost” individually (e.g. a tier the client unchecked when accepting) don’t count toward totals, and the Accepted Estimates by Service reports skip them. Lines still marked “draft” (not yet part of the quote — the proposal hides them too) are left out of totals, the PDF and the client portal the same way.
InvoicedSet once billing has started against the estimate (a deposit, milestone, or the full amount has been invoiced).

Approval Status runs on its own track: Not Required, Pending, Approved, or Rejected. It exists to hold an estimate back regardless of what stage says. An approval covers the total that was approved: if lines added afterwards push the total above it, Send and Copy link ask for approval again (clicking Send resubmits it), and the estimate can't go out until it is re-approved. On a Good / Better / Best estimate the approval covers the highest option (with its discount and tax), not the “starting at” total, because the client can accept any of them; once the client picks a tier, it’s that tier’s total.

Approval also holds back Accept, Convert to Job and Invoice. While an estimate needs approval and isn't approved — it's Pending or Rejected, it grew past the approved amount, or it was never submitted and your approval flow covers its amount — it can't be marked Accepted, converted to a job or invoiced. The buttons are greyed out with the reason on hover, and an amber bar under the header says what's needed. The client can't accept it either: the proposal link and portal tell them it's being reviewed. Someone who could approve it themselves (an admin, or the approver on every step still pending) can go ahead. To submit it, click Send as before.

The trap. An estimate can show stage “Sent” while its approval status is still “Pending.” Stage reflects where the estimate is in the sales workflow, not whether it’s cleared to actually go out — a pending approval blocks delivery even though the stage field already reads Sent. If a client says they never got an estimate you thought went out, check Approval Status first.

Manual vs. production-rate budgeting

Every service has a configured Budget Method (in service settings), and every estimate line item snapshots that method the moment the line is added:

  • Manual — budgeted hours are entered directly on the line, no formula involved.
  • Production Rate — budgeted hours are derived: hours = quantity ÷ the service’s sq ft per man-hour. A service added in Settings or imported from a CSV with a production rate is set to this method automatically; change it per service in the service’s own dialog.

One override applies regardless of method: if the line’s unit type is hr (hourly), the entered quantity is the hours — there’s nothing to derive.

If this split feels familiar, it’s deliberate. Manual is the Service Autopilot approach — a human estimates the hours a job will take. Production Rate is the Aspire approach — hours fall out of a measured area and a standardized rate for that service. The CRM supports both side by side, per service, so a shop migrating from either tool can keep working the way it already knows.

A worked example, start to finish

Say a “Mulch Installation” service is configured with Budget Method = Production Rate and a production rate of 1,000 sq ft per man-hour. A property’s Mulch Bed Sq Ft measurement is 8,000.

  1. Budgeted hours: 8,000 sq ft ÷ 1,000 sq ft/man-hour = 8 budgeted hours for one visit. With a single visit, total budgeted hours is also 8.
  2. Cost: the org’s breakeven (fully-burdened) labor rate is, say, $45.00/hr. Because the line’s Cost field is still at its never-set default of $0, it auto-fills the first time the line is added: 8 hrs × $45.00 = $360.00 total cost.
  3. Rate (price to the client): say the line is priced at $0.12/sq ft, quantity-based (calc type ×): 8,000 sq ft × $0.12 = $960.00 total.
  4. Margin: ($960.00 − $360.00) ÷ $960.00 = 37.5% gross margin — comfortably in the green band (30%+) on the line-item grid.
  5. Overhead: the $45.00/hr breakeven rate already includes overhead recovery and labor burden, so no overhead is added on this $360.00. Labor overhead and Labor Burden (or the flat overhead %) only apply to cost you entered yourself — a typed Cost, a labor rate set from the B.Hrs calculator, sub-items, equipment and Direct Costs. The estimate’s overhead nets against gross profit to give the net profit figure in the summary panel, and the Costs breakdown notes how much of the labor was costed at the breakeven rate.

Edit the Cost field directly at any point and that override sticks — the breakeven-rate auto-fill only ever applies while Cost is still exactly $0.

The B.Hrs cell has its own calculator popover for building that number up instead of guessing: enter Men and Hrs:Min to compose budgeted hours (e.g. 2 men for 2:30 = 5.0 hrs), or give it a target man-hour rate — defaulting to the org’s breakeven labor rate — and it solves for whichever of Cost or B.Hrs you leave it to fill in. Adjust Cost costs the line at exactly that man-hour rate: 2.00 hours at $67.14 is $134.28 of cost, even on a 12,000 sq ft line. The Cost cell stays blue and its tooltip shows the line’s rate; type a Cost to replace it, or type 0 to go back to the breakeven rate.

Why budget method is snapshotted per-line

It would be simpler for a line item to just read its service’s current Budget Method live, every time. The engine deliberately doesn’t do that: the method (and, for production-rate lines, the rate itself) is copied onto the line item at the moment it’s added, and stays there.

The reason is historical integrity. Say “Mulch Installation” is switched from Production Rate to Manual six months from now, or its production rate is retuned from 1,000 to 1,200 sq ft/man-hour after a crew turns out to be faster than assumed. Every estimate written before that change already has real budgeted-hours numbers baked into it — numbers a job may have been scheduled and costed against, or a client may have already accepted a price built on. If line items re-read the service live, changing one service setting would silently rewrite the economics of every past estimate that used it, with no record that anything changed. Snapshotting means an old estimate keeps meaning exactly what it meant when it was sent, and a service’s settings can be tuned going forward without touching history.

Complexity multiplier & Rate Matrix pricing

Two more inputs can override the plain manual/production-rate math above. Both are snapshotted onto the line item the moment it’s added or adjusted — same historical-integrity reasoning as budget method, above.

Complexity multiplier. Every line item has a Complexity popover (the icon next to the line’s notes button) set from 50% to 200%, defaulting to 100% (no adjustment). It scales the line’s Rate and Cost together, which is why it doesn’t move GM% — a harder job costs and prices proportionally more without silently changing margin. It also scales the effective hours used for cost, dashboards, and the total-hours column. Critically, the hours you see and edit on the line (“B.Hrs”) always stay the plain, unscaled number you typed or that production rate derived — complexity is applied fresh every time something re-reads the line, never baked back into the stored hours. That matters in practice: dial complexity up to 150%, then back down to 100%, and the line returns exactly to where it started instead of drifting.

Rate Matrix. A service can have banded pricing rows configured against one of a property’s custom fields (e.g. price breaks by Turf Sq Ft ranges). If the estimate has a value for the field a service’s matrix is keyed on, adding that service looks up the matching band and uses its rate, budgeted hours, and cost instead of the service’s flat production rate. The value is read from the property first (a built-in measurement such as Turf Sq Ft, or a custom field), then from the client, so an estimate with no property still prices from a client-level value. A line priced from a band is recorded as Manual budget method going forward, since its hours came from the matrix rather than a formula (a per-unit band on an area line is the exception and stays on the production rate). No value anywhere, or no matrix rows configured on the service, and the line falls through to the ordinary manual/production-rate behavior with nothing different. Like everything else here, the match is looked up once at add-time, not re-resolved later if the property’s field value or the matrix rows change.

Past the last band, the service’s overflow rule (“every Y over X adds $R”, set on the Rate Matrix tab) steps the price up from the last band instead of falling back to the flat rate. See Rate Matrix in the Services & Pricing guide.

Complexity and Rate Matrix are independent of each other and of budget method — a Rate Matrix line still gets its own Complexity multiplier on top of whatever the matched band set.

Reading the line-item grid

The GM% column color-codes each line’s gross margin, calculated from Rate, Cost, and Adjusted Rate:

  • Green — 30% or higher.
  • Gray — 10% up to 30%.
  • Red — below 10%.

Each line also has a Calc Type toggle between per-unit pricing (× — rate × qty × visits) and a fixed total ($ — the entered rate is the line’s total, regardless of quantity). A fixed line with several visits is the same work repeated: its price covers every visit, and its budgeted hours and auto-calculated cost both count every visit, so the margin isn’t overstated. Visits is a whole number, 1 or more; a value like 2.5 is rounded when you leave the cell, with a note.

A line's flat discount works the same way as the estimate-level one: it keeps the amount you entered. If the line’s total drops below it, only the total’s worth applies, and the rest comes back when the total goes up again.

An estimate-level flat discount keeps the amount you typed. If the subtotal is smaller than the discount, only the subtotal’s worth applies (a note under the field says so), and the rest comes back automatically when lines are added. On a Good / Better / Best estimate each option is discounted against its own subtotal.

Overhead on the estimate as a whole is either one flat percentage applied to total cost, or — when the org has configured any per-type overhead rate — broken out by cost type instead:

Cost typeOverhead setting usedWhere it comes from
LaborLabor Overhead + Labor BurdenLine items’ cost and sub-service sub-items, alongside any Direct Cost rows typed as Labor. Lines costed at your break-even rate get no overhead added — that rate already includes it.
Sub-ContractContract OverheadSubcontracted work entered as a Direct Cost.
Product/MaterialMaterials OverheadProduct sub-items on lines, and materials entered as a Direct Cost.
Asset/EquipmentEquipment OverheadEquipment on lines (per visit × the line’s visits), and equipment costs entered as a Direct Cost.
Service/OtherOther OverheadDirect Costs typed as Service or Other — there’s no dedicated bucket for “Service,” so it shares Other’s rate.

Both the breakeven labor rate and the per-cost-type overhead percentages are org-wide settings, not per-estimate — the breakeven rate is set from Equipt’s Job Costing bid-rate calculator (“Set as project rates”) or typed in Settings → Organization → Break-Even Labor Rate, and overhead percentages live in the org’s overhead settings.

No costs, no margin. If an estimate has revenue but no cost at all — typically a new account that hasn't set a breakeven rate yet, with no costs typed on the lines — the summary panel shows a “Set your breakeven rate” note and the margin and net profit percentages read “—” instead of a misleading 100%.

Service bundles and sub-items

A service bundle is a saved set of line items you can drop onto an estimate. Manage them under Settings → Estimates → Service Bundles. In the bundle editor, click + Add sub-item under any bundle item to attach a product or a subservice to it. Search finds your products (not maintenance parts) and your subservices; each sub-item has its own Visits (default 1 = charged once for the whole line; set it to the bundle item's visits to charge it on every visit), quantity (default 1) and rate, and a delete icon when you hover the row. Its total is Qty × Rate × Visits, and the amber warning appears if Visits is neither 1 nor the item's visits. The same On estimate and On invoice buttons as on an estimate line sit beside the sub-item's name, and you can type its unit Cost in the row (internal, never shown to the client); both come along when the bundle is applied. To rename a bundle sub-item or swap its product, delete it and add it again. When you apply the bundle to an estimate, its sub-items come with it, including when you pick it from Apply bundle… on an estimate that already exists.

The bundle editor has two tabs. Details holds Show when creating, the Estimate document and the line items. Display Settings holds the client-view toggles (visits, quantities, prices and so on) that are copied to the estimate when the bundle is used. Choosing an Estimate document links the bundle to one of your estimate-type documents: estimates built from it remember that document, and Send pre-selects it (otherwise your default estimate document is used).

  • Print or hide on the estimate. On an estimate line, the On estimate / Hidden button beside each sub-item's name toggles whether it is printed under the line on the client's PDF, the preview and the emailed copy. New sub-items print by default. On the PDF a printed sub-item shows its own amount on its row, while a hidden sub-item's amount is included in the line's total, and section and option subtotals include every priced sub-item, so they add up to the estimate total.
  • Print or fold into the service on the invoice. Beside it, the On invoice / Not on invoice button decides how the sub-item appears on the invoice once the estimate is converted to a job. By default (Not on invoice) its price stays inside the service's price and the invoice shows one service line. Turn on On invoice and, on one-time, waiting-list and recurring jobs, the invoice lists the sub-item as its own row (quantity × rate) under the service, and that amount comes out of the service row — the invoice total never changes. This applies to sub-services and materials alike, and to jobs converted after the setting was made (a job keeps the choice it was converted with). On a recurring job each visit's invoice lists the sub-item's per-visit share (its total ÷ the line's visits). Set the sub-item's Visits to the line's visits to charge it on every visit (a $10 sub-service on a 14-visit line: Visits 14, shown as $10 on each visit). Package jobs keep a single service line.
  • Names, descriptions and $0 lines. A line with a client-facing description prints just that description, so a cryptic service name stays internal. Turn on Service name with description in the estimate's client-view toggles (or the org default under Settings → Estimates → Client View) to print the name above the description on the PDF, the emailed estimate, the proposal page and the client portal. A line with no description always prints its name. A line priced entirely through its sub-items has a $0 own total, but it still prints even when "hide zero totals" is on, along with its printed sub-items. A sub-item's price is added on top of the line's own rate, so don't type the sub-item total into the line's rate too, or it counts twice.
  • On the job. When the estimate converts to a job, each service's sub-items copy to the job with their names and quantities only (no prices). The office sees them under the service on the job, and the crew sees them on the stop as the products to bring and the tasks to do. They don't bill and don't change inventory; the sub-item dollars are already inside the service price.
  • Equipment cost. A line can also carry internal equipment cost, which lowers its margin but is never shown to the client. Equipment is per visit: the quantity is what one visit uses, and the line’s equipment cost is that times the line’s visits (a $40 mower on a 6-visit line costs $240). On each equipment row the bold amount is the charge per visit (what the line price should cover); the cost and margin sit beside it in lighter text. See Equipment costs in the Services & Pricing guide.
  • Line notes box. The note icon on a line opens Estimate Desc, Job Note, Invoice Desc and Line Item tabs. For long quotes press Bigger at the top right of the box to widen it and make the editor taller; Smaller puts it back, and the browser remembers your choice.

Sub-items, equipment and pricing warnings on a line

Expand an estimate line to add sub-items with + Add Product / Service. In the dialog, choose Product to pick from your product catalog or Subservice to pick from your service catalog (or type a custom name). Picking a catalog item fills in the name, rate and cost, and you can still change them. For a subservice the rate is the service's default rate and the cost is its default budgeted cost.

  • Sub-items are added on top of the line's own Rate. A sub-item has its own Visits (default 1 = charged once for the whole line; set it to the line's visits to charge it on every visit), and its total is Qty × Rate × Visits. You can edit Visits, Qty, Rate and Cost right in the grid; the pencil opens the full form, which also has the Print on Estimate and Print on Invoice checkboxes (the same two settings as the On estimate and On invoice buttons beside the name). Use 1 or the line's visits: any other number (say 13 on a 14-visit line) shows an amber warning, because a sub-item can't be limited to some visits — its price is spread across all of them. The line's TP, T.Cost and GM% include its sub-items, and so do the estimate totals, the Invoice button and the Costs breakdown on the right (sub-services under Labor / Line Items, products under Product/Materials, which also decides which overhead they get). If you price a line as one lump sum in Rate and also add sub-items that make up the same work, the work is counted twice. Either put the full price in Rate and hide the sub-items, or leave Rate to cover only what the sub-items don't.
  • Equipment is never billed. Its charge only counts toward margin, so the line's Rate has to cover it. Example: 40 labor hours at $50 ($2,000, a sub-item), 5 dump fees at $60 ($300, a sub-item) and $510 of equipment charge gives $2,810 when the line Rate is $510.
  • Where a line's cost comes from. When Budgeted Hours are set and Cost is left blank, the Cost shows in blue: budgeted hours times your organization’s breakeven (fully-burdened) labor rate, or the line’s own rate if you set one with the B.Hrs calculator. Typing a number in Cost replaces it. A sub-service's own cost is separate, so a labor sub-item with a $0 cost doesn't double the line's labor cost.

Under an expanded line, an amber pricing warning appears when something usually means a mistake. Warnings never block saving.

  • The line's own price is less than the equipment charge on it.
  • An hourly catalog subservice is priced below your breakeven labor rate.
  • The same catalog product or service appears more than once under the line.
  • The line's costs are higher than its price (a negative margin).

Packages on an estimate

Use Add Package (next to Add Item) to quote a package program such as a 5-Step Fertilization & Weed Control plan. It adds a section header named after the package and one line per package service, in package order. Each line keeps the package’s visit count and per-visit price (the package’s own rate, or the service’s default if the package sets none). Quantity, tier, discounts and the estimate totals work exactly as they do on any other line. The package’s Description on Estimate, set in Settings → Packages, becomes the package’s wording on the proposal, and you can edit it on the estimate by clicking the description box under the package header.

If a package service has a Rate Matrix keyed off a property field (such as Turf Sq. Ft.) and the estimate’s property has a value for it, the matching band prices that visit instead of the package’s flat price; the visit's quantity is the client's measurement, and if there is none the package's own price is kept. A package step's price is per visit and is never multiplied by the client's square footage. To copy the first visit’s Qty, Rate, B.Hr, Cost or Adj Rate down to every other visit, use the copy buttons on the package header. Deleting the package header asks for confirmation, then deletes all of its visits, including any hidden by the status tab. A line you add after a package is its own line, priced and accepted separately, not part of the package. Adding the same package a second time is refused.

Each package ends with a Package subtotal row for its visits. To skip a step, set that visit’s status to Draft; Draft and Lost visits are left out of the subtotal, the estimate total and the proposal. Package visits are indented under the header.

Bulk actions. Tick lines in the grid (the header checkbox selects every line, not section headers) and a bar appears above it with Change Status, Rate Increase and Delete. Delete asks for confirmation first. The actions apply only to ticked lines that are showing on the current status tab (switching tabs clears the ticks), and lines already converted to a job are skipped with a note saying how many.

Lines already on a job are locked. Once a line has been converted to a job its Status, Visits, Qty, Calc, Rate, Adj Rate, discount, complexity and sub-items can't be changed on the estimate, and the line can't be deleted — hover a locked cell to see “Already converted to a job — change it on the job”. Budgeted hours, cost, equipment and notes stay editable. A converted line also can't be moved to Lost or Draft (the job would keep billing it while the estimate stopped counting it), and its sub-items can't be added, changed or removed. Once any line is on a job the estimate's own Discount and Tax Rate are locked too: changing them would re-split the price between jobs already converted and ones still to come, so the jobs would add up to neither price. Change the price on the job instead. Copying values down a package skips its converted visits. A +$ rate increase raises each line's total by that amount per visit, whatever its unit; on a per-unit line too small to carry the amount in whole cents, use a percentage instead.

What the client sees

  • A package shows as one main line — name, wording and total — with one checkbox. A package is all or nothing: the client accepts the whole package or none of it, whatever they tick, and the server enforces it.
  • The Package visits toggle in the estimate’s “What the client sees” settings (off by default) lists each visit under the main line as plain rows. Leave it off to show only the name, wording and total. It applies to the proposal page, the client portal, the PDF and the [estimategrid] table in emails.
  • Packages added before the toggle existed, or whose section header was removed, print as an ordinary section.

Converting

Converting an accepted package creates a Package job, not a plain job. See Jobs & Packages for the details. Package lines convert one package at a time, and never in the same pass as ordinary lines; the convert window offers a button per package. Duplicating an estimate keeps the package tags. The convert window lists each step's planned visit date: if the package's dates are already in the past the Program Start Date defaults to today, and a package with no dated steps can't be converted until its steps have dates. A package service that includes several visits becomes a single step with one visit on the job, billed at that line's full price when the visit is completed.

Where zone measurements come from

Production-rate lines need a quantity to divide by the service’s rate — that quantity usually comes from a property’s zone measurements: Turf Sq Ft, Mulch Bed Sq Ft, Gross Sq Ft, Parking Lot / Hardscape Sq Ft, Linear Ft Perimeter/Edging, Yards of Mulch.

These are kept on the client. Fill them in with More → Aerial Measurement on the client (trace the lawn and beds on a satellite map), or type them on the Edit Client dialog’s Custom Fields tab. If a production-rate line is coming out to 0 budgeted hours, check that the relevant measurement is actually filled in on the client’s Details tab.

Taking a deposit on acceptance

Set Deposit Required on the estimate header and the client is asked for it as part of accepting the proposal, before the acceptance is recorded. A deposit is never more than what the client is accepting: on a Good/Better/Best proposal it is capped at the package they picked (the figure on the page is exactly what the card is charged), and if they untick lines so the accepted total comes in below the deposit, it is capped at the accepted total rather than blocking acceptance.

  • Pay by card charges the deposit through Stripe there and then. It appears once your organisation has finished Stripe Connect setup; the amount always comes from the estimate, so the client can’t change what they’re charged. Your card processing fee applies on the same terms as an invoice payment (only above your threshold), and the client sees the split — deposit, fee, total — before confirming. They are credited the deposit; the fee is yours.
  • Pay by bank transfer (ACH) appears if you have ACH turned on. No processing fee. A bank debit takes a few business days to clear, and the proposal is accepted straight away rather than waiting on it — see below.
  • The manual methods (check, cash, ACH, credit card, other) do not charge anything. They only record that the client says they’re sending it: the estimate shows an amber “Client says they’ll pay $X by check” badge — never the green Collected badge, which is only for money actually received. A promise never counts as a deposit anywhere, so the client can still pay online later. Record it as a normal payment when it lands.
  • Skip for now accepts the proposal with no deposit at all. A deposit never blocks acceptance. But the deposit is still shown as due: on the client’s accepted proposal page (with Pay by card / bank transfer buttons when online payment is set up) and on their client-portal Estimates page. You and the sales rep get an Accepted without deposit notification and email so someone follows up.

Accepting in the client portal works the same way: the signing dialog says a deposit is due, accepting doesn’t wait for it, and the estimate then shows “Deposit due” with a Pay online link (the proposal link) when one has been sent. Staff are notified exactly as for a skipped deposit.

When a skipped deposit stops being due. A deposit nobody paid stays due on the proposal link and in the portal until one of these happens:

  • A deposit is paid (or a bank transfer for it is clearing).
  • The job is paid in full. Once the estimate’s own invoices (the estimate, the job or project converted from it, or a contract made from it) have been sent and none of them has a balance left, there is nothing to put a deposit down on, so the client is no longer asked for one. Draft invoices don’t count — they haven’t been billed yet.
  • You waive it. On an accepted estimate with an unpaid deposit, click Waive deposit under Deposit Required and optionally give a reason. The estimate then shows a grey “Deposit waived” badge with the date and who waived it (the reason is on hover), and the client’s proposal link and portal stop showing the deposit — including the “your payment failed” retry screen — and won’t take it. Nothing is charged or credited. Undo next to the badge makes it due again. Waiving needs the Edit estimates or Add/modify payments permission. Before a proposal is accepted there is nothing to waive — change Deposit Required instead.
  • The estimate is marked Lost.
A card deposit becomes a prepayment, not an invoice payment. It’s taken at acceptance, before any invoice for the work exists, so there is nothing to apply it to yet. It lands as a payment on the client with the full amount unapplied, and shows in the Prepayments figure on their record (not Credits — that line is for overpayments and goodwill credits). If you refund it before it’s used, the refund comes out of the unapplied amount and no invoice is touched.
A deposit is reserved for its estimate. It can only be applied to invoices for that estimate — the estimate itself, the job or project converted from it, or a contract made from it. It isn’t offered on the client’s other invoices, and an automatic card or bank charge on another invoice never spends it. The estimate shows a blue “$X reserved for this estimate” badge while it’s unused. If the estimate is then marked Lost with the deposit still unused, a red banner on the estimate prompts you to refund it (Accounting → Payments) or Release to general credit, after which it can pay any of the client’s invoices.

The deposit is applied for you when the invoice is issued. The moment an invoice for the estimate leaves Draft — you save it as sent, print it or email it — the estimate’s reserved deposit is applied to it, oldest deposit first, up to what the invoice owes. The balance drops (to zero if the deposit covers it, and the invoice is marked Paid) and the payment’s unapplied amount drops by the same figure. Nobody needs payment permissions for this to happen. It waits if a card or bank charge for the invoice is still processing or a payment on it is disputed.

  • A deposit larger than the first invoice keeps the rest reserved for the estimate’s next invoice, which takes it when that one is issued.
  • Other money the client holds (a prepayment, an overpayment, a deposit you released to general credit) is not applied automatically. The invoice shows it as “Credit available: $X”, with an Apply to this invoice button that uses the oldest money first. The PDF, the online pay page and the client portal show the same “Credit available” line, and an invoice that credit fully covers doesn’t get past-due reminders.
  • You can still split money differently by opening the payment and editing its allocation.
An invoice you email while it’s still a draft is issued as it goes out, so the PDF the client receives shows the deposit as Credit available and the balance drops right after. To send a PDF that already shows the deposit as paid, mark the invoice sent (or print it) first, then email it.
A bank transfer doesn’t hold up acceptance. ACH takes a few business days to clear, and the proposal is accepted the moment the client submits the debit — they aren’t left waiting and neither is the job. While it’s clearing the estimate shows an amber bank transfer pending badge next to Deposit Required: no payment exists on the client yet, because the money hasn’t actually arrived. When it clears it becomes a normal prepayment and the badge turns green.

If the deposit fails — a returned bank transfer (insufficient funds, closed account, a mistyped routing number) or a declined card — the proposal stays accepted. Only the money failed; nothing needs signing again. This is the same however the proposal was accepted — through the link, in the client portal, or marked accepted by your office. Four things happen:

  1. The estimate shows a red payment failed badge with the amount, the date, and the bank’s own reason on hover, and a Deposit failed entry is added to the client’s timeline. That reason is the useful part — “insufficient funds” means ask them to try again, “account closed” means pick up the phone.
  2. The client is emailed that their deposit didn’t go through, with the reason and a Pay deposit button back to their proposal link (unless their address has hard-bounced). The email is listed in the estimate’s email history.
  3. You’re notified — a Deposit failed bell notification and an email, to whoever already receives proposal-decision notifications, plus the estimate’s sales rep. Both can be turned off individually under Notification Preferences.
  4. The client’s original proposal link re-opens itself so they can pay it again. Re-visiting it shows a “your deposit didn’t go through” screen with the reason and the card / bank-transfer buttons, instead of the usual thank-you. They can’t change the amount, and there’s no Skip button this time — skipping is a choice made before accepting, and by now the deposit is owed.
The link closes again the moment a deposit is recorded, so it only ever allows one attempt at a time. This is worth knowing before you chase someone: they very likely can just pay it from the same link you already sent, and don’t need a new one. An accepted link never expires, so this holds however late the bank returns the debit.
Paid, but not accepted. The card is charged just before the acceptance is submitted. If the proposal expired, or you edited the estimate after sending it, in those few moments, the acceptance is refused but the deposit is real: it sits on the client as unapplied credit and you get a Deposit paid, not accepted bell notification (same recipients as proposal decisions, plus the sales rep). Re-send the proposal or refund the deposit.
Charged twice? If two deposit payments ever get through for the same estimate (for example the client paid in two browser tabs at once), the first is the estimate’s deposit and the second is not thrown away: it is added to the client’s account as ordinary general credit (not reserved for the estimate), noted on their timeline, and your admins get a Second deposit charge bell notification. Apply it to an invoice or refund it from Accounting → Payments.
If you change the deposit amount (or the card fee setting) while a client has a card payment half-started, their next attempt is for the new amount — the old pending payment is cancelled rather than reused, so they’re never charged the old figure.
Only the card and bank-transfer paths are real money. A client who picks “Credit Card” from the manual list has told you they paid by card somewhere else — nothing was charged here. The proposal page says so beneath those options whenever online payment is available.

What a new estimate starts with

  • Tax rate. A new estimate starts at the client’s default tax rate, or at no tax if the client is marked tax-exempt (Client is taxable unchecked). You can change it on the estimate.
  • Good / Better / Best. Before the client chooses a tier, the estimate total, tax and pipeline value use the lowest-priced tier (“starting at”). That comparison includes each tier’s priced sub-items, so a tier with large sub-items isn’t mistaken for the cheapest. The summary panel’s Costs breakdown counts the same tier only, not every option added together.
  • Photos. iPhone HEIC photos are accepted on an estimate’s Photos tab and converted to JPEG on upload, so they also show in the PDF and the emailed proposal.

Rate and probability limits

The estimate’s tax rate, overhead rate, and win probability are percentages limited to 0–100%. A value outside that range is clamped when you leave the field, so a typo like 825 can’t multiply through the totals. A Direct Cost row’s quantity and rate can’t be negative either.

Two people on one estimate. Saving a line, or the tax, overhead or discount in the summary panel, saves only what you changed, so it doesn’t put back something a colleague changed in the meantime.

Duplicating an estimate keeps its estimate-level discount, whether it is a percentage or a dollar amount. In the client portal, Hide $0 prices looks at the rate the line is actually priced at (its Adj Rate when one is set).

Converting an estimate to a job

Once an estimate is Accepted — whether you set the stage yourself or the client accepted online through the proposal link — a Convert to Job button appears in the estimate header. After a job has been created from the estimate, that same button reads View Job and jumps straight to it, so an estimate is never converted twice by accident.

  1. From the accepted estimate, click Convert to Job.
  2. Choose which line items to include — not every accepted line has to become part of the job. Lines that net out to $0 start unchecked so they don’t land on the job (and its invoice) as empty rows; tick them if you really want them. Lines the client declined (a tier or option they unchecked) and lines still marked Draft, which were never part of the quote, are not offered at all, and Draft lines are also left out when you create an invoice from the estimate.
  3. Pick a Job Type: One Time, Recurring, Project, or Waiting List. An estimate that already bills on its own converts only as a Project (the Job Type is locked and the window says why): one with a live invoice created from it (“This estimate has already been invoiced (#N)”), or one set to bill by milestones. Project jobs aren’t invoiced per visit and take over the estimate’s milestones when you link a project, so the client isn’t billed twice. Void the invoice first if you really want a regular job.
  4. Set the scheduled date (required for One Time; for Recurring it is an optional Start Date, since the Schedule drives the visits; use Waiting List when there is no date yet), assign a crew, and enter a Crew Size (men). The crew size is written onto the job and its first visit, so the Dispatch Board’s Men column is right from day one instead of reading 0.
  5. Confirm. The job is created and a “Job created” entry is logged on the client’s Activity timeline. The estimate’s photos and the files attached to it (a site plan, a signed scope) are copied onto the new job’s Files tab, marked “Transferred from estimate”, so the crew sees the site photos the estimator took. The originals stay on the estimate. If a copy fails you’re told, and the job is still created.
Discounts carry over. The job’s price is what the client actually agreed to pay: each included line’s own discount and its share of any estimate-level discount are applied to the job’s service pricing. A 10%-off estimate produces a job priced 10% off, not one priced at the undiscounted subtotal.
Invoicing straight from the estimate. Each invoice line gets a quantity and rate that multiply exactly to the estimate line’s total — for a per-unit line, quantity × visits units at the per-unit rate the total works out to (Adj Rate and complexity included); for a fixed line, or when that rate isn’t a whole number of cents, 1 × the line total. Editing anything on the invoice line then keeps its price. Each line’s priced sub-items are included in its invoice line (the same way Convert to Job folds them in), so the invoice bills the full amount the estimate totals, and on a Good / Better / Best estimate it bills the same tier the total is based on.
A multi-visit line becomes a per-visit price. An estimate line priced across several visits — 30 mows at $60 — is quoted to the client as the full $1,800, but the job stores $60 per visit, because that is what each completed visit invoices. The quantity and the number of visits are both divided back out, so quantity × rate × visits still equals the amount the client accepted, discounts included. If you are reconciling a converted job against its estimate, compare the estimate’s line total against rate × visits, not against the per-visit rate.
Snow jobs aren’t created this way — they’re created directly from Jobs → Add Job. Package jobs are created here when the estimate has a package on it (Add Package): the convert window locks Job Type to Package, takes the package’s lines one package per pass, and treats Scheduled Date as the program start.

Deleting an estimate

Open the estimate and click Delete (red, in the row of stage buttons), or tick estimates in the list and choose Actions > Delete Selected. You need the Edit Estimate permission (or Add Estimate, for an estimate you created and haven't sent yet). The estimate leaves your lists, its proposal link stops working, its follow-up sequences stop sending, any of its sequence messages waiting for approval are rejected, and any approval request for it leaves the approvers' queue; if it was made from a ticket, the ticket can be converted again. An estimate that has a job, invoice, contract, payment, project or change order made from it can't be deleted — cancel or delete those first, or mark the estimate Lost if you only want it out of your open pipeline. An estimate whose online deposit is still processing (a bank transfer takes a few business days) can't be deleted until the deposit clears or fails. If a deposit does arrive for an estimate that was already deleted, it is added to the client's account as ordinary credit.

Good to know

  • Package totals on the proposal. A package's printed total includes its visits' sub-items and line discounts, so it matches the estimate total.
  • Client-view toggles. Picking an Estimate Document or applying a bundle only asks whether to replace the client-view toggles when someone actually changed them on this estimate.
  • Estimate emails. Client documents used as the Estimate Email or Confirmation Email offer the estimate merge tags and a “View proposal” button link. If the confirmation document linked to an estimate document is deleted, the picker says so; until you choose another, the company's Accepted Email (or the built-in one) is sent.

More in Landscapt (CRM)

Clients, Properties & Leads
Client accounts, commercial hierarchies, service properties, and the activity timeline that ties it all together.
Jobs & Packages
The six job types, how a job's status differs from a visit's status, and how a Package template turns into a billed job.
Services & Pricing
The service catalog, bulk catalog price changes, and Price Adjustment runs — which prices seed new work and which ones actually bill.
The Dispatch Board
The daily scheduling screen crews and dispatchers live in — visits, crews, status, and how actual hours get calculated.
The Crew App
What a crew sees on their phone — the day's stops, clocking on and off, breaks, photos, and sending work back to the office.
Sales Meetings
Booking appointments per sales rep, the double-booking warning, and the split between a rep's direct reminder and the client-facing automation trigger.
The Waiting List
Jobs with a date range instead of a date, held for opportunistic scheduling — and how to actually get them dispatched.
Snow Jobs & Storm Dispatch
Storm events, priority dispatch, and the invoicing flow built specifically for snow.
Invoicing & Payments
How an invoice is born, how its status moves, and where the client's own PO number actually goes.
Contracts
Ongoing billing agreements — monthly amounts, seasonal overrides, sub-properties, and how signing and invoicing actually work.
Communication Automations
How sequences, triggers, and events work — and how Automations differ from Sales Campaigns.
Forms & Lead Capture
Building, publishing, and sharing public forms — and what happens to a submission once it lands.
Document & Email Templates
Building the reusable emails and text messages that go out with invoices, estimates, campaigns and automations — blocks, merge tags, buttons, previews and test sends.
Tickets
Support and service tickets — where they come from, how they're worked, and how they connect to the rest of a client's record.
Damage Cases
Tracking property damage and warranty claims tied to a job — what a case captures, how cost rolls up, and a real current limitation in how it connects to a client record.
Warranties
Tracking the warranties you give on walls, walkways, patios and renovations — when each starts and ends, how claims tie back to it, and expiry reminders.
Commissions
Paying sales reps a percentage of what they sell — plans and rules by service and sale type, how earnings are calculated, and locking a quarter into a statement.
Injury & Near-Miss Cases
Reporting injuries, illnesses and near misses from the field, following them up in the office, tracking self-paid costs, supervisor alerts, and the Accident Free Workdays KPI.
Job Photos
Field photo documentation, annotation, and before/after comparisons — attached to a job site, not a person.
Online Payments & Stripe
How a client actually pays an invoice online, how Stripe Connect keeps every org's money in their own account, and how the platform takes zero cut.
Browse all guides
© 2026 Landscapt. All rights reserved.