B2B field service SaaS

Field Complete was a complex B2B SaaS platform for service companies and contractor teams. It connected estimating, scheduling, dispatching, job execution, invoicing, payment collection, reporting and communication in one operational environment.

As the sole Product Designer, I owned work across web and mobile: turning complex business processes into clearer workflows, more consistent interfaces and reusable UI patterns across modules.

Field Complete served service businesses coordinating technicians, contractors, customers, jobs, approvals and payments. The architecture covered CRM and opportunities, workflow modules for jobs and work orders, financial modules, reporting, settings and business rules.

The product needed to connect office operations — planning, dispatching, estimates, approvals and invoicing — with field execution: jobs, updates, technician workflows, communication and payment-related actions.

The challenge was not simply to improve the UI. The product had connected workflows and data-heavy screens with operational and financial dependencies, so design had to make the system easier to understand across roles and modules.

Customer conversations, feature requests and recurring friction points informed refinement for business owners, dispatchers, workers, accountants and administrators.

I worked as the sole Product Designer across a broad product surface, combining day-to-day delivery with broader UX structuring and UI foundations.

Dashboards, schedules, jobs, estimates, work orders, project views, files, activity history and status tracking formed the daily operational core. The work focused on making dense, interconnected business logic easier to scan and act on.

Estimates, approvals, scope, line items, invoices, payment requests and billing states were not isolated finance screens. They depended on job status, project scope, taxes, customer communication and the preparation of customer-facing delivery.

My work focused on making these dependent flows coherent and usable where several business rules came together in one screen or modal.

Beyond core operations and billing, Field Complete also included reporting, analytics, messenger, notifications, attachments, external-facing widgets and mobile touchpoints. These surfaces served different tasks but needed to feel connected.

I worked toward a unified experience through recurring UI logic, clearer patterns and shared interaction foundations rather than treating every module as a separate mini-product.

Although the outputs were interface screens, the work was product-oriented: reconciling user roles and responsibilities, dependencies between modules, operational and business logic, internal workflow and external communication, and immediate delivery with long-term consistency.

This was the period where the role moved beyond screen design toward product structure, workflow architecture and system-level UX thinking.

This is an older, overview-level case, so the outcome is presented as product-structure and workflow design rather than a metrics-heavy optimization story.

Field Complete was one of the most formative projects in my career. It demonstrates operating as a single product designer in a complex B2B SaaS environment: not only delivering interfaces, but helping structure the product itself.