Workhorse

Overview

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.

We needed to identify the workflows contractors relied on most and connect them in an experience that was quick to understand and use in the field.

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.

We prioritized the lifecycle of a job, from the initial estimate through completion and payment, and designed supporting features around that workflow. The mobile experience needed to work in short bursts on a job site, with clear next steps.

I helped the team decide scope and sequencing by evaluating how each feature supported the contractor's primary workflows and reduced switching between tools.

Role and execution

I worked with design and engineering to shape product direction, clarify system boundaries, and keep the workflows connected as ideas evolved. I helped translate user needs and business goals into practical requirements for the team.

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 product concept connecting the main parts of a contractor's business. The team had a shared workflow and a defined initial scope to guide further development.

The work reinforced the value of understanding the whole workflow before deciding how much to include in an initial product.