I grew a plumbing company to $2.4M. Then I lost it. Now I build the software it needed.

A unified operating system for field service: one job cockpit, live dispatch, and communications that stay with the work.

• Job cockpitFocus
• Next.js 16Stack
• Active buildStatus

Happy customers go to public reviews and unhappy ones land in a private inbox first, so the reputation gets protected before it breaks.

• LiveStatus
• ReviewsFocus
• Mobile-firstSurface

AI-operated telephony that answers, routes, transfers, and summarizes, with a visual call-flow editor and a developer API.

• AI-operatedMode
• Visual flowsEditor
• Dev + opsAudience

One design language across products: Morph Panels, semantic tokens, and accessible primitives reused everywhere I build.

• Morph PanelSignature
• SemanticTokens
• This siteUsed on

A fast, neighborly site that ranks in two markets and makes calling feel obvious under stress.

• $2.4M yr-2Peak revenue
• CA + GAMarkets
• Speed + trustPriority

After ten years in plumbing, two master licenses, owning a company, and working inside three shops, I believe the industry’s obsession with average ticket is trading lifetime trust for a one-day sales number.

• Plumbing
• Customer experience
• Sales

Contractors do not need a larger feature checklist. They need software that protects the chain from first call to collected payment, keeps context attached to the job, and makes operational failure visible early.

• Field service
• Product
• Operations

Tokens, components, accessibility rules, and motion principles only become a system when products inherit them automatically. AI-generated interfaces make that enforcement more important, not less.

• Design systems
• UI
• Product engineering

Thorbis did not start as a feature list. It started with the operational failures I lived through in plumbing: lost context, weak job costing, missed calls, expensive seats, and software that never sees the whole company.

• Thorbis
• Field service
• Product