Why we built our own ERP instead of customizing one off the shelf

Phase 0 is the paid week (sometimes two) we spend learning enough about a shop to write a real statement of work for Phase 1. It's the most important week of the engagement and the one that determines whether the rest works. Here's what we actually do.

Why a paid discovery at all

Most ERP vendors sell on the demo. They put a polished product in front of a shop owner, the owner says "yes, that would work," signs a contract, and then six months later both sides discover the product doesn't actually fit. The doesn't-fit is the cost. It's how most ERP rollouts go sideways.

We do it the other way. We charge for the discovery week up front, deliver a written analysis at the end, and let the customer decide whether to continue. If they don't, they walk away with a use

Day 4 — desk work. We sit in the conference room (or the hotel, or the rental car) and start writing. The deliverable is forming. We sketch the operational map of the shop, identify the three or four highest-value problems Forge can solve, write the proposed Phase 1 scope, and put a number on it. We also identify what's out of scope — what the shop wishes was true but can't be done in six weeks.

Day 5 — walk through the proposal with the owner. We don't email it. We walk through it in person (or on a long Zoom if travel is gone for the year). We expect pushback on at least one thing. The pushback is the conversation that turns a generic proposal into a real one.

What the customer gets at the end

A document, six to ten pages, specific to their shop. It includes:

• A summary of the operation as we observed it. Not opinions — descriptions. The owner reads this part and says "yes, that's us."
• A list of the operational problems we think Forge can address, ranked by impact.
• A proposed Phase 1 scope. What we'd configure, what we'd customize, what we'd integrate, what we'd leave alone. Fixed price. Fixed timeline.
• A list of what's NOT in scope and why. This is often more important than what's in.
• An honest assessment of risks. The things that could make Phase 1 go sideways and what we'd do about them.

Why this works for both sides

For the customer: they get a real document they can act on, whether they continue with us or not. They've spent a week pressure-testing whether we know what we're doing. They've seen us listen instead of pitch. By Day 5 they know whether they want us in their shop for six more weeks.

For us: we don't sign engagements blind. We've seen the actual operation. We can put a real number on Phase 1 because we've measured the actual scope. The shop pays for the time it costs us to get this right, and we don't have to bake risk premium into Phase 1 to cover what we don't know.

We've never had a Phase 0 that didn't produce a useful document, even the times the customer decided not to continue with us. That's the discipline of the format — five days of structured listening produces a real artifact whether or not it leads to a sale.

What we don't do in Phase 0

We don't install anything. We don't load reference data. We don't touch the customer's QuickBooks. We don't ask for system access beyond read-only views of whatever they want to show us. We don't promise anything we haven't observed.

We also don't sign a Phase 1 SOW on Day 5. The owner takes the document home, sits with it, talks to their accountant, talks to their spouse, talks to whoever else makes a five-figure-decision with them. We follow up a week later. Sometimes it's a yes. Sometimes it's a not-now. Sometimes it's a not-ever, and we send the invoice for Phase 0 and move on.

That's the whole week.