OnTask on the OfRoot platform

Run service operations on the same platform that captures and routes demand.

OnTask is the operations-first edition: invoicing, reminders, workflow execution, payments, and reporting on the same customer record.

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

Choose the edition that matches the bottleneck

These are not separate technical stacks. They are two product modes on the same platform.

Compare plans

Growth edition

Helpr

Focus this edition

Lead capture and follow-up for service teams — inbound demand, review automation, and routing on the same shared platform as OnTask.

  • Lead capture pages
  • Email/SMS flows and review boosts
  • Basic analytics and attribution
  • Sentry observability

Operations edition

OnTask

Focus this edition

Operations software for local service businesses — lead follow-up, paperwork, payments, and reporting in one shared platform.

  • Secure authentication with roles, audit trails, and staff permissions
  • Automated lead capture, follow-ups, and review campaigns
  • Estimates, invoices, and automated payment reminders in one inbox
  • Public invoice links with Stripe Checkout and receipts

Why one platform is the better operating model

Shared CRM and lead routing

Every lead, contact, and follow-up path lives in one customer record instead of being split across separate products.

Automations that span the full lifecycle

Lead capture, nurture, reminders, invoicing, and reporting all sit on the same workflow layer.

Billing, permissions, and reporting

One account model for subscribers, teams, plans, and tenant-level access instead of duplicated admin overhead.

Clean upgrade path

Teams can start with growth or operations first, then add the other mode without replatforming or migrating customer data.

How teams expand on the platform

The platform is designed so the first product you buy does not trap the rest of your workflow outside the system.

Step 1

Start with Helpr

Use Helpr when the immediate bottleneck is lead capture, response speed, review generation, and top-of-funnel conversion.

Step 2

Add OnTask when operations get heavier

Move into invoicing, payment reminders, internal workflows, and day-to-day execution without changing systems.

Step 3

Or start with OnTask and add growth later

Service businesses that already have demand can begin with operations first, then layer Helpr on top for acquisition.

Platform rollout

Start with the mode that solves the immediate problem. Keep the upside of one system.

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.

Service Business Platform | OfRoot · OfRoot