When to run it
A closed acquisition or add-on, a 100-day plan with technology initiatives, and a new management team that needs facts.
Day one after close.Know what you bought.
The first 100 days: a technology baseline
The playbook in one paragraph
The deal has closed and the value-creation plan depends on technology. Ana builds a baseline of code, cloud, cost and delivery health in the first weeks, so the 100-day plan rests on evidence and progress can be measured.
Works with
- Repositories, cloud accounts and CI/CD at the company (read-only)
- Cloud and SaaS billing
- Ticketing and incident data
What Ana needs from you
- The value-creation plan
- Integration plans for add-ons
- Who owns technology at the company
How Ana runs it
Step by step.
5 steps from trigger to done - each one visible to your team as it happens.
- 01
Baseline the estate
Ana inventories applications, infrastructure, vendors and spend, and scores code, security, cloud and delivery health.
- 02
Find quick wins
Cost waste, critical exposures and delivery bottlenecks that can be fixed in weeks are listed with owners and effort.
- 03
Map plan dependencies
Each 100-day initiative is mapped to the systems it depends on, with the technical risks that could delay it.
- 04
Set measurable targets
Ana proposes the metrics to track - spend, exposure, deployment frequency, incident rate - against the baseline.
- 05
Track progress
The baseline is refreshed on a schedule so the operating team sees movement, not anecdotes.
Who approves what
Approval gates
- Access
- Company technology leader
- Plan changes
- Operating partner and CEO
- Board reporting
- Operating partner
What you get
Deliverables
- 01Technology baseline across code, cloud, cost and delivery
- 02Quick-win list with owners
- 03Initiative-to-system dependency map
- 04Tracked metrics against baseline
What usually goes wrong
And how Ana handles it.
Risk
A baseline that goes stale
It is refreshed on a schedule, not produced once.
Risk
Plans built on management’s assumptions
The baseline is drawn from systems, with evidence for each figure.
FAQ
Common questions.
Diligence answers whether to buy; the baseline gives the new owners a measured starting point and keeps tracking it.
Keep going
Related playbooks.
Private equity
Technology diligence before investment committee
A deal is heading to investment committee and the technology picture is a management deck. Ana reads the whole codebase, cloud and contract set in the data room and returns an evidence-linked view of risk and value-creation levers.
Read the playbook →Private equity
Running a portfolio-wide vulnerability program
Operating partners need to know which portfolio companies carry real cyber risk and whether it is going down. Ana normalizes findings across companies, ranks them by real exposure, routes fixes to named owners and verifies closure.
Read the playbook →Software
Upgrading a framework across dozens of services
A major framework or runtime version is going end-of-life and it touches every service. Ana plans the migration, upgrades each service in its own branch, fixes what breaks, and hands your team small, tested pull requests instead of one terrifying diff.
Read the playbook →See it in your stack
Run this playbook on your systems.
Thirty minutes, your repositories and cloud, one real instance of this job.