What to Ask Before Hiring an Acumatica Consultant

Choosing an Acumatica consultant is one of the highest-leverage decisions you'll make during an ERP project. The right partner gets you live on time with a system that works. The wrong one burns budget, blows deadlines, and leaves you worse off than when you started.

Here are the questions most companies don't think to ask — and the answers that separate real expertise from a polished sales pitch.

1. "Who will actually be doing the work?"

This is the single most important question and the one most companies forget to ask. Many firms sell with senior talent and deliver with junior consultants. Ask specifically: who will configure the system, attend our meetings, and be responsible for our go-live? Get names and certifications, not just titles.

2. "How many Acumatica certifications does your delivery team hold?"

Certifications aren't everything, but they're a baseline. If the people building your system aren't certified in the modules you're implementing, that's a problem. Ask for the specific certifications — Construction Business Consultant, Inventory & Order Management, REST API Integration Developer — not just a count.

3. "Have you implemented Acumatica in our industry?"

Acumatica for construction is fundamentally different from Acumatica for distribution. Industry experience matters — it's the difference between a consultant who understands your workflows on day one and one who's learning your business while billing you for it. Ask for references in your vertical.

4. "What happens when things go wrong?"

Every implementation hits bumps. What matters is how your consultant handles them. Ask about their escalation process. Is there a single point of contact, or will you be navigating a support ticket system? The answer tells you a lot about how the next 6–12 months will feel.

5. "What's your approach to data migration?"

Data migration is where most implementations fall apart. A good consultant has a documented migration methodology — mapping, cleansing, trial runs, validation. If the answer is vague ("we'll handle it toward the end"), that's a warning sign.

6. "What does post-go-live support look like?"

The first 90 days after go-live are critical. Ask what's included. Is there a dedicated support period? How quickly will they respond to issues? Some firms disappear the moment the contract is fulfilled. You want a partner who's still answering the phone three months after launch.

7. "Can you show me a project timeline from a similar implementation?"

A consultant who's done this before can show you what the journey looks like — milestones, dependencies, decision points. If they can't produce a realistic timeline based on similar projects, they're either inexperienced or guessing. Neither is good.