The First 30 Days After You've Bought It: A New Operator's Field Manual

The money has cleared. The seller has handed over the logins. You own a thing now – a newsletter, a micro-SaaS, a content site, whatever it was you spent weeks underwriting. And the first thing most new operators do with it is reach in and start changing it.

That instinct is what loses the deal after the deal is done.

Almost all the writing about small acquisitions stops at the handover. It tells you how to value the asset, how to do diligence, how to structure the transfer. Then the wire goes through and the advice goes quiet – exactly at the point where the asset is most fragile and you know the least about how it actually runs. The first 30 days is where the cumulative value of everything you checked before the purchase is either preserved or quietly destroyed. This is the playbook for preserving it.

The trap: changing things in week one

The failure pattern looks like this. A new owner takes possession on a Monday, looks at the homepage, decides the copy is weak, rewrites it by Wednesday, tweaks the pricing on Thursday, and pushes a redesign over the weekend because they were excited and it was theirs now.

Two months later, a metric has moved – usually the wrong way – and they cannot tell you why. Was it the copy? The price? The redesign? Seasonality? The natural churn that was always baked in? They changed four things at once, so the signal is gone. There is no way back to the baseline, because the baseline was the asset as the seller ran it, and they overwrote it in their first week.

The data the seller handed you describes the business as it was. The moment you change it, that data stops describing anything you can act on. You have spent good money to acquire a working system and a clean read on how it performs, and then you have blinded yourself to the second half before you used it.

So the opening rule of the first 30 days is narrow and strict: nothing changes in week one except the things that have to change. Ownership. Access. Billing. The plumbing. Not the product, not the pricing, not the brand. Those come later, deliberately, one at a time.

Week 1 – the ownership-and-access pass

Week one is logistics. It is unglamorous and it is the most important week of the four, because anything you miss here becomes a problem you discover at the worst possible moment – usually when an account locks you out or a renewal fails silently.

Work through every system the business touches and move it into your control. The list is longer than people expect:

Domain registrar and DNS
Hosting and any servers
The code repository
Analytics
Payment processor (Stripe, Paddle, whatever it runs on)
Email service provider and the sending domain
The customer-support inbox
Social accounts
Advertising accounts, if there are any

For each one, the move is not "I have the password." The move is: log in from a clean browser, change the recovery email to yours, remove the seller's access, and enable two-factor authentication on your own account. The recovery email is the one people skip, and it is the one that matters most – whoever controls the recovery address ultimately controls the account, regardless of who knows the current password. Microsoft has reported that enabling multi-factor authentication blocks over 99.9% of automated account-takeover attempts, which tells you how much of your asset's security sits in this single unglamorous step (Microsoft Support).

Treat this week as the diligence pass you could not fully run before you owned the thing. Before the sale, you were looking from the outside. Now you are inside, and you can verify what was actually true. If something is broken here – an account that was never really transferable, a payment rail tied to the seller's personal identity, a domain registered under a name that is not on the bill of sale – that is renegotiation territory, and you want to find it while you are still inside the support window the seller agreed to. This is the buyer-side mirror of the work a careful seller does before listing; if you want to see what that looks like from the other chair, the asset inventory that turns a scary handover into a boring one is the seller's version of the same checklist.

Week 2 – the operating baseline

With ownership secured, week two is for observing. Not improving. Observing.

You already have the metrics, because those came with the sale. What you do not have, and what the spreadsheet never tells you, is what it actually takes to keep this thing running. That is the gap week two closes.

Sit with the business as it operates and write down the things nobody documented. Find where the founder's brain sat in the workflow – the decisions that ran through them that no system ever captured. Watch a normal support week and note what kinds of questions come in. Trace where churn actually happens: a cancelled card is easy to see, but a quiet non-renewal or a reply-to-the-email cancellation that nobody flags will hide from you. And work out how the moving parts connect when something breaks at 11pm.

The output of week two is a written operating manual: the document you wish the seller had handed you and didn't, because most of it lived in their head and never made it into the sale. This is the same owner-dependency problem that makes businesses hard to sell in the first place – build it to sell from day one covers why founders create it and how. As the buyer, you inherit it, and writing the manual is how you dissolve it. The bonus is durable: do this properly once and you own a template you can run on the next acquisition, and the one after that.

Week 3 – one experiment, no commitments

Now, and only now, you are allowed to change something. One thing. Small. Reversible.

A single subject-line test. One pricing-copy tweak on a quiet page. One outreach email to a churned customer. A single A/B test on a renewal reminder. The point of week three is not to optimise the business – you do not understand it well enough yet to optimise anything. The point is to verify that you can change one thing and read the result cleanly.

