Why the first 100 days set the trajectory
The first 100 days after a retail or commerce acquisition are disproportionately important for technology. Not because you need to transform everything immediately, but because the decisions you make, and the decisions you deliberately defer, in this window establish the trajectory for the entire hold period.
I have seen this go both ways. Operating teams that move methodically through the first 100 days, stabilising operations, assessing the team, and building a realistic roadmap, consistently outperform those that arrive with a predetermined technology agenda and start executing before they understand what they have bought. The urge to act is understandable. You have spent months on due diligence, you have a value creation plan, and the clock is ticking. But premature action in technology creates problems that compound over years.
The playbook I use, refined across multiple post-acquisition engagements, breaks the first 100 days into three phases: stabilise and assess, deliver quick wins and make key team decisions, then build and align the roadmap.
Days 1 to 30: stabilise and assess
The first 30 days have one objective: understand what you have actually acquired at an operational level, without breaking anything. The due diligence gave you a snapshot. Now you need the full picture.
Do not touch anything yet
This sounds obvious, but it is the most commonly violated principle in post-acquisition technology management. New owners arrive with energy and a mandate for change. The temptation to start “fixing” things on day three is real. Resist it. Every change you make before you fully understand the system creates risk you cannot properly assess.
I worked with a PE-backed retailer where the new operating team decided, in the second week after close, to migrate email systems to the portfolio standard. It seemed low risk. It took down the integration between the email platform and the order management system for 72 hours during a peak trading period, because nobody had mapped the dependency. Stabilise first.
Meet the team, individually
Schedule one-on-one meetings with every member of the technology team in the first two weeks. Not group presentations. Individual conversations. You are trying to understand three things: what each person actually does and owns, what they think the biggest risks and opportunities are, and whether they are planning to stay.
Acquisitions create uncertainty, and the people most likely to leave are often the ones you most need to retain. Senior developers and architects with deep institutional knowledge will have recruiters calling them the moment the acquisition is announced. If you do not engage them early and signal that they are valued, they will be gone before you understand what they know.
Review every vendor contract
Pull every technology vendor contract and create a single register: vendor name, what it does, annual cost, contract end date, auto-renewal terms, termination clauses, and who internally owns the relationship. This exercise alone will surface surprises. In almost every acquisition I have been involved with, the contract review reveals at least two situations where the business is either overpaying significantly or locked into terms that will constrain the value creation plan.
Pay particular attention to contracts with renewal dates in the next six months. These are your first negotiation opportunities, and also your first risks if unfavourable terms auto-renew because nobody was watching.
Map critical systems and dependencies
Create a systems map that shows every major technology platform, how they connect, what data flows between them, and who is responsible for maintaining each integration. This does not need to be an exhaustive enterprise architecture document. It needs to be accurate enough that you can identify single points of failure and understand what will break if any one system goes down.
The due diligence report should have given you a starting point, but the operational reality is always more nuanced than what surfaces in a time-limited assessment. This is where the individual conversations with team members pay off: the people who maintain these systems daily know where the real risks are.
Days 30 to 60: quick wins and team decisions
With a solid understanding of the landscape, the second phase focuses on capturing early value and making the critical team decisions that will shape everything that follows.
Vendor renegotiation
This is the most reliable quick win in post-acquisition technology management. Most mid-market retail businesses have not renegotiated their major vendor contracts in years. They are often paying list price or close to it, on terms that favour the vendor.
A change of ownership is a natural negotiation trigger. Vendors know that acquisitions bring scrutiny, and they would rather renegotiate than lose the account to a competitor the new owners prefer. In my experience, focused vendor renegotiation in the first 60 days typically delivers 15% to 30% savings on the two or three largest technology contracts. For a business spending $2M annually on technology vendors, that is $300K to $600K in recurring savings with relatively little effort.
Start with the largest contracts by annual spend. Bring in procurement expertise if the operating team does not have it. And do not accept the first counter-offer. Vendors have more flexibility than their initial response suggests.
The CTO assessment
This is the single highest-leverage decision in the first 60 days, and it requires careful thought rather than a snap judgement. The question is not whether the current CTO is competent. It is whether they are the right person to lead technology through the value creation plan.
Many acquired businesses have CTOs who are excellent operators: they keep the lights on, they know the systems intimately, and they have strong relationships with the team. But the post-acquisition CTO role often requires different skills: the ability to build a strategic roadmap, manage a larger team, work with a board, execute a transformation programme, and communicate technology risk and investment needs to non-technical stakeholders.
Assess the current CTO against the specific demands of your value creation plan. If there is a gap, you have four options: develop the current CTO with coaching and support, supplement them with a senior hire who fills the gap, bring in an interim or fractional CTO to bridge while you recruit, or replace them. Each option has trade-offs, and the right answer depends on the specific situation.
What you should not do is remove the CTO without a succession plan. A leadership vacuum in technology during the post-acquisition period creates cascading problems: the team loses direction, decisions get deferred, and the institutional knowledge the CTO holds walks out the door with them. If you are going to make a change, have the replacement identified, if not already onboarded, before you make the move.
Security posture review
If the due diligence surfaced any security concerns, the first 60 days is when they need to be addressed. At minimum, ensure that access controls are reviewed post-acquisition, that former employees and contractors no longer have active credentials, and that basic security hygiene, patching, backup verification, incident response planning, is in place.
Security issues discovered after a breach are orders of magnitude more expensive than security issues addressed proactively. This does not require a full security transformation in the first 60 days. It requires a baseline assessment and immediate remediation of critical gaps.
Data visibility
One of the most common frustrations for new owners is the inability to get reliable operational data out of the acquired business. Revenue by channel, customer acquisition cost, inventory turns, platform performance metrics: the data exists somewhere, but extracting it into a format that supports decision-making is often surprisingly difficult.
Establishing basic data visibility in the first 60 days, even if it is a manually updated dashboard at first, gives the operating team the information they need to make evidence-based decisions. It also surfaces data quality issues early, which informs the longer-term data strategy.
Days 60 to 100: roadmap and investment plan
The final phase of the first 100 days is about translating everything you have learned into an actionable technology roadmap that aligns with the value creation plan.
Build the technology component of the value creation plan
The technology roadmap should directly map to the value creation plan. Every initiative on the roadmap should have a clear connection to either revenue growth, cost reduction, risk mitigation, or operational scalability. If a technology initiative cannot be tied to one of these outcomes, question whether it belongs in the first 12 to 18 months.
Structure the roadmap in three horizons. The first horizon, covering months one to six, focuses on stabilisation, quick wins, and addressing critical risks. The second horizon, months six to twelve, tackles the strategic initiatives that enable the growth plan: platform upgrades, new channel capabilities, data infrastructure. The third horizon, months twelve to eighteen and beyond, addresses longer-term architectural improvements and innovation.
Prioritise ruthlessly
The biggest mistake I see in post-acquisition technology roadmaps is trying to do too much at once. A team that was maintaining a stable operation is now being asked to simultaneously upgrade the commerce platform, migrate to a new ERP, implement a CDP, rebuild the mobile app, and modernise the infrastructure. It does not work. The team burns out, nothing gets delivered well, and the operating partners lose confidence in the technology function.
Pick the three to five initiatives that will have the most impact on the value creation plan in the first twelve months. Sequence them based on dependencies and team capacity. Be explicit about what you are choosing not to do and why. A focused roadmap that delivers results builds credibility and funding for the next phase. A sprawling roadmap that delivers nothing erodes both.
Set governance
Establish a technology governance cadence that connects the technology team to the operating partners and the board. Monthly technology updates that cover progress against the roadmap, key risks, budget tracking, and upcoming decisions. Quarterly deeper reviews that assess whether the roadmap is still aligned with the value creation plan and adjust as needed.
This governance structure serves two purposes. It gives operating partners visibility and confidence. And it gives the technology team a structured way to escalate issues, request resources, and get decisions made. Without it, technology becomes a black box that only gets attention when something breaks.
Technology standardisation across a PE portfolio
If the acquisition is part of a broader portfolio strategy, the question of technology standardisation will come up quickly. Should all portfolio companies run on the same commerce platform? Should there be a shared data warehouse? Should we standardise on common vendors?
The answer is nuanced. Standardisation delivers real value in specific areas: shared services like security monitoring, identity management, and data infrastructure; common reporting and analytics platforms that give the fund visibility across the portfolio; and vendor consolidation that creates negotiating leverage.
Where standardisation becomes premature and counterproductive is at the application layer. Forcing a recently acquired business onto the portfolio’s standard commerce platform in the first year, when the business has different customers, different operations, and different requirements, is a recipe for a failed migration that consumes the entire technology budget and delays value creation by 18 months. I have seen this happen more than once.
Start with shared services and data visibility. These deliver value without disrupting the acquired business’s operations. Save application-layer standardisation for when you have a clear business case and the operational stability to execute a migration safely.
Common mistakes
The same mistakes appear in post-acquisition technology management with remarkable consistency.
Replatforming too early is the most expensive one. The impulse to move to a “better” platform is strong, especially when the due diligence surfaced concerns about the current technology. But replatforming a retail business is a 12 to 24 month programme that consumes enormous team capacity. Starting it in the first six months, before you fully understand the business requirements and before the team is stable, dramatically increases the risk of failure.
Underestimating the existing team is the most common one. New owners often assume the technology team needs to be upgraded because the systems are not modern enough. In reality, the team that built and maintains the current systems often has deep operational knowledge that is irreplaceable in the short term. Assess capability fairly before making changes.
Ignoring technical debt is the most insidious one. Technical debt does not create visible problems until it does. It compounds quietly, slowing development velocity, increasing incident frequency, and making every future change more expensive. If the due diligence identified significant technical debt, the first 100-day plan needs to include a strategy for managing it, even if that strategy is simply allocating 20% of development capacity to debt reduction.
Measuring progress: what good looks like at day 100
At the end of 100 days, you should be able to answer the following questions with confidence. Do we have a complete and accurate map of our technology landscape, including all systems, integrations, vendor contracts, and team capabilities? Have we stabilised operations and addressed any critical risks identified in due diligence? Have we made or have a clear plan for the CTO decision? Have we captured quick wins, particularly through vendor renegotiation? Do we have a prioritised, resourced, sequenced technology roadmap that directly supports the value creation plan? Do we have governance in place to track progress and make decisions?
If the answer to all of these is yes, you are in good shape. The technology function has a clear direction, the team knows what is expected, and the operating partners have visibility into progress and risk. The trajectory is set.
If the answer to any of these is no, focus on closing the gaps before moving to the next phase. The compounding cost of unresolved ambiguity in post-acquisition technology management is real. Every week of unclear direction is a week of deferred decisions, lost productivity, and eroded team confidence.
Next steps
If you are navigating the post-acquisition technology phase for a retail or commerce business, get in touch. I work with PE operating partners and portfolio company leaders as a fractional CTO or technology advisor during the critical first 100 days and beyond. The goal is to stabilise operations, build a realistic roadmap, and ensure that technology accelerates the value creation plan rather than constraining it.
What to read next
- Technology due diligence: what investors actually need to know — The due diligence work that should inform everything that happens in the first 100 days.
- What usually goes wrong in retail technology transformation — The failure patterns that technology programmes must actively avoid.