Picture a founder who started a pet treat company in her kitchen. A few years in, she has expanded. She works with a co-packer, ships weekly orders to independent pet boutiques, and sells directly to consumers through an online shop.

Her business is healthy, but the back office is running on duct tape. Orders, available inventory, ingredient costs, and batch lot numbers all live across three different spreadsheets. Only she truly understands how the formulas connect. Every time an order comes in or a pallet ships, she spends her evenings typing numbers from one screen to another.When it is time to move beyond spreadsheets, the default instinct seems obvious: Get a familiar starter tool. It is cheap and everyone uses it. You can figure out 'real' operations software later when you are bigger.
It sounds like sensible advice, and most business owners hear the exact same thing.

When I began my career in 1989, small businesses were making a similar transition for the first time. Back then, it was paper ledgers. One of my first clients was an accounting firm manually copying check stubs onto 13-column green columnar paper. If the column totals did not balance across the page, staff spent hours hunting down the math error.

They could have moved from paper to an early spreadsheet like Lotus 1-2-3. That would have been an improvement, but it only would have automated adding up the columns. It would not have solved the underlying business workflow. Another client tracked customer invoices in one physical ledger and payments in a separate book, taking half a month just to calculate who was behind on their bills. Moving to software connected the pieces instead of just calculating rows faster.

Today, spreadsheets are the modern equivalent of that 13-column green paper.

The standard recommendation to buy a starter package makes sense if you run a simple business. If your main goals are seeing who owes you money and pulling a clean report once a year to hand to your accountant at tax time, an entry-level tool does the job.
If you make and sell physical products, taking that intermediate step often sets you up for an unnecessary detour. You do not always need to take the starter system route first.

Why is starting with basic software the default move?

The accountants and advisors giving that advice are not wrong. They are just recommending what works for the vast majority of small companies.
Entry-level accounting software is familiar and affordable. For a consulting firm or a very simple service business, a starter tool might be all the company ever needs. If your business primarily invoices clients for time and writes checks for monthly software subscriptions, the basic tools handle that smoothly.

The advice only breaks down when advisors assume every business grows the same way a service company does.

What changes when you sell a physical product?

Physical products introduce operational friction that service companies never have to worry about.

You need to know what is in stock and where it is sitting. You have to understand what each unit actually costs once you factor in raw ingredients and packaging. If you work with a co-packer or sell across multiple channels, like wholesale accounts alongside an online store, those moving parts multiply fast.

Starter systems were never built to handle that kind of operational detail. When a product business tries to run on an entry-level package, the software cannot keep up. So the business quietly starts running half its operations in spreadsheets right beside the accounting software.

I spoke with one business owner using a popular starter program who could never get an accurate picture of her true inventory. Her software could not reflect the conversion of raw materials into finished goods until the finished products were actually sold. Because she could never see what was truly available to ship, she kept tying up precious cash buying extra raw inventory just to ensure she never ran out.

Another founder told me that their team tracked every single lot number in external spreadsheets. The entry-level accounting software handled billing, but if a quality question or customer recall inquiry ever arose, answering which customer received which batch meant digging through separate spreadsheet tabs. They knew that as they expanded, relying on disconnected spreadsheets and bolt-on tools was an operational risk waiting to happen.

If a customer calls about a specific batch tomorrow morning, can you trace every order that batch went into within two minutes? If the answer involves cross-referencing three separate workbooks, your accounting package is not actually running your business. Your spreadsheets are.

What does skipping a step actually save you?

If you talk to an owner who has already been through multiple software transitions, they will tell you the software license is rarely the hard part. The real friction is changing how your people work and moving your data.

Taking the direct route saves you from paying that operational tax twice:

  1. One data move instead of two. Every time a business switches platforms, it has to migrate master records and clean up historical baggage. Doing that once is far easier on your team than doing it now and repeating the exact same painful exercise when you outgrow the system three years later.
  2. Habits get built once. When staff learn an entry-level tool, they build muscle memory around that tool’s specific screens and shortcuts. Then they discover what the software cannot do and plug the gaps with spreadsheet workarounds that become part of the daily routine. Moving to the right software later means untangling both the old system's habits and all the spreadsheet band-aids. When you start with the right operational tool, your team learns the proper workflow on day one.
  3. Starting from spreadsheets is surprisingly clean. Founders often assume that coming from spreadsheets puts them at a disadvantage compared to a company migrating from existing accounting software. Often the opposite is true.

