The Integration Plan: Sequencing the First Hundred Days

An integration plan puts the work in order. The plan states what has to be true on the first day, what follows across the first hundred, what each item cannot start until another has finished, who is answerable for it, and what is deliberately left alone until later. The ordering is the whole value. A complete list of everything that must eventually change is not a plan.

Underneath that sits a single idea worth holding on to. Two teams handed exactly the same list of tasks will produce two different outcomes, and the difference is not effort or talent. The difference is that one team worked out which items were holding the others up and started there. The other team started with whatever looked most inviting on a Monday morning. An ordering is a claim about dependence, and a claim about dependence can be checked. A list makes no claim at all. Nobody ever argues with a list.

Harivansh Packaging Limited, an invented listed manufacturer, makes rigid and flexible packaging for customers in food and personal care. Harivansh Packaging bought Sundarban Polymers Private Limited outright, a business that is unlistedA company whose shares are not admitted to trading on any exchange, so there is no market price for it and no public register of holders to read. and makes flexible packaging films. Enterprise value was Rs 1,320 crore. Deduct the Rs 180 crore of net debt that Sundarban Polymers carries with it, and what reached the sellers for their shares was an equity value of Rs 1,140 crore. The Rs 1,140 crore, the sum that actually left the buyer and arrived with the sellers, is the amount every figure below is set against. The Rs 1,140 crore was settled out of two pockets. Rs 140 crore came off the buyer's own balance sheet, emptying the cash line entirely, and the remaining Rs 1,000 crore was drawn as fresh borrowing on a facility carrying a contracted rateA rate written into one particular borrower's own facility agreement. It describes that agreement and says nothing about what borrowing costs anybody else. of 9.0 per cent.

What is an integration plan, and how is it different from a list?

A list of integration tasks is easy to produce and almost always accurate. Any team that has just bought a business, asked what has to change, will produce thirty items inside an hour: the two purchasing arrangements, the two payroll runs, the two sets of customer terms, the two ways of quoting a job, the two email systems, the two sets of safety procedures. None of it is wrong. All of it will eventually have to be dealt with. And a team holding that document has a document, not a plan.

The difference between a list and a plan is that a list says what has to change and a plan says what has to change first. The distinction sounds small and is not. An ordering carries information a list simply does not contain. An ordering says that the purchasing arrangement cannot be renegotiated before somebody is answerable for deciding between the two businesses. The same ordering says the first measurement cannot happen before there is something fixed to measure against. Both of those are testable statements. Somebody can look at them and say no, those two can in fact run in parallel. Nobody can look at a list and say that. A list has committed to nothing.

Think of a household moving to a new flat. Everybody can produce the list: transfer the electricity, redirect the post, register the children at the nearer school, buy a second cupboard, repaint the small bedroom. A smooth move and a miserable one differ in one respect: knowing that the school registration has a queue behind it and the cupboard does not. The registration goes on Monday and the cupboard goes whenever. The list is identical in both households. The order is what makes one of them sleep.

A team holding a complete list and no order will start with whatever is easiest to start, and that is not a criticism of the team, it is a prediction about how people behave when the next step is unspecified. The easiest thing to start is usually the most visible and the most enjoyable to talk about, and it is almost never the thing holding four other items up. The programme therefore spends its first six weeks producing a very good combined brand presentation. Meanwhile the supply arrangement carrying the saving has not been opened.

Why a hundred days, and not some other number?

The first hundred days is a working convention rather than a rule, and saying so plainly is more useful than defending it. Nothing in company law, in any listing requirement, or in the purchase agreement itself makes day one hundred different from day ninety four. No regulator publishes it and no standard sets it. The convention survives because two pressures happen to meet somewhere around there. Once those two pressures are understood, the number can be moved to fit the situation at hand without losing anything.

The first pressure is that the window has to be long enough to finish something real. Renegotiating one shared supply arrangement between two companies that have never bought together is not a two week job. Somebody has to establish what each side currently pays, get both sets of terms in front of one person, work out which of the two contracts can actually be opened without penalty, and then hold a conversation with a supplier who now has one customer where it used to have two and knows it. All of that is weeks of work before anything is signed.

