What Should a Family Business Know Before Buying Technology?

The software is priced by the month. The business is planned in decades. Buy for the handoff.

---

You run a business with your family's name on it, a vendor has just shown you something that answers the phone or chases the invoices, and the question you are sitting with is whether it will still be working when you are not the one running the place. This post is for the owner of a family business with fewer than twenty people, in a trade, a distribution yard, a shop, or an office, weighing a purchase that will outlast the meeting where it gets decided. You will get the numbers on how family firms differ from the companies most technology advice is written for, a four-question test to run before anything gets bought, what three generations of my own family's petroleum business taught me about fit, and one page to write this week before you sign anything.

Why does technology fail differently in a family business?

It fails at the handoff, not at the install. A family business is older than most, grows slower, and passes its tools from one set of hands to the next. A purchase that only the buyer understands becomes a problem the day the buyer is on vacation, in the hospital, retired, or gone, and in a family business that day is on the calendar whether anyone has written it down or not.

Start with what a family business is, by the numbers. The Small Business Administration's Office of Advocacy counts a business as family-owned when two or more family members own the majority of it, and in its February 2026 Frequently Asked Questions About Small Business, about one in four employer firms (26.1 percent) were family-owned in 2022. Those firms employed 15 people each on average against 11 for everyone else, and after management of companies and enterprises (the holding-company sector, at 42 percent), the industry with the highest share of family ownership was mining, quarrying, and oil and gas extraction, at 40 percent.

The same office's April 2024 fact sheet on family-owned businesses, built on the Census Bureau's 2021 Annual Business Survey, shows the shape that matters for a technology decision.

Read the table as a business owner. Family firms are older, less likely to be startups, more likely than non-family firms to have ten or more people on payroll, and their employment grew by less than one percent over a seven-year stretch in which non-family firms grew by eleven and a half. That is not a failing, though it is not safety either: the same fact sheet shows employment at small family firms falling 14.3 percent between 2017 and 2021. Read it as slow and long-lived. It means the person who signs for a tool and the person who inherits it are often two different people, sometimes twenty years apart, and the tool was chosen for the first one.

Then there is the number everyone in this world has heard: thirty percent of family businesses survive to the second generation and thirteen percent to the third. It is worth knowing where it comes from before you let it frighten you. The source is John L. Ward's 1987 book Keeping the Family Business Healthy, and Kellogg's page for the book repeats the popular version: less than one-third of family-owned businesses survive until the second generation. Family Business Magazine's review of that study adds what usually gets left out. The sample was 200 Illinois manufacturers listed in annual publications from 1924 to 1984. Ward's own sentence, as the magazine quotes it, was that 13 percent of successful family businesses last through three generations and less than two-thirds survive the second, and "through" gets misquoted as "to," which lops decades off the horizon in the retelling. By the magazine's arithmetic, 32 percent of the firms lasted at least sixty years, and nearly 13 percent lasted at least ninety as independent firms under the same name, which it puts well into a fourth generation. The study also counted a firm that was sold or merged as one that did not survive, so a family that sold well is in the failure column.

So the honest version of the statistic is this: the horizon you are planning on is measured in decades, and no software contract you will ever sign runs that long. That gap, between the life of the business and the life of the tool, is the whole subject of this post.

What should you decide before you look at a single tool?

What the business needs from the process the tool will touch, written down by the people who do that work today. A demo shows what the software can do. A written process shows what your business needs done. Buy against the second, or the purchase will be shaped by the vendor's feature list instead of your family's day.

Technology earns its keep when it is attached to a process the business has already described in plain words. A phone assistant is useless until someone has written what the team needs from a call in order to act on it. In my family's fuel and lubricants business, that turned out to be seven fields: the account, the product, the quantity, the delivery location, the timing, any access instructions, and who to confirm with. The phone system there is built around that card, and the card was written before any software was chosen.

The failure runs the other way more often than you would think. A real estate brokerage's platform I audited in August 2026 (de-identified, as every private client is here) had 179 configuration fields, none of them filled in, and 21 of 71 automations switched on with nobody able to say what the other fifty did. Somebody had bought the software with real money and real hope, and the process it was supposed to carry had never been written, so it sat in the account like a truck with no route. The subscription kept billing.

