01
Sales and invoicing
Quotes, orders, deliveries and invoices in one file, with the margin shown on every line.
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.
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.
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.
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.
The quantities on screen do not match the shelves. People count before promising a date, then order twice to be safe.
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.
01
Quotes, orders, deliveries and invoices in one file, with the margin shown on every line.
02
Purchase suggestions worked out from actual demand and each supplier’s lead time, through to receiving.
03
Quantities on hand, committed and on order, by location, updated with every movement.
04
Bills of materials, work orders and a production calendar, for companies that make things.
05
Invoices, payments and suppliers sent to your accounting software. Online store and other tools connected by API.
06
Sales, margins, stock turnover: indicators computed from the ERP’s data, with no spreadsheet export.
01 Discovery
See an order’s margin before sending it
Must-haveTurn an accepted quote into an order
Must-haveSee available stock while entering an order
ImportantSuggest purchases from demand and lead times
Must-haveReceive part of a purchase order
ImportantCompare two suppliers’ prices
LaterStop re-entering invoices in the accounting software
Must-haveSee payments received by customer
ImportantClose the month without manual reconciliation
Later02 Analysis
03 Data model
04 Mockups
05 Specification
As a sales rep, I want to see each line’s margin while I enter the order, so that I can fix a price before the confirmation goes to the customer.
06 Development
Partial receipt of a purchase order
Purchasing ODPurchases by supplier report
Reports NK30-day purchase suggestions
Purchasing LMPurchase orders sent to accounting
Integrations ABAverage cost updated on receipt
Inventory NKSupplier import from the old ERP
Migration LMPurchase order PDF sent by email
Purchasing ODApproval of purchases over $5,000
Purchasing AB07 Quality
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
Each module first runs alongside the old tool. Nothing is switched off until your team has signed off the cutover.
02
Your data is imported several times before the real cutover. Each gap is explained, then fixed at the source.
03
The ERP sends it invoices, payments and suppliers. A rejected send shows the reason the software gave.
Widely used tools: your ERP never depends on a rare technology. See our technologies
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.
01
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
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
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
Order processing time, billing errors, inventory turnover: we track the indicators that matter with you, so every change is judged on its results.
Manufacturer, distributor, retailer: each case study opens up the ERP and explains the rules behind its screens.
Working with Witify is simple and efficient. They created an ERP system specifically for us that meets our specific needs.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Free. No commitment. Reply within 24 hours.
Names and figures shown in the interfaces are examples.