What to expect from each deliverable
Audit, proposed solutions, the product itself and measurement: what each deliverable includes and how it helps you make decisions.
- Published
- November 13, 2026
- Reading time
- 3 minutes
- Written by
- The Roshal Lab team

A deliverable is only useful if it helps you decide
A forty-page report nobody opens again isn't a deliverable: it's a file. For us, every handoff has to leave you ready to make a specific decision, with the information you need and without us having to be in the room to explain it.
That's why each stage of the work ends with a different deliverable, designed around the question that needs answering at that moment. Here's what each one includes.
1. The audit presentation
This wraps up the diagnosis. It answers one question: where you're losing time, money or customers, and what to tackle first.
- A one-page summary that makes sense even if you weren't in the meetings.
- A map of the process as it actually works today, not as the manual says it does.
- The findings, each backed by evidence: data, interview quotes, screenshots of your systems.
- A ranking by impact and effort, separating what can be fixed in days from what needs deeper change.
- What we don't recommend doing, and why. Sometimes that's the most valuable part.
2. Proposed solutions and decisions
Once the problems are clear, we propose how to solve them. There's rarely a single answer, so we lay out options compared against the same criteria. The decision is yours, and it's an informed one.
- Two or three possible paths, including the simplest one, even if it involves no new technology.
- For each: what it solves, what it doesn't, the rough time and effort involved, and the risks.
- A prototype when you need to see the solution to have an opinion on it.
- A record of what was decided and why, so nobody has to guess six months from now.
3. The product or solution
This is what gets built: an automation, an internal tool, a website, an app or a change to a process. The rule is simple: it has to work in your real environment, not just in a demo.
- The working solution, deployed to production and tested with the people who will use it.
- The code, accounts and access, all in your name.
- The design files, so any team can pick up the work.
- A design system when the product is going to grow: documented components, styles and rules.
- User documentation for your team and technical documentation for whoever maintains the solution.
4. Measurement, metrics and maintenance
A project isn't finished when it's delivered. It's finished when we've confirmed it solved the original problem. That's why the last deliverable is measurement.
- The metric we agreed on in the first step, with its before and after values.
- A simple dashboard to track it without having to ask us for a report.
- Periodic reviews to catch drift early.
- A maintenance and improvement plan: what's worth doing next and what can wait.

