# Recruiting firm acquisition meeting agenda | SourceX

Canonical: https://refer.sourcex.si/resources/recruiting-firm-acquisition-meeting-agenda
Last updated: 2026-11-05

Hold a 30-minute meeting in five blocks and give each block's question to the one person who can answer it. Block one fixes the deal dates; block two asks whether the owner can link original placement guarantee terms to the later decisions made under them; blocks three and four cover where those records live and who owns them; block five produces a recorded decision: introduce the authorized contact to SourceX now, revisit after a documented milestone, or stop. Nothing is exported or shown.

This agenda is part of the [recruiting firm acquisition guide for staffing ATS partners](/guides/moment-recruiting-firm-acquisition-staffing-ats-partners), which explains why placement guarantee decision records matter. Use this page for the meeting itself: the invite, the run sheet and the close.

## Setting up a meeting inside a live deal

Acquisitions make people careful, and they should. A meeting that feels like a side project will not get honest answers, so settle the logistics first.

- **Invite only people already inside the deal.** Ask the owner who is cleared to know about the acquisition before you send anything. The invite title can be neutral: "Records review, 30 minutes."
- **State the rules in the invite.** "Description only. No files, exports or screen shares." People relax when they know nothing will leave the room.
- **Choose the moment.** The best window is after the integration plan names the target systems but before the data migration scope is frozen. Earlier, nobody knows what will move; later, nobody wants to reopen it.
- **Chair and notes.** You chair and take notes in a plain table: block, answer, who gave it, open item. Ask the integration lead to keep time.
- **Parking lot.** Questions about the integration itself (field mapping, user licenses, cutover weekends) go on a list for the project team. This meeting is about the closed history.

If the decision-maker cannot join, run the first four blocks with the others and book ten minutes alone with them for the fifth. An absent owner has not agreed to anything.

## Who answers which block

| Role | What they know | Blocks |
|---|---|---|
| Seller's owner or CEO, or acquirer's COO after closing | The deal dates, who owns the records, whether to talk to SourceX | 1, 4 and 5 |
| Operations or finance lead | How replacements, refunds and credits were decided in practice | 2 |
| ATS or back-office admin | Which objects, notes and attachments the system holds and what will migrate | 3 |
| Integration lead from the acquirer | The consolidation plan and the old system's fate | 1 and 3 |

## The run sheet: five blocks, five questions

Illustrative. A 150-person healthcare staffing firm is being acquired by a regional staffing group that will move it onto the group's ATS. The partner runs this agenda with both sides in the room after signing.

| Block | Question for the block | Who answers | What a good answer sounds like |
|---|---|---|---|
| 0-5 min: deal dates | When does the deal close, and when does the plan retire the current ATS and back office? | Owner and integration lead | "Closing is signed for a set date; the old ATS goes read-only a quarter later." |
| 5-12 min: terms to decisions | Can you link original placement guarantee terms to the decisions made later, case by case? | Operations or finance lead | "For most closed cases since 2020, yes: the client agreement is on the placement and the credit note cites it." |
| 12-18 min: where records live | Which systems hold placements, client agreements, credit notes and exception approvals, and which of them migrate? | ATS admin and integration lead | "Placements and guarantee period fields migrate; agreements and notes stay in the old instance." |
| 18-24 min: ownership | Which entity owns these records after closing, and do any client or MSP programs restrict reuse? | Owner, with counsel if needed | "The acquired entity owns them; two MSP programs are excluded by contract." |
| 24-30 min: decision | Does the company want to hear how licensing of its own operating history works, and who would lead it? | Owner | "Yes. The group COO will be the contact after closing." |

### What block two is really testing

Most firms can recite their standard terms. The question is whether a specific decision can be traced back to the specific terms that applied. Systems record part of the chain: Bullhorn's permanent placement billing summary report, for example, includes placement guarantee columns, Days Guaranteed and Days Pro-Rated, for each placement. The agreement itself, the reason a candidate left and the approval of any exception often sit in documents and email. A good answer names where each piece lives.

### Why block three needs the integration lead

The admin can describe the old system; only the integration lead can say what the new one will receive. Closed cases look finished, so notes, attachments and custom fields are easy to leave behind. The [Bullhorn data export page](/systems/bullhorn-data-export) describes what a standard export carries.

## Answers that should change the rest of the meeting

| What you hear | What it usually means | What to do next |
|---|---|---|
| "We have a standard 90-day policy." | Terms exist, but case-level links are unknown | Ask for one closed case to be described, not shown |
| "Credit notes are in the accounting system." | Outcomes exist separately from terms | Note which system, and move to block three |
| "The deal has not signed." | Confidentiality limits the conversation | Keep it light; the [sell-side kickoff agenda](/resources/sell-side-kickoff-meeting-agenda) fits better |
| "Most clients are on MSP programs." | Client terms may restrict reuse | Note which programs; stop for those |
| "We keep personnel files for a year." | A legal minimum is being mistaken for a plan | Clarify that history beyond the minimum is a separate choice |

The last row deserves care. Federal EEOC rules require private employers to keep personnel and employment records for one year from the record or the action, whichever is later. That is a floor for one category of record, not a decision about guarantee history.

## What the owner must hear before block five

**What SourceX does.** SourceX licenses approved business data directly from companies for AI training and evaluation, and manages agreement, rights review, data preparation, delivery and payout. Applying is not a commitment; [this explainer](/questions/does-a-company-application-guarantee-a-licensing-deal) covers why an application alone does not secure a deal.

**Your interest.** You are a SourceX referral partner. If a qualifying license completes and every payment condition is met, SourceX may pay you a reward. It is funded separately and never deducted from the company's payout.

**Fit.** The company needs 50+ full-time employees at peak (contractors excluded, which matters for staffing firms with large contract workforces), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. The [screening worksheet for staffing businesses](/resources/a-referral-screening-worksheet-for-staffing-and-recruiting-businesses) covers broader fit questions.

What stays unknown until SourceX reviews it: demand for these records, the rights review result, which client programs must be excluded, how candidate personal data is de-identified, any offer and any reward.

## The decision the meeting produces

| Outcome | When it fits | Who records it | What happens next |
|---|---|---|---|
| Introduce now | Block two is yes or partly, ownership is settled, the owner opted in | Partner | Send the [annotated introduction email](/resources/recruiting-firm-acquisition-introduction-email) |
| Revisit after a milestone | Authority changes at closing, or the migration scope is still open | Integration lead | Tie the follow-up to the documented closing or consolidation date |
| Stop | The owner declines, or client programs exclude the records | Partner | Note the reason; the integration carries on unchanged |

If the outcome is "revisit," the [archive context checklist](/resources/recruiting-firm-acquisition-archive-context-checklist) keeps the open items moving. Sign the Channel Partner Agreement before submitting any introduction. Attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application, with one partner per company. Illustrative only: at a USD 400,000 qualifying payout to the company, the default reward on a first qualifying transaction would be USD 70,000, the greater of USD 50,000 plus 5% and 15%; this is not a promise of earnings. The [rewards page](/rewards) lists every condition, and the [staffing and recruiting industry page](/industries/staffing-and-recruiting) covers the sector more widely.

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the meeting ended with "introduce now," [register as a partner](/register), confirm eligibility on [who qualifies](/who-qualifies), and read the [program terms](/terms) before the email goes out.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
- https://kb.bullhorn.com/bhone/Content/BH1/Topics/Reports/bh1CanvasPermPlacementBillSummaryReport.htm
- https://www.eeoc.gov/employers/recordkeeping-requirements
