Skip to content

Custom ERPdevelopment

Sales, purchasing, inventory and accounting connected in an ERP built around your operations. Our Montreal team extends the system you have or builds a new one, one module at a time.

Talk to an expert

For
SMBs and growing companies
Technologies
Laravel, Vue, MySQL, AWS
Team
Montreal, all across Quebec

01 At a glance

ERPs that grow with the business

An ERP is not delivered in one piece. The ones we build gain a module at a time, on the same code base, year after year.
  • 8

    case studies of ERPs and management systems Manufacturing, distribution, retail and services.

  • 8years

    of growth for Luminaire Authentik’s ERP The same code base since November 2018, extended and never rewritten.

  • 8

    kinds of documents Distribution MA’s ERP sends to QuickBooks Customers, suppliers, invoices, purchase orders, payments in and out, credit notes on both sides.

  • 21

    features to switch on in Statim, the ERP we develop Each company turns on the ones it needs, when it needs them.

02 When

When your tools fall behind your operations

A custom ERP pays off when your workarounds cost more than a system built for you. These signs come up often in our first meetings.
A large warehouse full of shelves and boxes, seen from above
  1. An order retyped from one program to the next

    The quote in a spreadsheet, the order in the management software, the invoice in the accounting package. Every copy is a chance for a mistake.

  2. Prices and thresholds applied from memory

    Customer price lists, approval thresholds, reorder rules: the system cannot apply them. Someone does it by hand. When that person is away, everything slows down.

  3. Inventory nobody trusts

    The quantities on screen do not match the shelves. People count before promising a date, then order twice to be safe.

  4. Growth held back by the tools

    A second warehouse, an online store, a new product line: each step adds another file or tool to stitch in by hand.

A new ERP is not always the right answer. If yours covers the essentials, the analysis will say so.

Between keeping everything and replacing everything, there is often a middle path: keep your accounting software, extend the ERP you have with the missing module, or build the core of the system around your operations. Our business and technical analysis prices each path before the first sprint.

03 Modules

An ERP built module by module

We start with the module where you lose the most time or money. The next ones are added on the same data, with nothing keyed in twice.

04 Method

From the first meeting to the first module

Seven steps, from understanding your operations to release. Each one ends with something you review and approve before the next one begins.

01 Discovery

Understanding your operations, department by department.

Meetings with every department the ERP will touch: sales, purchasing, inventory, production, accounting. We write down needs in the words of the people who do the work, then rank them with you. That list becomes the project’s reference: what is essential, what can wait.
Fig. 01 Needs noted in meetings, ranked by priority

02 Analysis

Deciding which tools stay, connect or move over.

Accounting software, old ERP, online store, spreadsheets: for each tool, we decide with you whether it stays and connects to the ERP, or whether its data moves into it. We also check what each integration allows, so there are no surprises along the way.
Fig. 02 What stays, what connects, what moves over

03 Data model

Designing the ERP’s data structure.

Customers, items, orders, stock, invoices: before any code is written, we draw the ERP’s tables and their links, then sign them off with you. A structure that is right from the start lets you add a module years later without redoing what exists.
Fig. 03 The data model, signed off before the code

04 Mockups

Reviewing the screens with your teams before development.

The most used screens are drawn as mockups first. The people who will use them every day comment on them, and we adjust until they approve. Fixing a drawing costs far less than fixing a screen that is already coded.
Fig. 04 A screen mockup, commented on by your teams

05 Specification

Documenting each feature and its business rules.

Each feature is described with its business rules and acceptance criteria: calculations, approvals, permissions, edge cases. You approve the specification. It becomes the shared reference for your team and ours.
Fig. 05 A feature described and approved in the specification

06 Development

Building in one-week sprints.

The team builds one module at a time. Every week, your project manager shows you in staging what already works. You watch the ERP take shape and can shift priorities along the way.
Fig. 06 A week of development, task by task

07 Quality

Testing every change before release.

Every change is reviewed by a senior developer and passes a suite of automated tests that check your rules: prices, taxes, quantities, permissions. Your key users sign it off in staging before release. What worked yesterday still works tomorrow.
Fig. 07 A change, from code review to production

05 Transition

A new ERP, while the old one still runs

The delicate moment of an ERP project is the transition. We plan it module by module, with your real data and your tools still running. QuickBooks, Sage or Acomba: whether and how each integration works is confirmed during the analysis.

01

One module at a time

Each module first runs alongside the old tool. Nothing is switched off until your team has signed off the cutover.

02

Trial imports until every count matches

Your data is imported several times before the real cutover. Each gap is explained, then fixed at the source.

