Rules engine narrative
The story we tell about why customers buy Helix: ops teams want to author their own routing logic, not file tickets to engineering.
The thesis
Mid-market ops teams (50–500 people) live with brittle, dev-mediated automation. Every rule change is a ticket. We give them a programmable surface they can author themselves — without an "if-this-then-that" toy ceiling. The unlock is performance (order-routing-v2) + a UI ops can use (rules-engine-customer-ui).
What this means for product
- The rules engine is the wedge.
- Latency is a feature (cf. use-protobuf-internal).
- The UI is the point of differentiation, not the API. zapier and workato have APIs; neither has a credible authoring UI for our persona.
What this means for GTM
- Lead with rules engine, not the platform.
- Design partners (acme-logistics etc.) become public references in 2026.
- See 2026-okrs for the KRs.
Backlinks · 5
↪people/jess-okafor…filled. Founder #2. ## Threads - 2026-okrs - rules-engine-narrative - freemium-self-serve ## Notes - Backfill fo…↪people/marco-li…ve]] ## Notes - Wants product to lead with narrative — see rules-engine-narrative (his ask). - Prefers a 1-page brief over a long doc; if it…↪people/maya-chen…jects/rules-engine-customer-ui]] - 2026-okrs - rules-engine-narrative ## Notes - Direct manager: jess-okafor (CTO, cu…↪strategy/2026-okrs…6, framed around the mid-market-thesis and the rules-engine-narrative. ## O1 — Become the rules-engine of choice for mid-market…↪strategy/mid-market-thesis…ur fundraise math. - Custom-everything is incompatible with rules-engine-narrative — we want one product, configured. ## Why not SMB - WTP pe…