← Complex requirements to product direction
Compliance-to-product case study

From spreadsheet-heavy compliance to a demo-ready product direction

An anonymised account of Daisy's work inside a climate SaaS team: turning dense UK energy compliance material, partner expertise and live consultancy spreadsheets into something the team could explain, demonstrate and build from.

At a glance

A credible product direction in six weeks

The work created a testable product model and the documentation needed to carry it into implementation.

Timeline

Six weeks from consultancy spreadsheets to demo-ready.

Validation

The product direction supported more than 20 client and partner demos.

Output

Clear documentation, a working prototype and implementation scope.

Delivery

The specification pack became the basis for engineering work.

The starting point

The opportunity existed before the product did

Clients and partners had a real compliance need, but the service still depended on specialist spreadsheets, repeated explanation and a prototype that did not yet carry the underlying logic.

Source material

Dense and distributed

Regulatory material, consultancy practice, partner feedback and product assumptions did not yet form one shared model.

Product shape

Important decisions were still implicit

The team needed to separate fixed compliance requirements from UX choices, commercial priorities and open questions.

Demonstration

The idea needed to become credible

Commercial conversations needed something concrete enough to explain the workflow without presenting illustrative screens as finished product behaviour.

Delivery

Engineering needed a reliable handover

The product direction had to preserve rules, exceptions, evidence and acceptance conditions beyond the prototype.

Daisy's contribution

Build the product model, not only the presentation

The work sat across compliance interpretation, product management, prototype review, specification, QA and handover.

  • Brought source requirements, partner knowledge and the working consultancy process into one traceable product model.
  • Separated compliance obligations from product choices, assumptions and presentational guidance.
  • Mapped the user journey, decision logic, evidence, exceptions and outputs across the end-to-end workflow.
  • Wrote the specifications, reviewed the working prototype and defined implementation and quality criteria.
How the work moved

Establish what was true before deciding what to build

The first task was not writing tickets or redrawing the prototype. It was reconciling regulation, specialist practice, customer expectations and commercial constraints so the team could see which decisions were fixed, which were product choices and which still needed evidence.

1. Reconstruct the current workflow

The consultancy spreadsheets showed how the service worked in practice, including information requests, calculations, professional judgement and outputs. That working process was compared with the source requirements rather than treated as the specification by default.

2. Separate compliance logic from experience design

Each important rule was traced to its source or interpretation. Product choices—such as sequence, language, progressive disclosure and where to ask for evidence—could then be challenged without losing the underlying obligation.

3. Shape and review a demonstrable journey

The product model became a working prototype that specialists, commercial stakeholders and delivery teams could review. The prototype made the sequence concrete; the specification carried the rules and exceptions a visual could not reliably hold.

4. Leave a buildable source of truth

The handover connected product flows, source decisions, expected behaviour, open questions, QA criteria and implementation scope. Engineering could work from the documentation without reconstructing the domain logic from meetings and spreadsheets.

What changed

In six weeks, the team moved from a spreadsheet-heavy consultancy process to a demo-ready product direction with clear documentation, a working prototype and implementation scope. It supported more than 20 client and partner demonstrations, while the specifications became the basis for engineering work.

Why this example matters

The difficult part was not turning a spreadsheet into screens. It was making the domain decisions visible enough for specialists to verify, commercial teams to explain and engineering teams to build. The same pattern applies wherever product work crosses regulation, data, professional judgement or complicated operational reality.

The reusable method

The companion guide explains how to turn specialist knowledge into a product workflow. The build-ready requirements test shows what the handover needs before development starts.

Next step

Bring the source material that has not become a product yet

A spreadsheet, regulation, specialist workflow or unresolved prototype is enough to start.