03

Your books stay in your accounting software

The ERP sends it invoices, payments and suppliers. A rejected send shows the reason the software gave.

06 Quality

Calculations that hold through every release

Your ERP carries your orders, your stock and your invoicing. A mistake there costs money. Here are the risks specific to an ERP and what we do to rule them out.
  1. Tests that replay your rules

    The risk
    A pricing fix throws off the taxes on another kind of invoice. Nobody notices until the customer does.
    Our choice
    Every rule (prices, taxes, quantities, approvals) has its own tests. The whole suite runs before every release.
    The gain
    The system grows without existing calculations changing behind your back.
  2. Access by role

    The risk
    A clerk edits a cost price or sees margins that are none of their business.
    Our choice
    Each role (sales, purchasing, warehouse, management) opens only the screens and actions it needs.
    The gain
    Cost prices and margins stay visible only to the people who need them.
  3. Every module tried before cutover

    The risk
    Finding an invoicing problem on go-live day.
    Our choice
    Each module lands in staging first, where your key users approve it with realistic data.
    The gain
    On go-live day, your teams already know the screen.
  4. A day of orders you can recover

    The risk
    An outage or a slip of the mouse wipes out a day of orders.
    Our choice
    A backup every day, sensitive data encrypted, and hosting on ISO 27001 and SOC 2 certified servers.
    The gain
    Your orders, stock and customer balances can be restored from the last backup.

The technology behind our ERPs

Widely used tools: your ERP never depends on a rare technology. See our technologies

Application
Laravel, PHP, documented APIs for your integrations
Interfaces
Vue, TypeScript, Tailwind CSS
Data
MySQL, versioned migrations
Integrations
QuickBooks, Shopify, REST APIs, depending on the tools to connect
Hosting
AWS, continuous deployment
Monitoring
Sentry, errors and performance in real time

07 AI

AI in an ERP, with a person in charge

Our developers use AI to move faster through repetitive work. It can also work inside your ERP, on specific tasks and under control.

In our work

  • Reading your old system’s exports to prepare the field mapping.
  • Drafting the tests for your pricing and tax rules, which the developer checks and completes.
  • Finding the rules an old system applies without documenting them.

In your ERP

  • Reading a supplier invoice and pre-filling the receipt for approval.
  • Answering a question about your sales or stock asked in everyday words.
  • Flagging an order whose margin or quantity looks unusual.

What stays in your hands

  • A price, an accounting entry or a payment: a person approves it.
  • Which modules come first: that is decided with you.
  • The code it helps write: same tests and same staging as the rest of the ERP.

Going further with AI

Document reading, search across your data, assistants for your teams: our AI integration service starts from your real tasks and keeps what truly takes work off your plate.

See our AI integration service

08 Go-live

A cutover prepared with your teams

Every module goes through the same steps before it goes live. The calendar takes your busy seasons and your fiscal year-end into account.
  1. Beta version A few users do their real work in the new module, with the old tool running alongside.
  2. Acceptance testing Your key users run their real cases in staging: an order, a receipt, an invoice.
  3. Data migration The final load, once the trial imports match.
  4. Production The cutover on the agreed date, then a last round of checks.
  5. Training Hands-on sessions, video tutorials and user guides for each team.

09 After

After go-live, a partner for what comes next

A live ERP changes how people work, and growth keeps shifting the priorities. We stay on as your technology partner: we watch what happens in the ERP, keep track of what automation and AI now make possible and advise you on what comes next. Monitoring in Sentry and updates are part of our support and maintenance offer.

01

Spotting the next bottleneck

When one step speeds up, another becomes the brake. We read the ERP’s data with you to see where time is lost now: orders waiting, approvals that stall, work done twice.

02

Automating what repeats

Reminders, reconciliations, reports, exchanges with customers and suppliers: we find the tasks the ERP can take over, with AI where it does better than a fixed rule.

03

Advising on what is worth building

A new module, an off-the-shelf tool connected properly or a small adjustment: we recommend the option with the best return, priced before it is planned. Sometimes the right answer is to build nothing.

04

Measuring what each change returns

Order processing time, billing errors, inventory turnover: we track the indicators that matter with you, so every change is judged on its results.

10 Work

ERPs that run real operations

Manufacturer, distributor, retailer: each case study opens up the ERP and explains the rules behind its screens.

View all projects

  • Luminaire Authentik

    Lighting manufacturing

    A 16,000 sq ft workshop. One ERP to run it.

    Custom ERP

  • Statim ERP

    Witify product, manufacturing ERP

    An order comes in. A finished product ships.

    Custom ERP

  • Original Garage Motosport

    Motorcycle parts, online retail

    Shopify sells the kit. The WMS counts its parts.

    Custom ERP

