GHL CRM & Automation Strategy
A Proposal from Cris Vinson / OZ Tech Development Corp
Prepared for: WonderLab, Rachel Wingman & Clement  |  Date: April 2026  |  Prepared by: Cris Vinson, OZ Tech Development Corp
We're the Engineering Team That Turns Your Vision Into Working Technology
Unlimited custom software, Gohighlevel Workflows, and AI projects. One flat monthly fee. Full code ownership. Your first project live in 4 weeks — guaranteed.
You bring the vision. We bring the engineering.
Executive Summary
WonderLab has built something worth protecting. Two locations in Sydney. A proprietary wellness framework. An active event series that fills rooms and generates paid registrations. A growing B2B presence addressing psychosocial safety, one of the most pressing compliance obligations for Australian employers right now. You have GHL running in the background, handling funnels, ticket sales, forms, newsletters, and gift cards.
What comes next is the layer underneath all of it.
What the Infrastructure Looks Like
Imagine a corporate buyer discovering WonderLab after an event. They visit your site, fill out a form, and within minutes receive a tailored sequence that speaks directly to their leadership team's needs. Not a generic welcome email. A message that reflects exactly where they are in their decision.
Imagine your front desk team seeing only what they need to see. Your sales team working a pipeline that tells them exactly what to do next. Every client journey, whether they came in for an INDIBA session or a Corporate Reset Day, tracked, automated, and feeding data you can use.

That infrastructure is what this engagement builds.
Engagement at a Glance
Investment Range
USD 3,000 to USD 10,000 + retainer
Timeline
1 week (Blueprint only) to 4 weeks (full build, assets ready)
Next Step
Confirm your preferred option and schedule the Foundations Session
See Section 9 for the full pricing breakdown.
Understanding Your Context
WonderLab is operating across two distinct client tracks.
B2C Track
Individuals seeking clinical skin treatments, body recovery, INDIBA therapy, AI skin analysis, and spa services.
B2B Track
Corporate teams and leadership groups seeking structured wellness programs, psychosocial safety support, and team reset experiences.
Both tracks are live. Both are generating revenue. And both are being managed across a team where not everyone has deep technical experience. That is exactly the right environment for a well-built CRM to do its heaviest work.
Your Event Program Is a Particular Strength
The WonderGrowth Power Lunch series runs with complete offer stacks: clear pricing, specific benefits, functional registration and payment capture.
The AI Burnout Conversation
The Mother Load
The Skin Deep Cellular Health Workshop
These events demonstrate that WonderLab can articulate a precise value proposition when the format demands it. That same precision is what a GHL CRM architecture carries into every other part of the business.
The 7 Wonders Framework
The 7 Wonders Wellness Experience is already defined. What this engagement does is take that framework and give it a customer journey for each wonder. Messaging. Touchpoints. The path a client travels from their first interaction with each wonder to a completed outcome.
That map becomes the operating system of the CRM.
You already have a GHL account in active use. The infrastructure exists. This engagement adds the intelligence layer.
Who We Are — Cris Vinson
GoHighLevel Gold SaaS Award
One of the most competitive recognitions in the GHL ecosystem.
1000+ workflows
In worked on in the span of 10 years using tools like Gohighlevel, Clickfunnels, Zapier, n8n, etc.
Cornell University Certificate
Digital Business Leadership certificate from Cornell University.
Cris Vinson is a GHL specialist with over ten years of hands-on experience inside the platform. He has managed more than a thousand GHL sub-accounts.
How Cris Works
Cris operates as a solo strategic consultant. His "team" is a combination of AI tools and OZ Tech Development Corp, a lean engineering unit engaged for technical builds, custom integrations, and software development beyond GHL's native capabilities.

This structure means you work directly with the strategist at every stage. There is no junior layer between you and the person who designed the plan.
OZ Tech Development Corp
OZ Tech Development Corp handles the engineering layer:
n8n Automation Bridges
Connecting GHL to external platforms and data sources.
Custom API Integrations
Linking your existing tools into a unified data flow.
Client Portal Development
Custom-built portals for client and team access.
Software Development Beyond GHL
Any requirements that sit outside GHL's native capabilities.
The engineering team operates on a task-based model with two active tasks running simultaneously at any time. More at unwiz.ai.
Approach & Philosophy
The Blueprint comes before the build. Every pipeline, automation, and workflow in this engagement is designed on paper first. Nothing is built until the architecture is reviewed and approved. This is not a common practice. It is the only way a GHL build of this complexity delivers what it promises.
User Stories Written in the Workshop
User stories are written in the workshop, not after it. Every user who touches WonderLab gets mapped: internal team members by role, external clients by segment.
Each story defines:
  • Who they are
  • How they enter the system
  • What they experience at every touchpoint
  • What a successful outcome looks like

