Your father's retirement dinner was on Friday. On Monday, the controller leaves a short note on your desk: two software renewals are due this quarter, the phone system needs a decision, and the IT consultant who has looked after the company for fifteen years is coming in Thursday to "walk you through everything." You have a hundred priorities, and technology isn't near the top of your list.
Most advice on taking over a family business covers ownership, governance, and family dynamics. Technology usually gets a line item. Yet a handful of IT facts can shape how smoothly the transition goes: who holds the keys, what renews when, and whether the backups actually work. Your first 90 days are the time to learn those facts, and the reasons behind today's systems, before you change much of anything.
At a glance
- Spend the first month listening and building an inventory of accounts, admin access, vendors, contracts, renewals, backups, and the people who keep it all running.
- Use the second month to secure the basics quietly: the company owns its domain and key accounts, leadership uses MFA, and someone has tested a restore.
- In the third month, build a roadmap where every significant decision is written down along with a way to reverse it.
Why technology belongs in your takeover plan
Successors are judged on their early decisions, and technology decisions are easy to make quickly. A new provider, a platform switch, or a big hardware purchase can feel like visible progress. They're also expensive to reverse if they turn out to rest on a misunderstanding.
The systems you're inheriting were built by people solving real problems with the budget and options they had at the time. Some of what looks dated was a deliberate choice. A server in the back closet might exist because a key customer's software required it, or because the internet connection failed during a busy season years ago. Understanding that history first keeps you from paying twice.
Days 1 to 30: listen and take inventory
Start with conversations. Meet with the outgoing leader, the long-time IT person or provider, the controller, the office manager, and a few of the heaviest users. Ask what works, what breaks, what they'd change, and why things are set up the way they are. Frame it as learning. Long-time staff can easily hear an inventory as an audit of their work, and their trust matters more than any single finding.
As you listen, build a simple inventory covering:
- Admin access. Who can administer email and files (usually Microsoft 365 or Google Workspace), the firewall, accounting, payroll, banking portals, and the website.
- The domain. Who owns the company's domain name, which registrar holds it, and which email address receives the renewal notices.
- Vendors and contracts. The IT provider, software subscriptions, phone and internet service, and equipment leases, with renewal dates and notice periods.
- Backups. What's backed up, where the copies live, how often they run, and when anyone last restored something.
- Single points of failure. One person who knows the passwords, one aging server, one internet line, one notebook in one desk drawer.
You don't need a polished document. A shared spreadsheet with an owner and a date for each item is plenty.
Understand the reasoning before you change anything
For each major system, ask why it exists in its current form. Who chose it? What problem did it solve? What would break if it disappeared tomorrow? Write the answers down, even when they're informal.
Some of those reasons will still hold. A specialized accounting package may fit your industry better than anything newer. Others will have expired quietly: the vendor that once required an on-site server now offers a cloud version, or the person who insisted on a certain setup left years ago. A short decision log separates the two, and it gives you credible answers when family members, board members, or lenders ask what you're planning and why.
Days 31 to 60: secure the basics quietly
A few changes protect the business without disrupting anyone. None of them needs an announcement.
Make sure the company owns its accounts
Start with the domain. It should be registered to the company, with the registrar account tied to a company email address that more than one person can reach. ICANN treats registrants as having rights and responsibilities, including keeping contact information accurate, and a domain registered years ago to a former employee or a web designer is a common surprise.
Then look at your Microsoft tenant, if that's where email and files live. Microsoft recommends assigning the Global Administrator role to fewer than five people, protecting every admin account with MFA, and keeping two cloud-only emergency access accounts that aren't tied to any one person. Their credentials belong in secure storage that the company controls, with an alert whenever they're used.
If an outside provider manages the tenant, ask exactly what access it holds. Microsoft's granular delegated admin privileges (GDAP) let a partner work with specific, time-bound roles that the customer grants explicitly, which is much easier to review than one broad, permanent login.
Turn on MFA for leadership first
The accounts that can approve payments, reach sensitive files, or change other people's access deserve protection first. Once every administrator account has MFA, extend it to the leadership team right away. Set it up in person, register a backup method for each person, and explain why it matters to the business. Leading by example helps when you roll it out to everyone else.
Test one restore
Ask the person who manages backups to restore something that matters, such as last month's accounting data or a shared project folder, into a safe location. Write down how long it took and whether anything was missing. A backup report saying "success" tells you the job ran. A completed restore shows the business could recover.
Do all of this alongside the long-time IT person or provider, never around them. Present it as continuity planning for the company. Clear ownership and documented access protect them too, because nobody can later claim they were the only one who knew.
Days 61 to 90: build a roadmap you can explain
By the third month, you'll have a list of findings. Sort them by business impact: what could stop operations, what is costing more than it should, and what is merely annoying. Then group them by area, such as identity and devices, email and collaboration, security monitoring, backup, business applications, physical infrastructure, and connectivity. Treating each area as its own decision keeps one change from forcing all the others.
For every change you recommend, record the problem, the options you considered, the expected cost over two or three years, who owns it, how you'll know it worked, and how you'd undo it if it doesn't. Time the bigger moves to contract renewals, so you're not paying for two systems or breaking an agreement early.
- Days 1 to 30
- Focus: Listening and inventory
- What you have at the end: A list of systems, access, vendors, renewals, and key people
- Days 31 to 60
- Focus: Ownership and basic protection
- What you have at the end: Company-owned accounts, MFA for leadership, one tested restore
- Days 61 to 90
- Focus: Roadmap and decisions
- What you have at the end: Ranked priorities, each with a cost, an owner, and a back-out plan
Bring the people who built it with you
The outgoing generation and long-time staff carry knowledge that no inventory captures. Keep them involved in the roadmap conversations. If the long-time IT person or consultant is stepping back, consider a paid transition period during which they document what they know and introduce you to vendors.
Hold off on announcing a new provider or a major platform change until you understand the current setup. A thoughtful first 90 days shows the family and the staff that you take the business seriously, including the parts that were built before you arrived.
Make your first technology decision a well-informed one
The goal of your first quarter is clarity: knowing who holds the keys, what it all costs, and what would happen if something failed. With that in hand, every later decision gets easier to make and easier to explain.
At CTP, we work with successors the same way, researching first and recommending last, with one named senior advisor and a written record of every significant decision. See how we approach IT strategy for private companies and family offices, or schedule a conversation about the technology side of your transition.

