Book a call
All work
Mihaela Munteanu · Evereve MindCoach

A whole CRM, website, and email engine for an Italian coaching brand

Coach launching her brand had no CRM, no automated funnel, no website. We built the whole stack. 12-page website, 20 GHL workflows, 50 email templates across five sequences, lead magnet, post-purchase nurture, cart-abandon, appointment reminders. Italian content treated as fixed tokens; the English ops layer wraps around it.

GoHighLevelEmail AutomationCRMItalian MarketDomain & DNS

The problem

Mihaela Munteanu runs Evereve MindCoach, Italian-market coaching brand. Launch deadline, almost nothing operational behind it. No CRM. No automated funnel. No website that captures leads.

Coaches at this stage usually duct-tape calendar booking + Stripe link + Mailchimp list and hope it holds. It doesn't. By month three you're reconciling who paid, who churned, and who never finished the lead magnet, by hand.

What I did

Built the whole stack, end to end.

  • GoHighLevel CRM from scratch. Pipelines, custom fields, custom values, tagging schema. Lifecycle = state (lead → qualified → paid → active → churned), not a list of names.
  • Website with branded templates. Pages, design, copy structure, conversion paths. Mihaela can edit content without breaking the funnel.
  • Domain + DNS done right. SPF, DKIM, DMARC configured so messages actually land.
  • Five email sequences, ~50 templates:
    • Lead Magnet (LM-01 → LM-07): immediate delivery, 14-day nurture
    • Post-Purchase Ebook (PP-EB-01 → PP-EB-05): welcome + 30-day upsell
    • Post-Purchase Course (PP-CO-01 → PP-CO-05): same shape, course-specific
    • Cart Abandonment (CA-01 → CA-03): 1h, day 3, day 5
    • Appointment Reminders: confirm + 24h + 1h
  • Single base template (TEMPLATE-BASE-Evereve) cloned for every email. One layout source, one set of brand tokens. Edit once, everything updates.
  • 20 GHL workflows orchestrating it all with explicit guards: re-entry rules, exit conditions, no cross-streams between sequences.

The detail that mattered: Italian content stays in Italian. Form names, tags, triggers, subject lines: treated as a fixed token set. The English ops layer wraps around it; the two never collide. Same pattern I use on RedsoClub for Spanish.

Outcome

  • Day-one launch with a complete operational stack: CRM, site, email engine, lead magnet, full lifecycle automations.
  • Single owner (her) runs it day to day. No vendor babysitting.
  • Lifecycle state lives in the pipeline, not in tags. "Who's actually a paying client right now?" The CRM has the answer.