Kodelytics subcontracts, so client names are not Kodelytics' to advertise. Each note gives the industry, the scale, what was owned versus what the team executed, and the number where one exists.
The role line is deliberate. Most of this work was delivered alongside developers and specialists who were not employees of Kodelytics, and a case note that implies otherwise is a claim that falls apart on a reference call.
More than $41,000 of unauthorized spend, active malicious campaigns, and no documented timeline of how access was obtained. First-line platform support was responding with templates, and the evidence needed for a credit claim was degrading by the day.
My role: led the forensic response, the documentation, and the platform escalation end to end. Team: the client's internal IT secured the surrounding Google Workspace accounts.
Google Ads
Google account security
MCC access governance
159 tracked work items, scoped and sequenced for a database automation program.
The development team understood the target state and could not express it as a plan the sponsor could fund or track. Requirements existed as conversations. There was no work breakdown, no sequence, and no way to report progress that meant anything to the person approving the budget.
My role: scoped and structured the program, and acted as the translation layer between the development team and the VP sponsor. Team: the client's database and platform developers owned technical design and implementation.
Azure DevOps
Azure Database for PostgreSQL
CI/CD pipelines
Jira
15+ locations, one attribution gap, quarterly reporting that runs itself.
Location data was not passing on conversion events, so per-clinic performance could not be attributed — corporate could see aggregate spend and aggregate conversions, and could not defend a budget decision at the clinic level. Quarterly reporting was assembled by hand, which capped both frequency and depth.
My role: owned the diagnosis, the reporting architecture, and the client-facing deliverables. Team: the agency's paid media leads supplied campaign context and executed account changes; I did not manage the ad accounts day to day.
GA4
Google Ads
Call tracking
BigQuery
Looker Studio
Cost per acquisition driven to roughly half the target.
Account structure did not allow budget to follow performance: facilities with strong unit economics and facilities with weak ones drew from the same undifferentiated setup, and conversion tracking issues meant reported CPA was not comparable between locations.
My role: account restructuring plan, tracking corrections, and the performance reporting the operator managed against. Team: the agency's paid media specialist executed in-platform campaign changes.
Google Ads
GA4
Call tracking
Looker Studio
154 data sources migrated. Zero unplanned outages.
The deployment had grown for years without an inventory. Nobody could state how many assets were in scope, which reports were used, or what each one depended on. A partner consultancy had been engaged for conversion work, but there was no sequencing, no validation standard, and three parties each holding part of the plan.
My role: delivery lead — inventory, sequencing, client IT coordination, and the migration tracker. Team: a partner consultancy's technical lead and two migration developers executing the workbook conversions.