This matters because of a principle every experimenter learns the hard way: change two things at once and you can no longer attribute the outcome to either. The other variable becomes a confounder, and your result is noise. As one analytics team puts it, bundling changes destroys the information you need to learn anything from them (Statsig). The new operator who redesigns everything in week one has bundled a dozen changes and kept none of the signal. The operator who moves one lever in week three keeps all of it.

There is a second prize hiding in this week. New owners regularly discover, when they try to change one small thing, that some part of the asset they assumed they understood is a black box – the email automation nobody can fully trace, the integration that breaks when you touch it, the metric that does not respond the way it should. Far better to learn that on a subject-line test than on the headline number that pays your mortgage.

Week 4 – the next 90 days plan

By the end of week four you are holding something genuinely valuable: clean ownership, a written operating manual, one verified change-loop, and a real read on where the asset's risks actually sit. That is a stronger position than most buyers reach in six months. Now you plan.

Write down three things, and only three:

The one metric you will watch weekly. Not a dashboard of twenty. The single number that tells you whether the asset is healthy. For a newsletter it might be sponsor sell-through; for a SaaS, net revenue retention. Pick the one that would worry you most if it moved.
The one structural change you will commit to over the next 90 days. One real improvement, chosen because the manual you wrote in week two showed you where the genuine leverage is – not because it caught your eye in week one.
The one thing you will explicitly not touch for six months.

That third item does the quiet work. It is the easiest to skip and the hardest to honour, because owning something makes you want to put your hands all over it. But the discipline of a no-touch list is what separates an operator who compounds an asset from one who fiddles it into the ground. Indiemaker's whole worldview rests on this: stability is a feature, and maturity is value. Most small assets are damaged not by neglect but by restlessness – the owner who cannot leave a working thing alone. Naming what you will not touch is how you protect it from your own enthusiasm.

What goes wrong if you skip the 30 days

Two failure patterns are worth naming plainly, because you will recognise the temptation toward both.

The first is the improver. They change the homepage in week one because it is theirs now and they have opinions. They mean well. Two months later the numbers have shifted and they cannot say whether their changes helped, hurt, or did nothing, because they never held the baseline still long enough to find out. They bought a clean signal and spent it on a redesign.

The second is the passenger. They never write the operating manual, so six months on they are still emailing the seller to ask how the sponsor process works or where a particular setting lives. The dependency they bought the business to escape has simply transferred to them, except now the person who holds the knowledge has moved on and stopped replying.

Both lose money, and both were avoidable for the price of four disciplined weeks. The 30-day playbook is the cheapest insurance policy in small-deal acquiring – it costs you nothing but the patience to not change things you do not yet understand.

A worked example

Take a $30,000 newsletter with 8,000 subscribers, sponsor-funded. Here is the playbook running in real time.

Week 1. The new owner moves the domain, the email service provider, and Stripe into their own accounts, changes every recovery email, enables two-factor authentication, and revokes the founder's access. In doing so they notice the sending domain was authenticated under the seller's personal Google account – a transfer landmine they raise while the support window is still open.

Week 2. They write the operating manual: how the founder chose sponsors, what the typical reply-to-the-newsletter support load looked like, which two sponsors accounted for most of the revenue. The concentration risk was visible in the numbers; the reason for it only became clear from the notes.

Week 3. One A/B test on a single subject line. Nothing dramatic. The result is clean and readable, and – more usefully – it confirms the sending setup actually works under their ownership.

Week 4. The plan: one metric (sponsor sell-through), one change (rewrite the sponsor pack over the next quarter, because the manual showed that is where the leverage sits), one no-touch (the editorial voice, frozen for six months, because that voice is what the 8,000 subscribers actually subscribed to).

Now run the same deal the other way. The buyer redesigns the newsletter template in week one because the old one looked dated. Open rates drop. Was it the template, the new sponsor mix they also changed, or ordinary churn? Three variables moved at once. No signal is recoverable. They are now operating blind on an asset they paid five figures to understand.

Same business. Same price. The only difference is whether the new operator could sit on their hands for a month.

That patience is the actual skill. The repeat acquirers – the buyers who turn one good deal into a portfolio – are not better at diligence than first-timers. They are better at the first 30 days. They have learned, usually by getting it wrong once, that the asset does not need their fingerprints to keep working. It needs them to watch, document, and wait – and to spend their changes one at a time, where the result still means something.

When you are ready for the next one, you can browse current listings on Indiemaker. The second time through, the first 30 days stops feeling like restraint and starts feeling like the obvious thing to do. That is the moment you stop being a buyer and start being an operator.