Skip to content
Back to work

LawRF — Statutory Audit Platform

A vertical tool for statutory audit under Italian ISA standards, taken from concept to a working prototype the client could use before development was commissioned.

Client work — source not public

Type
Product
Period
2026
Status
In design
Role
Architect & Product Designer

The problem

Statutory audit in Italy follows the ISA standards, and in most small and mid-size firms it is carried out in Word and Excel. Not for lack of software, but because the general-purpose tools do not follow the standard’s actual sequence: accept the engagement, assess risk, set materiality, work the checklists, document the evidence, sign the report — each decision traceable to the one before it.

The compliance burden lands on the auditor’s own discipline, and “show me why you concluded that” means reconstructing a chain of reasoning out of files.

What I built

The concept, delivered as something the firm could use rather than a document they had to imagine. A browser app with demo data and nothing to install: the auditor opens a link and walks their own process — engagements, the risk matrix, materiality, ISA checklists — and finds out inside ten minutes whether it understands their job.

Underneath, the domain is modelled properly, with the throwaway part confined to storage. The prototype is disposable at the infrastructure layer and permanent at the domain layer, which is what makes building one worth the time.

Where it stands

Designed and prototyped. The firm evaluated it against their own practice before committing budget, and the scope conversation happened against something they could click rather than a specification they had to trust.

What I did

  • Ran the functional analysis and wrote the project plan with the client
  • Modelled the audit domain: engagements, risk assessment, materiality, ISA checklists, working papers
  • Built a browser-only prototype with in-memory demo data — no backend, no database, no install
  • Defined the delivery plan in phases so the build could be commissioned incrementally

Impact

  • The client evaluated the real workflow before committing to development
  • Scope decisions were made against something they could click, not a document

Stack

  • Blazor WASM
  • .NET 10
  • PWA
  • DDD
  • Prototype

Recognise one of these problems?

If any of this looks like the system you are living with, that is usually a good place to start a conversation.