What I'm building.

The center of everything. A personal CRM that sits in front of the company system as a filter — every business card pulled is a card collected (rolodex meets Pokédex). Territory data on ~29,000 businesses, a six-stage pipeline (Untouched → Visited → Call List → Booked → Trial → Customer), a call cockpit, voice capture between stops, and a daily CADS scoreboard. By design it never writes to the company CRM directly: it reads, deep-links, and reconciles. A pipeline-only WaterDex 2.0 is in discovery — seven screens instead of 124, built for other reps too.

An AI assistant powered by Claude that lives in Telegram. Reads WaterDex through a read-only API, sends a weekday morning briefing and an evening outcome check-in, drafts follow-up emails, and reconciles the calendar. Sebastian can propose changes; a human tap confirms every one. The AI is structurally unable to write to company systems on its own.

"Our water is fine" deserves a factual answer. Nearly 1,000 Wisconsin water system reports built from EPA and Wisconsin DNR data — 700K+ compliance monitoring records — plus guides on microplastics, PFAS, and treatment, an interactive recommendation tool, and gated company pages with magic-link login.

A 3D open-world driving game about the actual job: a five-day week on Wisconsin streets, running the CADS funnel one office at a time. Chase camera, a sun that moves through the day into a lit-up dusk, rain, drifting, lane-following traffic with real signals, and AquaJug trucks racing you to the door. Every office is a wild encounter in a Game Boy-styled battle: the jug stack, the delivery driver, the monthly invoice. Answer objections with your party of Hydromon, throw the business card, fill the HydroDex. Then keep the appointment, dial in the demo, pick a contract term, and upgrade the truck at HQ. Gamepad and touch supported, with a booking link at the end because it doubles as a lead magnet. Built on Three.js in a single HTML file, with a 2D fallback for devices without WebGL.

Enter a meeting once — in Outlook, WaterDex, or chat — and the bridge reconciles the rest. Calendar mismatches surface on the front page. Writes to the company CRM go through a single, tightly gated outbox: one record at a time, the full payload shown before a confirm tap, per-day ceilings, every attempt logged and re-read back for verification. The strongest safety control is the one that structurally cannot be bypassed.

A public booking system for Bottleless Nation prospects. Availability accounts for drive time between stops, invitations and RSVPs go out automatically, reschedules need approval, customer data is encrypted, and every change lands in an immutable audit log. Bookings flow into Outlook and from there into WaterDex.

One front door for all of it, opening on a daily "edition" of what changed overnight. Inside: Groundwork (a long-form planning conversation for personal life, told to say "this doesn't need software" when that's true), Money Mode (a daily-number finance scoreboard), a Body room for health data, and an admin desk for this website. Sebastian sits in the corner.

The system that keeps the other systems honest, built on the PAUL framework — Plan, Automate, Unify, Learn. Service health monitoring, workflow automation, data quality, routing on a self-hosted OSRM engine, and self-healing. Phase 2, "The Watchdog," is deployed and sends a morning report. THE WHY Engine, an accountability workflow, runs inside it.

Where WaterDex's territory data came from. A FastAPI backend with TRS scoring (16 factors, seasonal multipliers, trigger events), company group aggregation, geocoding, deduplication, and nightly enrichment that fills judgement factors but never the ones only a field visit can answer. Now consolidated into WaterDex.