Safety & compliance SaaS·Sydney, Australia·2023–2026

Vouchd

Safety & compliance checklists teams actually finish on site

Live product at vouchdforms.com — field UX, hosting, and release support

Vouchd — case study

Client

Product-led team shipping Vouchd for construction, facilities, and operations-heavy businesses that need consistent checklists across sites and subcontractors.

Engagement

Websi as ongoing product partner: UX, engineering, hosting, email delivery, and release support alongside the Vouchd founders — not a one-off marketing site.

Duration

Multi-year product partnership

Vouchd (vouchdforms.com) is a field-first checklist platform for safety and compliance workflows — structured inspections, evidence capture, and audit-ready history without rebuilding the same forms in spreadsheets every quarter.

  • SaaS
  • Compliance
  • Field ops
  • Product

Starting point

Safety and compliance work was scattered across PDFs, one-off form builders, and photo rolls on phones. Supervisors couldn't see completion rates by site; auditors asked for history that took hours to reconstruct. The team wanted one product that field staff would actually open on a phone between jobs.

Challenge

Checklists had to work offline-tolerant in poor connectivity, stay simple for non-technical users, and still produce defensible records for compliance reviews. Marketing and product needed a credible public face at vouchdforms.com while engineering kept shipping workflow improvements.

Approach

We treated Vouchd as a product, not a brochure: tight loops with founders on field UX, progressive checklist templates, and clear states for draft → submitted → reviewed. Infrastructure went through Cloudflare for reliable delivery; transactional email via Resend so invites and alerts didn't land in spam. Each release balanced new checklist types with stability — because a failed submission on site is worse than a missing feature.

Supervisor reviewing completed site checklists on a tablet at a worksite desk

How it ran

Discovery through launch — emphasis changes by client; this is how this one actually went.

  1. 1

    Foundation · Product & brand

    Core checklist model, roles, public marketing site, and hosting on a stack the team can operate without a separate agency for every change.

  2. 2

    Field rollout · Templates & evidence

    Site-ready templates, photo and note attachments, supervisor views, and fixes from real crews using the app on active projects.

  3. 3

    Scale · Ops & reliability

    Cloudflare hardening, email deliverability, performance passes, and release discipline as customer sites and checklist volume grew.

  4. 4

    Ongoing · Vertical workflows

    New checklist packs, reporting hooks, and integrations scoped per industry — same team, incremental ships.

What we shipped

  • Public product site and signup path at vouchdforms.com
  • Field checklist UI with draft → submitted → reviewed states
  • Photo and note evidence attached to inspections
  • Supervisor views plus export-friendly audit history

Outcomes

  • →Single product surface at vouchdforms.com for positioning and signup
  • →Structured checklists replace ad-hoc PDF and spreadsheet variants
  • →Supervisors get completion visibility without chasing individuals by text
  • →Audit-friendly history — who completed what, when, with supporting evidence
  • →Ongoing platform for new vertical templates and workflow rules

Stack

  • Modern web app (responsive field UI)
  • Cloudflare (DNS, edge, performance)
  • Resend (transactional email)
  • Role-based access and checklist versioning
  • Export-friendly audit history for reviewers

Constraints

  • Field UX must stay fast on mid-tier phones — feature depth can't crowd the primary tap path
  • Compliance wording varies by industry; templates need guardrails, not infinite free-form
  • Email and domain reputation tied to verified sending — DNS and Resend setup kept explicit

What actually worked

Staying embedded with the product team and shipping thin vertical slices — one checklist type end-to-end before adding ten more. Separating 'get the job done on site' from 'admin configuration' kept adoption from stalling.

In their words

“Websi has worked like an extension of our team — shipping real product, not slideware. They sweat the field UX and the unglamorous reliability work that actually keeps customers on the platform.”

— Vouchd founding team

Planning something comparable?

Share the bottleneck, the tools you already have, and the timeline. We'll say whether we can help and what we'd tackle first.