Home
/
Ressources
/
Blog
/
Ofelia Agentic
/
Deal desk process: how to orchestrate it end to end, without chasing teams
Blog article

Deal desk process: how to orchestrate it end to end, without chasing teams

A deal desk process takes a deal with exceptions from the request to the booked deal. Each exception, from the discount to the SLA, goes to the right person, who decides in time and on the record. It works when it runs end to end as one orchestrated process, with one complete request, every step in order and every decision traced. Run this way, more deals close in the quarter they were forecast, margin holds on non-standard deals, and the trail exists before Finance or an auditor asks for it.

In short

  • The request goes in once, complete: scope, price, terms, credit and the draft contract.
  • Off-policy items go to their owners in parallel, each with a deadline. Owners get a reminder, then the request escalates, and nothing is approved by default.
  • Agentic tasks prepare the groundwork, such as a check against margin floors or a recommendation on credit terms, and a person validates each result.
  • A customer redline reopens only the step it touches, and the booked deal matches the approved terms.

Why a deal desk run by hand costs on both sides

It is the last week of the quarter. A rep promises a 99.9% SLA and a higher liability cap to get the signature, and someone says yes in a Slack thread. Two weeks later, the customer’s redline moves the liability cap again, and nobody sends it back to Legal.

Most deals pile up exceptions like these: a discount above the rep’s limit, 60-day payment terms, a clause outside Legal’s playbook, an SLA Delivery never confirmed. Every company already has rules for them, from discount thresholds to a credit policy and a Legal playbook. The friction is in running those rules across five teams, three tools and two inboxes.

The deal desk feels it first. Requests arrive as a thread and a CRM record, rarely complete, so the team goes back to the rep for the margin, the deal history or the draft contract. Then it chases each approver by email, and chases them again a few days later. It answers “where is my deal?” all day without a clear view of who holds it. And before booking, it checks the quote, the billing schedule and the payment terms line by line, while every customer redline starts the loop over.

“On the finance side: we did do the quote, it’s clean, the products are there, the billing schedule, the payment terms. On Sales Administration’s side: the signature is right, no data is missing, the documents haven’t been altered. That whole process, by hand.” Deal desk team member, software company

The cost lands on both sides of the table. Too slow, and the deal slips out of the quarter, the forecast breaks and the rep turns coordinator. Too loose, and exceptions pass off the record. The same exception gets a yes on Monday and a no on Thursday, margin and cash terms leak, and the CFO finds them at month-end, already signed. The COO inherits a commitment Delivery never confirmed and pays for it at go-live or at renewal. Meanwhile the deal desk does all the chasing and still carries the name of the brake. The quote-to-cash pillar maps where these leaks sit across the whole movement, and bringing Legal and Finance in at qualification removes part of them upstream.

The perfect deal desk process flow, from request to booked deal

Every company draws its own thresholds and names its own approvers. The stages below fit any size or sector, and each one has an owner, a deadline and a trace. The approval workflow sits in the middle of them, but it is only one stage of the process.

  1. The request. The rep sends one package with the scope, price, terms, credit details and draft contract. The process checks that nothing is missing before anyone is asked anything.
  2. The policy check. The process checks each term against the policy you already have. Standard terms go straight through, and it flags every off-policy item with the rule it breaks.
  3. Approvals in parallel, by threshold. Each flagged item goes to its owner at the same time: the discount to sales leadership, payment terms and credit to Finance, clauses to Legal, the SLA to Delivery. Where the VP Sales approves discounts up to a threshold and Finance stays out of the loop, the routing simply follows that rule.
  4. Deadlines and escalation. Each owner gets a deadline. The process reminds them, then escalates to their backup or their manager, and nothing is approved by default.
  5. The quote and contract, on approved terms only. The process generates them from what was approved, so no unapproved term reaches the customer.
  6. Customer redlines and signature. A redline is a new exception. It goes back to the owner of the term it touches, the liability cap to Legal or the payment terms to Finance, rather than to the whole chain. The process then follows up the signature in DocuSign or the e-signature tool you use.
  7. The booking check. The process checks the signed deal against the approved terms, from the quote to the billing schedule and the payment terms. Then the deal is booked, and those terms travel on to billing and onboarding.