The second pressure runs the other way. Everybody who arrived on the morning after completionThe day the shares actually change hands and the money is paid over. Everything before it is conditional and everything after it is the buyer's problem. arrived expecting the place to change. Some of them are looking forward to it and some are braced against it, and both groups are watching. If nothing observable has happened by the time three or four months have passed, the watching stops, and what replaces it is a settled belief that this purchase was paperwork rather than an event. The belief is very expensive to reverse. A second attempt at getting attention costs far more than the first.

A hundred days is roughly 14.29 weeks, and it is worth putting that against something in the transaction itself. The purchase ran 22 weeks between the term sheet and the day it completed, and nine of those 22 weeks were the conditions periodThe stretch between signing and completion during which the items both sides agreed had to be satisfied are worked through. Nothing has been bought yet while it runs.. Twenty two weeks is 154 days. So the first hundred days is 64.9 per cent of the time the transaction itself consumed before anybody had bought anything. The window that everyone treats as a sprint is in fact almost two thirds as long as the entire negotiation that produced it. Anybody who reads a hundred days as barely any time at all has the proportion backwards. The 22 weeks and the nine weeks belong to this transaction alone. A conditions period runs for as long as the conditions themselves take, and that can be three weeks or thirty.

The number itself carries no magic. Where the two businesses share one very large customer whose annual contract falls due in month seven, month seven is the horizon and a hundred days is an arbitrary interruption. The plan should say so. The convention is a default for people who have no better anchor, and a default that gets stated as a default is much harder to misuse than one that gets stated as a rule.

How many workstreams should there be, and what should each one be answerable for?

The practical answer is few enough that one person can hold the whole picture in their head, with each workstream answerable for a result rather than for a function. Both constraints in that sentence do work. The count constraint keeps the coordination load down. The result constraint stops a workstream turning into a standing department.

The difference between a result and a function is worth being precise about. A workstream called procurement is a function: it exists forever, it has no finish line, and asking whether it is complete is not a sensible question. A workstream called one shared arrangement in place with the three suppliers both businesses buy from is a result. Somebody can answer yes or no to it on a given Tuesday. A workstream defined as a result can finish, and a workstream defined as a function cannot. A plan built out of functions has no way of ever ending, and it will quietly convert itself into the permanent management structure of the combined business.

Now the count. The failure mode of too many workstreams is not that the work becomes too big; it is that the coordination becomes the programme. Every pair of workstreams that might have to talk to each other is a potential meeting, a potential interface, a potential handover that somebody has to chase. The number of such pairs is not the number of workstreams. For a count of n workstreams the number of pairs is n multiplied by n less one, divided by two, and that grows far faster than the count written at the front of the plan.

The opposite failure is real and it looks completely different. Too few workstreams and one of them, almost always the one called operations, quietly contains everything difficult. The operations stream holds the systems question, the two safety regimes, the stock in the wrong warehouse and the three people nobody has spoken to yet, and it is being run by whoever was available. The stream will report green for eleven weeks and then report a problem that has been present since week two. Nobody inside it had the standing to raise one part of it above the others.

What actually fixes the order?

The sequence is not a preference and it is not a ranking of importance: it is a finding, and what produces it is the set of dependencies between the items. A saving that requires one renegotiated supply arrangement cannot land before that arrangement is renegotiated. A systems decision that requires a data migration cannot land before the migration. A measurement that requires a fixed comparison point cannot happen before the comparison point is fixed. None of those three sentences expresses an opinion. Each is a statement about the world that somebody can be wrong about, and being wrong about it is discoverable.

The most valuable result of the mapping exercise has almost nothing to do with scheduling. Mapping the dependencies converts an argument about priorities into a question with an answer. Before the map, two workstream leaders in a room are two people with different views about what matters, and the one who argues better wins. After the map, the question is narrower and duller and vastly more productive: does one leader's item require the output of the other's, yes or no? If yes, the order is settled and neither person had to win anything. If no, the two can run at the same time and the argument was never necessary.

The same shift appears at a much smaller scale. Two people planning a wedding argue for an hour about whether to book the caterer or confirm the guest list first, and it is a genuine argument because both feel urgent. The moment somebody points out that the caterer needs a headcount, the argument stops. Nobody conceded. The dependency simply removed the need for anybody to have a view.

