Delivery Pipeline全新
Selling is half the journey. The SellioCRM Delivery pipeline takes care of the other half: when a deal is won, a delivery project is created automatically for the account, linked to the deal, at the Handoff stage, and moves through Planning, Execution, Validation, Delivery, Acceptance and Closed. Inside it you register Deliverables, what must be delivered and accepted, with due date, owner and billable amount. The customer accepts in their own portal, with your logo, and answers a satisfaction survey. When a billable deliverable is accepted, or when the project reaches Acceptance with a contract value, the system creates a draft invoice for finance to review and send: nothing is charged on its own. Administrators also track margin, satisfaction and an analytics panel, and can ask the Assistant what is at risk. The module is optional and starts off; an administrator turns it on under Delivery in the side menu, and nothing changes for what already exists.
- Delivery project created automatically on win, one per opportunity, linked to the deal and the account
- Seven stages: Handoff, Planning, Execution, Validation, Delivery, Acceptance and Closed, on a Delivery projects board
- Deliverables with Pending, In progress, Submitted for approval, Accepted and Rejected statuses, due date and billable amount
- Customer acceptance portal by link, with your company logo, and a CSAT and NPS satisfaction survey at the end
- Draft invoice per accepted deliverable or per milestone at Acceptance, never charging twice and never charging on its own
在 Sellio 中免费，你只需为机器付费
The Delivery pipeline is part of the free SellioCRM, as long as your account's infrastructure usage always stays under US$ 20 a month. Only the Assistant's narrated summary is metered against your AI usage; alerts and analytics use no AI.
No won deal falls into a void
The project is born on its own at the win, at the Handoff stage, so delivery starts the very moment the sale ends.
Invoices at the right time, reviewed by people
Acceptance creates a draft, a milestone creates a draft, and finance decides when to send. What was already invoiced is never charged again.
The customer takes part in acceptance
The portal with your logo gives the customer a place to accept and rate, and gives you an attributable record of every acceptance.
Margin before the project closes
Logged costs and real hours show the margin while there is still time to correct, with an alert when it turns negative.
Scope with a memory
Every scope change becomes a new version. When the 'that was not agreed' conversation comes up, the history answers.
Billing on acceptance AND by milestone, combinable: at project Acceptance, the contract value invoice deducts what was already invoiced through deliverables
Delivery templates that seed the standard deliverables on win, matched by product, account segment or amount range
Versioned, immutable scope: every edit of scope, exclusions, assumptions and acceptance criteria creates a new version, and the history stays
Project margin from logged costs and real hours on the execution board, with a negative-margin alert, visible only to administrators
From win to handoff with nobody having to remember
When an opportunity is won, the delivery project is created for the account at the Handoff stage, linked to the source deal, with customer, manager, dates, progress and contract value. It is idempotent: one project per opportunity, never two. If a template matches the product, segment or amount, the standard deliverables are born with it.
Deliverables that turn into acceptance and invoices
Each deliverable has a status, a due date, who accepted it and when. Mark it billable and set the amount: when the customer accepts, the system creates a draft invoice for the account, at most one per deliverable. Finance reviews and sends. Revenue is recognized on acceptance, independent of invoicing, and the report shows recognized versus deferred per project.
The customer accepts in their own portal
On the Delivery pipeline screen, generate the Client acceptance link for a project and send it. The link is bound to that project and that email, with no password: the customer sees pending deliverables, accepts, and the acceptance is logged with author and date. After accepting everything, they answer the satisfaction survey, CSAT from 1 to 5 and NPS from 0 to 10, which the team follows per project and in the overall summary.
Execution, margin and what is at risk
Each project can open an execution board, with tasks, dependencies and time tracking, and the real hours feed the project cost. Administrators see the margin (contract value minus logged costs, with an alert when it goes negative), satisfaction and the analytics panel: active projects, late ones, average progress, recognized and deferred revenue, deliverable health. Ask the Assistant: what is at risk in delivery?
- 1
An administrator opens Delivery in the side menu and turns the module on.
- 2
When a deal is won, the delivery project is created at the Handoff stage, linked to the deal and the account; matching templates seed the deliverables.
- 3
The team registers or adjusts Deliverables, sets due dates, marks the billable ones and, if they want, opens the execution board.
- 4
Generate the Client acceptance link and send it; the customer accepts in the portal and answers the satisfaction survey.
- 5
Acceptances create draft invoices and recognize revenue; track margin, satisfaction and analytics on the Delivery pipeline screen.
Software implementation
A template per segment seeds kickoff, configuration, training and go-live. The customer accepts each phase in the portal, and each billable acceptance creates the draft invoice.
Milestone-based consulting project
Contract value on the project and deliverables with no amount. At Acceptance, a single invoice for the contract value, minus anything already invoiced.
Agency with recurring deliveries
Execution board with tasks and hours per project; the real margin per customer shows up before month end.
Post-sale with a survey
At the end of each delivery, the customer's CSAT and NPS feed the overall summary, and the Assistant flags projects with low satisfaction.
Does the system charge the customer on its own?
No. Accepting a billable deliverable and reaching the Acceptance milestone create DRAFT invoices for the account. Finance reviews and sends. And a deliverable creates at most one invoice.
How does the acceptance portal work?
You generate a link for the project on the Delivery pipeline screen and send it to the customer. The link is bound to the project and the email, with no password, and shows only that project. The acceptance is logged with author and date.
Can I bill per deliverable and per milestone at the same time?
Yes. At project Acceptance, the contract value invoice deducts what was already invoiced through deliverables, so nothing is charged twice.
Who sees the margin?
Whoever manages the organization's settings. Labor cost derived from hours also requires the time cost permission. It is your company's cost, never the operator's.
What happens if I turn the module off?
No new project is created on win and the pipeline automations stop. What already exists remains accessible like any other record.