Write the process as the people who do it would describe it to a new hire on their first morning. What comes in, what has to be captured, who decides, who is told, what counts as done. If a father and a daughter describe the same process differently, that is the most useful page you will produce this year, and it is the page the tool has to fit.

What is the handoff test?

Four questions, asked before any purchase, each answered with a name. Who holds the keys. Who tells the system when the business changes. Whether a newcomer could run it from what is written. What the way out is. If any answer is a vendor, or "whoever set it up," the purchase is not ready, however good the demo was.

Each question protects against a different way a family business loses. The keys question protects against the death, divorce, or departure that turns a login into a lawsuit. The change question protects against the quiet drift where the system keeps answering with last year's prices. The newcomer question protects the generation that did not choose the tool. The way-out question protects against the vendor, which is the one party at the table whose interests are not the family's.

Why the test works is simple. Every one of those four failures happens later, often years later, and a demo is the one place none of them are visible. Asking the questions before you buy moves the failure forward to the only moment it costs nothing to fix.

Who should own the accounts in a family business?

The business, in accounts registered to an address the business owns, with more than one family member holding recovery access. Not a son's personal phone, not the bookkeeper's Gmail, not the vendor's platform. Ownership decides what survives a death, a divorce, a departure, and a price increase, and in a family business all four are on the horizon.

This is where family firms are more exposed than they look. Because the same people have run things for a long time, accounts accumulate under whoever happened to set them up: the website under a nephew who did it in 2014, the phone system under the office manager's login, the customer list inside a vendor's product with no export ever tested. Nothing breaks, so nothing gets moved, until the day the nephew is not speaking to anyone or the office manager retires. What owning your data means for a small business is a longer argument; the short one is that the customer list is often the most valuable file the business has, and what happens to that list if you leave the vendor tomorrow should be a question you can answer today.

Two assets deserve their own line. The phone number, because for a distribution or service business it is the number on the trucks and the one customers have called for decades; the business should be the named account holder and the party authorized to move the number, and someone should know where the account PIN is. And the domain name, because email, the website, and every login recovery flow through it. Both should be registered to the business entity, on an address that belongs to the entity, with two-factor sign-in on the registrar account and the renewal on a shared calendar.

At Scotty's Oil, the knowledge base the phone assistant reads from, the customer records, and the order history sit in accounts the family controls, and the choice was deliberate. A system a business owns rather than rents is the difference between one that compounds across a generation and one that vanishes when a software company shuts down or changes its terms.

What does the technology need from the family after it goes live?

Telling. Any system that answers questions or takes orders works from a maintained description of the business, most often a written one, and when prices, hours, products, or delivery areas change, somebody has to tell it. That is the maintenance contract in one sentence, and in the builds I have seen, the failures come months after launch, not on the first day.

The part of this work I am most careful to say out loud, as someone who builds these systems for a living: none of them should run without oversight. An assistant that answers the phone knows only what has been written for it. If a product is discontinued, a delivery area is dropped, or a price moves, and nobody updates the written knowledge, the assistant will keep giving the old answer, politely and with confidence, to every caller until someone notices. In my experience, small business automations that stop working tend to do so within the first six months, and the usual cause is not the technology. The business changed and the system was never told.

For a family business this is a staffing question, not a technical one. Name the person. In a business where a parent handles pricing and an adult child handles the yard, the pricing parent is the person who tells the system about prices, and that is written down next to their name. Put a fifteen-minute review on the calendar once a month: what changed, was the system told, what did it get wrong, and read three or four transcripts to hear it for yourself. In my experience, a system keeps working when a named person owns its upkeep; a system that runs without you in the room still needs you in the building now and then.

What did three generations at Scotty's Oil teach me about fit?

That the technology had to fit a business built on the phone, on long relationships, and on people who are usually in a truck rather than at a desk. The system that works there answers a call the way a trained desk person would and hands anything unusual to a human. Nothing about how customers reach the company changed. What changed is that no order waits for a free pair of hands.

The history is on the company's own About page, and it is a family-business history in every particular. Scotty's Oil Company began in 1967 with one truck, founded by Scotty Lankford and his stepson, my father, Bert Bennin. They spent sixteen years building it. Scotty passed unexpectedly in 1983, and my parents, Bert and Angela, grew it from petroleum delivery into fleet fueling, commercial fueling sites, bulk oil, and packaged products across Central Florida. In 2016 the business was sold. Five years later my parents brought it back, and today Jon Varney leads it in Orlando. Two generations of my family built and ran it, Scotty and then my parents, and I am the third to work on it, as the builder of the phone system it runs on now.

