Work

Proven

Compliance-grade notice and acknowledgement software

ComplianceSaaSProduct DesignFull-stack MVP
Role

Product Lead & Designer

Year

2026

Impact

Compliance workflow design • Problem validation • MVP architecture

01 — Overview

Overview

Proven is compliance-grade notice and acknowledgement software designed for organisations with distributed or field-based teams.

It enables businesses to send critical operational, safety, and policy updates, capture verifiable acknowledgements, and maintain audit-ready records that prove delivery and awareness.

I identified the problem, validated demand, designed the core workflow, and built the MVP foundation.

02 — The Problem

The Problem

Delivery cannot be proven

Many SMB operators rely on WhatsApp, email, or paper sign-offs to distribute safety procedures and policy updates — none of which create a verifiable record of who received what.

Audit trails are fragmented

Records sit across paper sign-offs, email inboxes, and chat threads. Documentation gaps are exposed only when something goes wrong.

Compliance is not defensible

In compliance-sensitive environments, "we told them" is not enough. Disputes rely on unverifiable claims, leaving operational and legal risk on the business.

03 — Market Insight

Market Insight

Discovery with field-service operators surfaced a consistent pattern: informal communication, hard-to-produce delivery proof, and documentation gaps exposed only when something goes wrong.

Existing tools fail operational workflows in different ways.

HR systems

Complex and document-centric.

E-signature tools

Contract focussed and extremely expensive.

Messaging apps

No audit trail or defensible proof.

The Clear Gap: No lightweight compliance acknowledgement tool exists for frontline operations. HR systems, e-signature platforms, and messaging apps all fall short — none deliver defensible proof at the price and speed operators need. That's the space Proven was built to fill.

04 — Product Approach

The Solution

Build the workflow around acknowledgement, not delivery.

Rather than build a full communications platform, the product centres on a minimal workflow that delivers immediate compliance value. Admins create and distribute notices; recipients open and acknowledge with one tap on mobile. The act of acknowledgement — not the message itself — is the unit of value.

Delivered throughAdmin workflow (create, distribute, monitor)Recipient workflow (mobile-first)

Make every interaction provably logged.

Timestamp and IP capture, an immutable audit log, and an exportable proof record. Together these establish defensible proof of awareness — not just message delivery.

Delivered throughTimestamp & IP captureImmutable audit logExportable proof record

Strip the surface to compliance essentials.

Clarity over complexity. A linear workflow — notice → acknowledge → proof — with operational simplicity and risk visibility. Every unnecessary feature was deliberately left out.

Delivered throughLinear workflowClarity-first interface

05 — Positioning

Positioning

Proven isn't a communication tool. It's a compliance accountability layer that reduces operational and legal risk.

Go to proven
Proven landing page

06 — Decisions

Key Design Decisions

Focus on Proof

Avoided feature creep by centring the product on defensible acknowledgement, not messaging.

Mobile-first Acknowledgement

Frontline staff interact primarily on mobile under time pressure. The experience was optimised for this context.

Immutable Audit Trail

Trust depends on verifiable, tamper-resistant records. Every interaction is permanently logged.

Minimal Workflow Surface

Reduced friction increases compliance completion rates. Every unnecessary step was removed.

07 — Reflection

Reflection

Proven demonstrates a problem-led approach to product design — validating operational risk and compliance workflows before expanding functionality.

The project strengthened my ability to identify market gaps, design outcome-driven workflows, and position products around business risk rather than features. It reinforced the importance of clarity, reliability, and proof in systems used under real operational pressure.