Knowledge bases, PM platforms, CRM architecture, Slack workflows, AI automation - connected into one coherent operating system. Not one perfect app. Clean integrations, real operational improvements.
Information architecture, SOPs, client playbooks, decision logs, meeting-to-knowledge pipelines. Notion, Confluence, or custom. Governed so it stays accurate and searchable.
PM platform design and implementation. Slack workflows, shared inbox integration, Google Sheets sync. Everything wired so status changes propagate and nothing falls through.
n8n automation pipelines, AI search/Q&A systems, context architecture that makes AI outputs reliable. Browser automation for repetitive flows. The layer that makes everything compound.
A growing FF&E manufacturer with no operational systems. Everything lived in email, scattered spreadsheets, and people's heads. Team across 4 countries with no shared tools, no SOPs, no knowledge base. Every process was manual, every handoff was a risk.
A fast-scaling construction tech company with a CRM held together by workarounds. Manual quoting eating 45+ minutes per lead. Escalations consuming ~50% of possible profit. Disconnected tools, no integration strategy, teams working around the system instead of with it.
AI search and generation are only as good as your information architecture. I design the context layer - constrained inputs, clean metadata, governed source documents - that makes AI outputs reliable. Not magic. Structure.
Escalations were eating roughly 50% of possible profit. No classification system, no routing logic, no visibility into patterns. Issues bounced between teams, resolution times ballooned, and the same problems kept recurring because nobody was tracking root causes.
Every department ran on different tools, different processes, different definitions of "done." Sales tracked work in spreadsheets, construction used email threads, HR had their own system. No single source of truth for who was doing what, no cross-department visibility, and no way to automate handoffs between teams.
Quoting took 2.5 days on average. Reps were manually measuring properties, calculating materials, looking up regional pricing, and assembling quotes by hand. The process was slow, error-prone, and couldn't scale. Two of the company's largest teams (100+ people each) were bottlenecked on this single workflow.
Managed a fully remote design team of ~15 people across time zones - one of the earliest remote management roles in a predominantly in-office Microsoft culture. Responsible for delivery pipeline, sprint coordination, and stakeholder communication across multiple product teams.
Architecture-trained. Tech-wired. I spent nearly a decade working under a co-founder of oDesk/Upwork across three companies. The most important thing he taught me: data, data, and more data points for everything. No gut feelings. No "I think." Measure it, prove it, then decide.
That principle shaped how I work. When I see a broken process, a manual bottleneck, a system held together by workarounds and good intentions, I can't leave it alone. I will map it, instrument it, find where the data says it's failing, and rebuild it.
I sit between engineering and business. I speak both languages fluently. When things are chaotic, I'm the person who brings structure - not by adding meetings or documents, but by building systems that make the chaos legible.
Let's build your operating system.
Get in touchI prefer working globally via Upwork - where both client and freelancer are protected.