A traditional ERP project fixes scope and lets the date float: exhaustive requirements up front, a plan that stretches to fit them, and a go-live date that is a forecast — one that slips as integration, custom code and data problems surface. T-Minus turns that round. The date is set on day one, typically 27 working days out, and everything counts backward to it. Anything that cannot be configured, migrated and rehearsed in time moves to a T-Plus wave.
Agree the go-live date in the kick-off and write it on the countdown board. From that moment the team never debates the date; every discussion is about scope.
Why 27 days is not heroics
It is not the old playbook compressed. Four phases that consume most of a traditional project are removed, because the platform removes the reason for them:
| Traditional phase | Typically | Why T-Minus does not have it |
|---|---|---|
| Systems integration | Months | One ledger, one data model — nothing to stitch together |
| Custom development | Months to years | Workflows, roles and rules are configured no-code and changed in minutes |
| Data migration project | Months | The Migration Cockpit runs an audited cutover with reconciled trial balances as a product feature |
| Big-bang training | Weeks | The role-aware action queue and ASK coach users inside the flow of work |
The five rules
- The date doesn’t move. Scope does. Every threatening requirement is triaged: configure now, T-Plus, or not a requirement.
- No requirement without a screen. Discussions happen in a live tenant with the customer’s sample data; a requirement is a gap on a screen.
- Configure, never code. A configuration pattern, a T-Plus deferral, or an honest no. Code breaks the countdown.
- Migrate balances you can audit, not history you can’t. Open items, balances and master data, reconciled and signed; history stays queryable in the legacy archive.
- One rehearsal beats ten workshops. The customer runs a real business day in parallel with legacy; the rehearsal is the gate.
Print them on the countdown board. When a discussion stalls, the Flight Lead names the rule it breaks — which ends most arguments faster than any escalation.
Skin in the game
A day-rate integrator is paid by the day and earns from change requests, so it is structurally rewarded when a project stretches. TRANXACT is priced as a share of the customer’s audited revenue: it earns nothing extra from a long project and everything from a customer who is live and growing. The method and the commercial model point the same way.
What the customer measures (proposed default)
| Measure | Target |
|---|---|
| Days to first posted invoice | T-0, before lunch |
| Trial-balance delta at cutover | Zero, with an audit trail |
| Rehearsal pass rate | 100% — the T-1 gate |
| "We need X" → "X configured" | The same week, no ticket queue |
| Modules live per quarter | Without re-implementation — T-Plus waves |
These live in the Artifact Toolkit’s KPI Scorecard from T-0 and replace the status deck in every steering conversation.
Calderwood Group signed for Accounting, CRM and Supply Chain. At kick-off its COO, the Countdown Owner, writes the go-live date — 1 October, the first day of Calderwood’s fourth quarter — on the countdown board. HRMS was always going to be phase 2; in T-Minus terms it is simply a T-Plus wave on the same ledger.
Try it At T-14 Calderwood’s head of sales asks for a bespoke commission calculation "before we go live, or the date will have to move". Which rules apply, and what are the possible outcomes?
Rule 1: the date does not move, so the request is triaged. Rule 2: it becomes a Fit Ledger line only as a gap on a real screen. Rule 3: if configuration can meet it and it can be configured and rehearsed before T-3, it is Configure now; if it needs code, it is a configuration pattern, T-Plus, or an honest no. The Countdown Owner decides the same day, and the answer is never "move the date".