Workproof
WorkProof is a lightweight job-tracking and proof-of-work system designed for small trade teams. It focuses on clarity, accountability, and ease of use across desktop and mobile without over-engineering the workflow.
PROJECT OVERVIEW
Designing a focused job-tracking system for operational accountability
WorkProof was designed as a response to the fragmented and manual systems commonly used by small trade businesses.
Many teams rely on text messages, photos, and memory to track job progress which leads to missed tasks, disputes, and lack of accountability.
The goal of this MVP was to design a single source of truth for job status, task completion, and activity without adding unnecessary complexity.
PROJECT
Workproof
ROLE
Founding Designer
TIMELINE
On-going
THE PROBLEM
Small trade teams lack a single source of truth for job execution
This fragmented workflow makes it difficult to track task completion, verify work, and understand job status in real time, leading to missed tasks, disputes, and a lack of accountability across the team.
01
Progress is unclear
Job progress is spread across messages, photos, and verbal updates, making it difficult for teams to understand what’s been done, what’s pending, and what requires attention.
02
Accountability breaks down
Without a clear record of task completion or evidence of work, teams rely on trust and memory, increasing the risk of missed steps, rework, and disputes with clients.
03
Teams operate reactively
Because job updates aren’t captured in real time, issues are often discovered after they’ve already impacted timelines, quality, or customer satisfaction.
CORE INSIGHT
Teams want tools that work immediately, not systems they need to set up.
UNDERSTANDING THE ENVIORNMENT
Manual teams don’t work in software, they work in motion.
Small trade teams operate across job sites, vehicles, and phone calls. Work happens in fragments between locations, tools, and people, not inside a single application.
Most existing tools assume consistent usage, attention, and process maturity. In reality, teams need systems that capture proof, progress, and accountability with minimal interaction.
MANUAL WORKFLOW
Fragmented job execution
Work is tracked across messages, photos, and memory.
Updates are inconsistent, progress is unclear, and accountability is only discovered when something goes wrong.
SYSTEMISED WORKFLOW
A single source of truth
WorkProof captures progress, proof, and ownership as work happens, creating a shared, reliable record that teams can trust without extra effort.
CORE INSIGHT
Clarity came from observing real workflows, not imagined ones.
OPERATIONAL DESIGN PRINCIPLES
A system built around clarity, speed, and trust
WorkProof was designed around the realities of small trade teams with time pressure, low tolerance for friction, and the need for clear accountability. These principles guided every structural and interaction decision across desktop and mobile.
01
Remove ambiguity
Every job needs a clear state, owner, and next action. WorkProof reduces guesswork by making job status, tasks, and updates explicit so teams don’t rely on memory, messages, or assumptions.
02
Make progress visible
Work in progress should be obvious at a glance. Photos, task completion, and activity updates surface proof of work as it happens, reducing disputes and increasing trust across the team.
03
Design for repeatability
Trade work is repetitive by nature. WorkProof uses consistent layouts, actions, and patterns so teams can move quickly between jobs without relearning the system each time.
CORE INSIGHT
When work is physical, clarity matters more than flexibility.
SOURCE OF TRUTH
A single, authoritative job record
Each job acts as the system’s source of truth, combining status, tasks, photos, and notes into one persistent record. This removes ambiguity, reduces disputes, and makes progress visible to everyone involved.
CORE INSIGHT
Disputes don’t come from bad work, they come from missing proof.
OPERATIONAL VISIBILITY
Operational clarity at a glance
Job status is visible across the system at all times.
Teams can see what’s in progress, what’s blocked, and what’s complete without messages, calls, or follow-ups.
CORE INSIGHT
Status should answer questions before messages do.
TEAM STRUCTURE
Built for teams, not just individuals
WorkProof is designed for multi-person teams from day one.
Roles, access, and ownership are clearly defined so work can scale without relying on constant supervision, messages, or manual coordination.
CORE INSIGHT
Systems scale teams. Messages don’t.
NEXT STEPS
A measurable lift in clarity, speed, and completion
WorkProof is currently at MVP stage, designed to validate core assumptions around accountability, visibility, and proof of work for small trade teams.
The product is now moving into backend integration and real-world usage, with the next phase focused on validating workflows, gathering feedback, and refining the data model before expanding functionality or monetisation.
01
Validate with real teams
Onboard a small group of local trade teams to observe real usage patterns, identify friction points, and validate whether the core workflows replace existing manual processes.
02
Refine workflows and UI
Use qualitative feedback and behavioral data to refine job flows, activity tracking, and mobile interactions with prioritising speed, clarity, and reduced admin overhead.
03
Simple, sustainable subscriptions
Explore a lightweight subscription model based on team size or active jobs, ensuring pricing aligns with the value delivered and remains accessible for small operators.
Other projects
Exploring new opportunities. I’m at my best in design-led teams that move fast and care deeply about interaction quality.
v0.05
UPDATED NOV 2025
SYSTEM CRAFT UI
GOLD COAST, AUSTRALIA
BUILD STABLE
DESIGNED & BUILT BY HARRY MAHER