AI Performance · Founder & Product Architect
Hocus Pocus Focus
An AI Chief of Staff for the work that matters.
4
Leaks addressed
One
Execution inbox
Human
Approval stays
The Problem
Ambitious people rarely lack vision; they lose time, money, energy, and attention inside fragmented inboxes, calendars, follow-ups, and task lists.
The AI Architecture
Hocus Pocus Focus centers execution around Magick, an AI Chief of Staff that prioritizes critical work, drafts replies for approval, plans tasks around energy, and scores daily progress.
What Aaron Shipped
- A unified execution inbox for email, messages, and critical work
- Approval-first AI reply drafting and follow-up automation
- A Now card that selects the next task from goals, energy, and calendar
- Daily productivity and energy scoring with a six-week planning view
The Outcome
A single execution layer designed to protect attention and put the right work into a founder's best hours without surrendering final control.
Under the hood
How it was built.
Tech Stack
Implementation Notes
The product unifies the decision surface rather than adding another task list, with AI preparing actions while the user retains approval.
Funnel Strategy
Problem-led story → waitlist → connected inbox and calendar → daily Now card → repeated execution and progress review.
The growth-engine model
One connected system, not six disconnected vendors.
Extraordinary connects brand, software, content, search, automation, and measurement—then stays close as a growth partner where the fit is strongest.
Browser layer
React 18 · TypeScript 5 · Tailwind
Declarative UI, compile-time type safety, design-token CSS that flips themes from one variable.
Build layer
Vite · esbuild · SWC · imagetools
Native ES modules in dev (instant reloads) and tree-shaken, code-split, hash-versioned bundles in prod.
Edge & delivery
Global CDN · HTTP/3 · TLS 1.3 · immutable caching
Every byte served from the user's nearest PoP. Long-lived caches because filenames are content-hashed.
Backend layer
PostgreSQL · PostgREST · RLS · JWT auth · Deno edge functions
Your schema is your API. Authorization enforced inside the database. Server code without server ops.
The tools are not the advantage. The advantage is seeing the whole engine, choosing what matters, and making every part compound the others.