One platform. Two product editions.
OfRoot is structured as one platform with multiple product editions. Teams can start with growth or operations first, then expand without replatforming, duplicating billing, or splitting customer data.
Platform model
One account, one tenant model, multiple product editions
Operational advantage
No split customer records between demand gen and execution
Commercial advantage
Start narrow, expand into more workflows without replatforming
These are not separate technical stacks. They are two product modes on the same platform.
Growth edition
Lead capture and follow-up for service teams — inbound demand, review automation, and routing on the same shared platform as OnTask.
Operations edition
Operations software for local service businesses — lead follow-up, paperwork, payments, and reporting in one shared platform.
Every lead, contact, and follow-up path lives in one customer record instead of being split across separate products.
Lead capture, nurture, reminders, invoicing, and reporting all sit on the same workflow layer.
One account model for subscribers, teams, plans, and tenant-level access instead of duplicated admin overhead.
Teams can start with growth or operations first, then add the other mode without replatforming or migrating customer data.
The platform is designed so the first product you buy does not trap the rest of your workflow outside the system.
Use Helpr when the immediate bottleneck is lead capture, response speed, review generation, and top-of-funnel conversion.
Move into invoicing, payment reminders, internal workflows, and day-to-day execution without changing systems.
Service businesses that already have demand can begin with operations first, then layer Helpr on top for acquisition.
Platform rollout
If the current problem is demand generation, start with Helpr. If the current problem is operational execution, start with OnTask. Both sit on the same foundation for CRM, automations, billing, and reporting.
