Digital Transformation Consultant, USA

Why US transformation starts with processes, data and people

Software is the easiest part of transformation to buy and the hardest to get value from when the basics are unclear. If two people quote different order statuses, or month-end depends on one controller rebuilding a workbook, a new platform will copy that confusion into a more expensive place. So the first stage looks at how work moves: who takes an order, who approves a discount, who releases a shipment and who decides a customer can buy on credit.

Data comes next. US mid-sized companies often carry customer and item lists in several systems, each slightly different, with duplicates left behind by acquisitions, new sales channels or a past migration that was never finished. I identify which records drive revenue and cash, and which system should own each one going forward.

Then people. Transformation changes jobs, and the staff affected know where the current process breaks better than any diagram does. I involve them early through short remote walkthroughs and note where roles, approvals or workloads will shift. That understanding shapes the process design work and the later ERP decisions, instead of surfacing as a training problem at the end.

Building a roadmap that respects state-level differences

A company that sells or hires in many states runs into rules that change at each state line: sales tax registration and exemption handling, payroll withholding and leave rules for remote employees, consumer privacy laws in a growing number of states, and licensing for some trades and products. None of these is a reason to delay modernization, but each one changes what a system must do and when it must do it.

I keep a plain-language register of the state-level factors that touch your operations, and I tag each one with the system that will handle it and the advisor who must confirm it. Your CPA, payroll provider and legal counsel make the compliance calls. The register makes sure those calls happen before configuration rather than being discovered during testing.

The register also drives sequencing. If expansion into new states is planned, a tax engine or payroll change may need to come before a CRM rollout. If remote hiring is spreading the workforce thin across the map, HR and payroll data may become the first integration rather than the last. The roadmap shows these choices openly, so leaders can see why one project precedes another. Requirements gathered here feed directly into ERP business analysis when a platform change is part of the plan.

Payments modernization as part of the plan

Payments are where many US transformation plans become very concrete. Plenty of mid-sized businesses still print checks, upload ACH files by hand, key card settlements into the ledger and match remittances from email attachments. Banks now offer more choices, including same-day ACH, instant payment rails and richer remittance data, and larger customers increasingly expect suppliers to accept electronic payment.

I treat payments as a process rather than a bank product. The review follows money in both directions: how invoices reach customers and how payments come back, how vendor bills are approved, scheduled and released, and how each movement is recorded and reconciled. Typical findings are approval steps that exist only in email, vendor bank details changed without a callback check, and reconciliation that relies on one person's memory.

From there the roadmap sets out which changes belong in the ERP, which in the bank portal or a payables tool, and which are simply policy, such as dual approval for new vendor bank details. Your bank and finance team choose the products and controls. I make sure systems and process fit together. Where connections are needed, the detail moves to integration design, and automation of approvals and reminders follows once the process is stable.

Adoption, governance and who owns the roadmap

Most stalled transformations did not fail on technology. They stalled because nobody owned the outcome, decisions waited for a monthly meeting, or staff drifted back to their spreadsheets after go-live. I set up governance that suits a company of your size rather than a corporate program office.

• An executive sponsor who owns the roadmap and settles trade-offs between departments.
• Process owners for selling and collecting cash, purchasing, the month-end close and lead handling, each accountable for how their process works after the change.
• A short decision log so the reasoning behind each choice survives staff turnover.
• Adoption measures such as orders entered in the new system, open exceptions and report usage, reviewed without blame.

Change management is planned alongside delivery, not after it. Each stage has role-level impact notes, training timed around your peak season and year-end, and super users who field the first questions. For US companies with staff spread across several time zones, I favor short recorded walkthroughs and written guides over long live sessions, because people return to them when they actually need the answer.

Where an independent consultant fits, and where AI fits

Software vendors, VARs and implementation firms each do valuable work, but each sees the business through the product they deliver. An ERP partner will scope the ERP well and may say little about the website, the CRM or the reporting layer. A marketing agency can improve the lead engine without knowing whether operations can fulfill what it sells. My role is to hold the whole picture, process, systems, data and growth, without commission from any of them.

That includes the website and lead engine. If organic search and paid campaigns produce inquiries that never reach the CRM with their source attached, leadership cannot judge what growth spending returns. Connecting acquisition to pipeline and revenue belongs in the roadmap, not in a separate marketing project.

On AI, I stay measured. There are useful, bounded uses: extracting data from vendor invoices, drafting routine replies, classifying support requests, summarizing long records. Each needs clean input data, a person who reviews the output and clear rules about what information may go to which service. I add AI steps once the underlying process and data are in order, and I say so when a simple rule or report would do the job. For the broader method, see digital transformation consulting and my roadmap guide.