Organised by what is most relevant to you. If your question is not here, the 30-minute call answers it directly.
These questions come from founders who know something is broken but are not sure whether an ERP is the right answer.
The honest answer depends on one thing: are your core processes documented? Not perfectly, but documented enough that someone other than you could follow them. If the answer is no, we recommend a process audit before any software is touched. Most businesses that come to us for ERPNext have some process work to do first. The 30-minute call is where we find out which side you are on.
Most implementations fail at handover, not during setup. The consultant exits at go-live, the team is overwhelmed, and within two weeks they are back on Excel. We stay with clients for a defined period after go-live, monitor daily usage, fix what surfaces in real operation, and do not exit until the system is the team's default. That commitment is in the engagement agreement, not just in the pitch.
A good rule: if you cannot describe a workflow in a paragraph without naming a specific person's habits, the problem is the process. ERP will not fix a broken process. It will run the broken process faster. We always map the process before configuring anything. If the process needs work first, we say so.
Probably some of them. The minimum behaviour change principle addresses this directly: we configure the system to fit how the team already works, not the other way around. Adoption rates collapse when implementation requires a wholesale change in how people think before they trust the system. We meet the business where it is and build from there.
Engagements are scoped individually based on the size of the business, the number of modules, and the complexity of existing processes. Every engagement is fixed-fee, scoped before work begins. No day rates that spiral. The discovery call is where we scope and provide a proposal. If ERPNext is not the right fit, we say that too.
During implementation, yes. After go-live, the goal is for ERPNext to replace the tools that are creating friction, not sit alongside them. Running parallel systems indefinitely defeats the purpose. We plan the transition with you so the team is not dropped into a cold switch.
These questions come from ops leads who have been tasked with fixing the chaos and want to know what working with an outside implementation partner actually looks like.
Meaningfully involved in the process audit and testing phases. We need to understand how your workflows actually run, which means conversations with the people who run them. The configuration itself does not require daily availability from your team. We keep the demand on your side predictable and respect that your team has a day job during implementation.
Written documentation of every configuration decision. Role-specific training for each team member based on their actual workflows, not a generic ERPNext tour. A post-go-live monitoring period where we stay available, fix what surfaces in real use, and confirm that the team is using the system as configured. The engagement does not end at go-live.
Most process documentation exercises fail because they produce documents, not systems. We document your processes as the foundation for an ERPNext configuration that runs them. The documentation has a purpose that extends beyond the document itself. Your team sees the output in the system they use every day, which is what makes the effort worthwhile.
The post-go-live monitoring phase is specifically for this. Real-use issues are different from testing issues. We stay available to fix what surfaces once the system is in daily operation. After the formal monitoring period ends, your team has documentation and the knowledge to handle most routine adjustments independently. For anything more complex, we remain available.
ERPNext has native integrations with several common tools. Where native integration exists, we configure it. What we do not do is write custom API connectors. Configuration-only applies to integrations as well. If a required integration does not have a native solution, we will tell you that clearly and discuss alternatives before the engagement begins.
ERPNext is an open-source enterprise resource planning system built on the Frappe framework. It covers accounting, inventory, purchasing, sales, HR, payroll, project management, and more in a single platform. No licensing fees. Actively maintained with regular updates. Used by thousands of SMEs across the globe. It is the only system we implement.
Custom code creates three problems for small businesses: it breaks on version updates, it requires expensive developer intervention to maintain, and it creates a dependency that is difficult and costly to exit. ERPNext has enough native flexibility to configure complete, fully functional implementations without writing a single line. We have done it consistently. The constraint is a feature, not a limitation.
We have configured ERPNext for manufacturing, trading and distribution, fresh produce export, medical supplies distribution, professional services, retail, wholesale, and FMCG. The module structure is flexible enough to handle the workflows of most SMEs. The pre-implementation process audit is where we confirm fit before any configuration begins.
We configure statutory compliance for the markets we work in. Kenya: PAYE, SHIF at 2.75% gross, NSSF under the 2022 Act, withholding tax at per-transaction thresholds. Nigeria: VAT, WHT, statutory deductions. UAE: VAT at 5%, WPS payroll processing, end-of-service gratuity. For markets outside these three, we research and document the relevant compliance requirements before configuration begins.
Because we do not write custom code, version updates are clean. Configuration-only implementations upgrade without the breakage that custom code causes. Your team can apply updates without needing us involved. That independence is one of the primary reasons we operate this way.
Fully asynchronously for most of the engagement. A weekly check-in call at a time that works across your time zone. Configuration updates and documentation shared via a shared workspace. Decision points clearly flagged so your team is never waiting on us. All work is delivered remotely. We have never needed to be in the same room to deliver a complete implementation.
Americas, Europe, Middle East, and East Africa. We structure availability around the client's working hours. The majority of our clients are international and based in those regions.
30 minutes. You walk us through the business: size, industry, current tools, the specific problems causing the most friction. We tell you honestly whether implementation is the right next step, what it would take, and roughly what it would cost. No pitch. No proposal sent before we speak. If you are not ready for implementation, we tell you what needs to happen first and you leave with a clear answer either way.
Yes. Standard NDAs are part of the engagement process. Everything shared during discovery and implementation is treated as confidential.
We work with businesses between 5 and 80 staff that have passed the point of needing to validate the core business. Pre-revenue or pre-product-market-fit businesses are better served by other priorities. If you are generating revenue and the operational constraints are becoming real, that is exactly when to start this conversation.
Two to three implementations simultaneously. That constraint is deliberate. It keeps quality consistent and ensures every client gets the attention the engagement requires. If we are at capacity when you reach out, we will tell you and give you an honest timeline for when we can begin.
The 30-minute call answers everything that is specific to your business. No pitch. No proposal before we speak.