ERPNext, implemented by engineers who actually run it.
We run ERPNext and Frappe HR in production every day — and we build custom Frappe apps on top of it. If your business has outgrown spreadsheets, we'll get you onto a system you own, not a subscription you rent.
An ERP you own outright — not a seat you rent.
ERPNext is a free, open-source enterprise resource planning system: one database for accounting, inventory, sales, purchasing, HR and more, instead of five disconnected tools that don't talk to each other. It's built on Frappe, an open-source application framework — which is what makes it customisable rather than a fixed menu of settings.
The difference that matters to a growing business: platforms like NetSuite, Zoho and most Odoo plans charge per user, per month, indefinitely. Add ten employees and your bill goes up forever. ERPNext is open source — you can self-host it, and there is no per-seat licence to negotiate as you grow. You pay for the implementation and for the people who run it, not for a login.
The tradeoff is real: self-hosted software needs someone who can configure it correctly, customise it where the defaults don't fit, migrate your data cleanly, and keep the server it runs on patched and secured. That work is what we do.
Why a business outgrows spreadsheets
- Inventory counts and the accounting ledger stop matching each other
- Nobody can see order status without asking three people
- Payroll and attendance are tracked by hand, and it shows
- Reports take a day to assemble instead of a click
- Growth means adding staff, not adding software subscriptions
The parts of ERPNext most SMBs actually use.
You don't need to switch everything on at once. We scope the modules that match your business and leave the rest off.
Accounting
Chart of accounts, invoicing, payments, bank reconciliation, multi-currency, financial statements.
Inventory & stock
Warehouses, stock levels, batch/serial tracking, reorder rules, valuation.
CRM & sales
Leads, quotations, sales orders, pipelines — one record from first contact to invoice.
Buying & suppliers
Purchase orders, supplier quotations, receipts — tied straight into stock and accounting.
HR & payroll
Employee records, attendance, leave, shifts, and Frappe HR's payroll structure.
Manufacturing
Bill of materials, work orders and production planning, for businesses that make what they sell.
Projects
Tasks, timesheets and billing tied to a customer or job, so project cost is never a guess.
Assets & more
Fixed asset tracking, and further modules — helpdesk, quality, education — configured as you need them.
From spreadsheets to a system you own.
Implementation & configuration
We map your real processes to ERPNext's modules — accounting, inventory, sales, purchasing — set up roles and permissions, and get your team live with training, not just a login.
Custom Frappe development
Real Frappe apps: server-side logic, custom doctypes, row-level permission rules, REST integrations and client scripts. We run a custom Frappe app in our own production instance today, not a demo.
HR & attendance (Frappe HR)
Employee records, shift rules, check-in devices, automatic attendance, leave and role-based access — configured to how your organization actually works, not the vendor default.
Hosting, hardening & support
We don't just deploy ERPNext — we harden the server it runs on, patch it, back it up, and monitor it. Secured by the same team that does penetration testing for a living.
We don't just configure ERPNext. We run it.
Most ERPNext partners are configurators — they set the modules to your requirements and move on to the next client. We built our own custom Frappe application and it runs our operations right now: timer-based timesheets, attendance calculated automatically from check-in devices against each employee's shift rules, and permission rules fenced at the row level, not just the module level.
That means when your ERPNext instance needs something the standard modules don't do — and most growing businesses eventually need something like this — you're talking to the people who wrote the custom logic we depend on ourselves, not a partner reading the same documentation you can read.
And because it holds your financials and customer data, it needs to be locked down. We're the same team that does penetration testing and Linux hardening for a living — security isn't a separate vendor bolted on afterward. If your ERP also needs a customer-facing front end, we build the website too.
Timer-based timesheets
Staff clock time against a task, not a form filled in at week's end from memory.
Automatic attendance
Calculated from check-in records against each shift rule — no manual attendance sheet.
Row-level permission fencing
Access controlled per record, not just per module — so a role sees only what it should.
Seven stages, agreed in writing before anything is configured.
Nothing gets migrated or switched on that isn't on the blueprint you signed off.
| Stage | What happens | You receive |
|---|---|---|
| 01Discovery | A working session on how your business actually runs today — not how a brochure says ERP should work. We map your processes, pain points and must-keep spreadsheets. | A written process map |
| 02Blueprint | Which ERPNext modules you need, what stays out of scope, what has to be custom-built, and a realistic timeline. Agreed and priced before anything is configured. | Fixed scope, fixed price |
| 03Configure | Company setup, chart of accounts, roles and permissions, workflows and the modules from your blueprint — built in a staging instance you can see as it happens. | A working staging instance |
| 04Migrate | Your existing customers, items, opening balances and historical records brought in and checked against your old system, line by line — not a bulk import and a hope. | Clean, verified data |
| 05Train | Role-based training for the people who'll actually use it day to day, plus written guides for your team to keep after we're gone. | A team that can run it |
| 06Go-live | A cutover date agreed in advance, with a rollback plan if anything doesn't check out, and us on hand while your team runs it for real the first time. | Live, with support on standby |
| 07Support | Hosting, patching, backups and an agreed response time — the same team that built it keeps it running and secured. | An AMC scoped to your instance |
Scoped to your business.
No published number here — an honest quote depends on your modules, data and how much needs to be built, not just configured.
Frappe & ERPNext development
Day-rate or fixed-scope, depending on what needs building.
Implementation
Quoted after a discovery call — covers modules, users and migration.
Hosting & support (AMC)
A monthly retainer, scoped to your instance.
Every implementation is scoped and quoted in writing before work begins. Request a quote → The same rules apply to everything else we do — fixed scope, fixed price, agreed first.
Common questions
What is ERPNext?
A free, open-source ERP covering accounting, inventory, CRM, HR, manufacturing and more. It's built on the Frappe framework, and you own the software outright — no per-user licence, ever.
ERPNext vs Frappe — what's the difference?
Frappe is the framework: the metadata engine, permissions system and app platform ERPNext is built on. ERPNext is the ready-made ERP application that runs on top of it. We work at both levels — configuring ERPNext, and writing custom Frappe apps and doctypes when the standard modules aren't enough.
How is this different from Odoo, NetSuite or Zoho?
Odoo, NetSuite and Zoho charge per user, per month, forever. ERPNext is open source — you can self-host it and own the code with no seat licence. The tradeoff is that self-hosted software needs someone who can configure, secure and support it properly. That's the part we do.
Can you actually customise it, or just configure the defaults?
We customise it. Custom doctypes, server-side business logic, row-level permission rules, REST API integrations and client scripts — not just ticking boxes in the settings screen. We built and run a custom Frappe app ourselves: timer-based timesheets, attendance calculated automatically from check-in devices against each employee's shift rules, and permission rules that fence off records by row, not just by module.
Can you host and secure it for us?
Yes. Self-hosted on infrastructure we manage, or your own cloud account — either way we harden the server, patch it, back it up daily and monitor it. This is done by the same team that does penetration testing, not handed off to a generic hosting reseller.
What happens to our existing data?
It gets migrated, not dumped. We map your current records — customers, items, opening balances, transaction history — against ERPNext's structure, run the import in staging, and check it line by line against your old system before we touch production.
Will our team actually be able to use it?
That's the point of the training and go-live stages. We train by role — the person doing invoicing learns invoicing, not the whole system — and leave written guides behind. We don't consider a project finished at login; we consider it finished when your team can run it without calling us.
What does it cost?
Implementation and custom development are quoted after a discovery call, because the honest price depends on your modules, data volume and how much needs to be built versus configured. Hosting and support run as a monthly retainer scoped to your instance. We don't publish a number here because a generic one would be a guess dressed up as a quote.
Do you do payroll?
We implement Frappe HR — employee records, shifts, automatic attendance and leave. Statutory payroll varies by jurisdiction, so we scope that module case by case rather than promising a one-size-fits-all setup.
Outgrown spreadsheets? Let's scope your ERPNext.
A discovery call costs nothing and gets you a written process map — whether or not you hire us to build it.