1
Request
One package, checked for completeness. Owner: the rep
2
Policy check
Standard goes through, off-policy is flagged. Owner: the deal desk rules
3
Approvals in parallel
Each item to its owner, by threshold. Owners: Sales, Finance, Legal, Delivery
4
Deadlines
Remind, then escalate. Nothing approved by default
5
Quote and contract
Generated on approved terms only
6
Redlines and signature
Back to the term’s owner only, then signature followed up
7
Booking check
Signed terms match approved terms, then booked
The deal desk process flow: seven stages, each with an owner, a deadline and a trace.

The approvers change from one company to the next. What never changes is that each team needs its part of the request, a deadline and a record of what it decided.

TeamWhat it decidesWhat the process hands it
Sales leadershipPrice and discount, by threshold (for example under 20%, 20 to 40%, above 40%)The discount, the margin and the deal history, with a deadline
FinancePayment terms and creditThe terms, the customer’s credit data and a recommendation to validate
LegalClauses and the liability capOnly the clauses outside the playbook, and later the redlines that touch them
Delivery or OperationsSLA, scope and capacityThe commitment the rep wants to make, before it reaches the customer
Deal desk or RevOpsThe rules and the flow itselfA view of every request: who holds it, since when, and what is left
Who decides what in a deal desk process, and what the process hands each team.

To see these stages run in Slack on one deal, watch the four-minute Revenue Lifecycle film.

Run it as one process: in order, in parallel, on the record

Most deal desks already have the pieces: a policy, a list of approvers, a spreadsheet of open requests. What they lack is something that carries the deal from one step to the next. Today the deal desk does that by hand. Orchestrated, the process carries the deal itself. An orchestration layer starts each step when the previous one is done, sends each owner their part in Slack or Microsoft Teams with the context attached, follows up, and records every decision. People keep the decisions. The coordination stops being their job.

The request arrives complete

The rep fills the request once, from where they already work, and the process asks for what is missing before anything is routed. The deal desk no longer rebuilds a package from three threads, and each approver gets exactly what they need to answer.

Reminders and escalation are part of the process

A deadline without a follow-up is a wish. In an orchestrated process, the reminder and the escalation are steps, written once, so they happen on every deal without anyone sending them. An exception never passes because nobody answered, and a deal never sleeps in commit for three weeks because Legal’s inbox was full. When Legal’s due date passes, the forecast can flag the close date, instead of the slip surfacing at the end of the quarter.

Everyone sees who holds the deal, and since when

The deal desk manager sees every request, the step it is at and how long it has been there. The rep stops asking, the CRO knows which committed deals wait on another team, and a customer redline reopens one step instead of the whole chain. The deal desk stops being the switchboard and becomes the owner of the rules, stepping in where a person’s judgment is needed.

Where agentic tasks help, and where a person decides

Some steps need judgment, and others mostly need preparation. Agentic tasks take the preparation. One can analyse the deal against the pricing policy and margin floors, another can bring Finance a recommendation on credit and payment terms from the customer’s data. Each one sits at a fixed place in the process, and its result goes to a person who validates it before the deal moves on. Agents never decide the sequence and never approve an exception: the process sets the order, and people sign off. That is what human-in-the-loop means in a deal desk. AI speed, human control.

What your tools already cover, and what sits between them

Your tools each do part of this well. Slack or Teams carry the conversation. Your CRM, Salesforce or another, holds the record of the deal. A CPQ prices standard deals and produces clean quotes, a deal desk spreadsheet tracks the open requests, and DocuSign collects signatures. Every one of them stops where a handoff begins, though. None of them carries the deal from Finance to Legal to Delivery, holds each deadline, escalates, or reopens the right approval after a redline. That work sits between the tools, which is where an orchestration layer runs, leaving each tool to do what it already does. The quote-to-cash definition places this step in the wider movement.

A ten-point checklist before your next non-standard deal

Use it to check whether your deal desk can run end to end, or where it still relies on someone chasing.

1
Thresholds written down per term: discount, payment terms, clauses, SLA.
2
One owner and one backup per threshold.
3
One request package, defined once and checked for completeness.
4
Approvals in parallel, not in sequence.
5
A deadline on every step, with its reminder.
6
An escalation path written before the first deadline is missed.
7
A re-approval rule for customer redlines.
8
Agentic tasks at fixed steps, each result validated by a person.
9
Every decision recorded: who, when, under which rule.
10
A booking check against the approved terms, and three measures: days from request to decision, share of deals within policy, share of deals reaching Legal with less than a week to go.
Ten things a deal desk process needs before the next non-standard deal goes through it.