Here is what fit meant in practice. Customers of a fuel and lubricants distributor call. They have called the same number for years, they are not going to download an app, and the highest-value calls come in bunches, on the days the trucks run longest. So the assistant, named Emma, lives on the phone. She answers, has a plain conversation, collects the seven fields a dispatcher needs, confirms them, and delivers the order to the team as a complete record. Every conversation is logged to the customer's contact record, so the next person on the account can see what was said. When a caller asks about something outside her written knowledge, she is built to hand off to a person instead of improvising. When a call is missed anyway, the caller gets a text back within minutes. The full build is described in its own case study.

What stayed with the family is the part a vendor would have automated first. Pricing, credit decisions, scheduling, and anything unusual still go through people who know the customers by name, because that is the business. And the knowledge base Emma reads from is the family's to maintain, which is the only way the system stays true to a company whose name goes back to 1967.

The lesson I took from watching my parents decide: they did not ask what the technology could do. They asked what the business needed done that was going undone, which was the order that came in while everyone was on a delivery. The build was shaped around one door, the phone, and around the way the family already worked. It did not ask them to become a different company.

Is a family business behind if it has not bought any of this yet?

No. From December 2025 to May 2026, between 17 and 20 percent of U.S. businesses reported using artificial intelligence in any business function. Use among firms with fewer than twenty employees did not change significantly over that period, and less than 20 percent of firms with four or fewer employees reported using it. As of that report, most of your peers had not adopted it. The advantage goes to the family that buys one door well, not the one that buys first.

The figures are worth laying out because they are the opposite of what the advertising implies. The SBA's February 2026 FAQ, citing the Census Bureau's Business Trends and Outlook Survey (a survey of businesses with employees), puts AI use between September 2024 and August 2025 at 7.6 percent of businesses overall, 11.4 percent for those with more than 250 employees, and 8.2 percent for those with fewer than five, under the survey's earlier question, which asked about AI used in producing goods or services. The Census Bureau's own May 2026 report on AI use at businesses covers December 14, 2025 to May 3, 2026, after the survey question was broadened to any business function, and finds overall use hovering between 17 and 20 percent, 37 percent among firms with at least 250 employees, 32 percent among firms with 100 to 249, and less than 20 percent among firms with four or fewer employees. Use rose over the period among firms with at least 20 employees and did not change significantly among firms with fewer than twenty. The two periods should not be compared directly because the question changed in November 2025. A Federal Reserve staff note from April 2026 on monitoring AI adoption documents the change and treats the two as separate series. It also observes that adoption among the smallest firms is stronger than would be expected based on size alone, a pattern it says has moderated under the new question.

Notice who the family-business surveys are written about. Deloitte Private's survey released in July 2025, the one whose headline says AI adoption tops the agenda for family-owned enterprises, polled 100 leaders of U.S. family companies with annual revenues of $100 million to more than $1 billion in the spring of 2025. Forty-two percent named increasing the use of AI as a strategic priority for the coming year, and two-thirds have added or are adding board members with technology expertise. That is a real finding about a real group, and it is not your group. Advice built for a company with a board and a technology committee, enterprise-wide AI strategy and all, is the wrong advice for a business of twelve people where the owner still answers the phone. The right amount of technology for a family business is the amount attached to a process you have written down, and not one tool more.

So the order of purchase, for a family business under twenty people, is short. First, the door where customers already arrive: the phone for a distributor or a service company, the inquiry form for a brokerage, the booking request for a contractor. Second, the record every conversation lands in, owned by the business. Third, follow-up, which in my experience is where a small business loses the most to slow or absent replies. Anything beyond that waits until the first three have run for a season.

And two refusals. If the intake process is not written on one page yet, do not buy the platform this quarter; write the page, it costs nothing and it is the specification. If the business is five people or fewer and the owner personally answers every call and likes it that way, a missed-call text-back, set up with the consent and opt-out handling that texting rules require, may be the entire purchase, and anyone selling you more than that has probably not asked how you work.

