The problem
FocusLadies is a leadership accelerator for high capacity women, with a Standard and a Premium membership. Each woman applies first. Kimberly reads the application, and the right women book a call with her before they join.
Before this project, that path was manual. The site was a copy of an older Lovable project and still showed copy for a different audience. The application was a single form, so a woman who stopped halfway was lost. FG Funnels had no FocusLadies tags, pipeline or workflows.
What Kimberly asked for
- No manual tasks: The site and FG Funnels must work together, from the first click to the member welcome.
- Keep every lead: Change the form into a survey, with only the basic details on page 1.
- Automatic follow up: Lead follow up, application vetting, confirmations and reminders.
- Copy, then adapt: Start from the workflow models that already existed in her account, and do not change the originals.
What I did
I started with a journey map: each step a woman takes, from the first visit to the member welcome. Kimberly answered the open questions on Slack, and I built from her answers.

The 7 automations
- Finish reminders: She fills page 1 and stops. After 1 hour she gets a reminder, and a second one 1 day later.
- Application received and vetting: Confirmation to her, all her answers to Kimberly, card at Application Received. After 2 hours the rule decides.
- Qualified: An invitation with the calendar link. If she does not book in 2 days, a short nudge.
- Not a fit: A kind note that invites her to FocusLadies on Substack.
- Call booked: A confirmation, then reminders 1 day and 1 hour before the call.
- No show or cancel: The reminders stop, the card moves to No Show, and she gets a link to book a new time.
- Member welcome: The card moves to Won: Member, she gets the welcome email and all sales follow up stops.

How it was done
Look before building
I read the FG Funnels account and the Lovable project before I changed anything. I listed the workflows, tags, fields, pipelines, forms and calendars that existed. I also listed the pages that still showed the older copy. This list became the cleanup plan, and Kimberly approved each removal.
The survey and the answer fields
Each question has its own custom field, so the answers are easy to read on the contact record. The survey creates the contact on a partial submission and adds a source value on page 1. That source tells the reminder workflow which new contacts came from the application.
Workflows that stop each other
A funnel can send a wrong email when two flows run at the same time. For this reason, each workflow removes the contact from the flows that no longer apply. A submit stops the finish reminders. A booking stops the nudge to book. A member welcome stops all sales follow up. A second application clears the old status tags first, so the rule vets it again.
The vetting rule waits 2 hours and checks if a decision exists. If Kimberly already moved the card, the rule does nothing. The emails go out from the stage change, so her manual decision and the rule use the same path.
The Lovable site, changed through GitHub
I connected the Lovable project to a GitHub repository. I made the page changes in code and pushed them, and Lovable synced and published them. This did not use her Lovable credits.

App connection without a sync
The brief asked to connect the two systems. The Lovable site has no database and no member accounts, so a webhook sync had nothing to keep in step. FG Funnels holds all contacts. The site embeds the survey and the calendar, and every email links back to the site. No manual step is needed, and there is one less thing that can break.
Testing and handover
I tested on the live account with three test applicants, one for each path. Each test used my own email address. I deleted the test contacts and their cards after the tests.

Every email sent as a test
The site checked on a phone
At handover, Kimberly got a project report, a test report and a short guide. The guide shows where each part is, how to change an email, how to change her call hours and how to decide on an application herself.
A next step for a Lovable site
The FocusLadies site is built in Lovable. A Lovable site or app can also become an iOS and Android app with the same code base, as I did for SoccerTrak. A Publish in Lovable then updates the website and both apps.
Where it stands
What I can and cannot claim
The funnel is live on focusladies.com, and the emails go out today. The 5 text reminders are built, but they send only after her text registration (A2P 10DLC) is approved. Until then, only the emails go out.
I did not wait for some steps in the tests. The second finish reminder comes 23 hours after the first one. The call reminders depend on a call date in the future. I checked these steps in the workflows, but I did not receive them. I do not have application or member numbers to publish yet, so this page shows only what I built and tested.
What This Project Does Well
Technologies Used
FG Funnels (HighLevel): surveys, custom fields, tags, pipelines, workflows, email templates, calendars, Stripe memberships. Lovable (React, Vite, Tailwind CSS) synced through GitHub, static prerender of the public pages, SiteGround DNS.
Ask AI for a summary of FocusLadies (Genius Life Group) by Frenchy Digital.
Open your assistant of choice with the question already written.
- Ask Claude for a summary of FocusLadies (Genius Life Group) by Frenchy Digital
- Ask ChatGPT for a summary of FocusLadies (Genius Life Group) by Frenchy Digital
- Ask Perplexity for a summary of FocusLadies (Genius Life Group) by Frenchy Digital
- Ask Gemini for a summary of FocusLadies (Genius Life Group) by Frenchy Digital
Ready to Build Something Similar?
Let's discuss how we can help transform your business with a custom digital solution.
