Automation, dashboards, and internal tools for operations-heavy teams.
I help small teams turn spreadsheet sprawl, manual reporting, API handoffs, and back-office cleanup into practical systems they can actually use and maintain.
Best fit for founders, solo consultants, agency owners, ops managers, and fractional COOs.
The sweet spot is work where operations, automation, software, and clear communication all meet.
What you can hire me for
Focused builds for teams that need cleaner workflows more than they need a giant platform migration.
Sheets and Apps Script automation
Turn spreadsheet handoffs, follow-up lists, and manual status checks into repeatable Google Workspace workflows.
Dashboards and reporting workflows
Build practical KPI views and reporting paths for teams that need cleaner visibility without a heavy BI rollout.
API integrations and CRM sync
Connect the tools already in use, reconcile messy records, and reduce duplicate entry across operational systems.
Python automation and cleanup scripts
Clean, normalize, enrich, and move data through small scripts that are documented enough for the team to trust.
Lightweight internal tools
Ship focused React or Next.js admin panels for the workflow that keeps escaping email, chat, and spreadsheets.
Good fit
You have a real workflow already running in Sheets, Gmail, Slack, a CRM, or a shared inbox.
Your team needs a small working slice before a larger build decision.
The problem crosses data cleanup, communication, reporting, and operations handoffs.
You want documentation and maintainability, not a black box.
Not a fit
Speculative app ideas without a clear operating problem.
Growth hacking, scraping, spam, or account-risk automation.
Projects that require publishing private client data or unverified claims.
Large enterprise rewrites that need a full agency team from day one.
Proof from the public lab
Public artifacts translated into buyer problems: follow-up systems, spreadsheet automation, API cleanup, and maintainable operational workflows.
Case Study: Public Automation Lab as a Workflow Systems Practice
How the public automation lab turns messy recurring work into reusable artifacts, documented workflows, and buyer-facing proof for operations automation.
Google Sheets CRM + Follow-Up Automation for Solo Consultants
A practical first lab build for solo consultants: a Google Sheets CRM that turns follow-up from memory into a repeatable operating system.
Automating Slack with Google Sheets: Posting Unique Messages from a Spreadsheet
I recently tackled this exact challenge, and after some tinkering with Google Apps Script and the Slack API, I’ve got a solution that works like a charm.
Mastering Slack Canvas Automation: A Journey Through API Quirks
From chasing ghost endpoints to battling undocumented limits, this journey taught me more about the Slack API than I bargained for.
How projects usually work
Start narrow, prove the workflow, then expand only when the operating value is clear.
Step 1
Diagnose the workflow
Clarify the job, the current tools, the handoffs, and the cost of the messy parts.
Step 2
Map the data path
Identify where records start, where they drift, and what the team actually needs to see or trigger.
Step 3
Ship a working slice
Build the smallest useful automation, dashboard, script, or internal panel that proves the system.
Step 4
Document and hand off
Leave behind the operating notes, setup details, and maintenance path so the system can keep working.
Bring the messy workflow.
A good first note includes the current tool stack, the recurring pain, the people affected, and what would count as a useful first win.