01 / Scope & baseline
Before the pilot: define data, responsibilities and measurable acceptance criteria. Weeks 1–2: map and curate the CSV workflow.
PROPOSED PAID PILOT
Prove the workflow. Then decide.
A focused six-week evaluation for manufacturers, with a baseline, agreed acceptance criteria and a documented go/no-go—not an open-ended ERP project.
Scope a paid pilotFixed quote after scoping
THE BOUNDARY
Six weeks. One site. One workflow.
- 5–10 users; one agreed operational workflow.
- Curated CSV dataset, not a wholesale migration.
- Weekly reviews, guided training and named responsibilities.
- Baseline and written acceptance criteria before execution.
- Documented go/no-go and data export at the end.
OUT OF SCOPE
Keep the scope honest.
Full ERP replacement, payroll, autonomous regulatory decisions, unverified integrations, payment collection and guaranteed deployment dates are excluded.
Keep existing accounting. Begin with CSV import/export; assess local accounting and e-invoice requirements later. AI is optional roadmap only.
A PRAGMATIC SEQUENCE
Earn the next phase.
02 / Execute & review
Weeks 3–4: run the agreed pilot workflow, train users and review exceptions each week.
03 / Decide & export
Weeks 5–6: compare against the baseline, document go/no-go and export the dataset. Later phases need a new agreement.
Is six weeks a deployment guarantee?
No. It is a proposed pilot duration. Start date, feasibility, scope and acceptance criteria are agreed after scoping.
What does it cost?
Fixed quote after scoping. No approved tariffs are published, and this website does not collect payment.
Can we leave with our data?
The proposed scope includes data export and a documented decision at the end. Agree formats and responsibilities before starting.
SMALL SCOPE. A REAL DECISION.
One workflow. Six weeks. Know what comes next.
A proposed paid pilot with agreed acceptance criteria, weekly reviews and a documented go/no-go.
Scope a paid pilotFixed quote after scoping. No payment collected here.