<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Tyson Martin on Medium]]></title>
        <description><![CDATA[Stories by Tyson Martin on Medium]]></description>
        <link>https://medium.com/@tyson.martin?source=rss-f3d8a6bff1fd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ax0IkNvWbHHttfrn_5fBKQ.jpeg</url>
            <title>Stories by Tyson Martin on Medium</title>
            <link>https://medium.com/@tyson.martin?source=rss-f3d8a6bff1fd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:20:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tyson.martin/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Answer a Technology Diligence Questionnaire Well]]></title>
            <link>https://medium.com/@tyson.martin/how-to-answer-a-technology-diligence-questionnaire-well-1c694f89dc1f?source=rss-f3d8a6bff1fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c694f89dc1f</guid>
            <category><![CDATA[due-diligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[private-equity]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[mergers-and-acquisitions]]></category>
            <dc:creator><![CDATA[Tyson Martin]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 12:58:05 GMT</pubDate>
            <atom:updated>2026-11-19T12:58:05.782Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A printed technology diligence questionnaire on a desk with notes and a pen" src="https://cdn-images-1.medium.com/max/1024/0*Ghl8XlZtqTDTQcSN.jpg" /></figure><p>The questionnaire arrives, usually a week into diligence, and it is always longer than expected. Hundreds of questions about architecture, vendors, security practices, people, and history. How a company answers it sets the tone for everything that follows. Buyers read answers for content. They also read them for how the company works.</p><p>The short answer: answer with evidence, name an owner for each answer, and put dates on anything that changed. Accuracy and consistency matter more than polish, and a fast honest answer beats a slow perfect one.</p><h3>Answer the question asked, with evidence</h3><p>The most common failure is answering a different question than the one asked. “Do you perform backups?” is not asking whether backups are a good idea. It asks whether they happen, how often, and when the last restore was tested. The answer that helps is the one with specifics: frequency, systems covered, and the date of the last test.</p><p>Where a practice does not exist, say so plainly and say what happens instead. A buyer who learns from your questionnaire that something is missing files it as a known item. A buyer who learns it later, from a system log, files it as a trust problem.</p><h3>Name an owner for every section</h3><p>Questionnaires expose who actually runs things. If the IT manager answers the infrastructure sections, the engineering lead answers the product sections, and the CEO signs the front page, that is a healthy picture. If one person answers everything, or answers route through a layer of review until they say nothing, the buyer notices both.</p><p>Assign each section to the person who runs that area, have them answer in their own words, and review only for accuracy. The texture of real answers from real owners is an asset. It is also nearly impossible to fake, which is why buyers look for it.</p><h3>Date anything that changed</h3><p>Diligence questions are often answered as if the company is frozen in time. It is not. Vendors changed in March. The new monitoring went live in June. The last penetration test was eighteen months ago because the firm was replaced. Dates turn a static answer into a trajectory, and buyers are buying the trajectory as much as the state.</p><h3>Keep the answers consistent with everything else</h3><p>The questionnaire is read alongside the management presentation, the data room, and the interviews. If the presentation says monitoring is real-time and the questionnaire says logs are reviewed weekly, someone will ask which is true. A short internal pass for consistency, before submission, catches most of these. The ones it misses, the buyer will.</p><h3>Frequently asked questions</h3><h3>How fast should we return the questionnaire?</h3><p>Fast enough to show the information is at hand, slow enough to be accurate. For most companies, one to two weeks. A same-day return reads as either very well prepared or not carefully read.</p><h3>What if we cannot answer some questions?</h3><p>Say what you can, say why the rest is unavailable, and say how it could be answered if the buyer needs it. Unanswered questions with a reason are normal. Unanswered questions with silence are not.</p><h3>Should answers be polished by leadership first?</h3><p>Review for accuracy, not tone. Over-edited answers that all sound like the marketing page create more questions than they resolve.</p><p>If a questionnaire has landed and the honest answers are harder to assemble than they should be, that is worth fixing before the next one arrives. CTO Input helps owners get their technology story into evidence shape. If that would help, we should talk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c694f89dc1f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Your managed services provider should not be your only source of technology advice.]]></title>
            <link>https://medium.com/@tyson.martin/your-managed-services-provider-should-not-be-your-only-source-of-technology-advice-a1dc2fda8a90?source=rss-f3d8a6bff1fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1dc2fda8a90</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[it-services]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Tyson Martin]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 12:26:01 GMT</pubDate>
            <atom:updated>2026-11-19T12:26:01.797Z</atom:updated>
            <content:encoded><![CDATA[<h4>A worked investment comparison shows where a provider recommendation needs a separate business judgment.</h4><figure><img alt="Two business professionals discuss documents while seated on a black sofa." src="https://cdn-images-1.medium.com/max/1024/1*WQ5qqw3mSERFTEnIb4aFbw.jpeg" /></figure><p>An attractive consolidation proposal deserves more than a product comparison. Imagine this hypothetical decision: a managed service provider recommends a new company-wide customer-service platform.</p><p>The proposal has a clear story: consolidate several tools, give employees one place to work, and reduce the time required to resolve customer cases. The provider would implement the platform and supply ongoing support.</p><p>The CEO likes the idea. Employees have complained about moving information between systems. The provider understands the environment and has put serious work into the recommendation.</p><p>There is still an important decision to make. Does the full proposal address the company’s actual constraint, and is it the most appropriate way to do so?</p><p>An independent evaluation should answer that question with more than a second opinion about the product. It should examine a common set of business requirements across genuinely different options.</p><h3>Establish what the investment must change</h3><p>In this hypothetical example, the operations leader wants customer cases resolved more consistently. The initial concern is that employees spend too much time transferring information between tools.</p><p>A review of representative cases reveals two different sources of delay. Some cases wait because required information must be entered twice. Others wait because nobody has clear authority to approve an exception for the customer.</p><p>The proposed platform could plausibly reduce duplicate entry. It cannot, by itself, determine who should approve the exception or how quickly the company should respond.</p><p>Separate those issues in the investment case. Otherwise, the expected improvement may attribute the entire delay to a problem the proposed software addresses only partly.</p><p>The business owner should define the workflow that needs to improve and the evidence that would demonstrate improvement. The technical evaluator can then assess which options support that workflow.</p><h3>Put three real options beside one another</h3><p>The first option is to keep the current tools while clarifying exception authority and improving the information handoff. This preserves the existing environment but leaves its limitations in place. It also provides a way to test how much of the delay comes from the operating process.</p><p>The second option is a narrower change to the case-management workflow. The company would replace or connect only the tools required for that work, while leaving unrelated functions alone. This depends on whether the relevant systems can exchange the required information reliably and within an acceptable support arrangement.</p><p>The third option is the provider’s full platform proposal. It may reduce fragmentation more broadly, but it also requires more migration, retraining, and business participation. Some included capabilities may not address a current priority.</p><p>Evaluate all three against the same operating requirement. A premium feature list should not allow the broadest option to redefine the problem in its own favor.</p><h3>Rebuild the cost comparison around what remains</h3><p>Now suppose the proposal assumes that existing subscriptions disappear after migration. Finance finds that one application must remain because another department relies on a function outside the replacement scope.</p><p>The proposed saving needs to change. The company would pay for part of the old arrangement while introducing the new one.</p><p>This is why the review should follow costs through the actual operating transition. Include overlap, migration support, integration work, internal participation, and the continuing administration required for each option.</p><p>Ask what must be true before an old service can be retired. Who depends on it? What evidence will establish that the replacement can support those uses? Are there relevant contractual constraints for the company’s advisors to examine?</p><p>Use consistent boundaries when comparing the options. A full-service proposal and a license-only alternative will otherwise appear comparable while assigning very different work to the internal team.</p><h3>Make commercial interests visible</h3><p>The provider expects to earn implementation and recurring service revenue from the recommended platform. That is a normal part of its business, and it does not establish that the advice is poor.</p><p>It does mean the company should understand how the recommendation relates to the provider’s delivery model. A platform may be attractive partly because the provider knows it well, has a commercial relationship with its supplier, or can support it efficiently.</p><p>Those advantages may benefit the customer. Ask how, and what tradeoffs accompany them.</p><p>Apply the same scrutiny to the independent evaluator. Any referral arrangements, resale interests, or expected implementation work should be disclosed. Independence needs to be understood in the actual engagement, rather than assumed from an advisory title.</p><h3>Choose a staged decision when the evidence supports it</h3><p>In this worked example, the analysis supports a narrower next step rather than immediate approval of the full platform.</p><p>Clarify exception authority now. Test the revised handoff on a bounded set of customer cases. In parallel, verify the technical and support assumptions behind the narrower integration option.</p><p>The comparison should then return with evidence about the remaining duplicate-entry burden, the quality of the proposed connection, and the cost of keeping the application that cannot yet be retired.</p><p>If those findings support a broader platform change, the company can evaluate it with a more accurate benefit and cost picture. If the smaller correction addresses the main constraint, management can avoid committing to unrelated change.</p><p>The provider remains a valuable participant. Its recommendation has helped expose an opportunity, and its expertise may be needed to implement the selected approach.</p><p>The company’s decision, however, now rests on a tested business problem, comparable options, and explicit assumptions. That is the additional value of independent advice: it can change the scope and sequence of the investment, not merely endorse or reject the provider’s preferred product.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1dc2fda8a90" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What a Quality of Technology Review Adds to a Deal]]></title>
            <link>https://medium.com/@tyson.martin/what-a-quality-of-technology-review-adds-to-a-deal-5095c0c83819?source=rss-f3d8a6bff1fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/5095c0c83819</guid>
            <category><![CDATA[due-diligence]]></category>
            <category><![CDATA[mergers-and-acquisitions]]></category>
            <category><![CDATA[private-equity]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Tyson Martin]]></dc:creator>
            <pubDate>Wed, 18 Nov 2026 12:57:32 GMT</pubDate>
            <atom:updated>2026-11-18T12:57:32.259Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A man points at a computer monitor while reviewing technology assessment findings" src="https://cdn-images-1.medium.com/max/1024/0*NPTjo0l99eOPb2cl.jpg" /><figcaption>What a Quality of Technology Review Adds to a Deal</figcaption></figure><p>Deals generate a great deal of analysis of the numbers, and comparatively little examination of the machinery that produces them. A quality of technology assessment exists to close that gap: it asks whether the systems, the team, and the codebase can actually deliver what the plan assumes they will.</p><p>The short answer: a quality of technology assessment examines three things other work does not. Whether the systems can support the growth plan, whether the team and knowledge are durable, and what it will cost, in effort and attention, to keep the machinery running while the plan executes.</p><h3>It tests the plan against the systems</h3><p>Every deal model assumes something about technology, even when it never says so. Doubling customers assumes the platform handles the load. Expanding into a new segment assumes the product can be configured for it. A quality of technology assessment takes the plan’s assumptions and checks them against how the systems are actually built and operated.</p><p>Sometimes the answer is reassuring. Sometimes the review finds that the plan’s second year depends on a system already at its limit. Either way, the buyer learns it while it is still information rather than surprise.</p><h3>It tests whether the people side is durable</h3><p>Technology in a mid-sized company is usually held together by a small number of people. The review looks at how knowledge is distributed: what is documented, what lives in one person’s head, and what happens to the systems if that person leaves. This is not an HR exercise. It is an evidence question about whether the organization that built the asset can keep operating it.</p><h3>It prices the quiet work</h3><p>Every technology estate carries maintenance that never appears in a pitch: the upgrades deferred, the patches pending, the manual workarounds that keep customers happy. A good review surfaces this ongoing cost of ownership in plain terms, because it competes with the growth plan for the same engineers and the same attention.</p><h3>What a good one produces</h3><p>The output should be readable by a non-technical deal team in one sitting: what the systems do, what condition they are in, what the team looks like, what the maintenance burden is, and what the findings mean for the plan. Evidence, not adjectives. If a review cannot point to what it examined, it produced an opinion, not an assessment.</p><h3>Frequently asked questions</h3><h3>How long does a quality of technology assessment take?</h3><p>For a mid-sized company, typically two to four weeks depending on access to systems and people. Compressed timelines are possible but trade depth for speed; that trade should be explicit.</p><h3>Who should perform it?</h3><p>Someone independent of both the seller and the deal’s cheerleaders, with enough operating experience to distinguish a real constraint from a cosmetic one. The value is judgment applied to evidence.</p><h3>Does every deal need one?</h3><p>Deals where technology carries the plan do. If the thesis depends on the product, the platform, or the data, the systems deserve the same rigor as everything else being verified.</p><p>If you are advising on a deal and the technology questions are being answered with reassurance instead of evidence, that gap is worth closing before close. CTO Input performs technology reviews built for deal timelines. If that would be useful, we should talk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5095c0c83819" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five questions a buyer’s technology due diligence team will ask.]]></title>
            <link>https://medium.com/@tyson.martin/five-questions-a-buyers-technology-due-diligence-team-will-ask-30899742c0d1?source=rss-f3d8a6bff1fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/30899742c0d1</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[due-diligence]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[mergers-and-acquisitions]]></category>
            <dc:creator><![CDATA[Tyson Martin]]></dc:creator>
            <pubDate>Wed, 18 Nov 2026 11:26:01 GMT</pubDate>
            <atom:updated>2026-11-18T11:26:01.501Z</atom:updated>
            <content:encoded><![CDATA[<h4>Expect the buyer to compare the management narrative with the records underneath it, especially where they disagree.</h4><figure><img alt="A neatly stacked set of documents with red index tabs sits on an office desk." src="https://cdn-images-1.medium.com/max/1024/1*yagqc9DeyIQSj5kVZqDmBQ.jpeg" /></figure><p>A buyer’s technology diligence team may begin with management’s presentation. The more consequential questions can emerge when the team compares that presentation with operating records, spending information, agreements, and delivery plans.</p><p>A discrepancy does not automatically mean someone has misrepresented the company. Documents may describe different periods, business units, definitions, or stages of completion.</p><p>The discrepancy still needs an explanation.</p><p>For founders, CEOs, and transaction advisors, useful preparation includes finding those differences before they become a prolonged exchange with the buyer. The objective is a transaction narrative that remains accurate when someone tests its supporting evidence.</p><p>The following five questions illustrate that challenge. Each example is hypothetical, not a description of a particular transaction or a universal diligence checklist.</p><h3>1. Why does the presentation describe one operating platform while the records show several?</h3><p>Suppose management describes a business that runs on a common platform. Application records show that an acquired division still uses a separate system, with employees manually transferring information into the shared environment.</p><p>The buyer needs to understand what “common platform” actually means. It might describe financial reporting while implying a broader level of operational integration.</p><p>Reconcile the statement to the current perimeter. Identify which divisions and workflows use the common platform, which remain separate, and how information moves between them. Have the people responsible for the work confirm the explanation.</p><p>If the presentation is ahead of reality, revise it. If the operating record is outdated, establish the current position with supporting evidence. Do not choose the more favorable version simply because it is already in the transaction materials.</p><p>The result should allow the buyer to distinguish today’s operating model from the intended future state.</p><h3>2. How does the technology cost model reconcile with invoices and staffing?</h3><p>A cost model might include managed services and software subscriptions while omitting technology work paid through another department, temporary support, or internal effort required to maintain manual processes.</p><p>A buyer comparing the model with invoices and staffing information could ask whether the stated operating cost represents the whole arrangement.</p><p>Work with finance to explain the scope of the model. Separate recurring operating costs, temporary arrangements, project expenditure, and any assumptions about work the buyer would absorb after closing.</p><p>If costs sit elsewhere, show where. If a temporary service must continue longer than assumed, update the relevant forecast. Avoid silently treating a desired future saving as a current operating fact.</p><p>The useful answer reconciles the records and preserves the assumptions. It does not require management to pretend that every future cost can be known precisely.</p><h3>3. Why does the security summary claim broader coverage than the underlying evidence?</h3><p>Imagine a security summary stating that an access control covers the company, while the supporting assessment excluded a division or a significant application.</p><p>The buyer could reasonably ask whether the broad statement describes a deployed control, a target condition, or an assumption that has not been checked.</p><p>Compare the summary with the actual assessment scope, date, exceptions, and completion evidence. Ask qualified security personnel to explain the gap and what further work would be needed to support a wider conclusion.</p><p>State the verified coverage accurately. Keep planned work, observed results, and unresolved uncertainty separate. If the gap is material to the transaction, address it through the appropriate management and advisory process.</p><p>Adding more reassuring language will not resolve a mismatch between the claim and the evidence.</p><h3>4. Does the integration plan reflect what providers have actually agreed to support?</h3><p>A transaction plan may assume a service can be combined, transferred, separated, or extended within a particular period. A provider’s scope document may describe a narrower service or leave a consequential dependency unresolved.</p><p>Before repeating the plan’s timing as a commitment, establish what the provider has confirmed and what remains an assumption.</p><p>Match the integration activities to the relevant service information and agreements. Ask appropriate technical and transaction advisors to assess operating dependencies, and have qualified legal advisors review contractual questions.</p><p>Do not infer a contractual right from a salesperson’s broad statement or from the fact that the company already pays for the service.</p><p>The answer may require a revised sequence, additional provider work, or a clearly identified open question. Keeping the distinction visible allows the transaction team to plan around what is known.</p><h3>5. How can the roadmap dates be reconciled with approved capacity?</h3><p>Management may present a roadmap showing several improvements before or soon after closing. The approved budget and staffing plan may support only some of that work.</p><p>A buyer could ask which dates reflect funded commitments and which reflect ambition.</p><p>Review the roadmap with the people expected to deliver it. Identify the resources assigned, the work already underway, the dependencies, and the competing operating demands. Include reliance on people whose availability has not been confirmed.</p><p>Where the records conflict, revise the delivery assumption or make the required decision explicit. Keep an improvement labeled as proposed until it has the support needed to become a credible commitment.</p><p>A less ambitious, supported plan is easier to assess than a comprehensive roadmap whose critical resources exist only in the presentation.</p><h3>Resolve the contradiction, then keep the answer consistent</h3><p>For each discrepancy, identify the authoritative source, the relevant date and scope, the explanation, and the person responsible for correcting affected materials. Make sure the corrected answer reaches the transaction team rather than remaining in one specialist’s inbox.</p><p>Do not erase the uncertainty merely to make documents agree. Explain it consistently and identify the next step needed to resolve it.</p><p>A buyer will make its own assessment. Your task is to ensure that management’s account of the business can withstand comparison with the business itself.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30899742c0d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The First Two Weeks of Technology Ownership After Close]]></title>
            <link>https://medium.com/@tyson.martin/the-first-two-weeks-of-technology-ownership-after-close-8ca87dee8bbe?source=rss-f3d8a6bff1fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ca87dee8bbe</guid>
            <category><![CDATA[due-diligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[private-equity]]></category>
            <category><![CDATA[mergers-and-acquisitions]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Tyson Martin]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 12:56:07 GMT</pubDate>
            <atom:updated>2026-11-17T12:56:07.137Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Colleagues discuss work around a laptop at an office table." src="https://cdn-images-1.medium.com/max/1024/0*3TNdzaVPc5SLAlpC.jpg" /></figure><p>The deal closed on Friday. By Monday morning, someone owns every technology decision at the company you just bought, and in most acquisitions nobody has said who. The first two weeks are not for transformation. They are for making sure the unglamorous questions have owners before something breaks.</p><p>The short answer: in the first two weeks, establish decision rights, incident authority, and an access review. Everything else, including the integration roadmap, works better once those three exist.</p><h3>Decide who decides, before the first decision arrives</h3><p>In the gap after close, decisions arrive that cannot wait for a steering committee. A vendor renewal hits its notice window. A key engineer gives notice. A customer demands a security answer. Each of these needs a named person with authority to act, and a clear line for what must come to the investor or the board.</p><p>Write it down in a page. Which technology decisions the portfolio company CEO makes alone, which need the operating partner, which need the board. The page matters less than the conversation, but the conversation does not happen without the page.</p><h3>Set incident authority explicitly</h3><p>If the company has a security incident in week three, who is in charge? The acquired company’s IT lead, the platform’s security team, an outside firm, the insurer’s panel? In the first two weeks, answer that question while it is still hypothetical. Confirm the incident contacts actually work: phone numbers, after-hours paths, and who can approve emergency spending without a meeting.</p><p>This is also the moment to learn what monitoring exists and who watches it. An alert nobody owns is a liability you now own.</p><h3>Review access while it is still easy</h3><p>Access accumulates. Former employees, departed contractors, vendors from two years ago, and in carve-outs, people who now work for the seller. In the first two weeks, get the list of who has administrative access to what, and remove what should not be there. This is cheap, fast, and much harder to do credibly six months in.</p><h3>What to leave alone</h3><p>Resist the urge to start the rebuild. System replacements decided in the first two weeks are usually decided on the thinnest information you will ever have about this company. The governance work above creates the structure that makes later decisions good. Let it do that job first.</p><h3>Frequently asked questions</h3><h3>Is two weeks really enough time to set up governance?</h3><p>For the three items here, yes. Decision rights, incident authority, and access review are each a few days of focused work. The full integration plan takes longer and should.</p><h3>What if the acquired company already has good processes?</h3><p>Then the two weeks confirm them and connect them to your escalation paths. The failure mode is assuming someone else’s process covers your accountability.</p><h3>Should the platform’s IT team take over immediately?</h3><p>Usually no. Immediate takeover breaks accountability before you understand what you bought. Observe first, assign authority, integrate deliberately.</p><p>If you have just closed a deal and the technology governance question is still “we’ll figure it out,” the first two weeks are the cheapest time to fix that. CTO Input works with investors and portfolio companies on exactly this window. If it would help, we should talk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ca87dee8bbe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The person who kept your systems running at $5M may not be equipped to build the organization you…]]></title>
            <link>https://medium.com/@tyson.martin/the-person-who-kept-your-systems-running-at-5m-may-not-be-equipped-to-build-the-organization-you-91fc20da8fca?source=rss-f3d8a6bff1fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/91fc20da8fca</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[business-growth]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Tyson Martin]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 10:26:01 GMT</pubDate>
            <atom:updated>2026-11-17T10:26:01.501Z</atom:updated>
            <content:encoded><![CDATA[<h3>The person who kept your systems running at $5M may not be equipped to build the organization you need at $50M.</h3><h4>Evaluate the work the business now requires, then give a trusted colleague a fair path into the next operating model.</h4><figure><img alt="Two businesswomen discuss work beside an open laptop in a bright office." src="https://cdn-images-1.medium.com/max/1024/1*SzU8x0lSgiVdmDpaU_vdUQ.jpeg" /></figure><p>The revenue figures in this title describe a change in scale. They are not a threshold for deciding whether someone is a capable technology leader.</p><p>Two companies with the same revenue can have very different technology needs. Customer expectations, locations, acquisitions, operating complexity, and the consequences of disruption all matter.</p><p>What deserves examination is how the work has changed.</p><p>A person who made an important contribution in the early business may still be carrying the same informal role while everyone expects a much broader set of capabilities. That is a difficult position for the individual and an unreliable arrangement for the company.</p><p>Before deciding that a trusted colleague has become the problem, examine the job leadership has asked them to do.</p><h3>Recognize the value of the early role</h3><p>In a smaller company, a capable generalist can make an extraordinary contribution. They know the systems, respond to problems, coordinate vendors, and help people keep working.</p><p>Their value often comes from responsiveness and practical knowledge of the business. Employees trust them because they understand how things actually get done.</p><p>As the company becomes more complex, management may begin expecting additional work: workforce planning, financial prioritization, cross-functional process design, cybersecurity governance, and the development of a team that can operate without constant intervention.</p><p>Those expectations can accumulate without any clear conversation about a changed role.</p><p>A new title will not resolve that mismatch. Neither will asking the person to become more strategic while every urgent support problem still reaches their phone.</p><h3>Describe the future work before judging the person</h3><p>Start with the business’s next stage. Which activities will require stronger technology leadership, and why?</p><p>An expanding operating footprint may require more consistent service delivery. New customer requirements may call for specialized security expertise. An acquisition may require integration leadership that the existing team has never needed before.</p><p>Translate those needs into responsibilities and decisions. Then decide which belong in the same role and which require separate capabilities.</p><p>Be careful about designing an impossible job. Expecting one person to provide executive leadership, manage every system, handle daily support, and cover specialized security work does not become reasonable because the company has grown.</p><p>The organization may need additional capacity, a clearer division of responsibilities, or access to specialists. A capability gap in the business is not automatically a capability failure by one employee.</p><h3>Have the conversation directly</h3><p>The discussion with the current leader should include their view of the work and their interest in what comes next.</p><p>Some people want to lead a larger organization. Others want to remain close to engineering, systems, or service delivery. Both can be valuable paths.</p><p>Ask which responsibilities they want to develop, which they already handle effectively, and where the current workload prevents progress. Explain the company’s needs without presenting an unstated replacement decision as an open conversation.</p><p>Specific examples are more useful than broad judgments about executive presence or strategic thinking. If priorities are unclear, examine how the current planning process works. If delegation is limited, ask whether there is anyone with sufficient capability and capacity to receive the work.</p><p>The conversation should distinguish skill, experience, interest, and organizational support. They are different issues and may require different responses.</p><h3>Make development a real operating choice</h3><p>If the person wants to grow into a broader role, agree on the work they will take on and the support they will receive.</p><p>That might include an experienced mentor, focused education, participation in business planning, or a specialist who can provide expertise the role should not be expected to contain alone.</p><p>It also requires subtraction. Identify which existing duties will move elsewhere, who will take them, and how service continuity will be protected.</p><p>Use meaningful work to assess progress. For a hypothetical development assignment, the leader might prepare a prioritized technology operating plan with business owners, explain the tradeoffs, and lead an agreed review cycle. Management can then assess the quality of the decisions and follow-through.</p><p>Agree on the evidence, review points, and support before the assignment begins. An undisclosed test with shifting expectations is neither useful development nor a fair basis for judgment.</p><h3>Design a respectful alternative when the fit differs</h3><p>Development into the broadest leadership role may not be the best option. The company might need another leader while the trusted employee continues in a role that makes better use of their strengths.</p><p>If that is the direction, make the responsibilities, reporting relationships, and decision authority clear. Avoid creating two overlapping leaders who must resolve every disagreement through the founder.</p><p>Treat knowledge transfer as planned work, with time and appropriate support. Do not turn the individual’s institutional knowledge into a reason they can never leave daily firefighting behind.</p><p>Any change affecting employment terms needs the appropriate internal process and qualified advice. The leadership principle is straightforward: communicate honestly, respect the contribution already made, and avoid promising a future role that has not actually been agreed.</p><h3>Build the organization the business needs</h3><p>Founders can feel caught between loyalty to an early colleague and responsibility for the next stage of growth. A clear operating design makes that discussion more constructive.</p><p>Determine the work, assess the available capabilities, ask what the person wants, and provide a credible path where one exists. Address genuine gaps without rewriting the value of their earlier contribution.</p><p>The company needs the right leadership capabilities for what comes next. The person who helped build it deserves a clear, respectful conversation about how they can be part of that future.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91fc20da8fca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Buyers Actually Test in Your Management Presentation]]></title>
            <link>https://medium.com/@tyson.martin/what-buyers-actually-test-in-your-management-presentation-39fc947bf11e?source=rss-f3d8a6bff1fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/39fc947bf11e</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[due-diligence]]></category>
            <category><![CDATA[mergers-and-acquisitions]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[private-equity]]></category>
            <dc:creator><![CDATA[Tyson Martin]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 13:06:04 GMT</pubDate>
            <atom:updated>2026-11-16T13:06:04.374Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A businessman presents to colleagues seated around a conference room table." src="https://cdn-images-1.medium.com/max/1024/0*VldxEEZOeBFdLnE4.jpg" /></figure><p>The management presentation is the first time a buyer checks whether the story and the systems agree. Most founders prepare the growth narrative and treat the technology section as an appendix. In our experience, the technology section is where sophisticated buyers quietly form their view of everything else.</p><p>The short answer: buyers use the management presentation technology content to test three things. Whether the numbers you showed them can be produced without heroics, whether the people presenting understand what they own, and whether the obvious problems are the ones you have already named.</p><h3>They test whether your reporting is a system or an effort</h3><p>Every management presentation has metrics. Retention, margin by customer, implementation cycle time. A buyer’s first technology question is rarely about the metric itself. It is about where the number comes from. If the answer is that someone builds it in a spreadsheet each month from three exports, the buyer has learned something important: the reporting does not scale, the number may not reconcile, and the person who builds it is a dependency.</p><p>Before the presentation, trace each headline metric to its source. You do not need a perfect data pipeline. You need to know which numbers are system-generated, which are assembled by hand, and which you would struggle to reproduce under questioning. Buyers forgive manual reporting in a small company. They do not forgive a management team that cannot say which is which.</p><h3>They test whether the presenters own the technology story</h3><p>Buyers watch who answers the technology questions. If every technical question routes to one person, that is visible concentration risk presented live in the meeting. If the CEO answers with language the CTO would not use, that is visible distance between leadership and the systems.</p><p>Decide in advance who answers what. The CEO should be able to describe what the technology does for the business and what it costs. The senior technical person should be able to describe architecture, team, and known weaknesses without reading from notes. If your company cannot field both of those answers from two different people, that gap will show up in the meeting whether you plan for it or not.</p><h3>They test whether you name your own problems first</h3><p>Every company has technology weaknesses. Buyers arrive assuming there are some you have not told them about. A management presentation that names the known issues, with what each one costs and what the plan is, converts a diligence finding into a management strength. A presentation that presents everything as healthy converts the same finding into a credibility problem later, when diligence surfaces it anyway.</p><p>The discipline is to list the weaknesses you already know about before the buyer lists them for you. Concentrated knowledge, an aging component, a vendor you have outgrown. You are not expected to have fixed everything. You are expected to know your own inventory.</p><h3>What to prepare before the slides</h3><p>The useful preparation is not better slides. It is a short internal worksheet: the metrics and their sources, the owners of each technology answer, the named weaknesses with cost and plan, and the two or three questions you hope nobody asks, with honest answers written down. Teams that do this work walk into the room calmer, and calm is legible to buyers.</p><h3>Frequently asked questions</h3><h3>How much technology detail belongs in a management presentation?</h3><p>Enough to show the systems support the business story: architecture at a diagram level, team shape, major vendors and costs, and known weaknesses with plans. Detailed documentation belongs in diligence, not in the first presentation.</p><h3>Should the CTO present, or the CEO?</h3><p>Both, for different questions. The CEO owns what technology does for the business. The senior technical person owns how it works and where it is weak. One person answering both reads as concentration risk.</p><h3>What if our technology genuinely has problems we have not fixed?</h3><p>Name them yourself, with the cost and the plan. Buyers price known problems far more kindly than discovered ones. The discovery is what damages a deal, not the problem.</p><p>If you are preparing for a sale and the technology section of the story feels like the weak slide, that is fixable, and it is much cheaper to fix before the first buyer meeting than during diligence. CTO Input helps owners prepare the technology side of this story so it survives the room. If that would be useful, we should talk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39fc947bf11e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why expensive technology projects fail to deliver the outcomes management expected.]]></title>
            <link>https://medium.com/@tyson.martin/why-expensive-technology-projects-fail-to-deliver-the-outcomes-management-expected-d0500a77d736?source=rss-f3d8a6bff1fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0500a77d736</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Tyson Martin]]></dc:creator>
            <pubDate>Mon, 16 Nov 2026 11:26:01 GMT</pubDate>
            <atom:updated>2026-11-16T11:26:01.512Z</atom:updated>
            <content:encoded><![CDATA[<h4>When a promised benefit fails to appear after go-live, diagnose the missing link before funding another solution.</h4><figure><img alt="Colleagues review a whiteboard with diagrams and colored notes." src="https://cdn-images-1.medium.com/max/1024/1*PkU4300ytSsWGY-g8lFoNg.jpeg" /></figure><p>A new order-management system can go live while the work it was meant to remove continues. In the hypothetical example that follows, management approved the investment partly to reduce the manual work required to correct customer orders.</p><p>The platform is live. The migration is complete. Employees are using it. Yet the operations team reports that corrections still consume much the same effort.</p><p>The implementation team points to completed milestones. Operations points to an unchanged workload. Finance wants to know whether the business case was wrong.</p><p>The company needs a benefits review that can distinguish those possibilities and lead to a corrective decision. Another status report on the implementation will not answer the question.</p><h3>Start with the benefit that failed to appear</h3><p>Choose the specific missed result. In this example, the concern is manual order correction, not whether the project generally counts as a success.</p><p>Recover the original definition of that benefit. Which work was expected to disappear? Which orders were included? What effort was measured before launch? How long was the new process expected to need before a meaningful comparison could be made?</p><p>The operating owner and finance should agree on what the available evidence can support. If the original baseline was weak, preserve that limitation rather than turning an estimate into a historical fact.</p><p>Then check whether the comparison is fair. A change in order volume or complexity can hide an improvement or make an unchanged process look better. Compare relevant work on a consistent basis and explain any material differences.</p><p>This first step may reveal a measurement problem. It may also confirm that the expected benefit genuinely has not arrived. Either result is more useful than debating whether the launch went well.</p><h3>Trace where the work still happens</h3><p>Observe representative orders with the employees who handle them. Include exceptions, because the standard path may not account for the work that originally justified the investment.</p><p>In the hypothetical company, standard orders now move through the new application. Orders with unusual delivery requirements still move into a spreadsheet, through an email exchange, and back into the system after someone resolves the exception.</p><p>That observation changes the question. Management should examine why the exception work remains and how much it contributes to the missed benefit.</p><p>The technology may be capable of supporting the workflow but configured incompletely. The workflow may require a decision the business has not made. Or the investment case may have assumed that the application could remove judgment that still requires human attention.</p><p>Those explanations lead to different actions. Calling all of them poor adoption would make the diagnosis less useful.</p><h3>Check the assumptions behind the workaround</h3><p>Ask employees what the spreadsheet allows them to do that the intended process does not.</p><p>Suppose, within the same hypothetical example, the exception requires agreement between sales and operations about a delivery promise. Neither department has authority to resolve the disagreement alone. The spreadsheet has become a queue for work awaiting a business decision.</p><p>The system cannot remove that delay merely by giving the queue a different interface.</p><p>The operating sponsor should clarify which commitments sales can make, who resolves exceptions, and what information the decision requires. The technology team can then determine whether the agreed workflow can be supported without unnecessary manual copying.</p><p>This is a narrower and more useful intervention than buying an additional module before understanding the cause.</p><p>It also changes accountability. The technology team remains responsible for its implementation work. The operating sponsor must resolve the business condition preventing the benefit.</p><h3>Run a bounded correction</h3><p>Agree on a limited set of comparable orders for the revised workflow, with the appropriate safeguards and support. Tell the employees involved what has changed and where to raise a problem.</p><p>The purpose is to establish whether the correction addresses the missing link. Check the manual effort, the quality of the completed orders, and any new burden shifted to another team.</p><p>Do not declare success simply because the new queue is empty. Work may have moved to email, been deferred, or reached customers with errors. Follow the process far enough to understand the result.</p><p>If the correction improves the outcome, decide how to extend it and retire the old workaround safely. If it does not, revisit the explanation before adding more scope.</p><p>Keep the comparison honest. A small, supported test can provide useful evidence without proving that every department or order type will experience the same result.</p><h3>Update the economics and the next commitment</h3><p>Even a successful correction may produce a different benefit from the one originally proposed.</p><p>Employees may gain capacity without reducing cash expenditure. That capacity can still matter if the company uses it for additional work, better service, or backlog reduction. Name the intended use and verify it with the operating owner.</p><p>If the business case promised cost savings, finance should assess which expenditure can actually change. Include the continuing support and exception-handling effort in that assessment.</p><p>Management may need to revise the forecast, narrow the next implementation phase, or stop an expansion that no longer has a credible case. Those are legitimate outcomes of the review.</p><p>The money already spent should not require the company to keep defending an assumption that the operating evidence has contradicted.</p><h3>Keep ownership until the outcome is understood</h3><p>After go-live, assign someone who can change the business process and remain responsible for the benefit. Give that person access to technical support and a review point tied to meaningful operating evidence.</p><p>In this example, the useful outcome is a clear explanation of the missed benefit, a tested correction where justified, and an informed decision about the remaining investment.</p><p>That is how management moves beyond an argument over project completion and starts improving what the technology was purchased to accomplish.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0500a77d736" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Target Says AI Is Core to Its Product. What Should You Verify?]]></title>
            <link>https://medium.com/@tyson.martin/the-target-says-ai-is-core-to-its-product-what-should-you-verify-c5cfe8574ef1?source=rss-f3d8a6bff1fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5cfe8574ef1</guid>
            <category><![CDATA[mergers-and-acquisitions]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[due-diligence]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Tyson Martin]]></dc:creator>
            <pubDate>Sun, 15 Nov 2026 13:02:57 GMT</pubDate>
            <atom:updated>2026-11-15T13:02:57.735Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Business colleagues review company data and analytics charts on a presentation screen in a meeting room." src="https://cdn-images-1.medium.com/max/1024/0*1kmBFfpQJrNNUKVO.jpg" /></figure><p>Two years ago, “we use AI” was a differentiator. Today it appears in nearly every acquisition target’s materials, from genuine machine learning products to a chatbot wired into a third-party API over a weekend. Both kinds of company may be worth buying. They are not the same company, and the difference is verifiable if you know what to ask for.</p><p>The short answer: AI due diligence verifies four things. What the product’s AI actually does, what it depends on (data, third-party models, key people), what it costs to run, and whether customers demonstrably use it. Everything else is the pitch.</p><p>The mistake is evaluating the claim. The work is verifying the machinery behind it. Here is what I would want to see.</p><h3>Verify what the product actually does</h3><p>Start with the workflow, not the demo. Ask where, exactly, AI sits in the product: which customer action triggers it, what it produces, and what happens when it is wrong or unavailable. A feature that drafts a suggestion a human reviews carries a different risk and value profile than one that acts on customers’ behalf.</p><p>Then ask who built it and what it is built on. There is a wide and legitimate spectrum between proprietary models trained on proprietary data and a thin interface over someone else’s API. Neither is automatically a problem. What matters is whether the company’s position on that spectrum matches its story, its pricing, and its claims about defensibility.</p><p>A useful test: ask the team to describe the last three meaningful improvements to the AI capability, who made them, and how long each took. Real capability leaves a trail of real work.</p><h3>Verify what the AI depends on</h3><p>Every AI capability rests on dependencies, and in an acquisition you inherit all of them. Three deserve direct attention.</p><p>The first is data. What data trains or grounds the system, what rights the company has to use it, and whether customer agreements support how it is being used. The exact legal questions belong with counsel, but the operational questions belong in diligence: where the data comes from, whose it is, and what happens to the product if a source withdraws.</p><p>The second is third-party models and providers. If the product depends on an external AI service, understand the commercial terms, the version and behavior-change exposure, and what the company would do if pricing, terms, or capabilities shifted. A product one API change away from a different personality is a dependency to price, not a detail to skip.</p><p>The third is people. If the AI capability lives in two engineers’ heads, the acquisition is partly an acqui-hire whether anyone calls it that. Know which individuals matter and what keeps them.</p><h3>Verify what it costs to run</h3><p>AI features have a cost curve that traditional software does not. Every customer query can carry a real, metered cost, and costs can scale with success.</p><p>Ask for the current monthly cost of operating the AI capability, how it is measured, and how it has moved as usage grew. Then ask the harder question: at the volumes in your investment case, what does the cost structure look like, and who has modeled it? You are not looking for a precise forecast. You are looking for evidence the company understands its own economics well enough that your model can trust theirs.</p><p>A target that cannot describe its AI operating costs has not finished building its business model, whatever the product looks like.</p><h3>Verify what customers actually use</h3><p>The strongest evidence in AI diligence is boring: usage. Which customers use the AI features, how often, in which workflows, and what happened when the features were unavailable? A capability customers rely on shows up in usage patterns, support tickets, renewal conversations, and references.</p><p>Ask to see adoption and retention for the AI features specifically, separated from the product overall. Then ask two or three customer references a direct question: which part of this product would you actually miss? The gap between the marketed capability and the answered question is the diligence finding.</p><h3>A one-page AI verification worksheet</h3><p>Complete this before treating any AI claim as part of the deal thesis.</p><p><strong>Product reality.</strong> Where AI sits in the workflow, what it produces, who built it, and what it is built on.</p><p><strong>Data foundation.</strong> What data the system uses, the company’s rights to it, and the exposure if a source changes or withdraws.</p><p><strong>External dependencies.</strong> Third-party models and providers, their commercial terms, and the plan if they shift.</p><p><strong>Key people.</strong> Who the capability depends on and the retention decision for each.</p><p><strong>Operating economics.</strong> Current and projected cost of running the capability, and who owns the model.</p><p><strong>Customer evidence.</strong> Usage, reliance, and reference answers specific to the AI features.</p><h3>Frequently asked questions</h3><p><strong>What is AI due diligence in an acquisition?</strong></p><p>It is the verification of what a target’s AI actually does, what it depends on, what it costs to operate, and whether customers rely on it, so the deal thesis rests on evidence rather than marketing.</p><p><strong>How do you verify a company’s AI claims?</strong></p><p>Ask where AI sits in the workflow, what data and providers it depends on, who built it, what it costs to run, and what usage and customer references show.</p><p><strong>What are the risks of AI built on third-party models?</strong></p><p>Pricing changes, terms changes, and behavior changes at the provider can all reach the product. Diligence should identify those dependencies and the company’s plan if one shifts.</p><p><strong>Does an AI feature automatically increase a company’s value?</strong></p><p>Not by itself. Value follows verified usage, defensible data and dependencies, and operating costs the company understands.</p><h3>Price the machinery, not the adjective</h3><p>AI is a real capability with real dependencies, real costs, and real evidence, and it deserves the same verification discipline as any other part of the technology stack. The targets that welcome these questions tend to be the ones with something underneath the claim.</p><p>CTO Input helps investors and acquirers verify technology and AI claims during diligence, in business language a deal team can use. If AI is load-bearing in your next deal’s thesis, run the worksheet before you run the model, and bring us in if you want the verification done properly.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5cfe8574ef1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Read a Technology Diligence Report Before You Advise on the Deal]]></title>
            <link>https://medium.com/@tyson.martin/how-to-read-a-technology-diligence-report-before-you-advise-on-the-deal-19f0eca73228?source=rss-f3d8a6bff1fd------2</link>
            <guid isPermaLink="false">https://medium.com/p/19f0eca73228</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[private-equity]]></category>
            <category><![CDATA[due-diligence]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[mergers-and-acquisitions]]></category>
            <dc:creator><![CDATA[Tyson Martin]]></dc:creator>
            <pubDate>Sat, 14 Nov 2026 13:03:10 GMT</pubDate>
            <atom:updated>2026-11-14T13:03:10.290Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A businessman in a suit reviews report documents at his desk while working on a laptop." src="https://cdn-images-1.medium.com/max/1024/0*HBsx23xeXTO9kRtJ.jpg" /></figure><p>If you advise on deals, you will regularly receive a technology or cybersecurity diligence report you did not commission and did not write. Your client will ask what it means. The summary page will offer a tidy answer, and the tidy answer is where the risk starts.</p><p>The short answer: a technology due diligence report is only as useful as its scope, evidence, and exclusions. Read those before the findings, separate what was observed from what was assumed, translate material findings into first-year ownership work, and check the appendices for what the summary leaves out.</p><p>A diligence report is not a verdict. It is a record of what a specific team examined, over a specific period, using specific procedures, within boundaries someone chose. Read it that way and it becomes genuinely useful. Read the summary alone and you may be relaying confidence the evidence cannot support.</p><p>Here is how I would read one before advising anyone.</p><h3>Start with scope and evidence, not the findings</h3><p>Before the first finding, find four facts: which entities, systems, and products were examined; what period the evidence covers; what procedures were performed; and what was excluded.</p><p>Procedures matter because they support different conclusions. A management interview, a policy document, a configuration screenshot, and a sampled operating test are not interchangeable. A report that relied on interviews and documents tells you what the company believes and intends. Only observed configuration and tested operation tell you what the company does.</p><p>Then check the exclusions against the deal thesis. If the investment case rests on a product line, a region, or an acquisition the company made last year, confirm the diligence actually covered it. A clean report on the wrong boundary is not a clean report.</p><h3>Separate observations, assumptions, and opinions</h3><p>Well-written findings blend three kinds of statement: what was observed, what was assumed, and what the assessor concludes. Your job as the reader is to keep them apart.</p><p>When a finding says a control “is in place,” ask what was actually observed and when. When it estimates remediation effort, ask what the estimate rests on: architecture reviewed, asset counts, vendor pricing, or none of those. An estimate without stated inputs is a placeholder, and placeholders have a way of hardening into plans.</p><p>Pay equal attention to what the report cannot say. “No evidence of” is different from “evidence of no.” Not tested, unknown, and excluded are legitimate states, and a good report names them. A report with no unknowns is usually a report whose unknowns were left for you to find.</p><h3>Translate each material finding into the first year of ownership</h3><p>Findings become useful when they connect to the plan. For each one that matters, ask four questions before you brief your client.</p><p>What business capability does this affect: revenue, customer commitments, continuity, reporting, or the deal thesis itself? What work follows, and does it need money, people, or calendar time the operating plan has not reserved? What does it depend on, such as an identity migration, a vendor contract, or a hiring decision? And who will own it after close?</p><p>This is the point where advisors earn their fee. The assessor’s job ends at the finding. Yours continues into the conversation between the finding and the decisions: what is asked of the seller, what is planned for after close, and what evidence will confirm it happened. The commercial consequences of those choices belong to your client and their deal counsel; your contribution is making sure the technology content of that conversation is accurate.</p><h3>Read the appendices for what the summary omits</h3><p>Summary pages are written to be read quickly, which means they are written to be incomplete. Before relying on one, spend twenty minutes in the back of the report.</p><p>Look for the population behind every percentage: the denominator, the sample, and the selection method. Look for severity labels and ask what would change them. Look for the list of systems not examined, requests not fulfilled, and interviews not granted. Those three lists, when they exist, are often the most honest pages in the document.</p><p>If the report does not provide them, that absence is itself a finding worth passing to your client, along with the option of a short follow-up scope to close the gap.</p><h3>A one-page report-review worksheet</h3><p>Complete this before you advise on any technology diligence report.</p><p><strong>Boundary.</strong> Entities, systems, products, and period covered, and whether the deal thesis depends on anything outside them.</p><p><strong>Evidence base.</strong> Procedures performed, what each supports, and the exclusions and unfulfilled requests.</p><p><strong>Finding quality.</strong> For each material finding: what was observed, what was assumed, what evidence would strengthen or change the conclusion.</p><p><strong>Ownership translation.</strong> The work, dependencies, and owner each material finding implies for the first year after close.</p><p><strong>Open unknowns.</strong> What remains untested or excluded, what could resolve it, and whether that can happen before the decisions it affects.</p><h3>Frequently asked questions</h3><p><strong>What should a technology diligence report include?</strong></p><p>Scope and boundaries, the evidence period, procedures performed, findings tied to business impact, remediation effort with its basis, and explicit exclusions and unknowns.</p><p><strong>What are red flags in a technology diligence report?</strong></p><p>Findings supported only by management statements, percentages without denominators, no stated exclusions, precise cost estimates with no stated inputs, and a summary with no unknowns.</p><p><strong>Does every finding need to be fixed before close?</strong></p><p>No. The useful question is what each finding means for the first year of ownership: the work, dependencies, cost types, and the named owner. Commercial decisions belong to the client and their advisors.</p><p><strong>How detailed should diligence be for a smaller deal?</strong></p><p>Scale the scope to the business decision. Even a light review should state its boundary, evidence, and exclusions so readers know what it does not establish.</p><h3>The report is the beginning of the diligence, not the end</h3><p>A technology diligence report does not tell your client what to do. It tells them what is known, what is assumed, and what is still dark. Advisors who read it at that level turn a procurement artifact into decision material, and that is what clients remember.</p><p>CTO Input performs independent technology and cybersecurity diligence and helps investors and their advisors interpret the results. If a report on your desk raises questions its summary cannot answer, those questions are usually worth one more week of scope. Ask them before the deal teaches you the answers, and call us if you want a second read.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=19f0eca73228" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>