The pipelines are built from these stories. Not the other way around.
Low-IT Environments Need High-Structure Systems
Access restrictions are not an afterthought. Every role (admin, sales, receptionist) is scoped from Day 1. Staff see only what they need to see.
Admin
Access everything
Sales
Access pipelines and messages
Receptionist
Access conversations, opportunities, and calendar
This is how a premium wellness experience stays premium at every touchpoint, including the internal ones.
The Build Starts Only When Conditions Are Met
Two things gate the build: a complete tech stack handover and documented assets. If content, credentials, or integrations are not in place, the timeline does not begin.
This is not a restriction. It is a guarantee that what gets built actually works.
Value Is Tracked, Not Assumed
Every engagement that moves through WonderLab's pipelines has a measurable value attached. GHL's opportunity value fields are configured from the start, not added later. This means pipeline performance, revenue forecasting, and client lifetime value are live data from day one.
Combined with API connections to the tools already in WonderLab's stack — Google Sheets, calendar systems, booking platforms, and AI voice infrastructure — the CRM reports on what is actually happening across every touchpoint, not just what GHL sees in isolation.
Two Active Tasks, Always in Motion
For retainer engagements, the team operates on a concurrent task model. Work is never waiting in a queue.
Concurrent Task Model
Two active tasks running simultaneously at all times. Work is never waiting in a queue.
Communication Channels
Communication runs through your preferred channel: Slack, Discord, or a dedicated client portal.
The Solution — What This Engagement Builds
WonderLab's GHL account currently handles transactions: ticket sales, form captures, funnel entries, newsletter delivery. This engagement builds the system that handles relationships.
The exact scope of automations, workflows, and integrations is finalized during the Foundations Sessions. What is defined upfront is the architecture. What gets built is determined by what the workshop reveals.
This is not vagueness. It is precision. Building before the workshop produces the wrong thing, built fast.
Phase 1 — Foundations & Blueprint
The Foundations Sessions are working workshops. Your team is in the room. We map every user: internal roles and external client segments. We define the messaging and customer journey for each of the 7 Wonders. We document what data moves, when, to whom, and through which channel.
The output is the Blueprint document. It contains:
  • The user story library
  • Pipeline architecture
  • Workflow maps
  • Access matrix
  • AI agent scope
  • Master template structure
This document is what Clement's team builds from in Option 1. It is what OZ Tech builds from in Options 2 and 3.
Phase 2 — Build: B2C Track
Pipelines are built across two primary tracks. The B2C track covers:
1
Individual Client Journeys
Mapped per service cluster, aligned to the 7 Wonders.
2
Smart Lists for Segmentation
By service history, lifetime value, and stage.
3
Automations Scoped from the Blueprint
Nothing is assumed. Scope is defined in the workshop.
Phase 2 — Build: B2B Track
The B2B track covers corporate leads from first inquiry through proposal, engagement, and renewal.
The Workplace Wellbeing Scorecard serves as the B2B entry point. Longer decision cycles are handled with defined follow-up cadence and handoff logic. Additional pipelines for events and membership are included. Automation scope, sequence count, and logic are defined in the workshop. Nothing is assumed.
AI Receptionist
GoHighLevel's AI receptionist is configured for appointment scheduling. The agent:
01
Handles Inbound Inquiries
Responds to incoming appointment and service requests.
02
Presents Availability
Shows real-time calendar availability to the client.
03
Confirms Bookings
Completes the booking and sends confirmation.
04
Escalates to Human
Hands off to a team member when required.