Older systems can carry years of history that nobody has looked at in a long time. I recently ran a test conversion for an owner and uncovered open sales orders lingering from twenty years ago. Because their legacy software had never been configured properly for drop-shipped goods, the system showed over half a million dollars in phantom negative inventory. Years of quick fixes and forgotten transactions had quietly piled up in the background.

When you transition straight from spreadsheets, you do not carry that history with you. You take your current customers, your active vendor list, your real items, and your opening numbers, clean them once, and start fresh.

Doing that cleanup once, straight into a system designed for product workflows, is a clean break. Doing it halfway into a starter tool just means kicking the real cleanup down the road.

Does operational software have to mean six figures and enterprise bloat?

When small business owners hear the words "operational software," they often imagine multi-year implementations and runaway budgets.

The software market does not help here. One of the biggest pitfalls facing growing product companies is the "starter" package that looks deceptively cheap. A vendor advertises a system that is free to start, or fifty dollars a month, specifically targeting the exact inventory or invoicing pain point keeping you awake at night.

To actually run your business, you need the order module. And the purchasing module. And seats for four team members instead of one. Before long, that "free" starter package snowballs into thousands of dollars in surprise monthly fees and paid add-ons.

The right system for a small product business is sized and priced for what you need to run it, without the enterprise bloat. Practical systems are designed to fit teams starting with just a handful of users, giving you the operational backbone you need on day one, including inventory visibility and lot tracking, while scaling naturally as your company grows. You do not have to buy modules you will never touch, and you do not have to shop for another system the moment your team expands.

The goal is a system sized for where you are today that will not require an emergency replacement three years down the road.

When is staying simple the right call?

Taking the leap to dedicated operational software is not the right move for everyone.

If you run a service business with no inventory, or only need clean books once a year to hand your accountant at tax time, a basic entry-level accounting tool is usually plenty.

And if you do not have real friction in your day-to-day operations, do not change your systems just because someone told you that you "should." If your current setup gets orders out the door accurately and gives you the visibility you need without draining your weekends, you do not need new software.

A good advisor will tell you that straight out. Software should solve clear operational pain, not create change for the sake of change.

How do you know which side of the line you are on?

If you are trying to decide whether to begin with a starter program or make the leap straight to operational software, walk through this quick checklist:

  • Do you track lots or expiration dates? If tracking a batch means maintaining a separate spreadsheet tab outside your books, you have already outgrown basic accounting software.
  • Are you selling in more than one place? If you balance wholesale orders alongside an online store, starter tools quickly turn into manual data-entry bottlenecks.
  • Does anyone re-type numbers between screens? If orders or quantities get manually re-entered from an ecommerce platform into your books, errors are only a matter of time.
  • Do you build reports by hand for your accountant or lender? If pulling inventory valuation or gross margin requires exporting data and writing formulas in Excel, your system is not giving you clear visibility.
  • Do you work with a co-packer or multiple component suppliers? The moment raw materials get turned into finished goods across different facilities, basic bookkeeping software loses track of what you actually have.

If you checked off two or three of those points, taking a detour through a starter system will likely mean shopping for new software again in a few years.

Where to go from here

You do not need an accounting background or an alphabet soup of tech jargon to choose the right tools. You got into business to make great products, whether that is pet treats, beverages or specialty food, not to spend your evenings untangling inventory spreadsheets.

We work directly alongside your existing outside accountant or bookkeeper. They continue handling your taxes and year-end work, while we set up the operational engine that tracks your inventory and your daily orders. And when you have questions, you get a direct line to an experienced human who knows your setup, not a generic support ticket queue.

If you are running your product business on spreadsheets and wondering which step makes sense next, let's talk through where things stand today.

March 21, 1989. That's when it started.

My first client was a small company running everything on paper. Actual ledger books. Handwritten entries. The kind of bookkeeping that required good penmanship and a sharp pencil.

We were moving them to BPI.  A DOS-based accounting system from ACCPAC. No mouse. No Windows. Just a blinking cursor and a lot of keystrokes.

The office manager was a one-person operation. She handled the books, answered the phones, dealt with vendors, kept the whole place running. And now she had to learn an entirely new way of doing her job.  While still doing her job.

After our training sessions, she'd meditate. Not as a wellness trend. Because she was overwhelmed.

