ClientMeta-ads agency, home-service contractors
Agency Command Center (Meta Ads + GoHighLevel)
Every morning, each client's spend, billing, leads and speed to lead from Meta and GoHighLevel, on one screen.A failed read shows as a failure, never as a quiet zero. Built solo, in production on the agency's own accounts.
Daily Meta + GHL syncsSigned ingest (HMAC)Failure rows, never zerosAlerts to chat, DMs, tasksSample data on screen
Learn moreShow less→
Description
A command center for a Meta-ads agency with about 50 home-service clients. A Next.js app on Supabase, fed by 24 n8n workflows on the agency's own n8n Cloud that read Meta and GoHighLevel each morning and in real time, write signed rows to one store, and alert the team where it already works. Everything runs on accounts the agency owns.
Problem it solved
The agency's reporting pipeline had been silently dead for about six and a half months while every run reported success, it covered roughly 36 of 108 ad accounts, and the dashboard the team used was failing 31 of its 38 CRM reads. The owner asked for a dashboard that is genuinely good, not a repair job, and ruled out a generic SaaS look.
What was done
Audited all 108 ad accounts and 73 sub-accounts first. Built the daily and real-time syncs (Meta, GoHighLevel, lead events, call-centre intake, lead quality, posting gaps), a signed ingest that checks signature, timestamp and schema version before any write, an error rail that files a failure row on any crash, the alert rail (client channel, DM, task board, delivery ledger) and ten app screens built around the daily check. Colour marks facts; a verdict appears only when the owner's own rulebook sets the target. On the GoHighLevel side: a lead-quality pipeline on every active account and an AI lead mover rolled out per account with the owner's OK. The first version ran on the agency's accounts three weeks in.
Case study →Row in the technical summary →
ClientAI receptionist for service businesses
Callixa: AI receptionist landing page
Landing page for an AI receptionist: a plumber lands and watches a plumbing call get answered and booked.Seven client review rounds on live URLs, 45 languages, live on the client's own Vercel team.
11-vertical video hero45 languages + RTLAA-safe accent splitLive URL per review roundGHL form + calendar slots
Learn moreShow less→
Description
A hand-coded landing page for an AI receptionist sold to trades, dental, legal and medical practices: a dark token-driven design system, a per-industry video hero with an 11-vertical switcher, a fully visible FAQ grid, plain-language pricing, and a language picker with 45 languages and a location-based default.
Problem it solved
The buyers are non-technical owners comparing the product with a human receptionist. The page had to demonstrate the product answering their kind of call rather than describe it, and the client's GoHighLevel page builder could not reproduce the fonts, tokens or components the design needed.
What was done
Turned the scope document into tokens and a ten-section page; ran four concept rounds and seven numbered client review rounds, each deployed to its own URL so the client compared live builds instead of screenshots; split the brand indigo into a decorative accent and an AA-safe text tint; proposed and shipped the page as a standalone static build with GoHighLevel supplying only form, calendar, CRM and tracking through marked slots; added the 45-language layer with generated dictionaries, a location-based default and right-to-left support; moved the deploy to the client's own Vercel team on their domain.
Live site (opens in a new tab) ↗Case study →Row in the technical summary →
ClientWeb design agency prospecting local businesses
WebPulse: scrape, score and rebuild engine + Studio
Finds local businesses with outdated sites, scores them with a vision model and rebuilds the good ones as live previews.Runs as Claude Code skills the agency drives in plain English; drafts are reviewed and redeployed from WebPulse Studio.
Apify + Playwright scrapeVision scoringBrand-repainted templatesOne Vercel project per nicheSheet delivery + outreach drafts
Learn moreShow less→
Description
A Claude Code-native kit for a web design agency: composable skills chain scrape, qualify, extract assets, build, deploy and deliver, with one autopilot command per city. WebPulse Studio puts the pipeline behind a login so the team reviews each AI-built draft, fixes copy, photos and logo, and redeploys from one screen.
Problem it solved
The agency's best pitch is a finished redesign of the prospect's own site, but doing that by hand costs hours per prospect when cold outreach needs thousands. The client turned down an n8n build and wanted to drive everything through conversation.
What was done
Built the six-stage pipeline with cost discipline: AI only for the judgment calls (vision qualification, photo scoring), deterministic code for everything mechanical (brand extraction, template fill, palette repaint, deploy). Pre-flags skip franchises and no-website listings before any paid call. One Vercel project per niche with a route per lead. Delivery lands in the client's Google Sheet with preview URLs and optional outreach drafts; automatic sending was left out on purpose.
Live preview (opens in a new tab) ↗Lead-gen demo (opens in a new tab) ↗Case study →Row in the technical summary →
DemoHome services, residential cleaning
FreshNest: cleaning-company site wired into GoHighLevel
A six-page cleaning-company site, hand-coded in Astro, with the quote form and booking calendar landing in GoHighLevel.One config file drives every page, so the next branded site is a config change plus a logo and photos.
6 pagesConfig-drivenGHL form + calendarNear-zero JSPrivacy + terms pages
Learn moreShow less→
Description
A sample cleaning-company website built as a repeatable system: every headline, service, review, service area, brand colour and GoHighLevel embed lives in one config file, and the components read from it. Fictional business, sample content, no invented review numbers.
Problem it solved
Cleaning companies need a fast, mobile-first site that drops every visitor into the CRM without a page builder, and an agency needs to launch the next one without rebuilding from scratch.
What was done
Built the six pages in Astro with scoped design tokens and a few kilobytes of hand-written JS; wired the quote form and booking calendar to GoHighLevel; wrote the client setup guide and the launch steps (config, assets, embeds, build, deploy, DNS); removed invented ratings in an honesty pass and added indexable privacy and terms pages.
Live site (opens in a new tab) ↗Row in the technical summary →
DemoHome services, residential cleaning
Trustworthy Cleaning: instant quote calculator
An instant-quote calculator for a real Austin cleaning company: the price rolls as you answer, and bars show what moved it.Contact details unlock the exact quote and a branded PDF; the office view shows the lead score and the webhook JSON for GoHighLevel.
Live rolling priceWhat-moves-this-number barsBranded PDF quoteLead score in viewGHL webhook payload
Learn moreShow less→
Description
A concept instant-quote tool on the business's own brand: palette, font, crew photos, services, checklist and service area come from their website, and the layout and motion are cloned from a named Dribbble reference (two cards, rolling price, range tick, driver bars). Every dollar is a labelled concept rule, because the business publishes no prices.
Problem it solved
The company's homepage promises "your price in about a minute, no walkthrough, no callback", then collects a lead form with no number behind it. The tool had to give the number, explain it, and hand the office a lead it can act on.
What was done
Built the three-step form and the live estimate card. Out-of-area ZIP codes get a straight answer, and offices or homes with 5+ bedrooms go to a person instead of a fake flat rate. Contact details unlock the exact figure, never the range, and the PDF breakdown matches the page. The payload uses the GoHighLevel workflow library's field names, with UTM attribution and timestamped SMS consent; sample mode sends nothing until a real webhook is pasted. A footer line marks it as a concept build.
Live site (opens in a new tab) ↗Row in the technical summary →
ProductionMy own
This site and its written door
The portfolio itself: static pages, an animated system map, and a form that lands in my inbox and on my phone.One Vercel function posts each message to a Telegram bot and to Gmail, then answers with a status per channel.
Vercel functionTelegram + GmailHoneypot + validationPer-channel statusmailto fallback
Learn moreShow less→
Description
A hand-coded static site (no framework, self-hosted fonts) with one serverless function behind the "send the task" form. The function validates the message, drops honeypot submissions, posts to a dedicated Telegram bot and sends a Gmail copy with the visitor's address as reply-to, then returns ok, skipped or failed for each channel.
Problem it solved
A bare mailto link does nothing on a laptop with no mail app, and a form that only emails can fail silently. The site needed a written door that works for everyone and tells me when a channel breaks.
What was done
Built the form with client-side checks and a mailto fallback for local copies and failures; wrote the function with per-channel results, so one request is the whole health check; kept secrets on the Vercel project only; added the animated system map component (inline SVG, reduced-motion fallback, off-screen pause, keyboard focus); set trailing-slash routing so relative links hold on the live domain.
The form →Row in the technical summary →
DemoAgencies and founders who quote services
Voice-note-to-quote Telegram bot
Speak a quote into Telegram and get a branded PDF back; reply with changes for a revised version.Built with Claude Code in the WAT shape: workflows anyone can read, one skill folder for brand and pricing, small tools.
Voice to transcript to JSONPlaywright PDFReply-to revise loop/approve + email draftWhitelist auth
Learn moreShow less→
Description
A private Telegram bot for one founder. Voice notes are transcribed, a model drafts the quote as JSON under a brand skill (voice guide, schema, pricing rules, examples), Jinja2 and headless Chromium render the PDF, and a reply-to loop applies the smallest change and re-renders. /approve archives the version and drafts the send-to-client email.
Problem it solved
A typed quote means opening the template, writing the summary in brand voice, structuring deliverables, pricing, terms and exporting, when the founder already knows what to say and could say it in a minute.
What was done
Designed the three-layer structure (workflows, agent skill, tools); built the transcription, draft, render, revise and approve paths with SQLite state in WAL mode; fixed a racy quote-ID generator with an atomic sequence table; moved blocking render and model calls off the bot's event loop; swapped the model provider mid-build in four files because the skill content was provider-agnostic. No hours-saved figure is claimed until it is measured.
Private build, walkthrough on request →Row in the technical summary →
DemoCourse creators and founders with video libraries
Video to Notion knowledge base pipeline
Ten talks in, 227 Notion rows out: concepts, captioned screenshots, entities, each deep-linked to the exact second.Resumable at every stage, so video 246 is a re-run, not a rebuild.
Model-chosen screenshotsCross-video consolidationResumable manifest4 linked Notion DBsMeasured cost $1.29
Learn moreShow less→
Description
A deterministic, resumable pipeline built for a 245-video brief and proven on ten public startup talks: acquire, proxy, transcribe (captions first), one structured watch pass per video, settled-frame capture around the moments the model flagged, embedding-based consolidation across videos, and an idempotent Notion publisher.
Problem it solved
Blind scene detection produces hundreds of unlabeled frames per video, 245 summaries are not a knowledge base, and a pipeline that cannot resume gets re-run from scratch a dozen times at that scale. The buyer also assumed model cost was the constraint; measured, it was not.
What was done
Wrote the stages as standalone scripts sharing one SQLite manifest; designed against Notion's real limits (data-sources model, about 3 requests per second, block and payload caps, three-call image uploads); built a pre-flight that checks token, sharing and write access step by step; measured the real token cost; published the library with schema, relations and uploads through the API. Video acquisition and caption parsing reuse an MIT tool credited in the repo; the orchestration, watch pass, capture, consolidation and publisher are original.
Walkthrough (opens in a new tab) ↗The Notion knowledge base (opens in a new tab) ↗Row in the technical summary →
DemoDTC brands and performance-creative teams
Meta static ads: template engine
A reference ad becomes a template JSON that has already been proven to render, with the copy as data.The validator exits non-zero on the mistakes that get templates rejected, so a batch is gated, not advised.
Contract + compile validationDeterministic rendersEmbedded fontsTransparent-cutout probe1080 x 1350 output
Learn moreShow less→
Description
Built as the work sample for a high-volume static-ads role where templates are pasted into the client's Laravel system. A conversion prompt turns a reference image into template JSON; the build step validates schema, copy lengths and defaults and compiles the template; the renderer produces PNGs at the declared size with fonts and images inlined so output never drifts between machines.
Problem it solved
Payment on approved briefs means a rejected template is unpaid work plus a round trip, and most rejection causes are mechanical: undeclared variables, overlong default copy, malformed defaults, templates that do not compile.
What was done
Wrote the Blade-subset compiler, the validator, the Playwright renderer with a contact sheet, and an alpha probe that confirms product cutouts are truly transparent; authored the template archetypes and six briefs. Scope kept narrow on purpose: the subset compiles only what production Blade also compiles.
Work sample, renders on request →Row in the technical summary →
DemoDTC brands
Static Ads Factory
Product photo in, scene imagery out: 40 tagged prompts, two provider families, a cost gate and a cache.Copy stays out of the pixels, so headline, price and call to action remain A/B variables in the template engine.
40 scene prompts6 buying presetsAuto model routingCost gate + dry runCurated trios per product
Learn moreShow less→
Description
The imagery half of a two-stage pipeline. A library of 40 scene prompts in six categories, selectable through six buying presets a media buyer speaks, is run per product; prompts that need in-image text route to the stronger text model; a dry run prices a batch before any spend; a cache and retry make re-runs cheap.
Problem it solved
Scene work and typography have different best models and different costs, and baked-in copy turns every headline test into a re-render.
What was done
Built the prompt library with tags and placement rules (Meta feed, Amazon main image white-only, A+ slots), the packshot helper that normalizes CDN images, routing by text need, the cost gate, the review sheet and offline smoke tests; documented the placement traps, such as off-white not being white.
Private tooling, samples on request →Row in the technical summary →
PracticeHome services, pet services, estate law (six practice brands)
GoHighLevel workflow library (11 specs)
Eleven GoHighLevel workflow specs with diagrams: one router, six brands, thin arms, from one sub-account.Designed and documented, with 34 email templates built. Not yet built inside GoHighLevel.
11 specs + diagramsCanonical lead schema51 namespaced tags34 email templatesSMS built but switched off
Learn moreShow less→
Description
A reusable automation layer for the six practice funnels: a closed vocabulary of real GoHighLevel steps, a canonical 21-field lead schema, three pipelines by commercial motion, colon-namespaced tags, custom values, six field maps, and eleven workflow specs, each with a Mermaid diagram checked by a structural validator.
Problem it solved
Six funnels collected six different field sets with inconsistent names, so no single router could attach to them, and an agency that re-clones a snapshot per client never ends up with a library.
What was done
Wrote the registry and the eleven specs (intake and auth, lead router, two quote engines, order and session, appointment lifecycle, welcome sequence, speed-to-lead and missed-call text-back marked off, review request with a rating gate, ops and failure handler); built 34 branded email templates on one shell; decided against A2P registration for a fictional brand and left every SMS step built and disabled. The build inside GoHighLevel is the next phase and is not claimed.
Specs on request →Row in the technical summary →
ProductionMy own
OLJ Watch: job-ad scanner
Scans a job board every 30 minutes, scores new ads against my skills and pay floor, and sends the matches to Telegram.The application letter is assembled from proof blocks, no model call, so it costs nothing to run.
Every 30 min8 searchesScore + hard blockersPay-floor parsingLetter from proof blocks
Learn moreShow less→
Description
A personal tool: eight keyword searches, a scoring rubric (platform skills, dashboards, automation, agency employer, role shape), hard blockers for roles I do not want, a pay parser that converts monthly and peso figures to an hourly rate, and a letter assembled from measured proof blocks with the portfolio link. A seen-list makes sure nothing is sent twice.
Problem it solved
Applying within hours of a posting is the edge on that board, and reading every new ad by hand all day is the opposite of automation.
What was done
Built the scanner, the scoring and filters (tuned against nine of my own accepted and rejected examples), the Telegram sender and the hidden scheduled task; added a check mode that grades a single ad with reasons, a dry run, and a stateless cloud mode for a hosted routine.
Row in the technical summary →
DemoLocal services (nail salons and med spas in the sample runs)
Beautiful Websites Kit
Four chained agent skills: scrape a niche in a city, score each site, rebuild the ones worth it, deploy.A build log forces a different palette, typeface and layout on every site, so no two come out alike.
4 skillsScrape, score, rebuild, deployBuild log for varietyVercel deploysRuns inside Claude Code
Learn moreShow less→
DemoAny team with policy or product documents
Doc upload to Gemini File Store RAG Q&A + evaluation score
Upload a PDF once, then chat with it: answers come grounded in the document, with citations.An optional evaluation path scores each answer and logs it to Google Sheets.
Form uploadAuto-indexingCited answersEval score to Sheet
Learn moreShow less→
Description
An n8n form accepts a PDF and indexes it into a Gemini File Store; a chat flow answers questions grounded in that store with citations. An optional evaluation path scores answers and logs them to Google Sheets.
Problem it solved
A team's policies and product documents live in PDFs nobody searches, and a chatbot that answers from general knowledge invents things.
What was done
Built the upload and indexing path, the grounded Q&A with citations, and the evaluation logging so answer quality can be tracked over time instead of trusted.
On the automation page →Row in the technical summary →
DemoLead generation for local-service outreach
Google Maps prospect scraper + website contact enrichment
Google Maps listings for a niche and city land in a Sheet, then each website is read for emails and social links.Repeat-prevention means a re-run only adds new businesses.
Apify Maps scrapeFirecrawl enrichmentEmail + social extractionRepeat prevention
Learn moreShow less→
Description
Apify pulls Google Maps listings for a niche and city into a Sheet; Firecrawl then reads each business website for emails and social links (LinkedIn, Facebook, Instagram, X), writes a contact-ready row, and skips anything already processed.
Problem it solved
Outreach lists bought or scraped by hand are stale, duplicated, and missing the contact detail that makes a first message possible.
What was done
Built the scrape-to-Sheet flow, the per-site enrichment with custom JavaScript parsing, and repeat-prevention so re-runs only add new businesses.
On the automation page →Row in the technical summary →
DemoAppointment-based local businesses
Instagram DM chatbot
Instagram DMs, typed or voice, answered from the business's own FAQ with conversation memory.Checks the next 14 days of Google Calendar availability and replies on Instagram.
Webhook intakeVoice transcriptionFAQ-grounded agentCalendar availabilityEcho filtering
Learn moreShow less→
Description
Instagram DMs arrive by webhook; echo messages are filtered, voice notes are transcribed with Whisper, and an AI agent grounded on a Google Docs FAQ with conversation memory answers questions and checks the next 14 days of Google Calendar availability, replying on Instagram.
Problem it solved
Appointment-based businesses lose DMs that arrive after hours or as voice notes, and a generic bot cannot answer in the business's own policies.
What was done
Built the webhook intake with echo filtering, the text-versus-voice routing and transcription, the FAQ-grounded agent with memory, the calendar availability tool and the reply path.
On the automation page →Row in the technical summary →
DemoFounders and executives
Telegram voice executive assistant
Dictate a request into Telegram; the agent looks up the contact, sends the email and books the meeting.Conversation memory and a quick "processing" reply so the sender knows it landed.
Voice transcriptionAgent with 3 toolsGmail sendCalendar bookingMemory
Learn moreShow less→
Description
Text or voice messages to a Telegram bot are transcribed, then an AI agent carries out the request with connected tools: contact emails from Google Sheets, sending through Gmail, booking in Google Calendar, with conversation memory and an immediate acknowledgement.
Problem it solved
Founders dictate tasks on the move; nothing turns "email Sam and book Thursday" into the email and the booking without a person in the loop.
What was done
Built the Telegram intake, the transcription, the agent with three tools and memory, and the acknowledgement reply.
On the automation page →Row in the technical summary →
DemoE-commerce, apparel
AI virtual try-on generator for WooCommerce
A model photo and a product photo from a Sheet become a "model wearing the product" image.The job is polled to completion, the image saved to Drive, the link written back, and the product updated.
Sheet-driven batchImage model job pollingDrive uploadWooCommerce update
Learn moreShow less→
Description
Model and product images listed in a Google Sheet are sent to an image model that renders the model wearing the product; the job is polled until complete, the image saved to Google Drive, the link written back to the Sheet, and the matching WooCommerce product updated.
Problem it solved
Try-on imagery for an apparel catalogue means a photoshoot per product; without it, listings show flat product shots.
What was done
Built the Sheet-driven batch, the Drive link conversion, the asynchronous job polling, the upload and write-back, and the WooCommerce product update.
On the automation page →Row in the technical summary →
DemoSales teams
Sales agent system
Four flows on one Google Sheets CRM: intake, AI follow-ups capped at three, booking concierge, no-show recovery.Any flow can pause or fail without breaking the others, because the Sheet is the only source of truth.
4 flows, 1 CRMAI follow-ups, max 3Calendly listener6-hour no-show sweepFull audit trail
Learn moreShow less→
Description
Four coordinated flows sharing one Google Sheets CRM: lead intake with IDs and dedupe, AI-personalized follow-ups capped at three, a Calendly booking listener that flips status instantly, and a no-show sweep every six hours that sends a reschedule email and updates the row.
Problem it solved
Most lost deals were never rejected. The follow-up lived in someone's head, and booked-but-ghosted leads were written off.
What was done
Built the four flows and the shared CRM state so any flow can pause or fail without breaking the others; the model writes each follow-up from the lead's own context and stops after three.
Build story →Row in the technical summary →
DemoAgencies and consultants
Fathom-to-proposal generator (Google Slides)
A recorded discovery call becomes a proposal deck: sections extracted by a model, a Slides template filled.The deck link is emailed for review and the CRM row updated, with nothing retyped.
Fathom webhookTranscript cleanupAI section extractionSlides template fillReview email + CRM update
Learn moreShow less→
Description
A recorded sales call arrives by webhook from Fathom; the workflow pulls the lead's details from Sheets, cleans the transcript, extracts proposal sections (title, bottlenecks, phases, pricing) with a model, copies a Google Slides template, fills the placeholders, emails the deck link for review and updates the CRM row.
Problem it solved
Writing the proposal deck after a discovery call is the same hour of work every time, and the details are already in the recording.
What was done
Built the webhook capture, the transcript cleanup, the AI section extraction, the Slides template copy-and-replace, the review email and the CRM update.
Build story →Row in the technical summary →
DemoAgencies running delivery in Notion
HighLevel pipeline stage to Notion clients sync
When an opportunity changes stage in HighLevel, the matching Notion client record updates in real time.Delivery always sees pipeline truth without anyone re-typing it.
Stage-change webhookLookup by contact IDReal-time Notion update
Learn moreShow less→
Description
The moment an opportunity changes stage in HighLevel, an n8n webhook finds the matching client in Notion by GoHighLevel contact ID and updates its pipeline stage.
Problem it solved
The CRM and the delivery team's workspace disagree about where a client stands, because somebody has to re-type the stage.
What was done
Built the stage-change webhook, the lookup by contact ID and the Notion update.
On the automation page →Row in the technical summary →
DemoAgencies
AI contract automation (closed deal to PandaDoc to onboarding)
A "Closed" update in the CRM sheet becomes a PandaDoc contract, with key terms extracted from the call transcript.A signature triggers the welcome email; an onboarding booking creates and shares the client's Drive folder.
Closed-deal triggerAI term extractionPandaDoc contractSignature monitoringOnboarding folder
Learn moreShow less→
Description
A "Closed" update in Google Sheets becomes a PandaDoc contract: key terms are extracted from the Fathom transcript with a model, a review link is sent, the contract ID and status are logged to the CRM; a signature triggers a welcome email, and a Calendly onboarding booking creates and shares the client's Google Drive folder.
Problem it solved
Between "yes" and a signed contract, deals stall on paperwork assembled by hand from a call everyone has already had.
What was done
Built the trigger, the AI term extraction, the PandaDoc document creation, the signature monitoring, the welcome email and the onboarding folder automation.
Build story →Row in the technical summary →
DemoOps teams
Notion business-ops suite (daily AI exec report + overdue escalation)
Every weekday at 5 PM, the day's Notion tasks become a KPI report with an AI executive summary, emailed to the CEO.Between reports, a 4-hour sweep reminds each assignee once a day and escalates after three ignored reminders.
Daily KPI reportAI executive summary4-hour overdue sweepEscalation after 3
Learn moreShow less→
Description
Two scheduled flows: every weekday at 5 PM, Notion tasks (done today, overdue, blocked, waiting on client) become a KPI report with an AI executive summary saved to a reports page and emailed to the CEO; every four hours a monitor sweeps past-due tasks, reminds each assignee at most once a day and escalates to the owner after three ignored reminders.
Problem it solved
Ops teams drift when nobody reads the board, and the owner finds out about overdue work in a meeting.
What was done
Built the daily report with the model summary, the 4-hour sweep with per-assignee reminder limits, and the escalation rule.
On the automation page →Row in the technical summary →
PracticeMarketing agency
AdFlow Performance funnel
Agency funnel in GoHighLevel: audit landing page, proposal step and onboarding sequence.Practice build on my own subdomain, not a client engagement.
Audit pageProposal stepOnboarding sequenceGHL forms + tags
Learn moreShow less→
Description
A multi-step agency funnel built in GoHighLevel on my own subdomain: an audit landing page, a proposal step and an onboarding sequence, with forms and tags carrying the lead between stages.
Problem it solved
Agencies lose prospects between a free audit and a signed proposal because each step lives in a different tool.
What was done
Built the three stages as one funnel with forms and tags carrying the lead between them. Practice build: no client, no traffic figures claimed.
Live funnel (opens in a new tab) ↗On the automation page →Row in the technical summary →
PracticeSolar installation
Pacific Coast Solar funnel
A solar landing page with an interactive savings calculator written in custom JavaScript.The visitor gets an estimate first and is asked for contact details after. Practice build.
Savings calculator (custom JS)Estimate before contactGHL form
Learn moreShow less→
Description
A solar landing page in GoHighLevel with an interactive savings calculator embedded as custom JavaScript, estimating savings from roof size and energy bill before the contact form.
Problem it solved
Solar leads bounce when the first screen asks for a phone number; a calculator gives value first.
What was done
Wrote the calculator and embedded it in the GoHighLevel page with the lead captured after the estimate. Practice build on my own subdomain.
Live funnel (opens in a new tab) ↗On the automation page →Row in the technical summary →
PracticePet waste removal
Pooch Scoop funnel
An opt-in funnel for a pet-waste-removal service with a zip-code check before booking.Out-of-area visitors never reach the calendar. Practice build on my own subdomain.
Zip-code checkService-area filterBooking after qualification
Learn moreShow less→
PracticeDental practice
Dental Haven funnel
A dental opt-in funnel written for anxious patients: reassuring copy, calm visuals, a short intake form.Practice build on my own subdomain, not a client engagement.
Empathy-first copyShort intake formGHL opt-in
Learn moreShow less→
PracticeEstate-planning law
Legacy Shield Law funnel
An estate-planning law funnel: opt-in page plus a post-consultation sequence that explains the planning tiers.Practice build on my own subdomain, not a client engagement.
Opt-in pagePost-consultation sequenceTier education
Learn moreShow less→
Description
An estate-planning law funnel in GoHighLevel: an opt-in page and an automated post-consultation sequence that walks the client through the planning tiers.
Problem it solved
Clients who book one consultation rarely learn what else the firm offers, so the firm never gets to offer it.
What was done
Built the opt-in page and the post-consultation education sequence. Practice build; no effect on case value is claimed.
Live funnel (opens in a new tab) ↗On the automation page →Row in the technical summary →
Nothing in this filter yet. Pick another, or show all.