Working with Witify is simple and efficient. They created an ERP system specifically for us that meets our specific needs.

Marjolaine Audet-Robert Managing Partner, My Civic Address

11 Questions

Questions and answers

Cost, timelines, integrations, migration: the questions that come up before an ERP project.

Another question? Write to us at info@witify.io or call 1 800 334 9031.

Is a custom ERP more expensive than a pre-built solution?

Up front, often yes. Over five years, the math is different: a pre-built ERP comes with per-user licences, add-on modules, configuration fees and the hours spent working around what it does not do.

A custom ERP is not priced per user. At Witify, it also starts from Sprintify: AI-assisted code generation with ready-made packages and components (Sprintify UI). The budget goes to what is specific to you. Our article on what an ERP costs walks through the comparison.

What drives the cost of a custom ERP?

Five factors weigh the most: the number of modules, the number and quality of integrations, the state of the data to migrate, the number of roles and business rules, and the time your team can give to reviews.

We can give a ballpark at the first meeting. The detailed estimate comes with the analysis, which splits the project into phases, each with its length in weeks. The work is then planned in one-week sprints. Starting with a single module keeps the first investment focused.

How long does it take to develop a custom ERP?

Usually between 4 and 12 months, depending on the number of modules and integrations. Your teams can use the first module while the next ones are built.

The analysis produces a schedule by phase, which we adjust with you around your priorities and busy seasons.

Should we choose Odoo, Acumatica or a custom ERP?

If a package such as Odoo, Acumatica, SAP Business One or Dynamics covers most of your operations through configuration alone, take it. We will tell you so.

Custom makes sense when your main workflows force you to bend the package: costly custom development, modules paid for but worked around, rules that end up in spreadsheets. In between, a hybrid approach keeps a package for accounting and builds the module that sets you apart, connected by API.

Compare the five-year cost, the integrations and how easy it is to leave, not just the demo. Our article custom ERP or existing solution offers a grid to decide.

Can we start with a single module?

Yes. It is the approach we recommend: the module that solves your biggest problem first, on a data model designed for the whole ERP. The next modules are added to it without another migration.

Meanwhile, your current tools keep running. They are switched off one by one, once your team has signed off the cutover.

Can ERP integrate with our current systems?

In most cases, yes. For each system you keep (accounting software such as QuickBooks, Sage or Acomba, an online store, a payroll tool), we check its APIs, its import and export options and its limits. The plan sets out the data exchanged, how often it syncs and how errors are handled.

For the migration, we prepare the field mapping and trial imports. Your team checks the results before the cutover. The feasibility and cost of each integration are confirmed during the technical analysis.

What if my business evolves and needs new features?

The ERP evolves with it. A new module, a second warehouse or a new integration is added on the existing base, tested and then approved in staging like everything else.

With our support and maintenance offer, improvements follow a roadmap set with you.

Who owns the code of our ERP?

You do. Ownership of the code built for your project is transferred to you once it is paid in full, as our contract sets out.

That ownership holds up in practice: the code is versioned, covered by automated tests and documented, on widely used technologies (Laravel, Vue, MySQL). Another team could take it over if you ever chose to.

How can I be sure that Witify will stay with us in the long term?

Our first clients, who came on board when we were founded in 2016, still work with us. Luminaire Authentik’s ERP has been growing with us since 2018, on the same code base.

Supporting and evolving the systems we build is part of our regular offer, not an exception.

Can Witify solve complex problems?

Yes. An ERP is made of special cases: customer pricing, unit of measure conversions, configurable products, stock reserved across several orders. Our case studies show a number of them, such as the FIFO cost of every case at Distribution MA or the five quantities tracked for each item in Statim.

When a problem is truly new, we break it down during the analysis and test it on a mockup before programming it.

How are you different from other ERP vendors?

We do not implement a software package: we design and develop the ERP ourselves, in Montreal, then keep evolving it after go-live.

We show our work rather than describe it: each case study publishes the ERP’s screens and rules. An ERP is also called an integrated management system: our page on custom integrated management software looks at it from that angle.

An ERP to extend or to build? Let’s talk.

A 30-minute meeting: you walk us through your tools and the path of an order. You leave knowing which module to start with and the rough cost to expect.

  • A 30-minute call with an expert, not a salesperson
  • A realistic budget estimate, backed by numbers
  • A concrete action plan, whether you work with us or not
Or write to us

Free. No commitment. Reply within 24 hours.

Names and figures shown in the interfaces are examples.