Use case

    Control your ERP spend before the renewal, not after

    Who this is for

    Operators at 20-500 person companies who signed an ERP for one problem and now pay for modules, seats, a partner retainer, and a middleware layer holding it together.

    What you'll walk away with

    A full landed cost of your ERP footprint and a defensible list of what to keep, right-size, or replace with a lighter tool before the next renewal.

    Place yourself first

    Count how many of these describe your team today. The read underneath tells you where to start, so you don't spend the quarter fixing the wrong layer.

    • The annual ERP invoice is materially larger than the number you signed.
    • Whole modules are licensed and barely used.
    • Seats are assigned to people who left or who only need read access.
    • A partner or consultant retainer runs continuously, not per-project.
    • Custom fields and workflows exist that nobody currently on staff built.
    • Reporting still happens in spreadsheets exported from the ERP.
    • A separate integration platform exists mainly to move data in and out of the ERP.

    Early

    4+ symptoms: you're paying for a platform you're using as a database. There is real money here.

    Building

    2-3 symptoms: right-size seats and modules at renewal; keep the core.

    Optimizing

    0-1 symptoms: the ERP is earning its cost. Optimize integrations, not licences.

    What's actually going wrong

    The license is a fraction of the landed cost

    Budget tracks the ERP line item, while implementation partners, integration middleware, add-on modules, and internal admin time are booked elsewhere.

    What it costs
    Renewal decisions get made on the smallest number in the equation, so nobody ever sees the real total.
    What fixing it looks like
    One landed-cost model: license plus modules plus seats plus partner fees plus integration spend plus internal hours.

    Modules bought for a roadmap that never happened

    Inventory, field service, or advanced financials were included in the deal and never rolled out.

    What it costs
    Recurring spend against zero adoption, renewed automatically each year.
    What fixing it looks like
    Per-module usage pull before renewal, then drop or renegotiate anything below a usage floor you set in advance.

    Seat sprawl

    Full seats issued to people who need a report, not the system.

    What it costs
    Full-seat pricing for read-only behavior, multiplied by headcount growth.
    What fixing it looks like
    Tiered access: full seats for operators, read-only or dashboard access for everyone else.

    Integration tax

    A middleware subscription exists mostly to keep the ERP synced with CRM and billing.

    What it costs
    A second recurring bill created by the first one, usually never re-evaluated.
    What fixing it looks like
    Check native connectors first; keep middleware only for the pairs that genuinely lack one.

    Renewal happens without leverage

    The conversation starts 30 days out with no usage data and no alternative priced.

    What it costs
    Uplifts get accepted because there's no time to do anything else.
    What fixing it looks like
    Start 120 days out with usage data, a costed alternative, and a walk-away number.

    Where ERP-adjacent spend actually hides

    LayerWhat teams usually runWhere the gap is
    Core ERPNetSuite, Odoo, Dynamics, AcumaticaModule bundle rarely re-audited after year one.
    AccountingQuickBooks kept alongsideTwo ledgers, one reconciled by hand.
    IntegrationsMiddleware subscriptionDuplicates native connectors you already own.
    ReportingExports to spreadsheetsPaying for ERP reporting you don't use.
    WorkflowPartner-built customizationsUndocumented, so change requests go back to the partner.
    DocumentsManual invoicing stepsAutomatable with a micro-service, not another module.

    Pricing and features change constantly—always confirm current details on the vendor's own site before you buy.

    The first 90 days, with named deliverables

    1. 1

      Days 1-21—Establish landed cost

      • Every ERP-related invoice from the last 12 months in one model
      • Per-module and per-seat usage pull
      • Internal admin hours estimated and priced
    2. 2

      Days 22-60—Right-size

      • Keep / right-size / retire decision on each module with the usage evidence attached
      • Access tiering so read-only users stop consuming full seats
      • Native-connector swap list to reduce middleware scope
    3. 3

      Days 61-120—Negotiate

      • Costed alternative scenario, including a lighter best-of-breed stack
      • Renewal brief with usage data, walk-away number, and target term
      • Documented workflows so the partner retainer becomes project-based

    Teams we've done this with

    Questions operators ask us

    Should an SMB replace its ERP or right-size it?

    Right-size first in almost every case. Replacement projects consume a year and reintroduce the same customization debt. Cutting unused modules, tiering seats, and moving the partner from retainer to project usually recovers more, faster, and with none of the migration risk.

    What does ERP actually cost a small business per year?

    The license is typically the smallest component. Once modules, seats, implementation or partner fees, integration middleware, and internal administration time are counted, the landed cost is routinely two to three times the number on the contract. That's why we model all six lines before making any recommendation.

    When is a lighter stack genuinely better than an ERP module?

    When the module exists to solve one workflow—invoicing, inventory counts, field checklists—and the rest of the platform isn't carrying it. A purpose-built tool or a scoped automation is often cheaper and faster to adopt than turning on another module and paying a partner to configure it.

    Want to build this in-house first?