Type at least 3 letters to search

ServicesDevelopment

ERP Development

ERP development that starts with the system you already have: we find out what works, what holds the business back, and then build what your operations actually need, whether that means improving your current ERP, integrating it, or replacing parts of it with a custom build.

The final price depends on the size and complexity of your operations; starting prices are below.

Pricing

from $50,000

9Years in the market
50+Team & partners
127Projects delivered
12Countries
Up to 700%Revenue growth
48hProject start

What we cover

An ERP is supposed to be the operational backbone of a company: inventory, orders, production, purchasing, finance, and the people who move them. In practice, many businesses run on an ERP that half-fits, surrounded by spreadsheets and manual workarounds that quietly carry the real process.

We do not start by selling a new system. We start by examining the one you have: what it does well, where the business has outgrown it, and which parts are worth keeping. Then we build around what your operations actually need: own what differentiates you, rent what is commodity, and connect everything so it works as one system.

Selected Work

Projects where the architecture of the whole business system, not just one tool, was part of the job.

How It Works

01

05

Discovery & Current-System Audit

We talk to the people who use the system daily and use AI-assisted code analysis to trace how orders, stock, and money actually move through it.

02

05

Keep / Fix / Replace Map

We document which parts of your ERP to keep, which to reconfigure, and which to build, with the reasoning for each decision.

03

05

Architecture & Scope

We design how the pieces fit together, including integrations with CRM, e-commerce, and accounting, and agree on phases.

04

05

Build & Integration

We implement the changes in phases, so the business keeps running while the system improves underneath it.

05

05

Launch, Training & Support

We migrate data, train your team, and stay on to support and evolve the system as the business changes.

Ready to find out what your ERP should look like?

What You'll Walk Away With

A clear picture of how your operations really run, and a system built around them instead of the other way around.

icon

A clear map of how your operations actually run

icon

A decision on what to keep, fix, or replace

icon

An ERP that fits the business instead of the template

icon

Current-System Audit Report

icon

Keep, Fix, Replace Map

icon

System Architecture Blueprint

icon

Integration Plan (CRM, e-commerce, accounting)

icon

Data Migration Plan

icon

Phased Implementation Roadmap

icon

Custom Modules for Your Unique Processes

icon

Team Training & Documentation

icon

Ongoing Support & Evolution Plan

How you can work with us

Whatever the format, the work is shaped around how your business runs, not a template, and what we build belongs to you. The same people and standards in three formats: choose the one that fits your stage, or combine them.

Pricing

from $50,000

These are starting points. The final price is set after a strategic session, and its $500 is credited toward the project.

All prices

Ask a question

Leave your contacts and we will contact you at a convenient time.

By clicking the "send" button, you consent to the processing of personal data.

FAQ

Do we have to replace our current ERP?

Not necessarily. We start by auditing what you already have. Often the right answer is to keep the core, reconfigure parts of it, and build custom modules only where your processes are genuinely different.

Isn't fixing an old ERP more expensive than starting over?

It used to be. Tracing errors through years of accumulated custom code often cost more than writing new code, and on large projects that cost went straight into the price of the product. AI-assisted code analysis with tools like Claude Code and Cursor changed that: we can read, map, and test legacy code far faster, so keeping what works is now a real option. Every finding is still verified by an engineer before anything changes.

What is the difference between CRM and ERP?

A CRM manages customers, leads, and sales. An ERP manages the resources of the whole company: inventory, orders, production, purchasing, and finance. Many businesses need both, connected so data flows between them.

Do you work with existing ERP platforms, or only build custom?

Both. We work with the platform you already use where it serves the business, and build custom software on Laravel where your processes do not fit a standard template.

When does a custom ERP make sense?

When your key processes are what makes your business different and a standard system forces you into workarounds. If a process is common to every company in your industry, renting it is usually smarter than building it.

How do you avoid disrupting the business during the change?

We work in phases. The existing system keeps running while new parts are built, tested, and connected, and data migration happens in controlled steps.

Do you work with businesses outside Seattle?

Yes. We are based in the Seattle area and work with companies in the United States, Ukraine, and the Middle East, with most of the work done remotely.

How long does it take?

The audit comes first and usually takes a few weeks, depending on the size of the system. The build is phased, so the business sees improvements step by step instead of waiting for one big launch.

Will I be able to track my project?

Yes. Every client gets access to our project portal: stages, approvals, documents and requests in one place.

How much does a custom ERP cost over five years compared with Odoo or Business Central?

A custom ERP at Peretz Agency starts from $50,000, and support from $1,000 a month, so the floor over five years is about $110,000 plus hosting, with no seat fees. As of October 2026, 25 users on Dynamics 365 Business Central Essentials ($80 per user a month, paid yearly) cost $120,000 in licences over five years, and on Odoo's Custom plan ($61.00) $91,500, before implementation partners and add-ons. At that size fit, not licences, decides; the gap grows with every user you add.

What data moves into the new ERP, and what stays in the old system?

Reference data moves first: items, units, suppliers, customers and price lists, cleaned of duplicates. Then come opening balances at an agreed cut-off date and the open documents, such as unpaid invoices and orders in progress. Years of closed history rarely need to be converted line by line; a read-only archive of the old system is often cheaper and safer. Every import is tested on a closed copy and reconciled before the switch.

Which department should move to the new ERP first?

Usually the one where errors cost the most, which is often inventory and purchasing: once stock and receipts are right, production and sales can rely on them. Finance moves last, when the documents feeding it are reliable. Each stage runs in parallel with the old system until the numbers match, and discovery sets the order and the dates for your company.

Who can change prices or write off stock, and is every change recorded?

Access is set by role before the screens are built: who may change a price, approve a purchase order, write off stock, close a period or see margins. Every change to a stock figure, a price or a document status is recorded with the user and the time, and a closed period can only be corrected with a new document. We check these rules with automated tests.

Can the ERP work with our accounting system and send invoices electronically?

Yes. We decide which system owns each figure: usually the ERP owns stock, costs and purchase prices, and the accounting system owns the posted ledger, so invoices and payments pass to it instead of being entered twice. The invoice data leaves the ERP complete and in the format your accounting system or e-invoicing provider accepts, and the response comes back to the document.

What do we receive at the handover of a custom ERP?

At handover you get the code, the deployment commands, the server requirements, a rollback procedure and an AGENTS.md file that describes the structure, the rules and the commands, so another team or an AI coding agent can continue the work. Your data sits in a model named after your business, and exporting it is a database query rather than a request to a vendor.