Token usage monitoring is built in from day one. Cost is not a post-launch surprise.
Integrations
n8n serves as the integration layer for anything outside GHL's native capabilities. This includes:
Google Sheets
Data import pipelines and live reporting connections.
Calendar & Booking Platforms
Connections to existing booking infrastructure.
AI Voice Infrastructure
Already in use — connected and unified.
Any Other API Connections
Identified during the Foundations Sessions.
Existing client data is migrated via CSV import with field mapping aligned to the new contact record structure.
Access & Training
Every role is configured before the build goes live.
Training is delivered per role, practical and specific, in your preferred channel.
User Stories & Journey Maps
Every pipeline, automation, and access role is built around a specific user. Before a single workflow is configured, every person who touches WonderLab gets mapped: who they are, how they enter the system, what they experience at each stage, and what a successful outcome looks like for them.
This mapping happens inside the Foundations Sessions. It is not a document produced after the workshop. It is produced during it, with your team in the room.
What Gets Defined for Each User
For every user type identified, the workshop produces:
Who They Are
Their role, relationship to WonderLab, and context.
How They Enter
Source, trigger, or action that brings them into the system.
Their Journey
Every stage they move through, in sequence.
Touchpoints
What communication they receive at each stage, through which channel.
Segmentation
What tags, lists, or fields categorize them for targeting.
Exit Conditions
What marks their journey as complete, converted, or lapsed.
User Categories to Be Mapped
The Foundations Sessions will cover three categories of users. The specific user types within each category are confirmed during the workshop.
Internal Team Members
The roles inside WonderLab that operate within GHL. Each role is mapped to the access level they need and the actions they take inside the system. Examples: front desk staff, sales team members, account administrators.
B2C Clients
Individual clients across WonderLab's service lines. Each segment has a distinct entry point, journey length, and conversion goal. Examples: first-time visitors, returning clients, event attendees, and members.
B2B Clients
Corporate buyers moving through a longer decision cycle. Each segment has distinct qualification criteria, communication cadence, and renewal logic. Examples: new corporate inquiries, active program participants, and renewal accounts.
User Story Format
Each completed user story follows this structure:
The full user story library is delivered as part of the Blueprint document at the end of the Foundations phase.
Deliverables — Option 1: Blueprint Only
1 Week
Strategy & Blueprint
  • Foundations Sessions (1–3 sessions, recorded)
  • User story library — all user types mapped with journeys, touchpoints, and segmentation tags
  • 7 Wonders messaging and customer journey map — one per wonder
  • Pipeline architecture document — stages, triggers, logic, access per role
  • Master Blueprint document — workflows, access matrix, AI agent scope, master template structure
  • Role-by-role GHL access guide
  • Messaging content checklist for email and SMS assets
  • Blueprint walkthrough session with Clement

Clement's team builds from the Blueprint. One revision round included within 60 days. 14-day support via preferred channel.
Deliverables — Options 2 & 3: Full Build
4 Weeks
Week-by-Week Overview
1
Week 1
Foundations & Blueprint — everything in Option 1, approved and build-ready by end of week.
2
Week 2
GHL Build — sub-account configuration, pipeline builds, templates, access roles.
3
Week 3
Automations & Integrations — AI receptionist, n8n bridge, data migration, calendar setup.
4
Week 4
Test, Train & Launch — end-to-end testing, staff training, QA, dashboard setup, handoff.
Week 2 Deliverables — GHL Build
  • GHL sub-account configuration
  • B2C and B2B pipeline builds with stage logic and smart lists
  • Events and membership pipelines
  • Lead segmentation, tags, custom fields
  • User roles and access restrictions locked
Week 3 Deliverables — Automations & Integrations
  • Automation builds (scope defined in Foundations Sessions)
  • Email / SMS / WhatsApp template library (based on client-supplied drafts)
  • Calendar setup — shared, per-staff, with booking pages
  • AI receptionist — appointment scheduling flow with escalation paths
  • Token usage monitoring configuration
  • n8n integration bridge — Google Sheets, data import, API connections
  • Data migration — existing client records via CSV
  • Social media account integrations
Week 4 Deliverables — Test, Train & Launch
  • End-to-end testing per user story
  • Staff training by role (receptionist, sales, admin)
  • AI agent QA
  • Dashboard setup — pipeline performance, LTV, event attendance, case study data
  • Handoff documentation
  • Book launch funnel (delivered within this timeline)

The 4-week timeline applies when all assets, credentials, and tech stack access are delivered at signing. If documentation is incomplete at signing, Foundations Sessions are used to produce it and the timeline adjusts accordingly.
Investment & Pricing — Overview
Three engagement structures are available. All begin with the same Blueprint foundation. The difference is who builds from it, and for how long.
Option 1
Strategy & Blueprint
USD 3,000
1 week · Your team builds
Option 2
Blueprint & Build
USD 10,000
4 weeks · OZ Tech builds
Option 3
Blueprint, Build & Beyond
USD 3,500/mo
Founding Member rate · 2-month minimum
Pricing Comparison Table
Option 1 — Strategy & Blueprint
USD 3,000
or USD 1,800 if pre-documented
You receive the complete Blueprint. Your team, led by Clement, builds from it inside GHL. Cris delivers the strategy, the architecture, the 7 Wonders messaging maps, the user story library, and a walkthrough session. Delivered in one week. One revision round included within 60 days. Fourteen days of support via your preferred channel.
This option is right when your internal team has GHL capability and you need a precise, complete plan to execute from.
Option 2 — Blueprint & Build
USD 10,000 · One-Time
Everything in Option 1, plus OZ Tech builds it. Full GHL build. All pipelines. All automations scoped from the workshop. AI receptionist. n8n integrations. Book launch funnel. The full unwiz.ai engineering stack. Thirty days of post-launch support via your preferred channel. Two revision rounds after the build. Completed in 4 weeks when all assets are ready at signing.
What the unwiz.ai stack delivers at this tier:
  • Unlimited custom software and AI projects scoped during engagement
  • Dedicated Product Manager and technical team throughout the build
  • Bi-weekly sprint cycles with live demos
  • First project live in 4 weeks (guaranteed)
  • Full code ownership — repository and documentation handed to you
  • Plain-English communication at every stage, no technical translation required
