ERP implementation

One system for the books, the stock and the payroll.

We implement ERPNext and the Frappe ecosystem - open source, no licence fee per user - or build the ERP custom when that fits you better. Most implementations that fail do not fail on the software - they fail on opening balances that never reconciled, a chart of accounts copied from a template, and staff who were shown it once. We do the unglamorous parts properly.

4 - 14 weeks: for a typical implementation
eTIMS: and Kenyan payroll built in
No licence fee: per user, ever

Where to start

Start with the part that hurts most

Few businesses need everything on day one. Most come to an ERP for one reason - eTIMS, payroll, stock across branches, or a cost per unit nobody trusts - and add the rest once that works.

eTIMS Every invoice through eTIMS, the moment it is raised. Payroll Payroll that keeps up when the deductions change. Manufacturing Know what each unit actually cost to make. Distribution Stock, credit and collections that agree across branches. Support and recovery Your system, looked after - or put right.

What you get

What an implementation covers

Accounts, stock, sales, purchasing, payroll and eTIMS on one system, set up, connected and looked after by people still here next year. We implement ERPNext and the Frappe ecosystem - open source, no licence fee per user - or build the ERP custom when that fits you better. Most implementations that fail do not fail on the software - they fail on opening balances that never reconciled, a chart of accounts copied from a template, and staff who were shown it once. We do the unglamorous parts properly.

Fit-gap before configuration

We map how your business actually trades against what ERPNext does out of the box, and write down every gap before anyone configures anything. Most of what people think needs custom code is a setting; the few things that genuinely do are priced up front.

Accounts, stock, sales and purchasing

A chart of accounts built for your business rather than copied from a template, warehouses and branches, price lists, credit limits, purchase approvals, and the reports your finance lead reads every month.

KRA eTIMS and Kenyan payroll

Sales and purchase invoices that clear eTIMS as they are raised, and payroll that handles PAYE, SHIF, NSSF and the Housing Levy - with the rates held as settings so the next change is an edit, not a project.

Payments matched to invoices

Mobile money, bank and card receipts pulled in and matched to the right customer and invoice automatically, so the receivables ledger agrees with the statement at month end.

Data migration that reconciles

Customers, suppliers, items, open invoices, stock on hand and opening balances moved from QuickBooks, Sage, Tally or spreadsheets - and checked against your closing trial balance before go-live, not after.

Custom work where the standard system stops

Industry workflows, customer portals, field apps and dashboards built as proper Frappe apps that survive upgrades - or, where it fits better, as a separate system that talks to ERPNext through its API.

How it runs

What happens, step by step

An implementation is not finished when the screens work. It is finished when your opening balances, stock and customer ledgers agree with the books you are leaving, your invoices clear eTIMS, and your team can close a month without calling us.

01 Fit-gap week We sit with finance, stores, sales and whoever runs payroll, and leave with a written scope, a migration plan, a fixed price and a go-live date. Week 1

02 Configure and migrate Company setup, chart of accounts, items, warehouses, taxes and workflows - with a trial migration of your real data that your accountant checks. Week 2 - 6

03 Integrate and train eTIMS, payments, bank, SMS and any custom apps connected and tested. Each team trained on its own workflow, on its own data, not on a demo company. Week 4 - 10

04 Go live and close the first month Final migration, cut-over, and the first month end closed together. Support carries on from the day you go live. Final weeks

When you should not buy this

If a business has a handful of staff, one location and simple stock, an ERP is more system than it needs, and an accounting package with eTIMS will do the job for a fraction of the cost. We will say so on the first call.

How the money works

The terms, before you ask for them

The same terms as any build we do, because an implementation that goes wrong costs as much as one.

Paid 40 / 40 / 20 Forty percent to start, forty when the trial migration is signed off, twenty after the first month end closes on the new system. The last fifth is earned after you have used it.

Your system, your data ERPNext is open source. You own the instance, the data and every custom app we write for you, and you can host it wherever you like - with us, on Frappe Cloud, or on your own servers.

Upgrades are planned, not discovered Custom work is written as separate Frappe apps rather than edits to ERPNext itself, so major version upgrades are a scheduled job rather than a rescue.

What it costs

What an ERP implementation costs

The software has no licence fee, so you pay for the work of setting it up properly and nothing per user. These are starting prices - the final figure is fixed in writing before any work starts, and does not move once it is.

Core

4 - 8 weeks

From KES 350,000

From USD 3,500 billed internationally

One company on accounts, stock, sales and purchasing, with eTIMS, migration from your current system, and training for each team. The fit-gap is included in the price.

Multi-branch or manufacturing

8 - 14 weeks

From KES 750,000

From USD 7,500 billed internationally

Several branches or companies, manufacturing, payroll, route sales or custom apps. Starts with a paid fit-gap week, credited in full against the implementation.

starting prices - fixed in writing before work starts, then they hold

Already on ERPNext? eTIMS, payroll and support are priced on their own pages. Hosting is billed at cost, and larger fit-gaps run as a discovery week.

Before you commit

What people ask before choosing an ERP

Are you an official ERPNext partner?

No. ERPNext is open-source software made by Frappe Technologies, and anyone may implement it. We are an independent implementer, and we will say so plainly rather than borrow a badge we have not been given.

Why ERPNext rather than Odoo, Sage or a custom build?

ERPNext is complete, open source and has no per-user licence fee, so the cost of adding staff does not climb every year. It is not always the right answer - a small business with simple stock is better on an accounting package, and a business whose core process is unusual may need a custom system. The fit-gap week tells you which.

How long does an ERP implementation take?

A single company with accounts, stock, sales and purchasing usually takes four to eight weeks. Manufacturing, several branches, payroll or heavy data migration push that towards twelve. The fit-gap week fixes the date.

Can you move our data from QuickBooks, Sage or Excel?

Yes. Customers, suppliers, items, open invoices, stock and opening balances are migrated, and checked against your closing trial balance before go-live. A migration that does not reconcile is not finished.

Where is ERPNext hosted, and who owns the data?

You own the instance and the data. We can host it on infrastructure we run, set it up on Frappe Cloud, or install it on your own servers. Because ERPNext is open source, you can move it later without asking anyone.

Can you fix an ERPNext system someone else set up?

Yes. We start with an assessment of the configuration, data and any custom code, then fix what is wrong at a fixed price, and support it from there.

Every question we get asked is on one page, if you would rather read the lot.

ERPNext and Frappe are trademarks of Frappe Technologies Pvt. Ltd. Noria Technologies is an independent implementer and is not affiliated with or endorsed by Frappe.

Not what you needed?

Discovery - Change your mind on paper, not in week nine. A week with the people who would build it, working out what actually needs building - before anyone writes code you paid for. 5 - 8 working days Review - You built something. Will it survive real customers? A review of software you built with AI, inherited, or quietly stopped trusting - before it holds real money. 3 - 10 working days Build - Built to be used every day, not demonstrated once. Customers, orders, stock, invoices, payments - built around how the work already moves, by people who are still here next year. 4 - 12 weeks Care - The year after launch is when it breaks. Monitoring, tested restores, patching, and a person who answers - monthly, from the day you go live. Monthly

Tell us what the current system gets wrong

Whether you are on spreadsheets, an accounting package you have outgrown, or an ERP nobody trusts - the call is free and ends with an honest view of what fits.

Free 30-minute call
Fit, timeline and budget range
A straight answer if an ERP is wrong for you

Or reach us directly

Weekdays, and we answer the same day.