What is an engineering calculation package and why does it matter to AI labs and data users?
An engineering calculation package is the bound set of design calculations behind a drawing or specification: design basis, loads and assumptions, step-by-step math, checker markups and the sign-off that released it. It matters to AI labs and data users because it shows quantitative reasoning that was independently reviewed and corrected, which is what agents for engineering work still struggle to do reliably.
For an M&A advisor with engineering firms on the sell-side list, this is a concrete asset to ask about. A firm that has stamped and archived calc packages for ten years holds a body of reviewed technical reasoning that does not appear in the firm's financial statements.
What does a package contain, and which parts carry value?
The value is in the sequence: assumption, calculation, review comment, revision, approval.
| Component | Typical content | Why it is useful |
|---|---|---|
| Design basis memo | Codes, criteria, loads, material assumptions | Context that frames every later step |
| Calculation sheets | Hand calcs, spreadsheets, software output summaries | Multi-step quantitative reasoning |
| Checker markups | Comments, corrections, questions to the designer | Error detection and correction, labeled by a human |
| Revision history | What changed after review and why | Before-and-after pairs |
| Approval record | Reviewer and engineer of record sign-off | A clear outcome label |
Checker markups are the standout. A calculation alone shows an answer. The same calculation with a reviewer's note and a corrected revision shows what a wrong answer looks like and how it was fixed. For the wider case, the explainer on why engineering and IT data is valuable gives background you can share with a client.
Who owns a calculation package?
Ownership is the first question an M&A advisor should settle, and the answer differs by document.
Documents employees prepare in their jobs are generally owned by the employer, while material from outside contractors may not be unless assigned in writing, according to the Copyright Office guidance on works made for hire. Engineering services agreements often add their own terms on who owns deliverables, and many clients own the final calculations they paid for or require approval before reuse.
That leads to a practical split:
- Firm-owned and cleaner: internal templates, standard calculation spreadsheets, design guides, checking checklists, QA procedures and internal review threads on firm methods.
- Client-owned or restricted: project-specific packages delivered under contracts that assign deliverables to the client, or that carry confidentiality terms.
- Needs a legal read: work done as a subconsultant, public-sector projects with their own records rules, and anything with a third party's proprietary inputs.
This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.
The firm-owned first rule
When screening a firm, ask what the firm itself owns before asking what it has produced for clients. A firm with years of internal checking comments on templates and methods, even if client packages are off the table, may still hold licensable material. Where project packages are involved, the company and SourceX review the contracts during qualification; the advisor does not need to resolve that.
When to raise it in an engineering firm sale
| Moment | Why it helps |
|---|---|
| Early sell-side preparation, while the data room is being planned | Records can be inventoried before systems change |
| After an LOI, while the buyer's technology plans are discussed | Buyer integration may retire the document system |
| Before a planned migration of document management | Exports are easiest while the old system is live |
| When an owner discusses a staged exit or earnout | A one-time license can sit beside the sale timeline |
Coordinate with the deal team first, since exclusivity of an AI-training license and the timing may interact with the transaction. The company and its advisors decide.
Screen for engineering firms
- ☐50+ full-time employees at peak (contractors excluded) and several years of documented operations
- ☐A document management or project system holding calc packages with revision history
- ☐Checker or peer-review markups kept, not only final stamped copies
- ☐Firm-owned templates, standards and methods documented separately from client work
- ☐An owner or principal reachable who could consider an exclusive AI-training license
The company fit checker and the data inventory builder give the principals a low-effort way to see whether the firm fits, and the guide on exception handling records explains why error-and-fix material gets attention. Compare it with how coding teams record fixes in infrastructure-as-code history.
What to say to a principal
Your firm's reviewed calculations show how problems get checked and corrected, and that kind of record is scarce. Some firms license the parts they own, with project details handled under rules they set. Would it be worth a short conversation to see what could qualify?
How do rewards work for advisors?
A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. The reward rate is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout. There is no cap per referred company. It is never deducted from what the company receives. Advisors who are registered or licensed should check their own firm and regulator rules on referral fees and disclosure before joining; the M&A advisor page covers the questions to ask.
Next step
If you advise engineering firms, register as a partner and introduce one firm through the referral form or your referral link. The firm can also start at sourcex.si/apply. The who qualifies page lists the baseline.