A process built around
delivery, not promises.
Every project runs through the same five-phase playbook. Requirements signed. Sprints tracked. Payments tied to milestones. You own the code from day one.
5
Milestones
4×25%
Payment splits
15
Days, Starter go-live
100%
Code ownership
The five phases
From first call to signed sign-off.
Phases 2 and 3 run in parallel — training starts while build continues — so your team is ready well before go-live.
Requirements & SRS
We sit with your team and document every workflow, role, and business rule into a signed ERP Requirements Document. It is what we build to. It is what you sign off against. Nothing gets coded without it.
Setup & Customisation
Server is provisioned, ERPNext is installed, and every workflow, report, and outgoing document is configured to match your business. Sales invoices, delivery notes, salary slips — all formatted to your standards.
Training & UAT
While build continues, we start training department leads in parallel. Your team uses the actual system with real data. Real users hit real edge cases. Bugs surface in UAT, not at month-end.
Go Live
Opening balances migrated. Live data flowing. Your team running on ERPNext. We stay on call through the first month, so the first VAT return, the first month-end close, the first weird vendor bill all happen with us watching.
Sign Off
Each module is formally accepted once its core workflows run without open critical issues. Final documentation, tutorial videos, and the stabilisation period wrap up. Module by module, scope by scope, the project formally closes.
The team
A dedicated sprint team behind every project.
Your project runs inside a sprint, not a ticket queue. Named engineers, tracked hours, visible progress. The board you see on this page is the same board your engineers work in every day.
22 / 40h
33 / 40h
23 / 40h
24 / 40h
Every project includes
What we deliver.
- Server setup and configuration
- Custom workflow, reports, document formats
- Team training and follow-up sessions
- Documentation and tutorial videos
- Data migration (opening balances)
- Major and minor system updates (under AMC)
You own everything.
All code, configurations, and project files are pushed to your GitHub repository every day. If you ever change direction, the codebase comes with you. No lock-in.
- Daily GitHub commits to your repository
- Full ownership of all customisations
- Client retains all deliverables at sign-off
- No vendor lock-in on your own system
Hosted on your cloud account
We set up on Frappe Cloud using your account. You pay hosting directly, typically $50/month for up to 30–35 users. No middleman margin on infrastructure.
Scope changes
How change requests work.
Your signed ERP Requirements Document defines the scope. Anything inside it is included. Anything outside it follows a clear process.
Document it
The change is written up clearly: what is needed and why.
Assess impact
We estimate the cost and timeline effect before touching anything.
Approve in writing
Both parties sign off. Work starts only after written approval.
Clarifications are not change requests. Refinements, logical implementations, and edge cases required to make agreed scope work correctly are included, not billed separately.
FAQ
Common process questions.
Does the 15-day Starter Package follow the same process?
The Starter Package uses a compressed version of the same process with a fixed, pre-defined scope. Requirements are gathered upfront using a structured playbook, customisation is limited to configuration rather than bespoke development, and training runs in parallel. The 15-day clock starts from advance payment.
What happens if something is out of scope?
Anything outside the signed ERP Requirements Document is a Change Request. It must be documented, assessed for cost and timeline impact, and approved in writing before work begins. Clarifications and logical implementations of what is already in scope are not change requests.
Who hosts the system?
We set up the cloud environment on your own account — typically Frappe Cloud. Hosting is paid directly by you. We recommend starting with the 2 GB plan ($50/month), which handles up to 400k transactions and 30–35 concurrent users.
Who owns the code and configurations?
You do. All code, configurations, and project files are pushed to your GitHub repository every day. You retain full ownership of everything we build. If you ever change your implementation partner, you take the codebase with you.
Can the timeline slip?
The timeline starts from the date of advance payment. Delays caused by late access, delayed feedback, or change requests can push timelines out. We flag these as they arise and document any revised estimates in writing.
What is included in the AMC after go-live?
The Annual Maintenance Contract covers technical and functional support on the agreed scope, all major and minor system updates, and Dxbitz-customised add-ons like UAE e-invoicing and HR. Support is tracked via the in-ERP helpdesk.
Ready to start?
Tell us what your business runs on.
We'll walk you through how phase 1 would unfold for your business: what we'd document, who we'd interview, how long it would take. Before you commit to anything.