Loading...
Loading...
Next step
A discovery call is 30 minutes with a consultant, not a sales script. We map your current process, tell you plainly what ERPNext or automation would and would not fix, and outline what a first phase could look like.
Methodology
Illustrative screens, sample data.
The stages
01
We learn how the business runs today and what it needs to do next.
What we do
What we need from you
What you get
A written summary of your processes and goals that you review and correct.
02
Modules, data flows and integrations are agreed before anything is built.
What we do
What we need from you
What you get
A design and scope document, and a plan with phases, that you sign off.
03
Accounts, warehouses, roles and workflows are configured.
What we do
What we need from you
What you get
A configured ERPNext test system containing your own data.
04
Only the gaps standard ERPNext cannot cover are developed.
What we do
What we need from you
What you get
Custom work that is documented, tested and separate from the ERPNext core.
05
Your data is cleaned, loaded and reconciled, and users test real work.
What we do
What we need from you
What you get
Reconciled opening data and a list of test results.
06
Each team practises its own work in a test system.
What we do
What we need from you
What you get
Users who have already done their own jobs in the system.
07
Opening balances are loaded and live work moves across.
What we do
What we need from you
What you get
Your business running on ERPNext.
08
Support, reporting and new phases as the business changes.
What we do
What we need from you
What you get
A system that keeps up with the business, with someone responsible for it.
FAQ
Typically 6 to 12 weeks for trading and service companies with standard processes, and 12 to 24 weeks for manufacturers with multi-level bills of materials, several warehouses or heavy customization. We confirm a timeline for your project after discovery.
No. Many projects go live in phases, for example accounting and stock first and further departments later. The plan agreed in solution design sets the phases.
Time from the people who run each process, a named owner in every department, and prompt decisions on open points. Projects slow down most often when decisions wait, not when software is hard.
We stay closely involved while your team settles in, then offer support covering questions, fixes, small changes and version upgrades. See our ERPNext support page for the options.
Often, yes. We start by reviewing what has been configured and what is missing, then agree what to keep, repair or rebuild.