What would I do this week?

Write the handoff page. One sheet, by hand if you like, listing every account the business runs on: the domain registrar, the phone carrier, the website host, email, the customer records, bookkeeping, the social pages, and any tool that talks to customers. Next to each: who holds the login, which email address it is registered to, whether that address belongs to the business or to a person, and what happens to it if that person is out for a month. Then move the ones on personal addresses to an address the business owns, and keep the sheet somewhere a second family member can find it.

The sheet takes an afternoon and costs nothing (moving accounts can take longer), and it tells you more about your exposure than any demo will. After that, the order card: what the team needs from a call or a form in order to act on it, in the words of the person who takes those calls now. With those two pages in hand you can sit through any vendor's presentation and know within ten minutes whether it fits.

If you would rather have help mapping it, Bennin Systems builds the system around how your family already works, one door first, and then teaches you to run it, so that what you buy this year is still yours in twenty. I'm not about winning. I'm about protecting.

Frequently Asked Questions

What counts as a family-owned business?

The Small Business Administration's Office of Advocacy counts a business as family-owned when two or more family members own the majority of it. By that definition, about one in four employer firms (26.1 percent) were family-owned in 2022, employing 15 people each on average against 11 for non-family firms, according to the Office of Advocacy's February 2026 FAQ.

Is it true that only 30 percent of family businesses survive to the second generation?

Not as usually quoted. The figure traces to John L. Ward's 1987 book Keeping the Family Business Healthy, a study of 200 Illinois manufacturers listed from 1924 to 1984. Ward wrote that 13 percent last "through" three generations, a word often misquoted as "to," and Family Business Magazine's review reports that 32 percent of the firms lasted at least sixty years and nearly 13 percent at least ninety. Treat the numbers as a long horizon, not a verdict.

What is the handoff test for buying technology?

Four questions, each answered with a name before a purchase: who holds the keys (domain, phone number, records, logins), who tells the system when prices, hours, or products change, whether a newcomer could run it from one written page, and what the way out is if the vendor disappears. If any answer is a vendor or "whoever set it up," the purchase is not ready.

Who should own the software accounts in a family business?

The business entity, on an email address the business controls, with recovery access held by more than one family member. The phone number and the domain name matter most, because customers call the number and every login recovery flows through the domain. Accounts registered to a relative's personal email or held by a vendor are the ones that turn into disputes.

What did Bennin Systems build for Scotty's Oil?

A phone assistant named Emma for the fuel and lubricants distributor my father and his stepfather founded in 1967 and my parents brought back after a 2016 sale. Emma answers calls, collects the seven fields a dispatcher needs, confirms the order, delivers it to the team as a complete record, logs the conversation to the customer's record, and hands anything outside her written knowledge to a person.

Is a small family business behind if it has not adopted AI?

No. From December 2025 to May 2026, between 17 and 20 percent of U.S. businesses reported using AI in any business function, according to the Census Bureau. Use among firms with fewer than twenty employees did not change significantly over that period, and less than 20 percent of firms with four or fewer employees reported using it. Most small family businesses have not adopted it yet, which leaves room to decide well.

What should a family business buy first?

The door where customers already arrive: the phone for a distributor or service company, the inquiry form for a brokerage, the booking request for a contractor. Then the record every conversation lands in, owned by the business. Then follow-up. If the intake process is not yet written on one page, write that page before buying anything, because it is the specification.

How much upkeep does a phone or order system need?

A named person and a short monthly review. The system answers only from what has been written for it, so every change to prices, hours, products, or service area has to be entered by someone whose name is on the task. Fifteen minutes a month to ask what changed, whether the system was told, and what it got wrong keeps a build working for years instead of months.

---

Stacy Bennin is the founder of Bennin Systems, where she builds the automated systems small businesses need but rarely have time to set up themselves: lead capture and follow-up that runs on its own, chatbots that answer questions and take orders around the clock, custom websites that act as an employee, and the back-office workflows that keep an operation from running on memory and sticky notes. Located in Montana, she works with businesses and real estate professionals anywhere in the United States. She is also a licensed Montana real estate broker affiliated with Legacy Lands Real Estate. Reach her at benninsystems.com.

Bennin Systems · Paradise Valley, Montana · (406) 224-3267 · benninsystems.com