Team system

The HelpNow delivery team, organized around accountable work

A role-based operating model for shipping HelpNow.au: strategy, product, engineering, operations, growth, compliance and Codex implementation support.

View roadmap Contact team

Executive and product

Sets scope, priority, business readiness and customer experience gates.

CEO / Founder
Product Owner
Project Manager
Ops Product Owner

Engineering and AI

Owns architecture, service boundaries, data contracts, implementation and verification.

CTO / Tech Lead
Backend
Frontend
Data / AI Owner
Codex implementation agents

Operations and supply

Keeps lead response, provider readiness, dispatch, proof loops and service quality moving.

COO / Ops Owner
Provider Ops Owner
Review / Trust Owner
Sales support

Growth and finance

Controls claims, tracking, paid acquisition readiness, pricing, payments and reporting.

Growth Owner
Marketing support
Finance Owner
Analytics / QA

Trust and compliance

Reviews legal claims, licensed-category boundaries, moderation and audit evidence.

Compliance Owner
Security
Moderator
QA

Current ownership

Active P0/P1 workstreams

Synced from operating model docs. Last status: 2026-05-14

PriorityWorkstreamOwnerState

P0Public quote → lead → admin dispatchBackend Lead + Ops Product OwnerCode done, keep as primary revenue path

P0Admin reassign + provider accept/declineOps Product OwnerCode done, needs regression coverage and operator doc

P0Payment/status safetyFinance Owner + Backend LeadCode done, keep guarded before paid flows

P0Legal/trust/analytics cleanupGrowth Owner + Compliance OwnerCode done, needs recurring audit before ads

P0Health, backup and deploy reliabilityDevOps OwnerLive, still has hardening backlog

P1Admin lead management UIOps Product OwnerV1 implemented; needs ops QA with staging data

P1Lead/job notificationsBackend Owner + Ops OwnerFollow-up from revenue funnel

P1Provider profile + compliance fieldsProvider Ops Owner + Compliance OwnerPartly supported, needs category matrix

Assigned by plan

Every non-trivial task must have owner, priority, boundary, acceptance gate and test evidence.

Codex with boundaries

Codex agents support research, frontend, backend, QA and docs work, but owners keep approval authority.

Updated from docs

Team and roadmap pages read the same project documents used for delivery control on staging.

Staging page reads live repository docs at request time.

Loading…