Each decision on the record is also what makes an audit trail exist before anyone asks for it.

“The deal desk teams we talk to rarely lack a process. They lack the time to run it, because they spend their days collecting answers the process should bring to them.” Thomas Carmona, Product Manager, Ofelia

How Ofelia Agentic orchestrates the deal desk, end to end

Ofelia Agentic is the governed execution layer for the revenue lifecycle, inside Slack and Microsoft Teams. It runs the deal desk process from request to booked deal, works with your CRM and any system you use, and leaves every decision to a person.

Ofelia answers and guides first. A rep asks in Slack or Teams: “Which approvals does a 25% discount with 60-day terms need?” or “Can I promise a 99.9% SLA on this contract?” A deal desk manager asks: “Who holds the Acme request, and since when?” Ofelia answers from your pricing policy, Legal’s playbook and your connected systems, and guides the person to the next step, with an action button to submit the request. The rep stops guessing the rule, and the deal desk stops answering the same question again and again.

The deal desk process itself needs more than answers, so Ofelia runs it as a workflow: the same steps on every non-standard deal, each owner receiving theirs with a deadline, and every decision traced. Take a non-standard deal, call it Acme. The rep launches the deal desk request from Slack. Ofelia checks that the package is complete and the terms against the policy, then sends the off-policy items to their owners at the same time. An agentic task brings Finance a recommendation on credit and payment terms, and Finance decides. Legal reviews only the clauses outside the playbook, and when its deadline passes, Ofelia reminds, then escalates. Nothing moves until the owners answer. Ofelia generates the quote on the approved terms, sends the customer’s redline back to Legal only, and follows up the signature. Before booking, it checks the signed deal against the approved terms, and Acme moves on to order, delivery and cash.

Watch one deal orchestrated from lead to renewal, in four minutes.

Ofelia generates the workflow from what you already have. RevOps or the deal desk manager hands over the approval policy, or describes it in plain language, and Ofelia proposes the model: steps, thresholds, owners and deadlines. The owner adapts it in the no-code Workflow Designer, tests it and publishes it into Slack or Teams, with no developer. A new threshold applies from the next request. IT keeps control of who can build and publish, of access and connections, and of the full audit trail, and everyone a deal needs can take part, CRM seat or not.

Run this way, approvals can take 40 to 60% less time, pricing compliance can reach 95% and more, and each rep can get 3 to 5 selling hours a week back. On pricing exceptions, the cycle can go from hours to minutes, with margin erosion on non-standard deals down 30 to 50%. Under the hood, Ofelia builds on Bonita BPM, which has run enterprise processes for more than 15 years at more than 130 enterprise customers.

The Revenue Lifecycle one-pager shows how Ofelia Agentic runs the whole revenue lifecycle. The operations and sales page shows how it fits your teams.

Say yes faster. Say no before it costs you. The right path is the fastest one.

Ready to orchestrate your Revenue Lifecycle?

Schedule a personalized demo and see how Ofelia can transform your operations.

Get a demo
Loic Barbaux
Senior Product Marketing Manager

Frequently asked questions
Short answers to the questions we hear most on this topic. Still curious? Our team is happy to talk.
What are the steps of a deal desk process?
A deal desk process runs in seven steps: one complete request, a check against the pricing and contract policy, approvals in parallel by threshold, a deadline and escalation for each approver, a quote on approved terms only, customer redlines sent back for re-approval, then signature and a booking check. Each step has an owner, a deadline and a record.
What happens when an approver misses a deadline in a deal desk process?
In an orchestrated deal desk process, the approver is reminded, then the request is escalated to their backup or their manager. Nothing is approved by default. The deal desk manager sees who holds the deal and since when, so a committed deal does not wait for weeks and no exception passes because nobody answered.
What happens when the customer redlines an approved term?
A customer redline is a new exception in the deal desk process. It goes back to the owner of the term it touches, the liability cap to Legal or the payment terms to Finance, not to the whole chain. Once it is re-approved, the contract is regenerated on the new terms and the signature is followed up.
Who owns the deal desk process?
RevOps or the deal desk manager owns the deal desk process: the thresholds, the owners, the deadlines and the escalation path. Each team owns its own decision, Finance on terms and credit, Legal on clauses, Delivery on SLAs. IT controls who can change the process, access to systems and the audit trail.