Technical due diligence checklist for investors and acquirers
A practical technical due diligence checklist for investors and acquirers: code, infrastructure, security, open-source licences, people risk and documentation.
An investor is two weeks from closing a round in a B2B software company. The financials are clean and customers are happy. Then someone asks who can deploy the product. The answer is one contractor, working from a personal laptop, with the only copy of the production database credentials. The code is in his personal GitHub account. Nobody in the company has ever run a build.
Technical due diligence exists to find this kind of risk before money changes hands. It is not a code review for style. It answers a narrower set of questions: does the company own and control its technology, can the product keep running and growing, what would it cost to fix what is broken, and what could go badly wrong. A focused review over one to three weeks, with access to the right people and systems, is usually enough to answer those questions with evidence.
Scope the review around the deal
Different deals need different depth. Agree the scope with the investor or acquirer before starting.
- Early-stage investment: focus on ownership, key-person risk, security basics and whether the architecture can support the growth plan.
- Growth investment: add scalability evidence, engineering process, cost of infrastructure and technical debt.
- Acquisition: add integration effort, licence compliance in detail, data protection obligations and contracts with technology vendors.
Ask for a data room with architecture documents, repository access, infrastructure account read access, and time with the CTO and at least one other engineer. Talking only to the CTO gives you one view. Engineers closer to the code often describe a different reality.
Code and architecture
The goal here is not to judge every line, but to see whether the codebase can be maintained and extended by people other than its authors.
- Repositories: where the code lives, who owns the organisation account, and whether all production code is in version control.
- Build: can a new engineer clone, build and run the product from documentation? Try it.
- Architecture: a current diagram of components, data stores and integrations, and whether it matches what is deployed.
- Tests: presence of automated tests, whether they run in CI, and whether they pass. Coverage numbers matter less than whether critical paths are tested.
- Dependencies: how out of date frameworks and libraries are. A framework several major versions behind can mean a costly upgrade.
- Hotspots: files changed most often and with most bugs. Git history shows this quickly.
# files changed most often in the last year
git log --since="1 year ago" --name-only --pretty=format: \
| grep -v '^
{{ pageBg }}
Infigini IT Services · Dehradun, India
Software, cloud and AI systems, built to last.
Infigini designs, builds and operates custom software for universities, healthcare providers and enterprises. Our work ranges from ERP platforms and AI knowledge assistants to the cloud infrastructure they run on.
{{ marquee }}
Services
Nine disciplines, one engineering team.
The same team handles architecture, build and production, so nothing is lost passing work between departments.
Our products
We also build products of our own.
Two proprietary platforms we own and operate, plus open-source libraries published on GitHub and npm. The patterns we recommend to clients come from running them.
Engineering stack
The technologies we use, organised by layer.
About Infigini
IT systems that organisations depend on every day.
Infigini IT Services builds software that simplifies infrastructure management and supports new ideas. We work with developers and organisations to build, deploy and scale their systems, with a focus on security, scalability and ease of use.
Our work covers campus ERPs used by thousands of students, AI assistants on Azure, appointment systems for clinics and hospitals, and the cloud servers they run on. We look after these systems from the first requirement through years of production.
Mission
To give organisations scalable IT systems that simplify infrastructure management, so that businesses of any size can work more efficiently and grow faster.
Vision
To become a global provider of next-generation IT solutions that integrate advanced technology into everyday operations.
Our values
{{ v.n }}
{{ v.t }}
{{ v.d }}
Industries
The sectors we work in.
Services
Services built around your operations.
One engineering team covers architecture, build and production operations. Choose a single discipline, or bring us in for the whole system.
Specialised services
Looking for something specific?
← All services
Service {{ svc.n }}
{{ svc.title }}
{{ svc.long }}
What's included
—{{ it }}
Loading…
Sound familiar?
{{ land.problemsTitle }}
What's included
{{ land.includesTitle }}
{{ x.n }}
{{ x.t }}
{{ x.d }}
Ways to work with us
{{ land.plansTitle }}
How it works
{{ land.stepsTitle }}
{{ st.n }}
{{ st.t }}
{{ st.d }}
Why Infigini
{{ land.whyTitle }}
Technologies we use
{{ t }}
FAQ
Questions we get asked.
Industries
Industries we build for.
Most of our work is for organisations whose systems carry real operational weight: campuses with thousands of students, clinics booking patients all day, and enterprises whose HR and finance processes cannot stop. These pages cover what we build for each sector.
Projects · {{ projectCount }}
Our work, from 2020 to today.
This list covers our platforms, client systems and open-source libraries. Client names are withheld at their request.
← All projects
{{ proj.cat }} · {{ proj.year }}
{{ proj.title }}
{{ proj.summary }}
Client{{ proj.client }}
Year{{ proj.year }}
Category{{ proj.cat }}
Visit live ↗
Context
{{ proj.ctxText }}
The challenge
{{ c.n }}{{ c.t }}{{ c.d }}
What we built
{{ b.n }}{{ b.t }}{{ b.d }}
How it fits together
{{ proj.architecture }}
Why this stack
{{ t.t }}{{ t.d }}
Related services and reading
Products
Platforms we run. Libraries we publish.
TechLogHub and EasySiteControl are proprietary platforms that Infigini owns and operates. Our open-source libraries are on GitHub and npm for anyone to use, and we use them in client projects too.
Proprietary platforms
Proprietary · Live{{ p.year }}
{{ p.title }}
{{ p.summary }}
{{ p.stackLine }}
Open-source libraries · GitHub & npm
{{ l.title }}
{{ l.year }} · {{ l.stackLine }}
{{ l.body }}
How we work
Five stages, from first conversation to production.
Each stage ends with a deliverable you keep. You get software you can use every two weeks, so nothing important arrives as a surprise at the end.
{{ s.n }}
{{ s.t }}
{{ s.d }}
You receive{{ s.out }}
Journal · {{ postCount }} articles
Notes from the engineering team.
Practical write-ups on cloud and DevOps, AI systems, ERP platforms and the frontend and backend work behind them, plus guides for teams planning a software project.
← Journal
{{ post.cat }} · {{ post.updatedText }} · {{ post.read }} read
{{ post.title }}
{{ post.dek }}
{{ post.byline }}
Loading article…
{{ b.x }}
{{ b.x }}
{{ b.x }}
Glossary
Terms we use, in plain English.
Short definitions of {{ glossCount }} cloud, DevOps, AI, data, security and business software terms, each with an example and links to the guides and services where it matters.
← Glossary
Definition
{{ term.term }}
{{ term.short }}
Loading…
{{ b.x }}
{{ b.x }}
{{ b.x }}
FAQ
Common questions.
These cover scope, timelines, ownership and what happens after launch. If your question isn't here, write to us.
{{ f.a }}
Contact
Tell us what you are building.
A few sentences are enough to start. We reply within one business day.
Registered office11 Shree Ram Puram Lane No.2,
Kanwali Road, Dehradun,
Uttarakhand 248001, India
GSTIN05AAIFI1118B1Z3
What happens next
{{ s.n }}{{ s.t }}{{ s.d }}
Thank you. We have your message.
An engineer will reply within one business day.
Legal
{{ legalTitle }}
Last updated 9 November 2026
{{ x.eyebrow }}
{{ x.h }}
Talk to us