Look at the two bars that share an edge. The baseline finishes on day 30 and the measurement starts there, not because somebody scheduled it neatly but because a measurement has nothing to compare against until a comparison point exists. Seventy days of trading then have to pass under that fixed point before the first reading means anything. Day 30 plus 70 days is day 100, and the fact that this plan lands exactly on the convention is forced by those two intervals rather than chosen to look tidy. Change either interval and the hundred stops being the answer. The convention did not set the sequence. The sequence happened to meet it.

What belongs in week one, in month one, and by day one hundred?

Three horizons, and each one earns its place by being defined by a different test rather than by a different level of urgency. Urgency is a feeling and everybody in the room has a different one. A test is a question with an answer.

Week one is tested by what breaks if it is not done. Not what is important, not what is visible, but what actually stops working on Tuesday morning if nobody attended to it on Monday. Month one is tested by what has to be settled so that other work can start. The criterion is completely different and catches a completely different set of items. Day one hundred is tested by what has to be finished before the first measurable amount can land at all. Most plans mix all three tests into one list and then wonder why the sequencing meeting takes four hours, and the reason is that the participants are not disagreeing, they are answering three different questions and comparing the answers.

Notice what week one is not. Week one is not for announcing the combined strategy, and it is not for deciding which of two enterprise systems survives. Both of those feel urgent and neither of them breaks anything if it waits. The failures that actually arrive are smaller. An employee does not know who to ask for leave, a customer calls the number they have always called and reaches somebody who says they no longer handle that account, and a supplier's payment run has quietly stopped because a bank mandate was in the seller's name.

Month one carries the items nobody outside the programme will notice and every later item depends on. The degree of combination confirmed in writing, before four workstreams each assume a different answer. The baseline signed off. The workstreams named with one person against each, not a department against each. And the dependency map itself, the one item that turns the remaining seventy days from a wish into a sequence.

How does the plan connect to the figure it has to produce?

Here is what separates an integration plan from a project timetable. A timetable says when things happen. A plan says which of those things is carrying the number, and for this purchase the number is knowable to the rupee.

Work it from the buyer's own ladder. Harivansh Packaging Limited earned profit after tax of Rs 225 crore on 18.00 crore shares, so earnings per share was Rs 12.50/-. Adding Sundarban Polymers brings in profit after tax of Rs 61 crore. The Rs 61 crore is deliberately rounded, it is the value locked across every treatment of this purchase, and on the exact chain the acquired business earns a little more than it. Set against the arrival, the fresh Rs 1,000 crore of borrowing at 9.0 per cent costs Rs 90 crore of interest in the first year. At a 25.0 per cent effective rate that leaves Rs 67.5 crore after tax. Start at Rs 225 crore, add the Rs 61 crore, take away the Rs 67.5 crore, and Rs 218.5 crore is what remains. On an unchanged share count earnings per shareWhat a single share is credited with out of a year's profit, being the profit attributable to holders spread across the shares in issue. Here the count never moves, so every change comes from the profit side. lands at Rs 12.14/-.

Rs 0.36/- across 18.00 crore shares is Rs 6.50 crore of profit after tax that has gone missing. But a plan cannot deliver profit after tax. A plan delivers operating amounts, and the operating amounts are then taxed. Grossing upWorking backwards from an amount that has already had tax taken off it, to find the larger amount needed before tax in order to be left with it. that Rs 6.50 crore at the buyer's own 25.0 per cent effective rate gives Rs 8,66,66,667/-, or Rs 8.67 crore. The Rs 8.67 crore, net of whatever it costs to obtain, is the entire delivery requirement of the plan, and every workstream in it either helps produce that figure or does not.

The size check that keeps the plan honest

Hold Rs 8.67 crore up against Sundarban Polymers Private Limited on its own, whose earnings before interest, tax, depreciation and amortisation (EBITDA) is Rs 132 crore, and it comes to 6.6 per cent. Hold it up against the two businesses together, whose EBITDA is Rs 609 crore, and it comes to 1.42 per cent. One fixed amount, two denominators, two proportions, and neither is truer than the other; what matters is that both are small. Now put the requirement next to the price.

