How to pilot superglue

1. Pick one implementation

Open-ended trials tend to fade out. Four weeks pass, nobody finds the time, and there is nothing to judge. A pilot works better with one implementation, a named owner, and a go-live date. Good candidates are projects already on the roadmap that keep slipping:

• An ERP implementation or module rollout (NetSuite, Sage Intacct, SAP, Business Central, or Acumatica), including migrating the legacy data
• Bringing a new entity, subsidiary, or acquisition onto your existing systems
• Onboarding a new customer onto your platform, including their historical data
• Retiring a legacy system that has been planned for a long time

Work with the team that owns the process: finance systems, operations, IT, or the implementation team. Bring them a proposal with the implementation, the owner, and the go-live date. Adjust it based on their input.

2. Record the "before"

Before you start, write down how your last comparable implementation went. Use numbers wherever you can. The project plan, the statement of work, and the calendar of workshops are good sources.

3. Give superglue your knowledge and your systems

superglue learns how your business works from what you already have: process documentation, configuration standards, the chart of accounts, data dictionaries, and the legacy system itself. The more it can see, the fewer questions it needs to ask. Then connect the target and source systems. Request access early. Service accounts and network access can take a week to get through IT. superglue's team helps with setup. Self-hosting is available if data cannot leave your environment.

• Target system: NetSuite, SAP, Sage Intacct, Business Central, Acumatica, or your own platform
• Source systems: the legacy ERP, spreadsheets, databases, the customer's or entity's existing systems
• Company knowledge: Google Drive, SharePoint, Confluence, process docs, past implementation plans
• On-prem and internal systems: through the Secure Gateway

4. Run the implementation

superglue does the implementation. It maps and migrates the data, configures the system, and keeps it in sync after go-live. Your team's role is the same as with any implementation partner: define the outcome, answer questions about how your business works, and sign off at milestones. Nothing goes live without your approval. While it runs, keep a short log:

• Each milestone and the date you reached it
• The questions superglue asked you. That is coordination work you did not have to do yourself.
• What you would have paid a partner for, or done in a workshop, at each step

Most of your evidence comes from this log. It is much easier to write as you go than to reconstruct later.

5. Measure the "after" and present the case

Answer the baseline questions again with the pilot's numbers. Leadership rarely has time for a long list. Pick the four or five most telling figures, put each next to its baseline, and add one quote from the person who owned the implementation.

Example layout. Replace with your own baseline and pilot figures.

"We brought the new entity live in three weeks. The last one took two quarters and an implementation partner."Example quote. Use one from your own team.

A typical pilot runs four weeks from kickoff to go-live, with one check-in per week. The weeks can shift with the size of the implementation. The check-ins stay the same.

1. Kickoff · Day 0
   Scope, baseline, access

   Agree on the implementation, the owner, and the go-live date. Go through the baseline numbers. Share the documentation superglue will learn from, and start the access requests for the target and source systems.

   Check-in: kickoff call with superglue. Everyone leaves with a written scope and a date.

2. Week 1
   Discovery and mapping proposal

   Systems are connected. superglue reads the source system and your documentation. It comes back with a proposed configuration and data mapping, plus the questions it could not answer on its own.

   Check-in: review the proposal, answer the open questions, and correct anything that does not match how the business works.

3. Week 2
   Configuration and first migration

   superglue configures the target system and runs the first migration into a test environment. The process team sees real records in the new system for the first time.

   Check-in: mid-pilot review. Walk through the configured system together and sign off on the mappings.

4. Week 3
   Reconciliation and acceptance

   Reconcile the migrated data against the source, resolve edge cases, and run the process end to end in the new system. The team that owns the process decides whether it is ready.

   Check-in: go or no-go decision for go-live.

5. Week 4 · Go-live
   Go-live and the evidence

   Final migration. The system goes live, and superglue keeps it in sync from here. Write down the before and after figures and the quote while they are fresh.

   Check-in: closing review. Present the case and agree on what the rollout looks like.

A pilot proves one implementation. Rollout is where the value adds up: the next entity, the next module, the next customer. Each one is done the same way, using what superglue already knows about your business, without starting the coordination from zero.

Bring your pilot evidence to a call with us. We will plan the rollout together: which implementations come next, how access is governed across teams, and what an enterprise contract looks like.