A calm, keyboard-first way for founders to spend time the way they intend — and the full-stack platform behind it.
A production SaaS built as a single Turborepo monorepo — web app, native desktop client, browser extension and admin console, all from one shared core. Behind a security-hardened Postgres backend (~100 tables, ~213 stored procedures, row-level security on every one) runs a fault-tolerant, offline-capable timer engine, a multi-provider planning layer that drafts each operator's day, and an MCP server that lets outside agents act on their work. Built on Next.js 16, React 19 and Supabase.
Operator Cadence isn't a task list — it's a loop. Each day is drafted, run as a timed sequence, tracked against goals, and picked back up exactly where it was left. That cycle is the spine the whole platform is built around.
Domain › Loop › Category › Next Action — the data model that recursively cycles, so an operator always resumes rather than restarts.
The signature subsystem: a ~2,400-line reducer state machine tracking time against goals across sequences of work. Optimistic updates roll back from the server; actions that happen offline queue to IndexedDB and drain via a Service-Worker background sync; a single global tick and Realtime + BroadcastChannel keep every tab and device in step.
A deliberate "fat-database": ~213 Postgres functions and ~111 triggers hold the transactional business rules, with route handlers as thin authenticated wrappers. Row-level security on ~100 tables, append-only audit logs, and a documented hardening campaign — every function flipped to INVOKER, every search-path pinned, EXECUTE revoked from anon.
The Daily Guide assembles real context — loops behind their goals, overdue actions, live calendar, and energy patterns learned from the operator's own history — then casts the model as a chief of staff and returns a validated, machine-parseable plan. One router spans three providers with bring-your-own-key, streaming, quotas and cost tracking.
An MCP server and a token-scoped agent API let outside AI agents read and act on an operator's loops and actions — gated by granular per-agent read/write permissions and HMAC-hashed keys. Agent dispatch is bounded by concurrency and pending-invocation limits, with a watchdog that sweeps stale work.
The highest-volume tables — time entries and activity logs — are partitioned, RLS enforced on the children. A performance-audit series dropped dead indexes and added materialized rollup caches so dashboards read pre-aggregated data. Two schedulers, async email & agent queues, rate limits and circuit breakers keep load in hand.
A Turborepo monorepo ships web, desktop, extension and admin from a shared @opcadence/core — the typed queries, Zod schemas and timer math that keep every surface behaving identically. The frontend is server-components-first with prefetch-and-hydrate, so pages arrive without client fetch waterfalls.
~30 feature areas and ~180 route handlers — dashboard, loops, sequences, calendar, inbox, reports and a deep settings tree. Keyboard-first: a ⌘K command palette, global search and multi-key chords.
A thin Tauri v2 (Rust) frame that loads the web app — no fork — adding a frameless always-on-top timer, system tray and a global show/hide shortcut. Pre-release build.
A WXT + React 19 extension that drops any page straight into the Inbox with its source, so a stray idea never breaks the operator's focus.
A separate console with its own auth — argon2 hashing, TOTP 2-factor, append-only audit logs and support impersonation with cascade cleanup.
Recharts dashboards — goal-vs-actual, allocation and trends — plus a dnd-kit calendar timeline with ghost blocks and a kanban board for triage.
A separate static Next.js site on a bespoke design system — a "stateless-first" build where only six files ship client JS, with generated OG images, full JSON-LD and end-to-end UTM attribution.
Built on Next.js, TypeScript, and Supabase — server components by default, a typed data layer, and AI tooling (Claude Code, Cursor) woven through the dev workflow to move fast without giving up rigor.
Pre-launch. Shaping the core product loop and validating it against how high-agency people actually plan and switch contexts before opening the doors.
The plan every time: once it ships, run it hands-on — product, growth, and operations — the same way I've operated software businesses for two decades.
Figures verified against the codebase. The desktop client is a pre-release build; a React Native mobile app referenced in internal docs is not yet built. Deployed single-region on Vercel + Supabase — "scale" here means partitioning, rollup caches and rate limiting, not a bespoke cluster.
I take on a small number of collaborations each year — usually where I can go deep on product and engineering. If that sounds like a fit, let's talk.