Platforms · Epicor
Epicor consultants who keep Kinetic connected and the plant running.
Kinetic runs the jobs, the inventory and the orders. We connect it to your CRM and your data platform, tune the directives and queries it runs on, and stay reachable when an export fails on a Saturday.
What we connect it to
- + your stack
If it has an API, we can connect it.
What we do
The three services, on Epicor.
-
Get Kinetic talking to the systems either side of it
One shipment feed or the whole customer, parts and jobs picture, moving reliably between Kinetic, your CRM and your data platform. Where a customisation sits in the path, we integrate around it rather than through it.
-
Directives and BAQs first, custom services where Kinetic stops
Much of the day-to-day ask is configuration: a method directive tuned, a BAQ that stops timing out, a dashboard that finally matches the screen it mirrors. Custom services and external endpoints enter where Kinetic does not reach, written so an upgrade does not quietly undo them, with business rules left in configuration your own team can change.
-
Hold the plant steady between upgrades
Inherited queries feeding reports nobody has reconciled, a scheduled export that fails silently, customisations carried through each upgrade by hand. We put eyes on the jobs, write down what each one is actually for, and stay reachable for the Monday-morning ones.
The everyday work
Not everything is a project.
Problems like these come up in every system, and not all of them are even problems. Some are an hour of advice, or writing down how something works before the person who built it leaves. Most take us minutes or hours, and you do not need a project with us, just send them over.
Fixes
- A BAQ that suddenly takes minutes to run
- A method directive that fires twice on one screen
- An export that failed on Saturday and surfaced on Monday
- A dashboard that stopped matching the screen it mirrors
Documentation
- The customisations written down before the next upgrade
- Runbooks for the exports and scheduled jobs
- A map of which directives fire where, and why
Advice
- A second opinion on an upgrade plan or quote
- Whether a customisation should survive the next version
- An hour on integration approach before you commit
Proof
Patterns we have already delivered.
Anonymised accounts of work our principals delivered in previous roles. These are the patterns that come up on Epicor in nearly every scoping call.
Consistent everywhere
Sync pricing and stock between ERP and CRM
How do pricing and stock stay consistent everywhere they're shown?
The result
One system of record feeding every surface
Read the case study
Handover-ready
Taking over broken integrations
How do you take over an integration built by someone who's gone?
The result
One job their own team now runs without us
Read the case study
Governed by design
One governed data platform for CRM and ERP data
How does data from every system land somewhere the whole business can trust?
The result
One governed home for every data feed
Read the case study
Common questions
What buyers ask before they call us.
How does an Epicor engagement usually start?
If the build is already clear, we start straight away. If something is broken today, a failing export or an upgrade deadline, we can step in within days. And if you are not sure what the fix should be, we can run a two to three week discovery that maps Kinetic and the systems around it, and you keep the blueprint whether or not we do the build.
Can you take on an Epicor build another team started?
Yes. Inherited directives, queries and export jobs are a normal starting point. We learn what runs today, write it down as we go, and only then change behaviour.
How is the work priced?
Per engagement rather than from a rate card. A discovery is a fixed fee for a time-boxed piece of work. A scoped delivery carries a fixed shape and a fixed price agreed up front, so the number does not move as we go.
Are you an Epicor partner?
No. We hold no Epicor certification and no vendor sponsorship, so nothing we recommend earns us anything beyond the engagement itself. What we bring is integration and data engineering applied to Kinetic.
Do you only take on project work?
No. A steady share of the week is small: a broken automation, a question that needs an experienced answer, documentation nobody ever wrote, or plain advice before you commit to something bigger. Most of those are minutes or hours, not days, and they get the same care whether you run a two-person business or an enterprise team. When one turns out to be bigger than it looked, you already know who is holding it.
Get started for free.
One call to understand the problem, and a written price if we can help.