A transformation, a build, or a growth project?
Choose between company-wide transformation, a focused build, and revenue acceleration. Start with the decision your business actually needs to make.
Start by asking what the company needs to decide. If you need to find the right work to change, begin with discovery across the operation. If you already have a specific bottleneck, scope a build. If your priority is growth, identify the commercial activity that limits the result.
At Outerscope Studios, these starting points correspond to transformation, capacity generation, and revenue acceleration. They describe the work an engagement needs to do, rather than the size of a software package.
Choose the starting point
| Your situation | Start here | First useful output |
|---|---|---|
| Several teams see opportunities, but nobody has agreed what matters most. | Transformation | A ranked view of the work, followed by selected implementations. |
| A known process needs a specific improvement or tool. | Capacity generation | A scoped system with acceptance criteria and an implementation plan. |
| You want to improve an established revenue channel or commercial motion. | Revenue acceleration | A named revenue driver, a baseline, and a testable intervention. |
Listen for the missing decision
Consider three illustrative requests from the same service company.
“We bought AI licenses, but use is uneven.” The immediate need is to understand roles, tools, and recurring work. Interview the people using the tools, inspect examples, and rank improvements. Buying another application before this work would leave the original uncertainty unresolved.
“Our support team copies information from Gmail into three systems.” The bottleneck is already named. Check permissions, the fields that need to move, and the cases that require review. A focused implementation may be sufficient; there is no need to examine every department first.
“We can deliver more projects, but proposals take too long.” Start with the sales process. Determine whether proposal turnaround is actually holding back conversions. The intervention could involve research, pricing preparation, approvals, or software. Measure the commercial result as well as the time saved.
Bring these five things to discovery
- A recent example. Show a real request from arrival to completion, with sensitive information removed where appropriate.
- The owner. Include someone who runs the process and someone who can approve changes.
- The pressure. Explain whether the problem is workload, quality, delay, adoption, or revenue.
- The constraints. Name the systems, permissions, deadlines, and decisions that must stay with a person.
- A useful outcome. Describe what you want the team to be able to do afterward.
Keep the path open to evidence
A focused build can reveal a wider process problem. A transformation audit can identify a small, valuable first implementation. Agree on the next decision and its evidence before expanding scope.
If you are still weighing the starting point, the approach questionnaire asks about your goals, the work under pressure, team confidence, and timing. If you already have several candidates, use the workflow audit worksheet to compare them. Once capacity has been recovered, give it a destination using the revenue worksheet.