Academy · Run your revenue loop · Lesson 5
Deliver the work: from a won order to a delivered project
Winning the deal is half the job; delivering it is the other half. This lesson covers how a won order becomes a tracked delivery project — planned, scored for health, watched by the client — so the customer never falls into the gap between sales and delivery.
The objective
Turn a signed order into delivered work — without leaving the CRM
Quote-to-cash got you a signed order. Now the job is to deliver it — and the most common way that goes wrong is simple: the deal closes in the CRM, and the work restarts in a totally separate project tool, where the client can't see progress and no one can tell whether the engagement is on track or over budget.
This lesson is the clean version: the won order becomes a delivery project on the same record, planned from a template, scored for health automatically, and watched by the client through a secure portal. It's the deal-to-delivery core of professional services automation, run on one system.
In this lesson
- What 'delivering' in a CRM means (and where PSA fits)
- How a won order becomes a delivery project
- Planning the work — tasks, checklists, templates
- How automatic health and the Risk Radar work
- Keeping the client in the loop with a portal
- How KudosCRM runs it — honestly
The definition
What does it mean to deliver inside a CRM?
Delivering inside a CRM means running the work you do after a deal is won — the project, its tasks, its budget, and the client's view of it — on the same customer record the deal closed on, instead of in a separate project tool. The won order becomes a delivery project, and sales context flows straight into delivery.
This is the heart of professional services automation (PSA): running a services business — winning the work, delivering the project, and billing for it — as one connected motion rather than three disconnected tools. The deal-to-delivery core is what KudosCRM does on one record; time-tracking, timesheets and resource management are the parts still on the roadmap.
The reason it matters: the hand-off from sales to delivery is where customers get dropped. A fresh project brief that loses the deal's context, a budget no one can see, a client left guessing — each gap erodes the relationship you just worked to win. Keeping delivery on the record closes the gap.
Why it matters
Three things good delivery always gets right
The tools vary, but the principles don't. Whether you run a 2-week onboarding or a 6-month implementation, the difference between delivery that builds the relationship and delivery that strains it comes down to these.
Keep delivery on the record
The moment sales and delivery split into two tools, context is lost — the contract, the scope, the history. When the delivery project is born from the order, on the same record, nobody re-keys and nothing falls into the gap.
Let health surface itself
A status someone updates on a Friday is a status you can't trust. When health is computed from real signals — overdue tasks, blocked work, schedule slip, budget — problems surface before the deadline, not after it.
Keep the client in the loop
Most delivery anxiety is just a client who can't see in. A read-only portal they can watch — progress, files, milestones — turns 'where are we?' into a link you send, not a meeting you schedule.
The process
The five steps of delivering the work
Your exact steps may vary, but most delivery flows follow this shape — and the goal is to make each hand-off automatic rather than a re-key into another tool.
Order → project
A won order becomes a delivery project in one click (or via a workflow), linked to the deal and company, with its budget seeded from the order total. Delivery starts from the agreed scope, not a fresh brief.
Plan the work
Lay the project out from a template (onboarding, implementation, launch) or add tasks with assignees, due dates and checklists — and flag the billing milestones that matter.
Run the board
Move the project across planning, in-progress, review, done and blocked; tasks roll up into a live progress bar, and the right work stays on top.
Watch health & budget
Health scores itself good, at-risk or off-track with a Risk Radar of reasons, and budget tracks against what you've invoiced — so a manager acts on a signal, not a surprise.
Show the client → bill
Share a secure, section-gated portal the client watches, and let a completed billing milestone raise a draft invoice — the clean hand-off into the billing stage.
How KudosCRM does it
Delivery, the honest version
In KudosCRM the whole motion runs on one record. A won order becomes a delivery project in one click, planned from a template, scored for health automatically, with budget tracked against what you've invoiced — and the client watches progress through a secure, read-only portal.
Two honest notes: project creation is one click or a workflow, not fully automatic for a brand-new workspace; and budget is tracked vs invoiced, not internal cost. Team timesheets, billable hours and a workload/capacity view are on the roadmap (shown with a “Soon” pill), not claimed as live.
What's actually built today
- Order/deal → delivery project in one click (or via a workflow)
- Project board — planning / in-progress / review / done / blocked
- Automatic health (good / at-risk / off-track) + a Risk Radar of reasons
- Budget vs invoiced — % invoiced, remaining & over-budget
- Project tasks — assignees, due dates, checklists & billing milestones
- Files — drag-drop, auto-categorized, versioned, signed downloads
- 3 built-in project templates (onboarding / implementation / launch)
- Members with roles — owner / editor / viewer / client
- A read-only client portal — password, expiry & section gating
- Role-based access across the team; bulk team invitations
On the roadmap (shown with a “Soon” pill, not claimed as live): team timesheets & billable hours, a workload / capacity view, cost-based budgets, fully-automatic project creation, an editable permission-matrix admin screen, and named teams / squads.
What happens next
From delivered work to a paid invoice
Deliver is Lesson 5 because it's where a signed order becomes real, delivered value. As the work progresses and billing milestones complete, the next question is the one Lesson 6 answers: how does delivered work turn into a sent — and paid — invoice? That's billing, the close of the revenue loop.
FAQ
Delivering the work, answered
Put the lesson to work
Turn a won order into a delivery project
Plan it from a template, let health score itself, and give the client a secure portal to watch — so delivery starts from the agreed scope and nobody falls into the gap between sales and delivery.