Guides
Written for the person who has to run the thing, not for the person signing the licence. Each one is specific enough to act on this week.
Erpification / Guides
Written for the person who has to run the thing, not for the person signing the licence. Each one is specific enough to act on this week.
Twenty scored statements about your data, your close and your inventory. No email required.
GuideWhat each stage produces, and what skipping it costs you at cutover.
ChecklistWhat to load, in what order, and how to prove it reconciled before go-live.
GuideHow to tell the difference before you spend a year on the wrong answer.
GuideThree decisions are one-way doors. Which changes are free, which are forward only, and which are never.
RunbookBuilt backwards from the rollback deadline: the irreversibility ledger, and the three exits at the gate.
GuideWhy falling ticket volume has two opposite causes, and the exit test a quiet retreat to the spreadsheet cannot pass.
GuideFour different things get called failure. A symptom lookup table for a project already in flight.
GuideHeadcount does not decide it. Count the records two systems both claim to own, then log the re-keying for two weeks.
ScriptThree transactions that each cross a boundary, a data pack left dirty on purpose, and a grade sheet with three columns instead of a score.
GuideA gap has more than one resolution and only one of them is on the quote. The admissibility test, six dispositions with their cost shapes, and why the party paid to close the gaps must not hold the pen on the disposition column.
GuideThree budgets, one invoice: the quoted price, your own payroll hours, and the output foregone. Never sum the columns. Prints no cost figure, and explains why the circulating ones cannot be traced to a sample.
MethodThe length of the close is the sum of your configuration gaps. Instrument three closes with a wait register before buying anything, then read the close log as a requirements document.
GuideOwnership follows the create button, not the org chart. The three questions that settle who owns a list, field-group ownership, and the retire-before-create rule.
Decision frameworkA decision per record class instead of keeping everything forever: four ways to keep data readable and what each costs, a read log, a review gate and a signed destruction certificate.
GuideDecided by a count, not by company size: the shared-record test, writers and readers with staleness as the deciding column, and the identifier precondition that makes either choice work.
The twelve-guide plan is complete. Each one was researched against what currently ranks for its question, written to what those pages leave out, and then checked by someone whose job was to find a reason not to publish it.
If a question none of these answers is in your way, write to hello@erpification.com and it goes to the front of the queue.