Services · Training and enablement
Role-based training for the people who will actually use it, and administrator training for the people who will change it. The goal is that your own team can build the next workflow without calling anyone.
The work
Training is where ERP adoption is won or lost, and it fails when it is generic. A warehouse team does not need the whole platform; they need goods-in, picking and stock checks, taught on screens configured the way yours are, with your item codes and your naming series. A finance lead needs the close, the reconciliation and the reporting. Same platform, different days.
We train by role, against your configured instance, and we train the people who will change the system hardest of all: your administrators. The aim is stated openly. Your team stops needing us. The first workflow your own admin builds unaided is the milestone that matters, because it is the moment the ERP becomes yours rather than something done to you.
What you get
Named up front so the engagement has a definition of done.
Separated by role (warehouse, finance, sales, buying) on your configured screens, using your records. No generic walkthroughs, no modules the audience will never open.
Permissions, workflows, custom fields, print formats and the Alpine builder itself. Your admin leaves able to design the next process, not just operate the current one.
Session material written against your processes and your screens, kept with the project. New joiners in two years read your words, not a vendor's.
People on the ground, or on a channel, for the first days of live operation. Questions get answered in seconds; bad workarounds never take root.
Pricing
No day rates and no sticker price. The estimate is derived from your situation. Each answer moves it, and anything genuinely unusual is scoped rather than guessed.
Estimated training and enablement cost
$0
fixed, one-time
An estimate, not a quote. Sessions are scheduled and priced against a written audience map.
Platform plans are priced separately on the pricing page. This estimate covers the training and enablement itself.
Questions
Close enough that it sticks: two to three weeks before, with floor support at the moment of change. Training in month one of a three-month project is training nobody remembers.
Portal users rarely need it. The portal is deliberately self-evident. Where suppliers or customers interact deeply, we produce short task-specific guides rather than sessions.
That is the normal case, and it is why training is role-based rather than platform-based. Each person learns four or five screens they will use daily, not the system's architecture. Adoption data after go-live tells us where to reinforce.
We certify competence on your instance, a practical assessment against your configuration. Frappe School offers formal courses on the platform itself for people who want the general credential alongside.
