IN BUILD / GOVERNED WORKFLOWS
Hoppy: The queue is the front door. Policy decides who opens it.
Hoppy runs a company's workflows across its teams. A workflow like quote to cash passes through Sales, Finance and Legal, and each step follows the published, versioned policy of the team that owns it, including an authority matrix of who approves what, at which amount. A person, their own assistant or a team's agent can do a step, and every action goes through one gate that answers allow, hold or deny. A held action waits in the approver's queue with its exact values frozen. Hoppy is its own product, independent of Quorai.
What is notable
- Once approved, an action runs exactly once, with exactly the values approved, and the person who asked can never approve it.
- Every decision lands on an append-only, hash-chained record, and each consequential action gets a signed receipt anyone can check offline.
- New agents start at Draft and are raised one level at a time by the owning team's head, and a budget pauses work before a call would pass its cap.
Your data
This version holds demo data for an invented company only, and no AI model is called.
The data is yours.
Why we built it
Every team already has rules about who may approve what. Hoppy exists so those rules decide every action, whether a person, an assistant or an agent takes it. It is in build, running on an invented demo company.