Connect the first workflow
Helm is most useful when modules connect around real customer work. A simple launch path is website page, first offer, first customer, first booking or order, first invoice or receipt, and a short review of staff and support preferences.
Do not try to finish every module before going live. Publish the smallest honest version customers can use, then add Store, Blog, Link Page, events, gift cards, loyalty, and roles when the plan and workflow need them.
Use Overview as the operating surface
Overview shows the setup checklist, urgent priorities, quick actions, recent customer activity, and the first signs of business pulse. Treat it as a daily workbench, not a locked onboarding course.
Manual checklist items are reminders only. Helm marks authoritative steps complete from real source data such as published pages, services, products, customers, invoices, receipts, orders, and team members.
Share Helm after the basics work
After your own workspace is usable, Settings includes a Referral program page with your referral link and code. Share it with merchants who could use Helm, but keep the explanation practical and avoid promising instant credits, cash payouts, or guaranteed rewards.
Referral rewards are tracked separately from the setup checklist. They depend on valid attribution, eligible paid conversion, and Helm review, so they should never be treated as part of the normal launch path.
Keep unsupported automation out of the promise
Helm can help merchants move faster without claiming full automation everywhere. Use supported manual paths, dashboard records, public links, and customer history where they exist.
Setup reminder notifications and onboarding-tip emails need safe source events or jobs before they should be triggered. Do not send them from a read-only Overview page load.