I design the systems that make growing companies run.
AI workflows, automations, APIs, cloud infrastructure, websites and web apps, operational dashboards, CRM architecture, and internal tools — designed from the business process outward.
The problem
Manual follow-ups, disconnected tools, unclear ownership, unreliable CRM data, and reporting held together by spreadsheets are usually symptoms of the same thing: the system underneath the business needs structure.
Capabilities
From automation and web applications to cloud-backed internal tools, I work across the technical layers needed to make an operation easier to run and easier to trust.
Case studies
Anonymized work across AI automation, operations, CRM, API integrations, dashboards, marketing systems, cloud-backed tooling, and technical troubleshooting.
The morning status check dropped from close to an hour of cross-referencing to a few minutes on one screen, and overdue follow-ups now surface themselves instead of waiting to be found.
View details
Encoding a new price list went from an afternoon of copy-paste per supplier to a few minutes reviewing flagged items, and the ordering sheets now update the same day a price list arrives.
View details
Lead research that used to take a rep an afternoon of tab-switching now takes a few minutes of review, and a new list goes from raw CSV to live outreach the same day.
View details
Pipeline reports went from guesswork to numbers the founder uses in weekly reviews, and the CRM stayed clean months after handover because the hygiene rules and SOPs did the maintaining.
View details
Coaches went from a growing backlog of unread check-ins to reviewing their full roster in a short daily pass, with at-risk clients surfaced the same day they submit.
View details
The daily status scramble across five tools became a two-minute glance at one screen, and overdue orders stopped being found by accident.
View details
Architecture process
The build starts with the process and the failure modes — not with whichever automation tool happens to be popular.
Understand how the work actually moves before choosing technology.
Find where information duplicates, breaks, stalls, or becomes ambiguous.
Choose the lightest reliable combination of automation, APIs, data, cloud, and custom code.
Implement workflows, integrations, dashboards, or internal applications in the right layer.
Missing fields, retries, permissions, rate limits, duplicate events, and unhappy paths.
Logs, dashboards, alerts, and review queues make systems trustworthy.
Written specs, diagrams, runbooks, and async walkthroughs become the source of truth.
Improve the architecture based on what the team actually needs after launch.
Technology across the stack
Tool choice follows the architecture. Explore the layers I work across — automation, AI, cloud, backend, frontend, integrations, and business systems.
Technology layer
Workflow engines, scripts, and operational automation — from visual orchestration to custom Google Workspace logic.
How I think
I care about architecture decisions, failure modes, observability, permissions, documentation, and whether the next person can maintain what I build.
I work from the business process outward — not from a favorite tool inward.
I can move between automation platforms, code, APIs, cloud, databases, and internal UI when the architecture calls for it.
I think about failure modes, observability, access, handover, and what changes when volume grows.
I document technical decisions so async teams can move without repeating the same conversations.
I can operate as a hands-on builder today and a technical systems partner as the business grows.
Work together
The default is written context, architecture diagrams, Loom walkthroughs, documented decisions, and structured updates. Meetings are used only when synchronous technical alignment is genuinely faster.
Send the current workflow, what is breaking, and the outcome you need. I’ll review it asynchronously and come back with focused questions or a recommended next step.