The price is enormous, the annual delivery requirement is small, and plans routinely get sized against the price. The habit has a reason worth naming rather than mocking. Rs 1,140 crore is the number everybody in the building has heard, it appeared in the announcement, and it feels like the measure of how serious this is. But it is a payment that has already left. The payment records what was risked, and it says nothing about how much programme machinery is needed now. A twelve workstream apparatus with a full time coordinator and a weekly steering meeting is a sensible way to chase a large number and an absurd way to chase 1.42 per cent of combined EBITDA.

The balance sheet the plan is written against

One constraint sits underneath everything above and a plan that discovers it in month three has failed at something basic. Emptying Rs 140 crore of cash and drawing Rs 1,000 crore of fresh borrowing leaves the buyer's own borrowings at Rs 1,740 crore, where they stood at Rs 740 crore the week before. On a consolidatedThe two companies' figures added together and presented as though they were a single business, rather than each shown on its own. view the purchase also carries Sundarban Polymers Private Limited's Rs 180 crore of net debt across the line. Combined net debt is lifted to Rs 1,920 crore. Underneath that sits the Rs 609 crore of combined EBITDA. The reading is net debt to EBITDANet borrowings divided by one year of operating profit before interest, tax and the accounting charges. It answers roughly how many such years the borrowings amount to. of 3.15 times, where before the purchase the buyer stood at 1.26 times. Adding 1.89 turns of leverage in a single transaction changes what any plan is allowed to propose. There is a second honest pairing and only a second. On a standalone view the buyer's own Rs 1,740 crore sits against its own EBITDA of Rs 477 crore, and that reading is 3.65 times. Putting a standalone numerator over a combined denominator produces a lower number that looks reassuring and describes nothing. The basis has to be stated every time either figure is quoted.

A first hundred days that needs significant spending is being written against that balance sheet whether it acknowledges it or not, and the plan should say so in its own opening lines rather than find out in a treasury meeting. None of that is an argument for spending nothing. The argument is that the plan should state, in its own words, that the cash position after completion is thin and the borrowings are heavier by 1.89 turns, so any workstream proposing up front spending has to carry that spending in its own numbers rather than assuming a pot exists.

Two things are worth doing with that control. First, move it a little, from day 30 to day 45, and watch the measurement bar slide right by exactly fifteen days. The slide is the arithmetic of dependence and it is dull in the best way: one item moved, one item moved with it, nothing else changed. Second, push it past day 85 and watch the bar vanish instead of sliding. Beyond that point the delay stops being a delay and becomes a loss. The first shared supplier arrangement is already in place, prices have already moved, and any baseline struck now contains part of the very change it was supposed to measure.

Which parts of the plan trace to a line in profit, and which do not?

Run every workstream through one question: does this end in an amount that will eventually appear somewhere in the profit ladder? For some the answer is obviously yes. A shared supply arrangement lowers what the combined business pays for the same material, and that shows up in cost of goodsThe rung of the profit ladder holding what it cost to make or buy the specific things that were actually sold in the period, before the running costs of the business are added on.. A duplicated overhead removed shows up in expenses. A joint customer win shows up in revenue.

For others the answer is just as obviously no, and this is where plans go wrong in a specific and avoidable way. Harmonising two sets of document templates does not produce an amount. Aligning two brand marks does not. Merging two policy manuals into one does not. A workstream that cannot be traced to a line in profit may still be entirely necessary, but it is not part of the delivery of value, and saying which is which up front prevents both from being reported as the same thing.

The right hand column deserves defending. The reflex on reading it is to cut everything in it. Do not. An item in that column can perfectly well be the item that has to happen first: a shared purchase order template may be the mechanism by which the supply arrangement becomes usable at all. Its position in the ordering is a dependency question. Its position in the delivery total is a different question, and answering them separately is the entire point.

How is the plan tracked without the tracking becoming the work?

There is a danger in tracking that rarely gets a warning. The warning sounds like an argument against being organised. A plan with weekly reporting on every stream turns into a reporting exercise that consumes exactly the people who were supposed to be delivering it. The drift happens gradually and every individual step is reasonable. A steering meeting wants visibility. Visibility means a status line per stream. A status line that says nothing looks bad, so each lead writes a paragraph. Paragraphs need collating. Collating needs somebody. Within two months the largest single activity in the programme is describing the programme.

