← The Archives Strategy · Product redesign · Programmatic SEO
AdSpot
I wrote the argument for turning a one-off ad service into a subscription platform, then designed and shipped the platform it became.
Brand and Digital Designer / Digital Marketing Strategist · Mar 2025 to May 2026
The problem
AdSpot sold display advertising one campaign at a time. The impressions model was squeezing margin and there was no recurring revenue underneath it.
Making that case meant writing it down first: where the money was leaking, and why subscription fixed it.
Then it meant building the thing, on GoHighLevel, which was never designed to be somebody else's product.
What I did
- Authored the written strategy for the pivot, showing the margin squeeze in the impressions model and the case for recurring revenue.
- Redesigned and replatformed the product on GoHighLevel, white-labelling the interface top to bottom with custom CSS and JavaScript so it reads as AdSpot rather than GHL.
- Delivered the first display-advertising product to run inside GoHighLevel, embedded via iframe with custom menu links and custom objects.
- Designed and shipped 997 programmatic SEO landing pages from one template and one data table, each with its own title, meta description, targeting content, FAQ, canonical URL and structured data.
- Rebuilt navigation into a full mega menu mapped across every product area, from lead management to AI agents.
- Redesigned the campaign cart into a pop-over modal with a floating access button, for usability and mobile.
- Built a seven-step onboarding application, then made the call to retire it when scope and timeline stopped justifying it.
- Learned a PHP, SQL and cPanel stack on the job, having not used it before the role.
What it did
- 997 landing pages live from one template and one data table, each one its own indexable page.
- A client site went from under 100 search impressions to more than 12,000 in 90 days, and click-through rose from 2% to 42%.
- One-off ad sales became a subscription product with recurring revenue underneath it.
The work
















Decks and documents
Retiring the onboarding build was the right decision and it still stings. Knowing when to stop is part of the work.





