Public product work

DropHaul: product work grounded in a real operational problem.

DropHaul is dispatch and operations software for portable sanitation operations. Matt Campbell designed, architected, and built the product, from product direction through the technical foundation. The public work shows the kind of product and architecture responsibility that informs his advisory guidance.

Start a conversationCompare advisory plans

What this work shows

DropHaul is a public example of carrying a product from an operational need into software people can use. It shows product direction, technical architecture, and connected workflows without relying on invented performance claims or unverified endorsements.

Product decisions begin with the business operation the software must support.
Technical foundations matter alongside the screens and happy path.
Operational context helps make architecture and trade-offs concrete.
Public screenshots show route planning, a mobile dashboard, and invoice workflow surfaces.

The work in context.

A product for a real operational workflow

DropHaul connects the moving parts of portable sanitation operations and dispatch teams. Its public product material presents route planning, business dashboard, receivables, invoice activity, and invoice status as connected parts of the work.

The point of the product is not a collection of isolated screens. It is a clearer way for an operational team to see and move work through the business.

That context matters when making technical decisions: the architecture must support the workflow people actually need to carry, not only the interface shown in a first demonstration.

Product direction and technical foundation together

Matt’s public role on DropHaul spans product direction, technical architecture, and building the product. Owning those decisions keeps the advisory perspective close to the responsibility of shipping software people rely on.

The work includes making trade-offs visible, choosing a foundation that can support the operation, and keeping the product understandable enough to improve over time.

Those are the same questions he brings to client work: understand the business first, decide what matters now, and build the capability to keep going.

Why this informs advisory work

Advice is sharper when it comes from someone who has carried the product and architecture decisions. DropHaul gives Matt a direct reference point for discussing the gap between a convincing prototype and software a team can operate.

The public example is intentionally specific about role and product context while avoiding claims about metrics, customer outcomes, integrations, dates, or third-party endorsement that are not published here.

For a business weighing technology or AI decisions, that perspective supports a conversation about constraints, ownership, review, and the next useful step.

Public product evidence.

These screenshots are existing public assets that show the product surfaces described on this page.

DropHaul business dashboard on an iPhone

The working principles visible in the product

The public DropHaul work reflects a product process that starts with the operation, makes trade-offs visible, and treats the technical foundation as part of the product rather than an afterthought.

Understand the operation
Start with the people, handoffs, and business work the product needs to support.
Make the product direction clear
Choose the workflows and product decisions that make the next useful result visible.
Carry the technical foundation
Treat architecture and connected systems as part of the responsibility of shipping the product.
Keep the next improvement possible
Leave a foundation the team can understand, operate, and improve as the business changes.

Publicly visible product work

This page documents the public product context and role, not a private client engagement report. The visible work includes product direction, technical architecture, and software surfaces for portable sanitation operations.

Operational product direction

A product shaped around dispatch and portable sanitation operations rather than an abstract demonstration.

Technical architecture

The technical foundation required to connect the moving parts of the product and its workflows.

Route and dashboard views

Public screenshots showing route planning and operational dashboard surfaces across iPad and iPhone.

Invoice workflow views

Public screenshots showing invoice status, receivables, and collection progress in a focused workflow.

What this case study does and does not claim

This case study is limited to facts already published on Promotion Devotion’s public site and assets. It describes Matt’s role and the product context without presenting unverified business results.

No performance metrics, customer testimonials, or independent endorsements are claimed here.
No dates, integrations, or implementation details are added beyond the existing public material.
The product itself is available at drophaul.app for visitors who want to see the public product site.

Explore the surrounding work, read the background, or start a conversation about the decision in front of you.

Visit the public DropHaul product site

Read Matt’s background and experience

Read the prototype readiness guide

Discuss your own product or system