The discipline that prevents it has two halves and both are needed. Report against a baseline and against dates fixed before completion, and report exceptions rather than status. The first half removes the argument about what the target was. The target was written down while nobody yet had a reason to shade it. The second half removes the reward for writing. If the rule is that a stream running to its fixed date says nothing at all, then silence is the normal state and the report is short by construction. The report then carries the three items that have moved, and those three are exactly what the meeting needs to talk about.

Most households already run something like this without calling it a programme. Nobody sends a weekly update confirming that the electricity bill was paid on time; the phone call happens when it was not. Exception reporting is the ordinary way people handle anything routine, and programmes abandon it only because a steering meeting once asked to see everything and nobody wrote down when to stop.

What does the plan say it will not do?

A plan that names what will not be attempted in the first year is a stronger document than one that does not, and the reason is asymmetry. An exclusion written down has to be argued back in, in front of people who can see it was considered and deferred. An exclusion that lives only in somebody's head returns as scope, quietly, usually around month four, carried in by a reasonable person who genuinely does not know it was ever decided.

The exclusions list is also the only part of the plan that keeps it finite. Everything else in the document is a commitment to do something, and documents made entirely of commitments have no natural size. One short list saying what is out gives the programme an edge.

The wording of each exclusion matters as much as the choice of which items to exclude. No item is forbidden forever; every one says not in the first year. The distinction matters. An exclusion phrased as a refusal invites a fight, and an exclusion phrased as a deferral invites a date. The people who wanted the single finance system are not being told no. The refusal is a queue position: the first hundred days is already carrying the items the Rs 8.67 crore depends on, and the single finance system starts after.

What can an ordering not fix?

One honest limitation, and it is the one most likely to be quietly ignored by everybody holding the document. An ordering decides when things can happen and never whether they can. If Rs 8.67 crore of extra operating profit, net of what it costs to obtain, was simply not available from these two businesses put together, then the best sequence anybody has ever written produces the same shortfall on a tidier schedule and with better paperwork.

The tell is easy to spot. A plan whose opening assumes the promised amount will arrive, and spends the rest of itself allocating that amount across quarters, is a schedule for an arrival rather than a plan to produce one. A real plan carries the two questions separately: here is the sequence, and here is what each item is currently believed to yield, with the belief attributed to somebody. The second half is uncomfortable to write. Discomfort is exactly why it gets replaced by the first half.

Who outside the programme cares how this is ordered?

The ordering is not an internal housekeeping matter, and four different readers use it for four different things.

A lender reads the plan for what it demands of a balance sheet that has just taken on 1.89 turns of leverage. Consolidated net debt to EBITDA moved from 1.26 times to 3.15 times on completion, and the lender's question is not whether the integration is well designed but whether the first hundred days requires cash the buyer no longer has. A plan whose early items are decisions and confirmations rather than spending answers that question favourably without arguing. A plan whose first quarter is full of system purchases and site moves does not, however good the sequencing is.

An analyst covering the buyer cannot see the plan and reads for its shadow. The outside sees only what management said the purchase would produce, and whether any comparison point was ever named. If a company states an amount and never states what it will be measured against, an analyst learns something real about how the number was arrived at. The absence of a stated baseline is itself information, and it is available to somebody who has never been inside the building.

The buyer's own board reads the plan for the one thing it can actually control. A board cannot renegotiate a supply arrangement and cannot sequence a data migration. A board can insist that one named person is answerable, that the baseline is fixed before completion rather than after, and that the exclusions are written down. All three are governance decisions, they take a single meeting, and each of them makes every later meeting shorter.

And now the household version. The discipline is not a corporate invention. A couple taking on a home loan and a renovation in the same season is running an integration. The dependency is the same shape: the loan disbursement has to land before the contractor starts, and the contractor cannot be sequenced around a date nobody has confirmed. The baseline is the same too, and it is the one people skip. Without a written record of what the electricity bill and the monthly grocery spend were before the renovation, nobody can say afterwards what the new place actually costs to run, and an opinion stands in for a figure for years.

Harivansh Packaging Limited, Sundarban Polymers Private Limited, Devyani Kulkarni and Ashwin Rege are invented.
Educational material. Not advice on any investment, tax, budget or market position.