How to pilot superglue
Run one implementation with superglue, go live, and collect the evidence you need to roll it out.
Introduction
A superglue pilot is one real implementation that goes live. It covers one system or one entity and runs for two to four weeks.
Enterprise implementations take months because of coordination between the business, IT, and a partner. superglue learns your business from your existing documentation and does the implementation.
The pilot succeeds when the implementation is live by the end date and the owning team would choose superglue again.
The pilot process
1. Pick one implementation
Choose one implementation with a named owner and a go-live date, agreed with the team that owns the process. Good candidates are roadmap projects that keep slipping:
- An ERP implementation or module rollout, including the legacy data migration
- Bringing a new entity, subsidiary, or acquisition onto your systems
- Onboarding a new customer, including their historical data
- Retiring a legacy system
2. Record the "before"
Write down how your last comparable implementation went, with numbers. The project plan and the statement of work are good sources.
Baseline questions
- How long did it take from kickoff to go-live?
- How many people were involved, including partners?
- How much of their time went into coordination?
- How many rounds of data mapping and reconciliation were needed?
- What did external implementation days cost?
3. Give superglue your knowledge and your systems
superglue learns from what you already have: process docs, configuration standards, data dictionaries, and the legacy system itself. Request access early, because IT approvals can take a week.
- Target system: your ERP or your own platform
- Source systems: the legacy ERP, spreadsheets, and databases
- Company knowledge: process docs and past implementation plans
- On-prem systems: through the Secure Gateway, or self-host superglue
4. Run the implementation
superglue maps and migrates the data, configures the system, and keeps it in sync after go-live. Your team answers questions and approves each milestone. Keep a short log:
- Each milestone and its date
- The questions superglue asked you
- What you would have paid a partner for at each step
5. Measure the "after" and present the case
Answer the baseline questions again with the pilot's numbers. Present the four or five most telling figures next to their baselines.
| Metric | Last implementation | Pilot |
|---|---|---|
| Kickoff to go-live | 5 months | 3 weeks |
| People involved | 9, incl. partner | 2 |
| Data mapping and reconciliation rounds | 4 | 1 |
| External implementation days | 40 | 0 |
Example figures.
The four weeks
A typical pilot runs four weeks with one check-in per week. The weeks can shift with the size of the implementation.
- Kickoff · Day 0Scope, baseline, access
Agree on the scope, the owner, and the go-live date. Review the baseline, share your documentation, and request system access.
Check-in: kickoff call. Everyone leaves with a written scope and a date.
- Week 1Discovery and mapping proposal
superglue reads the source system and your documentation. It proposes a configuration and data mapping, with its open questions.
Check-in: review the proposal and answer the open questions.
- Week 2Configuration and first migration
superglue configures the target system and migrates the data into a test environment.
Check-in: walk through the system together and sign off on the mappings.
- Week 3Reconciliation and acceptance
Reconcile the data, resolve edge cases, and run the process end to end.
Check-in: go or no-go decision for go-live.
- Week 4Go-live
Final migration. The system goes live, and superglue keeps it in sync. Record the after figures.
Check-in: closing review. Present the case and agree on the rollout.
From pilot to rollout
Each next entity, module, or customer runs the same way, using what superglue already knows about your business. Bring your pilot evidence to a call, and we will plan the rollout with you.
Ready to scope a pilot?
adina@superglue.ai · superglue.ai · superglue.ai/docs