What a technology due diligence audit covers
- Software and architecture. How the product is built, how well, and who else could maintain it.
- Scalability. Whether the systems can carry the growth the deal model assumes.
- Infrastructure and cost. Hosting, age of the equipment, and what it costs to run.
- Data. Whether customer, order and financial data reconcile, and where they live.
- Security and access. Who holds the passwords, the domains, the code and the accounts.
- People and process. How much of the operation depends on one person, and what is documented.
- Vendors and licenses. Third-party software, contracts and anything the business does not actually own.
What you receive
- A written assessment in language owners, investors and lenders can act on.
- A risk register: what could fail, what is undocumented, and what depends on a single person or vendor.
- A remediation plan, ordered by what affects value most.
- A debrief with your deal team, so the findings reach the people making the decision.
The review is scoped to the questions the deal needs answered and the time the deal allows.
Who it is for
- Acquirers and private investors evaluating a company whose value depends on its software or systems.
- Owners preparing to sell or raise, who want to find the problems before a buyer does.
- Lenders and boards who need an independent view of a technology they did not build.
Proof: acquisitions I have assessed and integrated
At Profit Streams, a technology rollup in restaurant point of sale, online reservations, reviews and loyalty, I was the product architect. I worked with the CEO on M&A diligence to identify and evaluate acquisition targets, carried out the technical assessments of prospective acquisitions, and then led the integration of the companies we bought into one product suite. I oversaw millions in monthly spend and acquisitions.
So I have had to live with my own findings. Whatever a review missed before closing became my problem to integrate afterwards, and that is the standard I review to.
I have also founded, co-founded or helped lead more than 20 companies, raised capital, and taken Set Jet to the doorstep of a NASDAQ listing. And I have done the fixing a review recommends: see the case studies.
After the report
For buyers, I can stay on to stabilize and integrate what you acquired. For owners, I can lead the remediation before you go to market. More detail is on the technology due diligence service page.
Frequently asked questions
Is this a software due diligence or an IT due diligence?
Both. The review covers the software a company has built and the technology it runs on: infrastructure, data, security, vendors and the team.
Do you review source code?
Yes, where the target's value depends on its software. I look at how it is built, how it is maintained, and whether someone other than the original author could take it over.
Are you a large firm?
No. III, LLC is my own practice, based in Scottsdale, Arizona, and working with buyers and sellers across the United States. You work with me directly.
Can the review be kept confidential from the target's staff?
The scope and the way the review is run are agreed with you first, including who at the target is told and when.
We are selling in a year or two. Is it too early?
No. It is far better to find and fix problems on your schedule than on a buyer's. The two-minute scorecard is a quick first read.