What you actually get

LifeCycle OS is a working system installed inside your own accounts — not a template you assemble yourself. Every install includes:

  • A Notion command center — Pipeline, Clients, Payments, Tasks, Onboarding, and Offers databases, fully connected, with a single dashboard: today’s work, overdue items, and watch views that surface cold leads, stuck onboarding, and at-risk clients automatically.
  • Automations built in Make.com (Core and Full tiers) — new-lead follow-up, payment-to-onboarding conversion, no-contact reactivation with AI drafts, renewal prompts, overdue-invoice handling, alumni offboarding, and AI proposal drafts. Each one live-tested in your workspace before handoff.
  • A daily health signal — your dashboard shows a green “System OK — last verified” line, updated automatically every day. If that date ever goes stale, you know before anything is lost.
  • Documentation — a plain-language user guide, FAQ, and privacy/data notice, plus a recorded verification pass logged in your workspace.

What you need to provide

About 15 minutes of clicks, total. You never share passwords — every connection is approved on your own screen.

  1. A Notion account (free plan works for Foundation)
  2. A Make.com account on the Core plan (~$9–16/mo — Core and Full tiers only)
  3. Two-click authorizations for the tools your tier uses: Gmail, Google AI, and (Full tier) your form, booking, payment, and DM tools
  4. The 4-minute intake form describing how you actually work

What happens after you apply

  1. Day 0: You apply (4 minutes, no call). Reviewed within 24 hours.
  2. Day 1–2: Start time confirmed by email with a short prep checklist.
  3. Prep: You duplicate the template into your Notion, approve the tool connections (~15 minutes of clicks), and answer any configuration questions async.
  4. Build: 3–5 business days (Foundation), 5–7 (Core), 7–10 (Full). Fully async — no meetings.
  5. Verification: Every automation is tested in your workspace with fake sample data — a lead is created, a payment is marked paid, a client goes quiet — and each expected result is checked field by field. No green pass, no handoff.
  6. Handoff: You receive a recorded walkthrough, the user guide, and the verification record. The system is running and it is yours.

What “done” looks like

  • Every purchased automation has passed a live test in your workspace, logged with date and results
  • The daily “System OK” line is green on your dashboard
  • Test data is removed; your databases are clean and locked against accidental structural edits
  • You know the two things you ever need to do: glance at the green line, and forward any error email

Example: a typical Operator-mode install

Illustrative walkthrough — this is the mechanism, not a testimonial.

Problem: A consulting business closing clients through calls and DMs. Follow-ups happen when someone remembers. Onboarding differs depending on who handles it. Two leads last month were simply never answered.

Process: Core install. Their intake described the real flow: inquiry → call → proposal → payment → onboarding. The system was configured to that flow — when a payment is marked paid, the client record, onboarding checklist, welcome email, and first follow-up task are created in the same minute, the same way, every time. When any lead or client goes 14 days without contact, a follow-up task appears with a pre-written draft based on that person’s actual notes and goals.

Result: The backend stops depending on memory. Follow-ups, onboarding, and renewal prompts fire on schedule whether anyone is thinking about them or not — and the daily green line proves it’s still running.

Boundaries — what’s included and what isn’t

Included: everything listed in your tier, configured to your workflow; live verification of every automation; the walkthrough, documentation, and support window for your tier; one round of configuration adjustments within that window.

Not included: writing your marketing or sales content; lead generation; custom automations beyond your tier’s list (quoted separately on request); your tool subscriptions (Notion, Make.com, AI usage — typically $0–20/mo total); ongoing changes after the support window unless you’re on Flow Assurance.

Three rules keep your system safe (they’re also the only ways to break it): don’t rename database fields, don’t move or delete the databases themselves, and don’t edit inside Make.com. Everything else — adding records, pages, views — is yours to use freely.

Support and revisions

  • During your support window (14 days async on Core; 14-day Q&A + 30 days async on Full): fixes, questions, and one round of configuration adjustments, ~1 business day response.
  • After the window: the system keeps running — it doesn’t need me. For ongoing monitoring, expiring-connection fixes, and monthly improvements, Flow Assurance is $79/mo, cancel anytime. Without it, you keep a maintenance guide and handle occasional re-authorizations yourself.
  • If something errors: you’ll get an automatic email. Forward it. That’s the whole procedure.

Apply for LifeCycle OS → · Read the FAQ · Policies & contact