Optified - One page before you spend a dollar: what an ERP project charter actually needs

Most ERP projects fail before the first invoice is raised

Not because the software was wrong. Because nobody wrote down, in one page, what the project was actually for — and six months later, three people have three different answers to "what are we trying to achieve here."

A project charter sounds like corporate paperwork. For a 20-person NZ business about to spend five figures replacing its core systems, it's the cheapest insurance you'll buy all year.

What actually needs to be on the page

• The problem, in one sentence, with a number attached. Not "our systems are outdated" — "we spend roughly 6 hours a week re-entering the same job data into two systems, and it's getting worse as we grow." If you can't put a number on it, you're not ready to spend money fixing it.
• What "done" looks like. Specifically. "Staff can raise a quote from stock, inventory updates automatically, and the accountant doesn't need to re-key anything into Xero." Vague success criteria are how a $25k project becomes a $60k project.
• Who actually decides. Not who's in the room — who can say yes, and who can quietly kill it by not showing up to the second meeting. Name them before you start, not after the project stalls.
• What's explicitly out of scope. This is the line most owners skip, and it's the one that saves the most money. If payroll integration isn't in this phase, write that down — because six weeks in, someone will ask why it isn't done yet.
• The budget ceiling and the walk-away point. Not just what you're willing to spend — what result would make you stop and reconsider, rather than push through on sunk cost.

Why this matters more for ERP than almost anything else you'll buy

A new phone system is contained — it does one thing. An ERP touches quoting, inventory, invoicing, sometimes payroll, and every person who works with any of those. Scope drifts fast when there's no anchor document to point back to when someone says "while we're in there, can we also..."

The businesses that get ERP implementations right aren't the ones with the biggest budget. They're the ones who spent an afternoon writing one honest page before they spent a dollar on software.

If you're weighing whether an ERP project is even worth starting, Optified ERP is built around exactly this discipline — a scoped, fixed-price build on ERPNext, with the charter conversation as step one, not an afterthought once things have already gone sideways.

Want this measured for your business?

Book a free 20-minute Value Scan and we'll tell you whether there is a commercially meaningful opportunity in the process that hurts most. If there isn't, we'll say so.

Not ready to talk? Estimate what one process costs you a year with our free calculator.