Leads land everywhere except the CRM
Form fills, DMs, referrals, a business card from an event. Four sources, four inboxes, and no single place that says who is actually in play right now.
Certified HighLevel Admin · Davao, PH · Works US hours
I build the HighLevel system your business already assumed it had.
Most accounts have a CRM in name only. Leads sit in three places, follow-up depends on someone remembering, and the pipeline is a guess with stages on it. I go into your sub-account and build the pipelines, workflows, and forms that hold it together, then document it so your team can run it without me.
Book my build call
Fifteen minutes. You leave with the shape of the build whether or not you hire me.
- HighLevel Certified Admin
- A seven-stage pipeline and seven workflows, built and tested end to end
- Ships GHL-connected apps, not only sub-account config
Certified HighLevel Admin
01 / The problem
01
02
03
04
You bought HighLevel. You still run on memory.
Follow-up happens when someone remembers
You said you would get back to them. Three days passed. The lead went cold and nothing in the system noticed.
The pipeline is a guess with stages on it
Cards sit in the wrong column because nothing moves them. Any number you pull out of it is fiction, so you stop pulling numbers out of it.
Nobody else can touch it
Whatever exists lives in one person's head. The moment they are unavailable, the system stops.
These are build problems, not discipline problems. A workflow that fires at 2am does not need to be reminded.
02 / The work
A short list. All of it real, all of it mine.
I designed, built, and run every system below. The screens are from the actual builds.
GoHighLevel
A seven-stage sales pipeline, tested to the last email
A full sales pipeline for an Amazon PPC management business, built inside HighLevel and run against real contacts before it was called finished.
01
New Lead
10%02
Contacted
25%03
Appointment Booked
40%04
Consultation Completed
60%05
Proposal Sent
75%06
Closed Won
100%07
Closed Lost
0%Only the two terminal stages carry an honest probability. The rest are a ladder, not a forecast.
- Seven workflows, one per stage, each tested end to end with every email verified in a real inbox
- Entry covered by a form trigger and a booking trigger together, because a stage-change trigger never fires for the first stage
- Branch logic tested against pipeline stage rather than opportunity status, so it stops chasing people who already moved on
- Internal alerts routed to a user rather than a typed address, which is what keeps junk contacts out of the database
What it proves: I build pipelines that survive contact with real leads, and I test the delivery rather than trusting the execution log.
Live · HighLevel API v2
One printed QR code that keeps working after the event ends
A prospect scans a code at a booth, fills a short form, and lands in HighLevel already tagged to the event they were standing at. No app, no manual list, no typing names in afterwards.
- Live at
go.workwidkirk.com, with the original single-tenant version still serving atqr.workwidkirk.com - Multi-tenant: a page per handle, each with its own HighLevel credentials, logo, photo, and colours
- Contacts created and auto-tagged
event-<slug>through HighLevel's API v2, authenticated with a Private Integration Token - Six scan-page templates, and 959 tests green
What it proves: I work HighLevel from both sides, inside the builder and against the API when the builder cannot do the job.
Blueprint, not a client build
Three mapped pipelines for a dental practice
New patient, recall, and treatment acceptance. Stage definitions, entry and exit conditions, and the workflow that has to sit behind each transition, written so the build can be executed from the document without a second discovery call.
- Covers the awkward stages most maps skip: waiting on a decision, follow-up needed, declined for now
- Each stage carries its trigger, its exit condition, and the message that fires on the way out
Framed honestly: this is design work I did on spec, not a live client account. It is here because the mapping is the part most builds get wrong.
FastAPI · PostgreSQL · deployed
An Amazon PPC web application, built because the manual version cost hours
A multi-user application holding the tools I use to run Amazon ad accounts, all behind one login.
- Bid Optimizer, Placement Optimizer, Bid Reversion, Keyword Relevancy Checker, PDP Info Grabber, and a search-term analyser
- FastAPI backend, PostgreSQL, JWT auth, deployed and in daily use
- Each tool takes the reports Amazon actually exports and returns an upload-ready file, so nothing is retyped
What it proves: when a build needs to leave HighLevel for a custom tool, a real database, or an integration, I can take it there.
03 / What I do
01
02
03
04
05
Pick one, or have the whole thing built.
HighLevel CRM build
Sub-account architecture from scratch: pipelines, stages, custom fields, tags, and a naming convention that still makes sense a year later.
Workflow automation
The follow-up, the internal alerts, the stage movements, the reminders. Built to fire correctly, then tested against a real inbox before you ever see it.
Forms, funnels, landing pages
Hosted in HighLevel or built in code and wired back to it. Either way the lead arrives in the pipeline tagged and attributed.
AI-assisted web builds
Sites and internal tools built in code rather than dragged together in a builder, for when the builder ceiling is the thing in your way.
Audit and repair
An existing account that runs but does not work. I find the workflows that log as executed and deliver nothing, and fix them.
04 / How it goes
01 — Call
02 — Map
03 — Build and test
04 — Handoff
Four steps. You are needed for two of them.
Fifteen minutes on what breaks today
You leave with the shape of the build and a price, not a proposal to be sent later.
The document before the build
I write the pipeline, the stages, and every workflow as a document first. You approve the map. Changes are cheap here and expensive later.
Real leads through the real system
Built in your sub-account and run with real emails, real inboxes, real stage moves. Nothing is called done because a log said delivered.
Documented enough to leave alone
A one-page document, plus notes inside the workflows themselves, so whoever inherits it can read what each step does without calling me.
05 / Where this comes from
Years of running systems that break in public.
Amazon advertising, at scale
I managed $11.7M in ad spend across four accounts, returning $30.6M in sales at a 38.4% blended ACoS across 613,674 orders. Monthly budgets peaked past $300k. Accounts inherited, restructured, and made to hold, including two regulated categories where a mistake is not only expensive.
Tier 2 technical support for Comcast Xfinity
Tier 2. I fixed live services on the phone, took the escalations that came off other reps’ queues, and carried an upsell target on the same calls. Years of being the person a customer reached after the system had already failed them, which is a fast education in what a broken process costs at the other end.
Why it matters here
Ad accounts and support queues punish the same thing: a process that only works while someone is watching it. Everything I build in HighLevel is built for the day nobody is.
$11.7MAd spend managed
$30.6MSales returned
38.4%Blended ACoS
613,674Orders
- HighLevel Certified Admin
- Certified Amazon PPC Specialist
06 / What a build includes
What you get, and what it takes.
Every build ships with
- A written pipeline and workflow map, approved before anything is built
- The build itself in your own sub-account, which you own outright
- End-to-end testing with real contacts and verified email delivery
- A one-page handoff document, plus notes inside the workflows
- Two weeks of fixes after handoff, at no charge
Timeline
A single pipeline with its workflows usually lands within a week. A full account build runs two to three.
Billing
Builds start at $800, as a one-time fee invoiced on completion. A monthly retainer only if you want me on call afterwards.
Ownership
The sub-account is yours. Nothing is locked to me, and the handoff exists so you can stop paying me without losing the system.
07 / Before you ask
Six things people ask before they book.
Do I need to already be on HighLevel?
No. If you are on it, I build inside your sub-account. If you are not, part of the first call is working out whether it is the right tool for what you are doing. Sometimes it is not, and I will say so.
Can my team run it after you leave?
That is what the handoff is for. Every workflow carries notes explaining what each step does, and you get a one-page document covering the whole system. If your team needs a developer to change a follow-up email, I built it wrong.
What if I only need one thing fixed?
Then that is what you pay for. A broken workflow does not require a retainer to look at.
How do you charge?
Builds start at $800, as a one-time fee invoiced on completion. Where it lands above that depends on how many pipelines and workflows the build covers, and you get the number on the call rather than in a proposal afterwards. Any retainer is optional and priced separately.
Where are you, and does that matter?
Davao, Philippines. I work US hours and overlap most European schedules. Everything in the work section was delivered remotely.
Do you have client testimonials?
Not for HighLevel work yet. This is a newer part of what I do, and I would rather show you the builds than borrow someone else's words. Everything in the work section is mine, and I can walk you through any of it live on the call.
08 / Start here
Tell me what is breaking.
Short and specific beats long and vague. I reply within one business day.
Booking costs you fifteen minutes and gets you the build plan either way.
Prefer email? kirkjabeduremdes26@gmail.com
The booking form goes here.
The GoHighLevel form is being wired to this page. Until it is live, email works just as well and reaches the same inbox.
Email me instead