Deployed Core
Customer-facing infrastructure
Voice and SMS infrastructure, GoHighLevel operations, website and funnel, server-side attribution, database, and production deployment.
Technical Product Case Study
What shipped, where it broke, and how the lessons changed my product judgment.
I built Office OS to test whether AI could do more than generate answers. Could it carry work through communications, CRM, calendars, attribution, approvals, and recovery? The core systems are deployed, and the architecture supports multiple tenant-scoped businesses and independent worker runtimes. It is built and ready to onboard customers without rebuilding the platform for each business.
Customer-Ready System
The system already supports tenant-scoped configuration, separate business knowledge, role-specific assignments, controlled tools, and independent worker runtimes. Each customer receives their own identity, knowledge, assignments, permissions, channels, and operating context while the same platform serves every business.
Deployed Core
Voice and SMS infrastructure, GoHighLevel operations, website and funnel, server-side attribution, database, and production deployment.
Operating in Production
A phone-accessible AI office manager, persistent operating context, CRM outreach synchronization, and selected research and production workflows.
Operating Library
A 45-skill operating library, 12 composed workflows, research tools, programmatic video, approval components, health checks, and agent evaluations.
Ready to Onboard
Add the customer's knowledge, assignments, tools, permissions, channels, and runtime through configuration. The platform itself does not need to be rebuilt.
My Role
I directed the product, architecture, decomposition, integration, deployment, and operating decisions. I used coding agents extensively because they let one builder test ideas at a pace that previously required a team. I did not treat generated code as delegated judgment. I decided what the system should do, where a person must stay in control, which failures mattered, and whether the result was safe enough to keep.
My operating instincts came from six years in underground mine dispatch. I monitored ventilation, gas-detection, compressed-air, crushing, conveying, and production systems while coordinating work across people, equipment, and departments. In that environment, a persuasive demonstration meant nothing if the system failed during an exception.
The Operating Problem
Small businesses already have phones, calendars, customer records, websites, advertising accounts, and payment tools. The owner still has to carry context between them, notice what was missed, approve risky decisions, and recover interrupted work. Office OS was my attempt to make the worker the product rather than adding another dashboard for the owner to operate.
01
Sets direction, approves consequential actions, and handles exceptions.
02
Receives instructions, prepares briefings, and delegates bounded work.
03
Apply procedures, tools, permissions, approval rules, and evidence requirements.
04
Carry work through CRM, phone, calendar, web, data, media, and advertising tools.
Proof 1 · Live
The communications system resolves the business from the number called, assembles the voice agent at call time from approved configuration, injects customer and business context, exposes real calendar and CRM tools, and creates a human handoff when the agent reaches its limit.
A knowledge-base lookup sat directly in the live-call path. When it slowed down, assistant creation stalled. Calls could end before the caller heard a response.
I added a four-second boundary, reduced context gracefully when retrieval was slow, and supplied a safe fallback assistant. A slow dependency now reduces answer quality instead of losing the call.
Customer-ready design: communication paths resolve tenant context from the request, then load that business's identity, knowledge, tools, calendar, and operating rules.
Proof 2 · Live
I treated attribution as a durable identity and event problem rather than a browser-pixel feature. The system captures campaign and visitor context, recovers it when a later CRM event arrives, and delivers the normalized event independently to Meta, GA4, Google Ads, TikTok, and LinkedIn.
1,766
Current system activity, including browser, engagement, and funnel events.
5
Each receives events independently so one failure cannot block the others.
140
Recorded platform attempts. They are not presented as 140 customer conversions.
1
Website and CRM sources use the same conversion logic and evidence trail.
Database uniqueness prevents retried webhooks from creating duplicate sends. Platform failures are isolated. Test traffic stays visible internally but is withheld from advertising optimization. Atomic data updates stop concurrent enrichment from erasing unrelated event details.
Proof 3 · Built and Working
The skills library contains 45 current skills and 12 composed workflows across research, positioning, writing, SEO, creative production, browser work, publishing, video, knowledge, and engineering. The count is not the important part. The operating contract is.
01
What the employee must know before it starts.
02
Deterministic steps, judgment rules, examples, and counterexamples.
03
Which tools and actions are allowed, gated, or prohibited.
04
What must be recorded to prove completion and improve the next run.
Assignment routing chooses the most specific match, fails closed when routes are ambiguous, uses a bounded last-known-good result during temporary failures, and records assignment context with the work. Focused routing tests pass.
Customer-ready design: the skill library and assignment-routing model provide the operating standard. Each business can receive its own assignments, evaluation cases, permissions, and authority without changing the underlying runtime.
Proof 4 · Live CRM Path
The agent queries the configured calendar, offers actual openings, finds or creates the customer, and writes the appointment into the business's operating system.
If another person takes the slot between search and booking, the tool returns the conflict and requires a fresh availability check. Communications are stored first-party before optional CRM synchronization, and failed contact creation can resume from persisted state.
Customer-ready design: A platform-agnostic CRM router allows each customer's operating hub to be configured at the tenant layer while preserving the same employee, assignment, communication, and attribution model.
Proof 5 · Working Components
Agent quality is not only the model's answer. It includes whether the system used the right context, stayed inside its permissions, requested approval at the right time, recorded what it changed, and could recover after a provider or process failed.
Customer-ready design: these controls make customer deployment safe. Every assignment can carry its own permissions, approvals, escalation rules, evidence, and scorecard while preserving the same operating model.
Breadth With Boundaries
Market, keyword, competitor, website, search, and social research tools feed a staged content and creative pipeline. A programmatic video engine has produced verified media outputs.
Agents can work through APIs, CLIs, browser automation, database tools, and an MCP router. The live stack runs across Fly.io, Cloudflare, Supabase, Vapi, Twilio, and GoHighLevel.
Some complete pipeline runs have failed on provider quotas and malformed model output. Not every capability runs in every workflow by design. Additional links are activated when an operating need justifies them, and the failures already observed shaped the recovery architecture.
Two Corrections
01
The live-call failure changed my default. Dependencies receive time limits, degraded modes, visible errors, and recovery behavior before they sit on a consequential path.
02
I proved several capabilities before one repeated customer workflow had earned the full surrounding system. If I restarted, I would begin with one consequential workflow, instrument its real use, and expand only after the evidence justified additional scope. Autonomy and complexity are earned one bounded responsibility at a time.
What I Am Looking For Now
I spent 1.5 years building and operating 1000x Sales and its underlying AI systems. I am no longer actively operating the company. I am now looking to commit full-time to a team where I can apply this zero-to-one range against a focused customer problem and a tighter feedback loop.
I am most useful close to customers and the product: finding the real constraint, building the smallest useful version, watching where it fails, and hardening only what earns the right to scale.