Seven funnels, ready to run.
A starter for every funnel high-ticket teams run, on Close or GoHighLevel. Pick one below to see it built.
01 of 07
VSL to call
A video sells the call, an application qualifies the lead and a closer takes it from there.
- VSL page612
- Application214
- Booked call96
- Confirmed81
- Live call71
- Close14
Sample workspace, 1 to 26 September. A stage PYLO does not count says so rather than showing a zero.
Building it in PYLO
5 steps from signed to counted.
- 01
Pick the starter
Choose the VSL to call starter on Close or GoHighLevel. It builds the pipeline, statuses, UTM fields and flows for you.
- 02
Send one connect link
The client connects the CRM, Calendly, Typeform and the processor from one link, and each tile shows whether records are arriving.
- 03
Run it in shadow
PYLO runs beside the current setup and writes nothing. Its figures sit next to the old ones, with a reason for every difference.
- 04
Set the flows live
When the runs look right, each flow writes for real, from the CRM status to the setter alert.
- 05
Read every stage
Every stage from opt-in to close, with the rate between each, so the stage losing people is plain to see.
- You connect
- Close or GoHighLevel, Calendly, your payment processor, your Meta ad account and your domain. Typeform, or PYLO's own forms, and PYLO's booking pages and landing pages if you would rather not run Calendly and a page builder.
- PYLO counts
- Opt-ins, applications, qualified applications, bookings, confirmations, live calls and closes, with cash verified by the processor.
02 of 07
Webinar
One live session sells the call, with registrants checked against the webinar host so the show rate is real.
- Registration412
- RemindersNot counted here
- Attendance168
- Booked call71
- Close12
Sample workspace, 1 to 26 September. A stage PYLO does not count says so rather than showing a zero.
Building it in PYLO
5 steps from signed to counted.
- 01
Pick the starter
Choose the webinar starter on Close or GoHighLevel. It builds the pipeline, statuses, UTM fields and flows for you.
- 02
Send one connect link
The client connects the CRM, Calendly and WebinarJam or Zoom from one link, and each tile shows whether records are arriving.
- 03
Run it in shadow
PYLO runs beside the current setup and writes nothing. Its figures sit next to the old ones, with a reason for every difference.
- 04
Score the run the night it airs
Who registered, who turned up and who was still there when the offer went up, for every run.
- 05
Read the chain to the close
Registrants through to closes, every stage counted and every rate shown with both of its numbers.
- You connect
- Close or GoHighLevel, Calendly, your payment processor, your Meta ad account and your domain. WebinarJam or Zoom for registrations and attendance.
- PYLO counts
- Registrants, who attended and how long they stayed, who was still there at the pitch and how many booked.
03 of 07
DM setter
Content starts the conversation and a setter books the call from the inbox.
- ContentNot counted here
- DM1,728
- Setter540
- Booked call108
- Close16
Sample workspace, 1 to 26 September. A stage PYLO does not count says so rather than showing a zero.
Building it in PYLO
5 steps from signed to counted.
- 01
Pick the starter
Choose the DM setter starter on Close or GoHighLevel. It builds the pipeline, statuses, UTM fields and flows for you.
- 02
Send one connect link
The client connects the CRM, Calendly and the processor from one link, and each tile shows whether records are arriving.
- 03
Run it in shadow
PYLO runs beside the current setup and writes nothing. Its figures sit next to the old ones, with a reason for every difference.
- 04
Setters report from their phone
Today's calls, the post-call form and a two-minute EOD on their phone, with DM closes logged like any other.
- 05
Read the DM chain
Conversations to bookings from the setters' reports, then live calls and closes from the calendar and the CRM.
- You connect
- Close or GoHighLevel, Calendly, your payment processor, your Meta ad account and your domain. Setter access to the Instagram inbox through Meta Business Suite, never the password.
- PYLO counts
- Conversations, setter end-of-day reports, bookings, DM closes and setter commission.
04 of 07
Free community
A free Skool or Circle community warms people up until they ask for a call.
- JoinNot counted here
- NurtureNot counted here
- Booked call44
- Close8
Sample workspace, 1 to 26 September. A stage PYLO does not count says so rather than showing a zero.
Building it in PYLO
5 steps from signed to counted.
- 01
Pick the starter
Choose the free community starter on Close or GoHighLevel. It builds the pipeline, statuses, UTM fields and flows for you.
- 02
Send one connect link
The client connects the CRM, Calendly and the community from one link, and each tile shows whether records are arriving.
- 03
Run it in shadow
PYLO runs beside the current setup and writes nothing. Its figures sit next to the old ones, with a reason for every difference.
- 04
Follow every buyer after the sale
Every buyer becomes a student the day they pay, and the ones at risk are flagged before the refund window closes.
- 05
Read the community chain
Applications through to closes on the community lead source, with anything not recorded shown with its reason.
- You connect
- Close or GoHighLevel, Calendly, your payment processor, your Meta ad account and your domain. Admin access to the Skool or Circle community.
- PYLO counts
- Joins, bookings and closes, and on Circle the members who have gone quiet.
05 of 07
Outbound
SDRs power dial a saved view or work a cold email list, and book calls for the closers.
- Dial or cold email6,694
- Conversation875
- Booked callNot counted here
- CloseNot counted here
Sample workspace, 1 to 26 September. A stage PYLO does not count says so rather than showing a zero.
Building it in PYLO
5 steps from signed to counted.
- 01
Pick the starter
Choose the outbound starter on Close or GoHighLevel. It builds the pipeline, statuses, UTM fields and flows for you.
- 02
Send one connect link
The client connects the CRM, Calendly and the dialer from one link, and each tile shows whether records are arriving.
- 03
Run it in shadow
PYLO runs beside the current setup and writes nothing. Its figures sit next to the old ones, with a reason for every difference.
- 04
See who is on the phones
Dials, connects and talk time for every rep, from PYLO's dialer or read from Aircall or JustCall, with speed to lead alerts.
- 05
Dial when leads pick up
Pick-up rate by hour and by number, so the team calls when leads answer and burned numbers are caught early.
- You connect
- Close or GoHighLevel, Calendly, your payment processor and your domain. PYLO's own dialer for the dials, or Aircall or JustCall if you already use them.
- PYLO counts
- Dials against the day's pace, conversations, SDR end-of-day reports and bookings.
06 of 07
Challenge
A multi-day challenge with a session each day, ending in an offer to book a call.
- RegistrationNot counted here
- Day 1Not counted here
- Final dayNot counted here
- Booked callNot counted here
- CloseNot counted here
Sample workspace, 1 to 26 September. A stage PYLO does not count says so rather than showing a zero.
Building it in PYLO
4 steps from signed to counted.
- 01
Pick the starter
Choose the challenge starter on Close or GoHighLevel. It builds the pipeline, statuses, UTM fields and flows for you.
- 02
Send one connect link
The client connects the CRM, Calendly and WebinarJam from one link, and each tile shows whether records are arriving.
- 03
Run it in shadow
PYLO runs beside the current setup and writes nothing. Its figures sit next to the old ones, with a reason for every difference.
- 04
Count every session
Each day's session gets its own figures, so the day that loses people is plain to see.
- You connect
- Close or GoHighLevel, Calendly, your payment processor, your Meta ad account and your domain. WebinarJam for the sessions, if you host them there.
- PYLO counts
- Registrants, attendance at each session, bookings and closes.
07 of 07
Affiliate signup
A creator gives a course away, reps follow up each opt-in, and the creator is paid for every signup that stays past the window.
- Opt-in1,341
- Dial or DMNot counted here
- Signup through your link159
- Kept past the window62
Sample workspace, 1 to 26 September. A stage PYLO does not count says so rather than showing a zero.
Building it in PYLO
4 steps from signed to counted.
- 01
Pick the starter
Choose the affiliate signup starter on Close or GoHighLevel. It builds the pipeline, statuses, UTM fields and flows for you.
- 02
Send one connect link
The client connects the CRM, Discord and the ad account, with the program's tokens through a key drop from one link, and each tile shows whether records are arriving.
- 03
Set the program once
Set the program, its window and its payout. A signup counts as kept only once the program's records say so.
- 04
Every creator side by side
Opt-ins, kept signups, commission and ad spend per signup for every creator.
- You connect
- Close or GoHighLevel, Discord, your landing page, your Meta ad account, the affiliate program's API token and the sales portal's token, both sent through a key drop.
- PYLO counts
- Opt-ins per ad, signups the program kept, pending and reversed, commission pending and earned, and ad spend per signup.
Run your funnel in PYLO.
Pick the starter, send the link and read every stage by tomorrow.
Setting one up yourself? Read the docs