Option 3 — Blueprint, Build & Beyond
USD 3,500/month
Founding Member Rate
2-Month Minimum
Everything in Option 2. The blueprint fee is waived at the 2-month minimum commitment. Two active tasks running simultaneously at all times. Unlimited task requests. Custom software development beyond GHL via n8n and the OZ Tech engineering stack. Communication via your preferred channel: Slack, Discord, or dedicated client portal.

This is the Founding Member rate. OZ Tech is accepting 5 Founding Members at USD 3,500/month — locked in at that rate permanently. After these 5 spots fill, the base rate moves to USD 4,500/month for all new clients. WonderLab has been offered one of these spots.
Founding Member Commitment
Rate Locked Forever
USD 3,500/month locked in forever — USD 12,000/year savings vs future rate.
Priority Onboarding
Start within 7 to 10 days of signing.
Direct Founder Access
Direct access to founders, including quarterly strategy sessions.
Founding Member Bonuses
All 7 Founding Member bonuses (valued at USD 17,494 in Year 1). Lifetime Founding Member status.
This option is right when the GHL build is the beginning, not the end. When custom integrations, ongoing automation expansion, and engineering support are part of a longer roadmap.
Why OZ Tech vs the Alternatives
There are other ways to build what WonderLab needs. Here is an honest comparison.
Add-Ons & Payment Terms
Add-Ons (Option 3)
Payment Terms
  • Option 1: 50% on signing · 50% on delivery
  • Option 2: 50% on signing · 50% on delivery
  • Option 3: Monthly billing from onboarding · auto-renewal · cancel anytime with 30-day notice · 2-month minimum · Blueprint fee waived
Build Condition
The build begins upon receipt of complete tech stack access and documented assets. If documentation is not ready at signing, the Foundations Sessions are used to produce it. This is factored into the timeline.
Timeline & Process — Option 1
1 Week
Client involvement: 4–6 hours
Condition: Service documentation and team availability confirmed before session
Timeline & Process — Option 2
4 Weeks
Assets Ready at Signing
Client involvement: 8–10 hours total
Condition: All assets, credentials, and tech stack access delivered at signing
Timeline & Process — Option 3
2-Month Minimum + Ongoing
Follows Option 2 timeline for the initial build. Retainer activates at onboarding. Engineering tasks submitted via preferred channel. Two tasks run simultaneously at all times. Scope expands as WonderLab's needs evolve.
What Gates the Timeline
Two things compress or extend the schedule.
Asset Readiness
Email templates, existing client data, GHL credentials, and service documentation all need to be in place before the build begins.
Team Availability for Review Checkpoints
Three client review moments exist in the timeline: Blueprint approval, mid-build check, and pre-launch QA. Each takes approximately two hours.
This Engagement Will Work If
Your team can attend and participate in the Foundations Sessions
Full tech stack access and credentials are provided before or at signing
Clement (or your internal team) is available for review checkpoints during the build
The 7 Wonders framework is clearly defined and your team can speak to each wonder
Decisions on scope, messaging, and user journeys can be made during the workshop, not after
You are building a long-term system, not a quick fix
This Engagement Will Not Work If
Asset Documentation
Asset documentation is scattered, unavailable, or still being created.
Decision-Maker Availability
Key decision-makers cannot commit time to the Foundations Sessions.
Strategy Replacement
The expectation is that the CRM will replace a strategy that does not yet exist.
GHL Access
GHL access and credentials are not ready at the start of the engagement.
Approval Complexity
Sign-off on scope and architecture requires multiple rounds of approval from stakeholders not present in the workshop.
Premature Results
The goal is to see results before the system is fully live.
Next Steps — Step 1
Step 1
Choose Your Option
Review the three engagement structures and confirm which path aligns with your current timeline and build capacity.
Option 1
Strategy & Blueprint — USD 3,000 · 1 week · Your team builds
Option 2
Blueprint & Build — USD 10,000 · 4 weeks · OZ Tech builds
Option 3
Blueprint, Build & Beyond — USD 3,500/mo · Founding Member · OZ Tech builds
Next Steps — Step 2
Step 2
Schedule the Foundations Session
Once an option is confirmed, we schedule the first Foundations Session. This session maps the 7 Wonders customer journeys, the user story library, and the full service architecture. It is the starting point for all three options.
Next Steps — Step 3
Step 3
Sign and Begin
Upon signing and receipt of the first payment, the Foundations Session is confirmed and the engagement begins.

