company-1-medspa/README.md, every file in company-1-medspa/brain/ (brand-voice.md, key-context.md, offer.md, policies.md, rules.md), and the three data exports in company-1-medspa/data/ — crm.csv, ads.csv, metrics.csv. No other file was opened, and nothing outside this report was changed. Every number below is computed from a specific CSV row, cited next to the number. Data exports are current through the July 14, 2026 snapshot noted in the README; June 2026 is the most recently completed month in the export.
| Metric | June 2026 | May 2026 | Change | Source |
|---|---|---|---|---|
| Revenue | $43,900 | $49,600 | −$5,700 (−11.5%) | metrics.csv row 153 (Jun 2026, total_revenue, 43900) vs row 139 (May 2026, total_revenue, 49600); source system booking_system |
| Active memberships | 121 | 117 | +4 (+3.4%) | metrics.csv row 157 (Jun 2026, memberships_active, 121) vs row 143 (May 2026, memberships_active, 117) |
| Membership movement | +7 new / −3 cancelled | +8 new / −3 cancelled | net +4 vs net +5 | metrics.csv rows 158–159 (Jun memberships_new=7, memberships_cancelled=3) vs rows 144–145 (May memberships_new=8, memberships_cancelled=3). 117 + 7 − 3 = 121 and 112 + 8 − 3 = 117 (April active count, row 129), so the movement rows reconcile to the active-count rows in both months. |
| Meta ad spend | $5,317.00 | $5,486.00 | −$169.00 (−3.1%) | metrics.csv row 160 vs row 146. Cross-checked by summing every ad-level row in ads.csv for the month: rows 390–421 (June, 32 line items, Reporting starts=2026-06-01) sum to $5,317.00; rows 358–389 (May, 32 line items) sum to $5,486.00 — both match the metrics.csv rollup exactly. |
| Meta leads | 154 | 154 | 0 (0.0%) | metrics.csv row 161 vs row 147. Cross-checked by summing Results across ads.csv rows where Result indicator = actions:onsite_conversion.lead_grouped: June rows 390–421 sum to 154 leads; May rows 358–389 sum to 154 leads. Both months land on the same total by coincidence of the underlying ad-level numbers, not a data error — see line items below. |
| Cost per Meta lead | $34.53 | $35.62 | −$1.09 (−3.1%) | Computed: spend ÷ leads for each month using the figures above ($5,317.00 ÷ 154 = $34.53; $5,486.00 ÷ 154 = $35.62). Not a value stored directly in either file. |
| Consult show rate | 72% | 74% | −2.0 points | metrics.csv row 164 (Jun 2026, consult_show_rate, 0.72) vs row 150 (May 2026, consult_show_rate, 0.74); source system crm. For context, booked consults were 57 in June (row 163) vs 60 in May (row 149). |
crm.csv gives a Status Change Date and Opportunity Created per contact, but for older opportunities these reflect when the record was last touched or created in GoHighLevel — not a confirmed appointment date. The actual appointment calendar lives in Vagaro, which is outside the three files this report is allowed to use. Rebuilding the show rate person-by-person from crm.csv alone produced numbers that don't reconcile to the booked_consults totals in metrics.csv, so this report uses the CRM system's own monthly rollup row instead of a hand-built substitute.
metrics.csv row with source google (leads_google, google_reviews_count, google_rating_avg) — for every month in the file, including June — carries the identical last_synced timestamp 2026-05-26T09:12:41Z. That connector has not actually refreshed since May 26, so June's Google numbers are repeats of a stale pull, not a real June measurement. None of the metrics requested for this report rely on Google data, so nothing above is affected — this is noted so the number isn't mistaken for a live June figure elsewhere.
Out of 73 contacts currently sitting in the Consult Complete stage with a quoted Lead Value (crm.csv), only 12 carry any note about outreach at all. Of those 12, four show a documented outbound message with no reply and clean, unambiguous contact details — the counting bar this report uses. The other eight either show a reply already came back, show an unrelated intake note, or show contact information that can't currently be trusted (see Section 3). The remaining 61 have no note either way and are not included here, since this report only counts a person when the record itself shows an outbound message that got no reply.
| Patient | Quoted plan | Quoted amount | Consult date | Why this person is on the list |
|---|---|---|---|---|
| Dawn Kucharski | Sculptra, 3-vial plan | $2,340 | 06/10/2026 | crm.csv row 166: plan quoted 06/10/2026 with Marisol; note reads "texted 06/16, no reply." Last Activity is 06/16/2026 — nothing logged since the unanswered text. Still in Consult Complete, not Won. |
| Melissa Braithwaite | Laser hair removal, full-legs package | $1,800 | 05/22/2026 | crm.csv row 297: full-legs package quoted 05/22/2026 with Yesenia; note reads "brynn texted 05/26, no reply." Last Activity is 05/26/2026 — nothing since. Still in Consult Complete. |
| Esme Flores | Botox, first visit | $350 | 07/08/2026 | crm.csv row 227: note reads "called twice, mailbox full" — two outbound call attempts, neither reached her. Status Change Date 07/10/2026, Last Activity 07/12/2026, still Consult Complete with no reply logged since. |
| Omar Tran | Sculptra series | $2,340 | 07/09/2026 | crm.csv row 1717: note reads "called twice, mailbox full" — same pattern, two unanswered outbound calls. Last Activity 07/14/2026, still Consult Complete, no reply logged. |
Also reviewed, not included: Felicia Ogundipe, Julian Chandra, Zoe Hsu, and Aaron Calderon all have quotes and open Consult Complete records with outreach notes, but each note shows the patient already replied or is actively engaging ("hot, likely to close"; "asked for saturday"; "said she is comparing dates"; "needs to check school pickup before booking") — so the no-reply bar isn't met and they're left off this list. Eva Aranda and Laila Browning have notes, but about how they found Citrine Vale (Yelp, parking), not about follow-up outreach. Penelope Costa's note is a consult-content note, not an outreach record. Ingrid Salcedo-Marsh is quoted and unresolved but is excluded for a different reason — see Section 3.
brain/offer.md (last updated April 2026) states: "Botox is $13 per unit. Vale Glow Club Gold members pay $11 per unit." brain/rules.md (last updated November 2025) states: "When a patient asks what Botox costs, the answer is $12 per unit before any membership discount."
Cited: brain/offer.md line 7; brain/rules.md line 23. offer.md itself warns "if anything anywhere disagrees with this file, ask Marisol before quoting a patient," and key-context.md instructs: "Do not answer a price disagreement by guessing which document 'probably' wins."
This report does not assume the newer file is correct. Marisol decides which figure is current and which file gets corrected.
crm.csv row 2269: completed consult, Consult Complete, quoted $2,250 for a Cheek + Lip Filler Plan on 04/30/2026, still open. The note reads: "got married, new number somewhere." Last Activity is 05/14/2026, with nothing logged since. The phone and email on file may no longer reach her, and there's no second record in crm.csv (matched by phone or email) that shows an updated contact.
This person is not on the follow-up list, because her identity's current contact information is uncertain, not because there's no interest or no quote. Marisol or Brynn decides whether to re-verify her contact details before anyone reaches out.
This report reports June and May consult show rate directly from metrics.csv (rows 164 and 150, source crm), because the per-contact date fields available in crm.csv — Status Change Date and Opportunity Created — do not reliably reconstruct which calendar month a given consult actually happened in; they reflect GoHighLevel record activity, not the Vagaro appointment calendar. A row-by-row attempt (grouping Consult Complete/No Show/Won by these date fields) does not reconcile to the booked_consults totals in metrics.csv. Vagaro itself is outside the three files this report is built from.
This report uses the CRM's own rollup number rather than guessing at a substitute methodology. If Marisol wants a person-level audit of June consults, that needs a Vagaro export, not just crm.csv.
Every Google-sourced row in metrics.csv (leads_google, google_reviews_count, google_rating_avg) carries the same last_synced value, 2026-05-26T09:12:41Z, across every month in the file — Jul 2025 through Jun 2026 alike. That means June's Google row is a repeated last-known value, not a real June reading.
This report does not state a June vs. May Google trend, because there isn't one to state — the connector hasn't moved since May 26. Confirming whether the Google Business Profile connector is actually still live is a question for Lexi, not something this report resolves.