# The RISE method > RISE is the four-phase method Risen Digital uses on every engagement: Research and Roadmap to understand the process and agree what to build first, Implement and Integrate to build it in draft mode connected to your systems, Scale and Support to widen permissions and volume on evidence, and Empower and Evolve to hand the system to your team with the training and documentation to keep improving it. Each phase ends with something you keep and a decision about whether to continue. Source: https://risendigital.io/guides/the-rise-method Publisher: Risen Digital Updated: 2026-09-21 ## At a glance - **Research and Roadmap:** We map one process end to end, find where the data lives, and agree a first build with a written definition of done. - **Implement and Integrate:** We build the first version read-only and in draft mode, connected to your real systems, and review it with you every week. - **Scale and Support:** We widen what the system may do alone as its track record earns it, add volume and processes, and put monitoring in place. - **Empower and Evolve:** We train your team, hand over documentation and evaluation sets, and agree how the system keeps improving after we step back. - **What you bring:** A process owner with time each week, access that starts read-only, and honest feedback on what the system gets wrong. Every engagement we run follows the same four phases. This page explains what happens in each, what you receive at the end of it, what we need from you, and why the phases sit in this order. Treat the timeline as the typical shape, not a promise. ![A team working through a plan together at a whiteboard](https://risendigital.io/images/experience/whiteboard-team-1600.jpg) ## Why is the RISE method ordered the way it is? Because each phase settles the biggest remaining unknown before you spend on the next: what to build, whether it works on your data, whether it can be trusted with more, and whether your team can run it without us. AI projects fail in predictable places. The wrong process gets chosen. The first version works on a demo and not on real records. Permissions widen before the evidence supports it. The partner leaves and nobody inside the company understands the system. RISE puts a phase in front of each of those failures. The order also matches how trust is built. You cannot judge us on a roadmap, so the first build is small and comes early. You cannot trust software with write access until you have watched it draft correctly, so it starts read-only. Your team cannot own a system it has not been taught, so training and documentation are a phase, not an afterthought. ## What does a RISE engagement look like from start to finish? A typical engagement moves through the four phases in order, with a decision point at the end of each. The spans below are a typical shape; a bounded process runs shorter and a platform runs longer. _Interactive on the web page: The four phases of a typical engagement. The timeline shows four phases in sequence. Research and Roadmap typically runs a few weeks and ends with a process map, a data and access map, and a first build agreed in writing. Implement and Integrate is the longest phase and ends with a working system in draft mode connected to your systems, with weekly reviews along the way. Scale and Support widens permissions and volume on evidence and adds monitoring and a support arrangement. Empower and Evolve hands the system to your team with training, documentation and an improvement plan. Each phase ends with something you keep and a decision about whether to continue._ ## What happens in Research and Roadmap? We learn how the work is actually done, where the data lives and where the exceptions are, then agree the smallest first build that would be worth having. - **What we do** Interview the people who do the work, watch the process, read the documentation that exists and write the parts that do not, and inventory every system involved and what access it allows. - **What you get** A process map with the exceptions marked, a data and access map, a scoped first build with a written definition of done, and a roadmap of what could follow if the first build earns it. - **What you bring** A process owner with a few hours a week, introductions to the people who do the work, and read-only access to the systems on the map. - **Why it comes first** Choosing the wrong process is the most expensive mistake in the project, and it is cheapest to avoid before anything is built. > **It is fine to stop here** Some engagements end after this phase with a roadmap and no build, because the research showed the process was not ready or the value was elsewhere. That is a good outcome, not a failed one. ## What happens in Implement and Integrate? We build the first version against your real systems, in draft mode with read-only access, and review real cases with you each week until the drafts are consistently right. - **What we do** Build the tools the system needs to read your records, write the instructions and rules, connect the agreed integrations, and run real cases through it in shadow mode, where it proposes and a person confirms. - **What you get** A working system you can watch handle your own cases, an evaluation set built from those cases, weekly review notes, and a change log that shows what was fixed and why. - **What you bring** An hour or two each week to review cases with us, quick answers when the system finds a rule nobody wrote down, and honesty about what it gets wrong. - **Why it comes second** Nothing about an AI system is certain until it meets real data. Building small and reviewing weekly finds the problems while they are cheap. The weekly review is the heart of this phase. We look at cases together, including the ones the system got wrong, and decide whether the fix is a tool, an instruction, a missing document or a rule you had not written down. Prompts are usually the last thing we change. ## What happens in Scale and Support? We widen what the system may do on its own as its track record earns it, add volume and neighbouring processes, and put monitoring and support in place so it stays healthy. - **What we do** Raise permissions in narrow steps with written limits, add the next process from the roadmap, set up monitoring and alerts for drift and failures, and agree who responds when something goes wrong. - **What you get** A system that completes routine cases itself within limits you set, alerts when it is unsure or when something changes, a support arrangement, and a clear breakdown of what it costs to run. - **What you bring** Decisions about limits and thresholds, someone on your side who receives alerts, and the patience to widen on evidence rather than on a date. - **Why it comes third** Permission widened too early is how automation loses a team's trust. This phase makes every widening a decision backed by a record. ## What happens in Empower and Evolve? We hand the system to your team: training for the people who will run and change it, documentation and runbooks, the evaluation sets, and an agreed way to keep improving it after we step back. - **What we do** Run training sessions for owners and operators, write the runbooks, hand over the repository and the evaluation sets, and agree a cadence for proposing, testing and releasing improvements. - **What you get** A team that can operate the system, explain it and change it, documentation someone else could pick up, and a plan for how it evolves as your business does. - **What you bring** Named people who will own the system, time for the training, and a decision about how much ongoing support you want from us. - **Why it comes last** A system nobody inside the company understands is a liability, however well it works. This phase is what makes the engagement finish rather than fade. ## Frequently asked questions **Q: How long does the RISE method take?** A: It depends on how documented the process is, how accessible the systems are, and how far you want to take it. A bounded process with existing integrations moves through the phases quickly; a platform that touches many systems runs longer. The spans on this page are a typical shape, and each phase ends with a decision about whether to continue. **Q: What access does Risen Digital need at the start?** A: Read-only access to the systems the first process touches, and introductions to the people who do the work. Write access comes later, in narrow steps with written limits, once the system has shown it drafts correctly on your real cases. **Q: Who owns the code, the prompts and the data at the end?** A: You do. The repository, the prompts, the configuration, the evaluation sets and the documentation are yours, and you can see them from the start of Implement. Empower and Evolve exists to make sure your team can use them without us. **Q: What if the research phase shows the process is not ready?** A: Then the engagement ends with a roadmap instead of a build, and we say so plainly. Usually the roadmap names what would need to change, such as documenting the rules, cleaning a data source or opening an API, so you know what readiness looks like. We consider that a good outcome. **Q: How is RISE different from a normal software project?** A: A normal project can specify most behaviour up front. An AI system's behaviour is only known once it meets real data, so RISE puts a review loop on real cases at the centre, starts read-only, and treats widening permissions as a phase in its own right. It also treats hand-over as a phase, because a system your team cannot run is not finished. ## Related pages - [90-day AI implementation roadmap](https://risendigital.io/guides/90-day-ai-implementation-roadmap) - [AI readiness checklist](https://risendigital.io/guides/ai-readiness-checklist) - [How to choose an AI development partner](https://risendigital.io/guides/how-to-choose-an-ai-development-partner) - [What is a business operating system?](https://risendigital.io/guides/what-is-a-business-operating-system)