I don't blame her. She was learning something completely foreign while her bosses wouldn't even pick up the phone during our sessions. Every interruption meant backtracking. Every phone call meant losing her train of thought.

So I said something.

I pointed out that every interruption extended the training ... and extended my invoice. Suddenly, the bosses found time to answer their own phones.

That was my first lesson in ERP consulting: the software is the easy part. The people are the hard part.

What's Changed: Everything

Back then, there was no way to import data from paper ledgers. Clients typed in every customer, every vendor, every open invoice.  One by one. From handwritten records. Into a system they barely understood.

Now? We have migration tools. We export from the legacy system, clean up the data, and import it into the new one. What used to take weeks of manual entry now takes days of careful mapping and validation.

The technology has changed beyond recognition:

  • DOS → Windows → Cloud. I've migrated clients through every era.
  • Fax orders → EDI → E-commerce integrations. I've watched order entry go from paper to fully automated.
  • Stand-alone PCs → Networked servers → Hosted systems. I've helped clients stop worrying about their server closet.
  • Manual reports → Real-time dashboards. I've seen CFOs go from waiting days for financials to pulling them up on their phones.

I've moved clients off systems you've probably never heard of ... DacEasy, BPI, Peachtree DOS, ACCPAC DOS ... and onto modern platforms that would've seemed like science fiction in 1989.

What Hasn't Changed: GIGO

Garbage In, Garbage Out.

It was true in 1989. It's true today.

You can have the best software on the market. The slickest interface. The most powerful reporting engine. But if your data is messy, incomplete, or outdated, your new system will be just as useless as the old one.

Before every migration, I tell clients the same thing: we need to clean house first.

  • Customers who haven't ordered in five years? Archive them.
  • Vendors you haven't used since 2018? Don't bring them over.
  • Items with descriptions like "MISC PRODUCT DO NOT USE"? Delete them.
  • Open invoices from a decade ago that will never be collected? Write them off.

The new system isn't a fresh start if you're dragging all your old messes into it.

This is the conversation nobody wants to have. Cleaning data is tedious. It forces decisions that have been deferred for years. But it's the difference between a system that works and a system that everyone hates.

What I Never Saw Coming

In 1989, I couldn't have predicted:

  • That I'd still be doing this 36 years later. And still learning.
  • That some clients would stay with me for decades. I have clients I've migrated through three, four, even five systems over the years.
  • That the human challenges would stay exactly the same. People still resist change. Still fear new systems. Still need someone to advocate for them during training.
  • That "the cloud" would mean something other than weather.

But here's what surprises me most: companies are still running on systems that should've been retired years ago.

I just finished a migration from DacEasy. A system that hasn't been updated in over a decade. The company was holding it together with workarounds and prayers, terrified that one Windows update would bring everything down.

They didn't know what they were missing. They thought manually emailing invoices one at a time was just how it worked.

It's not.

What 36 Years Taught Me

  1. The software is never the whole story. Training, buy-in, clean data, and realistic expectations matter more than features.
  2. Advocate for the person doing the work. That office manager in 1989 taught me that. If leadership doesn't protect training time, the implementation will struggle.
  3. Don't automate a broken process. If your workflow is a mess on paper, it'll be a mess in software. Fix the process first.
  4. "Good enough" has a shelf life. Every system that's "working fine" today will eventually hit a wall. The question is whether you'll migrate on your timeline or the system's.
  5. Trust is everything. Clients don't stay for 30 years because of software. They stay because they trust you to tell them the truth...  even when it's not what they want to hear.

The Work Hasn't Changed

The tools are better. The interfaces are prettier. The integrations are more powerful.

But the core work is the same as it was on March 21, 1989:

  • Understand how the business actually runs, not how the org chart says it should.
  • Clean up the data before it poisons the new system.
  • Train the people, not just the software.
  • Be the person who answers the hard questions honestly.

If you're running a system that's held together with workarounds, or you're drowning in spreadsheets because your software can't keep up, that's the work I do.

I've been doing it for 36 years. And I'm not done yet.

 

~Audrey Quick, Founder of AGS Enterprises Consulting LLC

Audrey has spent 35+ years helping businesses manage ERP implementations and accounting software transitions.  If you're evaluating your options, we can book a free 15-minute call 

~Audrey Quick, Founder of AGS Enterprises Consulting LLC

Audrey has spent 35+ years helping businesses manage ERP implementations and accounting software transitions.  If you're evaluating your options, we can book a free 15-minute call