A technology risk register records problems and exposures. It does not, by itself, explain which technical capabilities a proposed operating plan depends on. That needs a separate set of testable assumptions.
For this article, a technology investment thesis means the technical assumptions inside an operating plan. It is an operational planning exercise, not a recommendation about whether to make an investment or what to pay.
The short answer: write down what systems, data and team must be able to do, identify the evidence that would test each claim, and give each open question an owner. Keep the risk register alongside this work rather than treating it as the entire review.
Here is how to write one.
The risk register is the floor, not the ceiling
A risk review asks about issues such as unsupported systems, key-person dependency, security gaps and technical debt. A capability review adds another question: can the systems and team do the work the proposed plan requires?
Similar risk lists can hide different capabilities. One platform may have evidence of handling the expected workload while another has not been tested. Record that distinction rather than treating the absence of a listed risk as proof of capacity.
Turn the thesis into technology claims
Start with the reasons you are doing the deal, and ask what each one requires from technology. Every deal thesis implies a small set of claims that can be written down and tested.
For example, a growth plan might require higher transaction volume; an integration plan might require reliable exports and shared identifiers; a product plan might depend on release capacity. State the requirement and its constraints before proposing a test.
Write measurable claims with context. An illustrative capacity question is whether the system can handle a defined workload while meeting agreed response-time and reliability targets. An integration question might ask what prevents a particular data flow from working. Do not substitute a generic ninety-day promise for an assessment.
Test the claims in diligence
Each claim becomes diligence work with a pass and a fail. Scale claims get tested against architecture, infrastructure design, and actual load data. Margin claims get tested against the true cost to run: licenses, maintenance, infrastructure, and the people behind all three. Integration claims get tested against how the last acquisition actually went, if there was one, and against how standardized the stack really is. Roadmap claims get tested against shipping history and engineering capacity.
The output is a record of what the evidence supports, what requires more work and what remains unknown. Separate observed facts, estimates and untested assumptions. Leave transaction valuation and investment decisions to the responsible decision-makers.
Carry it past closing
After a transition, carry the verified requirements into the operating plan with owners, dependencies and review dates. Unverified claims remain open questions, not accepted capabilities. Where more work is needed, define the next test before treating it as complete.
Review assumptions when conditions change, such as a workload increase, a key departure or a vendor change. Use the review to decide which evidence needs refreshing.
A thesis-to-technology mapping worksheet
Deal thesis. The two or three reasons this deal pays off, in the deal team’s own words.
Technology claims. For each reason, what the systems, data, and team must do, written as testable sentences.
Diligence tests. The evidence that proves or breaks each claim, and the answer found.
Model impact. The operational work, dependencies and estimates associated with each answer.
Post-close owners. Who carries each claim into the value creation plan, and when it is next reviewed.
Frequently asked questions
What is a technology investment thesis?
A short statement of what the target’s technology must do for the deal to pay off, written before close and managed after. It converts the deal thesis into specific, testable claims about systems, data, and team.
Which deals need one?
Use this worksheet when an operating plan depends on scale, integration, data quality or delivery capacity. The scope should follow the actual technical dependencies.
How is this different from technology due diligence?
A capability worksheet complements a risk review. One makes the required capabilities explicit; the other records problems and exposures. Both should state the limits of their evidence.
Who owns it after close?
The operating partner or portfolio executive who owns the value creation plan, with the portfolio company’s technology leadership. If nobody owns it, it was a diligence artifact, not a thesis.
Make the technical assumptions visible
A short statement of what the systems must do is useful only if it can be tested. Write the requirement, check the evidence and keep an owner attached to unresolved questions.
CTO Input works with investors and portfolio companies on exactly this: turning deal theses into technology claims, testing them in diligence, and carrying them into the first hundred days. If a deal is in front of you, we are glad to help you write the technology side of it.