Workhorse was an early-stage mobile app concept aimed at solving a common but persistent problem for contractors: running an entire business from the field without juggling disconnected tools. Estimates, jobs, invoices, expenses, scheduling, and client communication were all technically solvable problems, but rarely treated as parts of the same system.
My role was to help define what an all-in-one experience should actually mean in practice, and to ensure the product vision stayed grounded in what could realistically be built, adopted, and used day to day by contractors working under real-world constraints.
The problem
Most contractors were already using software, but each tool only addressed a narrow slice of the workflow. Job details lived in one app, invoicing in another, expenses somewhere else, and communication outside the system entirely. The constant switching introduced friction, slowed work in the field, and increased the likelihood of missed steps or delayed payments.
The challenge was not adding more features, but deciding which workflows truly mattered and how to connect them without overwhelming the user. Contractors needed speed and clarity, not another complex system that required training or configuration before it became useful.
The approach
Workhorse was framed around the idea that jobs, clients, and money are inseparable in a contractor’s business. Rather than treating estimating, scheduling, invoicing, and communication as separate modules, the product was structured so these actions naturally flowed from one another.
From a product standpoint, this meant prioritizing the core lifecycle of a job—from initial estimate to completion and payment—and designing supporting features around that flow. The mobile experience needed to work in short bursts, often on a job site, with minimal friction and clear next steps.
My focus was on helping the team make disciplined decisions about scope and sequencing. We evaluated features not by how impressive they sounded, but by how directly they supported the contractor’s primary workflows and reduced context switching in the field.
Role and execution
I worked closely with design and engineering to shape the product direction, clarify system boundaries, and ensure the experience remained cohesive as ideas evolved. Rather than acting as a sole decision-maker, I helped translate user needs and business goals into practical constraints the team could build against.
This included defining what belonged in the initial product versus what should be deferred, aligning expectations around technical complexity, and keeping the experience grounded in the realities of mobile-first use for non-technical users.
Outcome
Workhorse resulted in a clear, unified product concept that treated a contractor’s business as a single system rather than a collection of disconnected tools. The project reinforced the importance of restraint in early-stage products and the value of designing around real workflows instead of feature checklists.
It also reflected a recurring theme in my work: effective platforms are not defined by how much they can do, but by how well they reduce friction across the work that matters most.