Why we built Helpward

Helpward exists because the on-demand economy already solved logistics and left the harder problem on the table: trust. You can summon almost any service through a phone now. You cannot — most of the time — verify that the person showing up was vetted in a way that warrants letting them into your home, or into your car, or near a member of your family.

We built Helpward to close that gap. Every helper passes Stripe Identity verification and a third-party criminal background check (Checkr in the US, Triton in Canada) before they can take a single task. Every booking is covered by $1M-per-incident platform insurance. Pricing is published before the booking; payment is held in escrow until the customer marks the task complete.

What the rest of the industry got right

We didn't start from a position that the existing players were stupid or lazy. They optimised brilliantly for the variables they cared about — supply liquidity, time-to-arrival, customer acquisition cost. The marketplaces are huge because those optimisations work; if you've ordered DoorDash this week you've seen them working.

What got optimised at the same time — quietly, by accident in some cases and deliberately in others — was the worker side of the equation. Surge pricing turned into a worker pay cut. Background checks were outsourced to cheap providers with high error rates. Dispute systems were tilted heavily toward the customer because the customer has the credit card. The platforms got better; the workers got squeezed; the customers got dependable speed and unreliable safety.

Where we're trying to be different

• Helpers keep 80% of base + distance fees and 100% of tips. The 20% we keep funds insurance, verification, support, and engineering — not customer-acquisition arms races.
• Pricing is flat. A $4.50 service fee plus the helper's base. No surge, no per-minute escalation, no 'priority queue' upcharge.
• Background-check adjudication is policy, not algorithm. A human reviewer reads every flagged record and writes the call. The policy is published at /safety/background-checks — we'll defend any disqualification or approval publicly.
• Disputes use an asymmetric communication model: the customer's verbatim description stays private, but the helper sees the category and is given a chance to respond. Neither side gets to bully the other through the dispute system.
• We publish a quarterly transparency report with stats pulled directly from the production database. If a number looks bad, we publish it anyway.

What we're not trying to be

Helpward is not trying to be the cheapest option. We can't be — the costs of identity verification, background checks, insurance, and support are real. We pass them on at $4.50 a booking, and that's the deal. If you want the cheapest option, there are plenty of alternatives. If you want the worth-the-booking option, that's what we're building.

We're also not trying to dispatch as much as possible. The matching engine doesn't push helpers tasks they don't want. The schedule editor exists so helpers can say when they're available — and have customers see it on their public profile. We'd rather have 500 helpers who love being on the platform than 5,000 who feel coerced by it.

What's next

Helpward is live in 10 metros: Vancouver, Toronto, Montreal, Seattle, San Francisco, Los Angeles, Austin, Chicago, New York, and Miami. We add cities as the verified-helper supply meets a quality threshold — typically when we can hold response time under 20 minutes during peak hours. We expect 5 more cities live by end of 2026.

If you want to read the operational craft in more detail, the safety microsite at /safety is where we go deep. If you want to help build it, we're hiring across operations, trust & safety, engineering, design, and community at /careers. If you have feedback — even harsh feedback — hello@helpward.com reads everything.