Deal desk approval process records: what a company holds and how to spot them

What are pricing and quote approval histories?

A deal desk approval history is the trail a company leaves each time a salesperson asks for something outside standard pricing: a larger discount, extended payment terms, a non-standard clause, a custom bundle. Each request carries a reason, a reviewer, a decision and, later, an outcome.

That sequence of ask, justification, review and result is rare in public data. It shows how a business weighs margin against win probability, which is exactly the kind of multi-step judgment that AI developers building agents want to study. For a fractional CFO, these records often sit close to the finance function, so they are easy to describe even when you never open a customer contract.

What does the record actually contain?

The useful unit is the approval thread, not the final invoice. A complete thread links several artifacts.

Outcome labels matter most. A thread that ends in a recorded win or loss is far more useful than a pile of undated quotes.

Where do these records live?

Most companies spread the trail across several systems, and the spread is a good sign.

• CRM opportunity records and approval objects, including the field history behind each stage change.
• A configure-price-quote tool or quoting module, where versions and approval rules are stored.
• Email and Slack or Teams threads in a deal desk channel, where the real debate usually happens.
• Finance or billing systems, which hold what was actually invoiced after the approval.
• A shared drive with pricing policies, discount matrices and board-level pricing decks.

A company that keeps approvals in a formal workflow tool for five or more years, and has kept the chat threads too, is a stronger candidate than one that approves discounts by text message. The company fit checker gives a preliminary, non-binding screen once you have the basics.

What rights and privacy questions come first?

Pricing histories look internal, but they are full of other people's information. Three questions decide whether they can be licensed at all.

1. Whose terms are these? Customer-specific pricing is often covered by confidentiality clauses in the customer contract. Where it is, the company needs consent or a redaction approach agreed before anything moves.
2. Who is named? Sales reps, approvers and customer contacts appear in threads. Employee notices and privacy policies matter, and de-identification and redaction rules are agreed with the company before any work begins.
3. Is any of it already encumbered? Records tied to a pending dispute or a legal hold need separate handling; see litigation hold: can records under a legal hold be licensed?.

You do not resolve any of this as a partner. You flag the questions to the sponsor; SourceX handles the rights review with the company.

How can a fractional CFO recognize a company with a deep trail?

You often learn the answers in a normal monthly review. Use this short screen, which we can call the ASK test: Approval workflow, Stored history, Known outcomes.

• Approval workflow: is there a written discount authority matrix, and do requests go through a tool rather than hallway conversations?
• Stored history: can the company still pull approval threads from at least three to five years ago, including from retired CRM or quoting tools?
• Known outcomes: does each thread link to a won or lost opportunity and, ideally, the invoice that followed?
• Breadth: does the company have 50+ full-time employees at peak (contractors excluded) and a sales team large enough that discount exceptions are a routine, weekly event?
• Sponsor: can you reach the CEO, CFO or owner directly?

Two or three yeses make a conversation worthwhile. The full baseline is on the who qualifies page.

How does this fit into a normal CFO engagement?

You do not need a special meeting. The topic comes up naturally when you are already in the numbers.

If the company is also considering how a one-time payment would be treated in forecasts, the scenario planning template helps frame the range of outcomes, and the audit considerations for a new license revenue stream covers what auditors tend to ask. For the timing of the conversation itself, see year-end tax planning meetings.

What should you say to the CEO or CFO?

Do not describe specific deals, customers or margins, and never ask the company to send you samples.

How does the introduction work?

1. You register, then send the sponsor your referral link or submit the company on the referral form with basic fit details only.
2. SourceX checks size, history, data breadth and rights with the sponsor.
3. The company lists the systems that hold approvals in a data inventory, which the data inventory builder can help structure.
4. Redaction rules, price and terms are settled before any buyer sees a record.
5. Buyers review the scope; once a company is deal-ready they typically respond within about two weeks.
6. If the deal closes, delivery follows an executed agreement and the company's authorization.

How are partner rewards handled?

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 cumulative per referred company. The reward is payable only after the buyer pays and SourceX receives its fee; a lead, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. The reward is a share of SourceX's fee and is never deducted from what the company receives. If you are a fractional CFO who takes engagement fees from the company, disclose the referral relationship and check your own professional and contractual rules first; read the program terms for details.

When are approval histories the wrong fit?

• Approvals live in personal email with no retention policy, or the CRM was replaced without an export.
• Most pricing is customer-specific under strict confidentiality clauses with no consent route.
• Exceptions are rare, so the volume of approval threads is thin.
• The same records were already licensed for AI training.
• Nobody can run an export or own the inventory.

Next step

Run the ASK test on one client this week. If it passes, register as a partner and make the introduction, or have the owner apply directly at sourcex.si/apply using your referral link.