Free pilot to permanent work: a 16-week record
The account below is Illustrative, built for this page. A 240-person data and analytics consultancy runs monthly reporting for a client under a master services agreement and a fixed-fee statement of work. The client asks for something extra.
| Week | System | Event | Cumulative non-billable hours |
|---|---|---|---|
| 1 | PSA | Client request logged: "weekly data-quality check, free for a four-week pilot" | 0 |
| 1 to 4 | Time tracker | 6 hours a week logged to a non-billable task, "Pilot: DQ check" | 24 |
| 5 | PSA | Pilot end date passes; the ticket is not closed and no follow-up is created | 24 |
| 5 to 12 | Time tracker | Check becomes routine; 12 hours a week, same non-billable task | 120 |
| 13 to 15 | Time tracker | Account review flags the task; hours continue while pricing is discussed | 156 |
| 16 | CLM | Amendment to the statement of work signed: weekly check added at $6,000 per month from week 17 | 156 |
The past 156 hours were written off. The business decision is clear in hindsight: an agreed pilot, an unplanned conversion to permanent work, a review that caught it, and a priced amendment. It is clear only because three systems were read together.
What metadata can a referral partner collect about service-request-to-scope-resolution without reading private content?
Treat it as a ten-question interview with the COO or head of delivery, answered from memory. Write down the answers, not any examples.
- Which PSA or ticketing tool holds client requests, since when, and roughly how many requests a year?
- Which time tracker holds hours, since when, and roughly how many consultants log time?
- Which CLM or contract repository holds agreements and amendments, since when, and roughly how many amendments a year?
- Who administers each system?
- What code, if any, appears in all three: project number, work order, client code?
- Do pilots and free tasks get their own codes and end dates?
- After approval, can time be reclassified, and who can do it?
- Are amendments linked to their parent agreements, and do they reference the request that caused them?
- Does the firm know that free work sometimes becomes permanent, and how does it catch it (account review, utilization report, client renewal)?
- Have any of the three systems been replaced, and what history moved across?
The packet those answers produce (Illustrative)
| Packet field | PSA (new request) | Time tracker (delivery effort) | CLM (agreed scope adjustment) |
|---|---|---|---|
| Object types | Requests, tickets, projects, tasks | Time entries, approvals, task codes | Agreements, amendments, parent links |
| Years held | 2018 to today | 2018 to today | 2020 to today; older contracts as PDFs |
| Rough volume | About 3,000 client requests a year | About 180 consultants logging weekly | About 120 amendments a year |
| Reference carried | Project number | Project number and task code | Client code; project number in some amendments |
| Owner | Head of delivery | Finance operations | Commercial lead |
| Unknown | Whether pilots get end dates | How often approved time is reclassified | Share of amendments that cite a request |
Harvest's help pages, for example, describe approved timesheets as locked until an administrator withdraws approval, and Ironclad's describe amendments linked to a parent contract. Those details tell you which questions to ask; they do not imply SourceX connects to either tool.
Unknown until review: confidentiality and data-use terms in client contracts, personal data in time narratives, buyer interest, the offer and any reward. The scope creep adjudication guide covers the related change-order trail, and the contract review workflows page covers the CLM record type.
Sponsor and fit
Introduce someone who can open a licensing discussion: usually the CEO, COO or managing partner. Name the head of delivery and the finance or commercial lead as the people who can answer the interview. The guide to operational knowledge in a professional services firm explains how to raise the topic with partners.
Before introducing, check: 50+ full-time employees at peak (subcontracted consultants excluded), documented operating history, rights to license, 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.
What stays unknown until SourceX reviews it: demand for this record type, the rights review result, how client and personal data would be handled, the offer and any reward. Related: Jira Service Management request history and the systems hub.
Go deeper on service-request-to-scope-resolution records
- How to link requests, hours and amendments across systems: a guide to the shared codes that join PSA, time and CLM records.
- Service-request-to-scope-resolution completeness checklist: a checklist of the breaks that leave a scope trail incomplete.
- What a single-system PSA or time export leaves out: a guide to the context lost when only one system is exported.
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 a services firm can answer the ten questions and link its amendments to the requests behind them, register as a partner, check it against who qualifies, and read the program terms before you introduce its COO.