
The HighLevel build you can't afford to get wrong.
I'm Wil Kirwan. I build the systems behind creator launches and franchise rollouts. I also take on the HighLevel problems established businesses have spent too long working around.
From Software to HighLevel
Wil Kirwan
Founder of Times 20 Consulting
I've worn a number of hats in my career, working in everything from pro sports to insurance to contenr creation. With 15 years of experience in software development and product management in startups, I decided to take a break and start a woodworking business. Because of that, I ended up meeting John Malecki.
Shortly after, I started helping John with Discord automations, then ClickFunnels. When he moved to HighLevel, he asked me to figure out the implementation. A few projects grew into a retainer. I still approach a HighLevel build the way I approached a product release. I want to see how it behaves when a real customer uses it.

Who We Work With
Where the build earns its keep
A franchise opening, a creator launch, and a business stitching together five tools have different stakes. The build starts with what you're on the hook to deliver.
Franchisors
If every new territory means your staff has to set up calendars, configure service areas, and field tech calls, that work piles up with every sale. Franchise Force Multiplier gives each operator a configured HighLevel account and training. My team owns the shared setup, territory rollouts, and ongoing support.
Explore Franchise Force MultiplierContent Creators
When your audience is ready to buy or sign up, the systems behind the launch have to carry it. I build the path from comments and DMs to subscriber capture and email delivery. For paid products, I connect checkout to the right onboarding and access so your team can focus on the launch.
See a Creator BuildBusiness Owners
If the business is growing and your people still re-enter the same information or rescue the same handoff, I trace the work across the tools and rebuild the part that keeps costing you time. You'll see what can move into HighLevel, what needs to stay connected, and how the team can run it from there.
Start With a BuildThe Build Standard
What “Best in the World” looks like in a build
A workflow can fire and still send a customer the wrong link. I check what happens between the systems and what the person at the other end can actually do.
Make the launch hold up
For Entrepenicky, I built what happens after a viewer says yes. I handled inbox setup and warmup, hooked signup into HighLevel, and built the email sequence that takes a new subscriber from their first email to the weekly send.
Check what the customer receives
I check the templates for estimates, invoices, receipts, and portal access. I set up a dedicated payments sending domain where it makes sense, then trigger the messages and open the actual links from the customer's side.
Decide what the agent can own
I define what the agent can answer, when it can book, and when a person has to take over. I test it with incomplete requests and awkward questions before it talks to real customers.
Own the reply and the handoff
I trace inquiries from the channel where they came in. Then I build the routing, the reply, and the coverage when the usual person is out. I check what the customer sees and what the team receives.
Make the systems agree
I decide where customer, deal, and location data belongs. Then I wire the form, pipeline, booking, and billing together so information reaches the right record without someone copying it over.
Open the account and trace the problem
I follow the workflow, check what it depends on, and review what connected tools can access. You can see what I'd keep, where the build fails, and what I'd take on first.
How We Work
We agree on what finished means.
Agree on what has to work
We start with what a customer or operator needs to do and where today's setup gets in the way. Before I quote, we agree on the scope and how we'll know the build is ready.
Build it. Run the real test.
I design the account around those decisions and run the agreed scenarios from both sides. I check what the customer gets, what the team sees, and what happens when a step goes wrong.
Walk the team through it live
At handoff, I run through the build with your team and leave Loom recordings for the jobs they'll own. We agree up front on support and who handles changes after launch.
Customer Case Study: Roamin Restrooms
Take bookings while the owner is out on a delivery.
I worked with the founders from day one. We designed the system around an operator who could be out delivering a trailer when the next inquiry came in. Here's what I built into HighLevel so taking that request wouldn't require a staffed office.
- Collect the event details the operator needs
- Route to an online reservation or confirmation call
- Follow up about extras like Starlink or a generator
From inquiry to rental
Inquiry: A customer asks for a trailer. The system collects the event date and venue.
Routing: HighLevel directs the customer to book online or schedule a confirmation call.
Booking: The customer completes the reservation or talks through the job with the operator.
Follow-up: After booking, the system can send an offer for extras such as Starlink or a generator.
Bring me the build you need to get right.
Tell me what the system has to do, where it gets stuck today, and what depends on getting it right. We'll use the call to see whether the work is a fit.