This proposal is valid for 30 days from the date of issue.
Contact Cris Vinson
Cris Vinson OZ Tech Development Corp
  • Website: cvinson@unwiz.ai
  • Whatsapp: +639171152303
Appendix: Interactive investment comparison available at unwiz.ai
The Blueprint — What It Contains
The Blueprint document is the foundation of every engagement option. It is produced during the Foundations Sessions and reviewed before a single line of automation is written.
1
User Story Library
All user types mapped with journeys, touchpoints, and segmentation tags.
2
Pipeline Architecture
Stages, triggers, logic, and access per role.
3
Workflow Maps
Visual documentation of every automation flow.
4
Access Matrix
Role-by-role GHL access guide.
5
AI Agent Scope
Configuration parameters for the AI receptionist.
6
Master Template Structure
Email, SMS, and WhatsApp template framework.
The 7 Wonders — Customer Journey Per Wonder
The 7 Wonders Wellness Experience is already defined. This engagement gives each wonder its own customer journey: messaging, touchpoints, and the path a client travels from first interaction to completed outcome.
That map becomes the operating system of the CRM. One journey per wonder. Defined in the Foundations Sessions. Built into the pipelines.
GHL: From Transactions to Relationships
What GHL Does Now
  • Ticket sales
  • Form captures
  • Funnel entries
  • Newsletter delivery
  • Gift cards
What This Engagement Adds
  • Relationship management
  • Automated client journeys
  • Pipeline performance tracking
  • Revenue forecasting
  • Client lifetime value data
The Foundations Sessions — What Happens in the Room
The Foundations Sessions are working workshops. Your team is in the room. The output is not a summary of what was discussed. It is the actual architecture of the system.
01
Map Every User
Internal roles and external client segments — all mapped with entry points, journeys, and exit conditions.
02
Define 7 Wonders Messaging
Customer journey and messaging for each of the 7 Wonders.
03
Document Data Flows
What data moves, when, to whom, and through which channel.
04
Produce the Blueprint
The complete architecture document, ready for build.
B2B Entry Point — The Workplace Wellbeing Scorecard
The Workplace Wellbeing Scorecard is the defined B2B entry point. Corporate buyers moving through a longer decision cycle enter the pipeline here.
1
Scorecard Completion
Corporate buyer completes the Workplace Wellbeing Scorecard.
2
Qualification
Distinct qualification criteria applied. Follow-up cadence begins.
3
Proposal & Engagement
Tailored proposal delivered. Program engagement begins.
4
Renewal
Renewal logic triggers at defined intervals.
Cris Vinson — Credentials at a Glance
10+
Years in GHL
Hands-on experience inside the platform.
1K+
Sub-Accounts Managed
More than a thousand GHL sub-accounts managed.
1
Gold SaaS Award
Elite performance recognition.
5
Founding Member Spots
Available at USD 3,500/month — WonderLab has been offered one.
What WonderLab Gets — The Full Picture
Across all three options, the engagement delivers a system that handles relationships, not just transactions. Here is what that means in practice:
A Corporate Buyer Gets a Tailored Sequence
Not a generic welcome email. A message that reflects exactly where they are in their decision.
Your Front Desk Sees Only What They Need
Role-scoped access from Day 1. Premium experience at every internal touchpoint.
Your Sales Team Knows Exactly What to Do Next
A pipeline that tells them. Not a spreadsheet. Not a guess.
Every Client Journey Is Tracked and Feeding Data
Whether they came in for an INDIBA session or a Corporate Reset Day.
Ready to Begin
This proposal is valid for 30 days from the date of issue.
Step 1
Choose your option — review the three engagement structures and confirm which path aligns with your current timeline and build capacity.
Step 2
Schedule the Foundations Session — maps the 7 Wonders customer journeys, the user story library, and the full service architecture.
Step 3
Sign and begin — upon signing and receipt of the first payment, the Foundations Session is confirmed and the engagement begins.
Cris Vinson · OZ Tech Development Corp ·
unwiz.ai