Discovery sprint

    Know what needs changing before you start

    Rig’s engineers map your systems and record walkthroughs with the people who run each process, in a fixed-price sprint. You leave with the maps, the gaps and a plan you can price.

    Book a discovery sprint

    Most migration plans are written before anyone has watched the work

    Architecture documents show how the systems were designed. The spreadsheet in the middle of order to cash, the field only finance understands and the record keyed into three places only show up when someone watches the work. A plan built without them is priced on guesses, and the gaps appear during cutover.

    What you leave with

    Everything the sprint produces stays with you, whether or not a migration follows.

    • Out-of-date diagrams

      A live Systems Map

      The map shows every system, the flows between them and what depends on what, built from your documents and from the systems themselves.

    • Undocumented processes

      Workflow maps

      Recorded walkthroughs with the people who run each process become step-by-step maps, each step linked to the system and field it uses.

    • Unknown joins

      Schemas and join keys

      We document the tables behind each process and how records match from one system to the next.

    • Surprises at cutover

      A list of gaps

      Workarounds, duplicate entry and open questions go on the list before anyone prices the build.

    • Everything in scope

      The core systems

      We set aside systems outside the day-to-day work, so the plan covers the ones that run your transactions.

    • Open-ended pricing

      A fixed scope and price

      You agree the scope and price for the migration before any build starts.

    How the work runs

    1. Start read-only

      We start on read-only access to your main systems and the architecture documents you already have.

    2. Record the walkthroughs

      Our engineers sit with the people who run each process, such as order to cash or credit control, and record the work screen by screen.

    3. Build the maps

      Rig turns the documents, the systems and the recordings into the Systems Map, workflow maps, schemas and a list of gaps.

    4. Agree the plan

      You decide what to keep, migrate, retire or rebuild, and that decision sets the scope of the migration.

    What comes next

    Common questions

    How long does the sprint take, and what does it cost?

    Both are fixed and agreed before we start, sized to the number of systems and processes you want mapped.

    Who on our side needs to be involved?

    We need the people who run each process, for a recorded walkthrough of their daily work, and someone who can grant read-only access to the systems.

    Do you need access to production data?

    No. The first version of the map can come from your architecture documents and the walkthroughs, with read-only access to the systems. Wider permissions follow only for the phase you approve.

    What if we decide not to migrate?

    You keep the maps and the plan. Some teams use them to brief a systems integrator, and some decide the change is smaller than they feared.

    Can we run it with an agent opportunity assessment?

    Yes, together or separately. The sprint maps how the work runs today, and the assessment shows which agents are worth building on top of it.

    SOC 2 Type 2EU and US hostingRole-based accessYour warehouse or ours

    Talk to Rig

    What work do you want to improve?

    Tell us where your team spends time, loses money or needs better information.
    In a 30-minute call, we’ll discuss the data and systems work that could help.

    Book a discovery sprintUse the platform with your team, or add our engineers.