Om Vortex + Brain Game Growth Partner Agreement
A unified growth system for Om Massage and the Brain Game coaching brand, built and managed by Alchmy.
1. Engagement Overview
Provider: Alchmy (Yanick Chiasson)
Client: Om Massage / Matthew Mackay
Term: Six (6) months from Start Date (the "Engagement Term").
Objective
Design, build, and optimize a unified growth system for Om Massage and the Brain Game coaching brand, consisting of three paid media engines, a new coaching brand website and funnel, a 180 day content plan, and upgraded systems (Kim, IVR, CRM, VA enablement).
2. Deliverables and Services
2.1Growth Engines, Om Massage
Provider will build and manage three integrated "engines," each defined as ads plus landing experience plus AIO and SEO configuration plus tracking.
2.1.1 Vortex Engine (Flagship)
- Strategy and structure for the Om Vortex acquisition funnel.
- Meta and Google Ads campaigns for Vortex, including campaign and ad group structure, ad copy and basic creative direction, and ongoing bid and budget adjustments within agreed budgets.
- Dedicated Vortex landing page: wireframe and layout, conversion focused copy, AIO content setup, on page SEO (titles, metas, headings), and schema implementation for relevant services or offers.
- Tracking: pixels and tags configured on the landing page, conversion events for lead, booking, and other key actions.
2.1.2 Red Light Engine
- Google Ads search campaign for red light therapy.
- Dedicated or clearly separated red light landing experience (page or section), including copy improvement and layout optimization, AIO and on page SEO, and schema implementation for the service.
- Conversion tracking for leads or bookings.
2.1.3 Massage Engine
- Google Ads search campaign for massage.
- Optimized massage landing experience (page or section), including copy and layout optimization, AIO and on page SEO, and schema implementation for the service.
- Conversion tracking.
2.1.4 Analytics and SEO Foundation
- Configuration of tracking to capture search visibility and conversions for Om Massage and key offers.
- Implementation or correction of LocalBusiness and Service schema on the main site to support visibility.
2.2Brain Game Coaching Brand
2.2.1 Platform and Website
- Research and recommend the most appropriate platform stack for the coaching brand (for example Wix, Skool, Circle).
- Design and build a coaching brand website around Matthew, including a home page (positioning, key outcomes, credibility), an about page, a Brain Game core offer page, an Om and Retreats structure for future retreats and experiences, and an apply and contact page with forms.
2.2.2 Brain Game Funnel
- Define and implement one primary funnel for Brain Game: a lead magnet or VSL entry point (opt in or video page), an application or call booking step, and a confirmation or thank you experience.
- Connect the funnel to the CRM as described in Section 2.4.
2.2.3 180 Day Content Plan and Workflow
- Create a 180 day content map for Brain Game and Om, including topics, angles, and calls to action aligned to Brain Game and Vortex objectives, and recommended formats (video, posts, emails).
- Design a "record once, VA repurposes and posts" workflow, with guidance on frequency and channels and templates and examples for the VA to follow.
- Maintain ongoing coordination with Client's VA via Slack (or similar agreed channel) to clarify priorities, coordinate execution, and reduce repetitive weekly meetings required from Matthew.
Provider supplies strategy and structure. Client's VA executes publishing and day to day content work.
2.3Systems, Kim v2 and IVR
2.3.1 Kim v2, Text AI Assistant
- Review existing Kim flows and identify errors and bottlenecks.
- Redesign and rebuild Kim as a "digital receptionist" to capture lead and client data cleanly, verify availability and service options based on agreed rules before confirming or proposing bookings, respect rules for timing and duration, and hand off correctly to booking flow or human follow up (for example through CRM tasks or messaging).
2.3.2 IVR (Phone Menu)
- Simplify and reconfigure the IVR menu to provide clear options and paths for callers and route appropriately to Kim, voicemail, or direct line according to Client's preference.
- Continue diagnosing and resolving known "dropped call" issues within the phone and IVR flow, to the extent they are within Provider's control on the configured system.
2.4CRM, SOPs, and VA Enablement
Provider's role with respect to Client's VA (Edraly) is enablement only. Provider does not act as Edraly's manager or employer and does not own or direct her day to day output. Client retains responsibility for resourcing, managing, and directing the VA.
Provider will
- Configure or update the CRM to support Vortex, red light, massage, and Brain Game funnels, including tagging, pipelines, and basic automations for lead capture, nurturing, and follow up.
- Develop advance plans, schedules, and SOPs for the VA's recurring tasks (content workflow, CRM tasks, KB updates) so execution follows an agreed plan instead of ad hoc direction.
- Provide the VA with written SOPs for her recurring tasks. After the VA has had time to review the SOPs and compile her questions, Provider will hold an onboarding and training session to walk through all SOPs together, followed by a later follow up session. Both sessions will be recorded and the recordings provided to the VA for reference.
- Support the VA in learning to modify and update Kim's knowledge base, including how to test and validate changes safely before they go live.
- Relay information or requests to the VA on Client's behalf when needed for coordination.
Provider will not
- Manage, supervise, or evaluate the VA's day to day performance.
- Take on the VA's output as Provider's own deliverable.
Urgent or rush items that fall outside the agreed planning cycle and outside Provider's scope are routed by Client to the VA, which is part of why Client maintains a VA. Provider remains available to quote urgent work outside Provider's scope, but such work should be raised with Provider when the need is identified, not at the point implementation is expected.
Division of responsibilities
The operating division between Client's VA and Provider is as follows. The VA (Edraly) performs simple, repeatable operational updates using the SOPs, forms, and pre made prompts created by Provider: therapist information, FAQs, basic knowledge base updates, promotions, and pricing updates. These tasks are designed to require no technical expertise. Provider retains ownership of the underlying system: new workflows, complex automation changes, integrations, optimization, troubleshooting, and the continued proper functioning of what Provider has built.
Enablement includes a short, defined transition period during which Provider guides and supports the VA as she becomes comfortable with these updates, through the SOPs, onboarding and training sessions, and validation steps described above. The transition for a given task ends once its SOP is delivered and the VA has completed that task with validation. After transition, requests that go beyond simple operational updates are not transferred to the VA; they return to Provider and are handled as defects under Section 4.1 when caused by Provider's build, or as requests under Schedule A2 Clause 7 otherwise. Nothing in this Section transfers technical responsibility for the system to the VA or to Client.
All SOPs, planning frameworks, and process documentation created by Provider for this enablement remain the intellectual property of Alchmy. As an exception specific to this engagement, based on the terms of a prior agreement between the parties, the VA enablement SOPs will be provided directly to Om Massage.
2.5Strategy and Reviews
Two strategy or review calls per calendar month during the Engagement Term, focused on performance review of engines and funnels, offer and messaging adjustments, and prioritization of next implementation tasks within the agreed scope.
Calls are typically 45 to 60 minutes and conducted via video conference unless otherwise agreed. Each call includes dedicated time for current issues, new ideas, and website updates, in addition to the performance review above.
2.6Meta Lead to Booking Automation (New Deliverable)
This is a new build requested after the original Package A scope was defined. It is not part of the Kim v2 rebuild in 2.3.1, which covers reconstruction of existing flows, the three agreed keyword triggers, and the booking availability workflow only. Section 2.6 is engaged as an addition to the Package A scope. It is priced in Section 3 as a one time fee of 300 CAD, prepaid, and Client has accepted this deliverable with the exclusions and platform constraints stated in 2.6.2.
2.6.1 Included in v1
- Trigger: when a Meta lead form is submitted (Facebook or Instagram), Kim responds within seconds with a new client welcome message and the active promotion.
- Kim answers questions about Om Massage and the current offer from her knowledge base, and directs the lead to online booking.
- Automated follow up reminders (up to three) if the lead has not booked, on an agreed schedule.
- Promotion routing by promo code: where Client configures a distinct promo code per campaign, Kim delivers the matching code. Where Client uses a single universal code, Kim delivers that.
2.6.2 Explicitly out of scope
The following are excluded from 2.6 because they cannot be delivered reliably with the current platform setup. Each is stated with its reason so expectations are matched on both sides.
- Automated per ad source detection inside Messenger or Instagram DMs. Meta lead form messages arrive in a near identical format and do not carry the originating ad or promotion. Reliable routing depends on promo code structure configured by Client (2.6.1), not on Provider parsing the source from the message.
- Automated new client versus existing client verification. A Facebook or Instagram identity does not reliably match the name or email a person uses to book in the Wix booking CRM, which is a separate system managed by a third party. Any automated match would produce false positives that create client relations incidents. Eligibility verification therefore remains a manual step performed by Client's team once a booking comes through, as Client proposed.
- Any change, refinement, or iteration beyond the v1 defined above is handled under Schedule A2 Clause 7 (New Requests Outside Defined Scope).
3. Fees and Payment Terms
Package A, Full Growth Partner (Founder Partner Rate)
Package A fee: 12,000 CAD, split into two equal installments.
- First installment (6,000 CAD): due at invoice date.
- Second installment (6,000 CAD): due 30 days after the invoice date.
Section 2.6, Meta Lead to Booking Automation: one time fee of 300 CAD, added to the Engagement investment and prepaid with the first payment under this Agreement. This fee covers the v1 scope defined in 2.6.1 only. Changes or iterations beyond v1 are handled under Schedule A2 Clause 7.
Total Engagement investment: 12,300 CAD. The Section 2.6 fee is included in the first payment, making the first payment 6,300 CAD and the second 6,000 CAD.
All advertising spend, platform fees, phone system costs, and third party tool subscriptions are paid directly by Client and are not included in these service fees.
4. Implementation Commitment
Provided Client meets the responsibilities defined in Schedule C of this Agreement, Provider commits to completing the Package A engines (Vortex, Red Light, Massage), the Brain Game site and funnel, and the 180 day content plan within the Engagement Term, with core assets targeted for completion within the first 90 days.
If defined deliverables are not completed within the Engagement Term under those conditions, Provider will complete the remaining defined deliverables at no additional service fee, within the original scope, until they are live or delivered.
4.1 Definition of Completion ("Done")
A deliverable is "Done" when the conditions below are met. Once a deliverable is Done, further changes are new requests handled under Schedule A2 Clause 7, not continued work on the original deliverable. This definition exists so that both parties share one finish line for each item and no deliverable stays open ended.
Unless a deliverable's own section states otherwise, "Done" means all of the following:
- Live: the asset or system is deployed and functioning in its production environment.
- Tested: Provider has run the deliverable through its intended primary path at least once and confirmed it performs as specified.
- Integrated: the deliverable is connected to the systems it depends on for the scope defined (for example, a funnel connected to the CRM, a landing page firing its conversion events).
- Walked through: Provider has presented the deliverable to Client once, live or by recording.
- Documented where applicable: for systems the VA operates (CRM flows, Kim knowledge base, content workflow), an SOP exists per Section 2.4, supported by a recorded training session where applicable. Documentation is not required for one off assets such as a single landing page.
Approval note: once a deliverable is presented as Done, Client has the approval window in Schedule C Clause 4 to raise a defect (something not performing as specified). Defects are corrected within the original scope at no additional charge. Requests for changes to specification, added capability, or new behavior are not defects and are handled under Clause 7.
Per deliverable completion criteria
| Deliverable | Done when |
|---|---|
| Growth Engine (each: Vortex, Red Light, Massage) | Campaign live, landing experience live with copy and schema, conversion tracking firing and verified, walked through once. |
| Brain Game website (v1) | Agreed pages live, forms submitting to CRM, walked through once. Copy revisions after this run through Clause 4 (defects) or Clause 7 (changes). |
| Brain Game funnel | Entry point, application or booking step, and confirmation live and connected to CRM, tested through one full pass. |
| Kim v2 | Rebuilt flows live, agreed keyword triggers active, booking availability workflow live and tested, one consolidated revision round completed per 2.3.2, VA documentation delivered. |
| IVR v2 | Reconfigured menu live and routing as agreed, one consolidated revision round completed per 2.3.2. |
| Meta Lead Automation (2.6) | v1 trigger, response, promo delivery, and follow up reminders live and tested through one full pass. Out of scope items in 2.6.2 are not conditions of Done. |
| 180 day content plan | Content map delivered and agreed, workflow handed off and tested once with VA. |
| CRM and VA enablement | Pipelines and automations for the funnels live, SOPs and training delivered per Section 2.4. |
5. Schedule A2, System Integrity and Access
This Schedule sets the operating rules for availability, reporting, system access, and third party coordination across the Engagement. It exists to keep responsibility matched to control: Provider is accountable for what Provider builds and manages, and Client is accountable for what Client's own team, contacts, and access decisions affect.
Primary channel is Slack, secondary email. Response windows apply once required intake information is provided (see Clause 3), not from the moment of first contact. For requests with complete intake information, Provider responds within one to two business days. For confirmed outages affecting live bookings, Provider responds within twenty four hours.
Provider's schedule during the Engagement Term is nonlinear due to a new dependent and does not follow fixed business hours. Deliverables and the cadence above are the operating commitment, not clock hours or on call availability. This Engagement is a growth partnership, not an on call helpdesk.
Provider will implement tracking and provide monthly reporting covering traffic, leads, cost per lead, booking conversion, and engine level performance for active campaigns.
This is an implementation and optimization engagement, not a guarantee of revenue, profit, or booking counts. Results depend in part on factors outside this Engagement's scope, including Client's booking follow up, in clinic conversion, pricing, and staff execution, which remain Client's responsibility.
Provider built systems, including CRM automations, workflows, and knowledge bases, are shared assets. Client and Client's staff retain access needed for their own operational use, including routine data entry and cleanup in connected sheets.
Where an issue arises in a Provider built system, diagnostic and repair time is billed at 98 CAD per hour by default. Provider will credit that time back only if diagnosis confirms the issue originated in Provider's own build, not in Client side use, edits, or third party changes.
Before diagnostic work begins on a request flagged as urgent, Client will provide the exact time the issue occurred, the action taken before it and when, what Client attempted to resolve it, and a direct example (for example, the name of the client involved with a timestamped call or message). Work does not begin, and the response windows in Clause 1 do not start, until this information is provided.
Provider is responsible for training Client's VA on agreed SOPs for Provider built systems. Provider is not responsible for errors, changes, or damage the VA causes outside those SOPs, or on assets modified without following trained process, regardless of whether the VA had standing access to the asset for other purposes.
Provider will review third party vendor performance, including TRND, during scheduled strategy calls and will flag concerns. Provider will not manage, supervise, or be held responsible for a third party vendor's deliverables or results. Full vendor management or takeover of vendor scope is available as a separately scoped and priced addition.
Only Matthew Mackay and any co owner formally named by Matthew in writing may direct scope changes, authorize new work, or approve deviations from this Agreement. Requests from any other individual, including staff or family members, will be confirmed with Matthew before Provider acts on them.
Requests for CRM modifications, automations, or system changes not listed as deliverables in this Schedule are handled as follows. Client receives up to 2 hours per month of minor changes at no additional charge, defined as configuration edits or small adjustments completable in under thirty minutes each. Any request exceeding that allowance, or any new build, is scoped and quoted before work begins, with estimated hours and cost confirmed in writing.
New requests are not absorbed into existing deliverable hours regardless of similarity to work already in scope.
6. Schedule B, Project Timeline
There is no phase sequence or fixed timeline in place at signature. Provider and Client will hold a priorities meeting after this Agreement is signed and the first payment is received. That meeting sets which deliverables are actioned first and in what order, including the placement of Section 2.6. A phase timeline reflecting the outcome of that meeting will be provided to Client afterward.
Dates
Engagement Start Date: July 1, 2026 | Engagement End Date: December 31, 2026
These two dates mark the boundaries of the Engagement Term for purposes of fees, renewal, and the implementation commitment in Section 4. They are not a commitment that any specific deliverable completes by a point inside that window. The priorities meeting and the phase timeline that follows it govern sequencing.
Sequencing and Pace
Once set, phases are ordered by dependency, not by calendar month. A Phase begins once its dependencies are Done per Section 4.1, and Provider works through the sequence at the pace described in Schedule A2 Clause 1. This means two phases may run concurrently where they do not depend on each other, and a Phase may take longer or shorter than a calendar month based structure would suggest, without that being a breach of this Agreement.
Provider will give Client visibility into current Phase and next Phase at each strategy call under Section 2.5, so progress stays observable without a fixed date acting as the measure of it.
Provider and Client may update the phase timeline in writing as needed to reflect capacity, approvals, and dependencies.
7. Schedule C, Client Responsibilities
The following responsibilities are required for Provider to deliver the scope in Schedule A and to meet the implementation commitment in Section 4.
1. Access and Technical Setup
Client will:
- Provide Provider with admin level access (or equivalent) to website platform(s), CRM, ad accounts (Meta and Google), phone/IVR system, and the coaching platform once selected.
- Ensure payment methods and subscriptions for required platforms remain active for the duration of the Engagement Term.
2. Brand, Offers, and Content Inputs
Client will:
- Provide existing brand assets: logo, colors, fonts, photography, existing copy, prior promos, testimonials, etc.
- Confirm offers, pricing, policies, and constraints (schedule limits, blackout periods) in a timely manner.
- Record requested video/audio content for Brain Game and Om (VSLs, training snippets, authority content) according to an agreed cadence.
3. VA Resourcing and Management
Client will:
- Maintain Edraly (or an equivalent team member) as Client's resource, with capacity to execute the content workflow, routine CRM tasks, and KB updates described in Provider's SOPs.
- Manage, direct, and supervise the VA's day to day work, schedule, and performance. Provider's role is limited to planning, enablement, and training as described in Section 2.4 and Schedule A2.
- Ensure the VA has access to Slack (or an agreed communication channel) and is responsive to Provider for planning and coordination purposes.
- Ensure the VA attends relevant handoff and training sessions scheduled by Provider.
- Route urgent or rush requests to Provider rather than directly to the VA outside the agreed plan, consistent with Section 2.4.
4. Approvals and Feedback
Client (or designated decision maker) will:
- Review and provide approvals or consolidated revision notes on major deliverables (landing pages, key flows, site layout, key copy) within seven business days of presentation.
- Provide timely feedback on strategy decisions (offers, positioning, priorities) so Provider can proceed without extended delays.
If approvals or revisions are delayed beyond this window, Provider may adjust the Timeline accordingly without being considered in breach of the implementation commitment.
5. Advertising Budgets and Policies
Client will:
- Set and fund advertising budgets directly in the ad platforms.
- Communicate budget changes, pauses, or policy constraints (promo blackout dates, discount rules) at least five business days in advance where practical.
- Handle any required compliance review or legal approvals for claims, guarantees, or regulated language in ads and pages.
6. Legal, Compliance, and Risk
Client is responsible for:
- Ensuring all marketing claims, guarantees, and representations used in ads, landing pages, and offers comply with applicable laws, regulations, and professional standards.
- Providing Provider with any required disclaimers or language that must appear on the website or in communications.
- Reviewing and approving final copy and structure from a legal/compliance standpoint.
Provider will not be liable for regulatory or legal issues arising from approved Client content, offers, or policies.
7. Meetings and Communication
Client will:
- Attend or delegate attendance for the two monthly strategy/review calls.
- Respond to Slack (or agreed channel) messages that require decisions or approvals within a reasonable time frame, ideally within one to two business days.
- Notify Provider as early as possible of changes that materially affect scope, timing, or feasibility (sudden schedule cuts, staffing changes, service changes).
8. Dependencies and Impact on Implementation Commitment
Client acknowledges that Provider's implementation commitment in Schedule A assumes timely access, inputs, approvals, and participation as outlined above, plus stable access to required tools and platforms during the project.
If Client responsibilities are not met, timelines and deliverables may be delayed and the implementation commitment window may be extended by mutual written agreement to reflect those delays.