Services
A price tells a customer how much. A proposal, a contract and an invoice also have to say what: the milestones, what the customer receives, how long it takes and when they pay. Services is where you write that down once, per service you sell, so nobody retypes it for every lead.
Services live under Configuration → Services in the sidebar.
What a service holds
Section titled “What a service holds”Milestones and tasks — the stages of the work, in order. A milestone is either broken into tasks, each with a duration, or a single phase with a duration of its own. Durations add up per unit and are never converted: three days and two hours stays “3 days · 2 hours”.
Deliverables — what the customer receives. For a “Website design only” service that might be: UX/UI design, components library, sitemap, 5 pages, mobile version, Figma file, guidelines. Deliverables are the list a proposal and a contract spell out. A service without any falls back to listing its milestones’ tasks.
Price shares — optional, per milestone. They split the service’s price across its milestones, so a proposal can show “UX/UI design — €1,400, Handoff — €600”. Milestones left blank split whatever the others leave; with none set, the split is even.
Payment schedule — optional. How the price is paid: a deposit on signing, a payment after a given milestone, the balance on completion. The percentages must add up to exactly 100%. 50 / 50 sets up the most common schedule in one click.
Variables — a service name, completion date and feedback days that fill the
matching {{project_name}}, {{completion_date}} and {{feedback_days}}
fields in a document. Blank leaves the document’s own value alone.
Prices come from your pricing rules
Section titled “Prices come from your pricing rules”A service never sets the price. The lead’s total is always what your pricing rules produced — the same figure the customer saw in the widget and in the estimate email. Shares and schedules only split that total, and every split is rounded so the amounts in a document add up to it exactly.
Linking services to answers
Section titled “Linking services to answers”In Pricing Rules, each rule can include services. When the rule fires for a visitor’s answers, the lead carries those services:
Service type is Website design only → + €2,000, includes Website design only
A lead records which services it matched and how much of its total each one carries. You can see and change that on the lead — see Leads.
What gets filled in
Section titled “What gets filled in”When you create a document from a lead that has services:
| Document | Filled in from the lead’s services |
|---|---|
| Proposal | Process (milestones with durations), Timeline, the deliverables list, a priced breakdown above the total, and the payment cards. |
| Contract | Deliverables, Timeline, the Fees rows, and the deposit and balance. If the lead already has a Proposal, its deliverables list wins — it is what the customer already saw. |
| Invoice | One priced line per service (or per milestone, for a single service), adding up to the total due, and the paid / balance row from the schedule. |
Everything is copied once, when the document is created. Editing a service later does not change documents that already exist.
A lead without services still works: Proposals fall back to the template’s own rule groups, and invoices to a single line for the total.
Removing a service
Section titled “Removing a service”Archive takes a service out of the library and out of the pickers. Leads that already matched it keep it, and documents can still be created from them, so nothing already quoted loses its scope. An archived service stops being brought in by pricing rules.