WorkCase 01Status: Beta

AI + Field Service Operations

PortaScout

0 → 1 AI operations application for portable sanitation businesses — an industry running on texts, phone calls, and spreadsheets.

OutcomeIn beta with real operators before pilot
PortaScout — cover
AI + Field Service Operations2026
PortaScout — cover
§ 01

At a glance

0 → beta
PRODUCT BUILT INSIDE ROCK & CALIBER, NOW PILOTING WITH REAL BUSINESSES
1 wedge
POSITIONED AS TRUSTWORTHY BUSINESS ASSISTANT THAT KNOWS THE INDUSTRY — NOT A BASIC REPLATFORM
3 personas
FOCUS WAS ON SCHEDULERS, TECHNICIANS, CUSTOMERS DESIGNED END-TO-END
Branding
A BRAND BUILT TO STAND THE TEST OF TIME, NOT A ONE-OFF AI-GENERATED LOOK-ALIKE
§ 02

Context

Portable sanitation is an industry with real revenue that most product designers have never touched. Operators run on spreadsheets, radios, and calls -- often, because they like it and "if it ain't broke don't fix it." On the other end of hte spectrum are legacy vendors sell heavyweight replatforms these teams can't absorb.

My partner and I built PortaScout first for our own field operations business contacts — before pitching it to anyone else. That framing forced honesty: the product had to work for the teams we already had, not the team we wished we had. Reality hit hard and fast, but what came out of it was something spectacular.

§ 03

Constraints

  1. 01

    The buyer is a small operator with no time for a rollout — the product had to plug into their existing workflows and dispatch process, not replace them.

  2. 02

    Technicians work with gloves on, in trucks, in bad weather. Every screen had to survive that environment, every click had to be well worth it.

  3. 03

    Oversight had to be intentional, not absolute — operators spook easily and need to trust the system before they'll let it schedule a route unattended.

  4. 04

    Zero-budget brand and product moment — the launch had to punch above its weight against much larger vendors. How did we do it? We spoke directly to the people, not above them.

§ 04

Approach

01

Defined the product wedge before designing a screen

Positioned PortaScout as a specialized tool for scheduling, routing, and coordination — built first for field ops. Considering what other competitor tools existed, the consumer sentiment around those tool, plus pricing and features -- with that framing clear, we could define and optimal MVP scope, mitigated adoption risk, and had a successful pilot structured.

02

Mapped the end-to-end operation, not just the app

Built service blueprints and swimlanes across customers, schedulers, technicians, and system-owned steps. Working from real workflows exposed where delays, handoff failures, and swivel-chair work were actually happening — and where PortaScout could remove friction without breaking accountability or trust.

03

Designed AI as the carrot, not the stick

Our users are skeptical of AI. Period. PortaScout's job was to suggest appointment windows, optimize daily routes, and write only essential data back into the systems of record. Humans needed to stay in the decision seat; while the AI stayed "on deck" to tackle the work no one wanted to do anyway. We learned AI needed to be the "ah ha" moment for skeptics.

04

Built a brand designed to age

PortaScout's brand was its calling card - as it developed a voice, the visual system, and product identity had to feel current in 2026 and still credible five years out. It needed to be recognizable, witty, unapologetic, and unmistakably "not just another field service tool."

Easily and highly recommend her. Great attitude, great work ethic, great outcomes. She's a pleasure to work with — among the best I've had a chance to work with. She's rock solid.
Terry Moran — Software Engineering Manager, Google
§ 05

Artifacts

Identifying the market gap
Identifying the market gap
The solution — white-labeled CRM/FSM for sanitation
The solution — white-labeled CRM/FSM for sanitation
Solving for drivers & dispatch
Solving for drivers & dispatch
A web-based app that's stupid-simple
A web-based app that's stupid-simple
Customer portal, customized
Customer portal, customized
Branded portals for customers
Branded portals for customers
PortaScout Branding Book (PDF)
PDF
PortaScout Branding Book (PDF)
§ 06

Outcome

Established a clear 0 → 1 product built inside Rock & Caliber, now preparing to enter beta with real field operators.

Clarified PortaScout's position as a specialized, high-context routing and scheduling layer — not a heavyweight platform — making it a credible pilot candidate alongside larger vendors.

Produced the strategic artifacts (value props, competitor comparisons, workflow models, board-ready narrative) that support pilots, partner conversations, and the next phase of launch.

§ 07

What I'd do differently

I'd bring an operator into design reviews earlier — not to validate directions we'd already committed to, but to sit inside the ambiguity with us. The clarity we got from designing with our own team on speaker phone was worth more than any research readout.

§ End of case 01

Next case → 2025 · Enterprise Payments Platform

Payment Platform Transformation