Migrating from Moxo to DueReason
Moxo is a client-portal workflow platform where AI agents prep requests and a named approver decides. See what a signed, verifiable grant adds.
Updated · 8 min read
In short
- Moxo markets itself as "AI approval workflow software": agents prep budget, vendor and hiring requests inside a branded client portal, and a named approver decides over a magic link - its entry Business plan is priced from $99/month (or about $80/month billed annually), with custom pricing above that.
- Its focus is breadth across parties - a portal shared with clients, vendors and outside counsel, with documents, e-signature and messaging in one thread - rather than a decision object with its own signature and lifecycle independent of the portal that hosted it.
- DueReason does not replace a client portal, a document thread or e-signature - it answers the one approval question a Moxo flow ends on, with a signed grant, a hash-chained ledger and an agent-native surface behind the answer.
- Moxo's external-party breadth is genuinely different from DueReason's model: DueReason's guest responses cover one outside approver answering one request, not a shared, branded workspace for an ongoing relationship with a client or vendor.
If you run approvals through a Moxo portal - an AI agent assembles the context for a budget, vendor or hiring request, and a named approver decides from a magic link, often with a client or vendor also present in the same portal - this walks through what that decision does today, and what changes if you move the approval step itself to DueReason.
What Moxo does today
Moxo positions itself as "AI approval workflow software": an agent preps a request - validating documents, assembling context - before it reaches a named approver, who decides from a one-click magic link that needs no account, usable by someone outside your organization as easily as by your own team. Routes can be sequential chains or parallel sign-offs with amount thresholds that skip levels, reminders and escalation run automatically if a request stalls, and a decision trace records what the agent read and recommended alongside who approved and when. The platform's wider pitch is the portal around that decision: branded workspaces shared with clients and vendors, document versions, e-signature and messaging in one thread. Pricing starts with a Business plan from $99/month billed monthly (roughly $80/month billed annually) for a limited number of workflows per month, with custom pricing for Business/Enterprise tiers and forward-deployed engineering - verify the current figure on moxo.com before quoting it, since vendor pricing pages change without notice.
That portal-first design is also what an approval inside Moxo is: one module of a shared workspace built around an ongoing relationship with a client or vendor, not a decision with its own identity, signature or lifecycle independent of the portal that contains it.
What happens after a request is approved
A decision in Moxo is recorded in its own decision trace - what the agent prepared, what the approver saw, who clicked approve and when - inside that portal. What is not part of that mechanism is a signed, independently verifiable object the next system checks before it acts: the trust sits in the request having been marked approved inside Moxo's own workspace, the same gap the Kissflow migration guide describes for a process step with no record a downstream system can check on its own. Moxo's one-click magic links are built for an approver reached through that one portal; nothing in the mechanism is a published, agent-native way for a pipeline or a coding agent to file a request and wait on a decision without a portal involved at all.
The same shape in DueReason
Moxo's portal is general-purpose across request types, so no single DueReason template is a 1:1 replacement for the whole workspace - DueReason answers the approval question one request asks, not the client-portal relationship around it. Map the request, not the portal: for a budget, vendor or hiring request, Payments and refunds, Vendor onboarding or Hiring offer from Settings → Templates cover that shape directly; for a client-facing sign-off such as a deliverable or draft awaiting a client's go-ahead, Content and publication sign-off is the closest template, or a custom action models the exact question if nothing close exists yet.
Whichever action models the request, once it is decided DueReason issues a signed, single-use grant bound to the exact payload - the amount, the vendor, the deliverable - which whatever acts next verifies, rather than trusting that the request is marked approved in the right portal.
What changes, not just what moves
- A grant the acting system checks, not a portal status trusted at the source. DueReason's signed grant is bound to a hash of the exact payload and verified by whatever executes the decision, so a changed amount or recipient after approval is refused rather than carried out because a request happened to be marked approved in the portal.
- A hash-chained ledger, not a portal's own decision trace. Moxo's trace records what one workspace saw; DueReason's ledger is an append-only, hash-chained record from the moment a request is filed, checkable on its own without opening the portal that hosted the decision.
- Evidence built into the action, not a shared document thread. Moxo's strength is the thread itself - versions, comments, e-signature alongside the conversation; DueReason's
evidencesetting (none, text or document) is narrower by design, built into the action definition so the record always carries exactly what the approver was shown, without needing the full thread to reconstruct it. - An agent-native surface a pipeline can call directly, not only a portal an agent preps for a human. The same actions are reachable from
@duereason/sdk, the MCP server, the GitHub Action or the REST API, so a coding agent or a pipeline canrequestApproval()andwaitForApproval()on its own, with no portal, workspace or branded client view involved at all.
Where Moxo's breadth is genuinely different
Moxo's client-portal model is not a gap to paper over: a branded, persistent workspace shared with a client or vendor across many requests, documents and conversations over time is a real product, and DueReason does not build one. DueReason's guest responses (`guest-respond`) let a named outside approver decide one specific request from a signed link with no account - the same one-click reach Moxo's magic links give - but that is one request answered once, not an ongoing shared workspace with message history, document versions and e-signature for a relationship that spans many requests. If what you need from Moxo is that persistent client-facing surface, keep it for that and add DueReason for the specific decisions inside it that need a signed, independently verifiable record.
Moving one approval step over
- Pick the one decision you want to move - not the whole portal - and find the closest DueReason template (Payments and refunds, Vendor onboarding, Hiring offer, Content and publication sign-off) or define a custom action if nothing close exists yet.
- Recreate the people who decide that request as members of the action's approver group, in place of Moxo's named-approver assignment.
- For an outside party (a client or vendor) who needs to answer without a DueReason account, use a guest response on that one request in place of Moxo's magic link - the same no-login, one-click reach, scoped to a single decision rather than a standing portal.
- For requests an agent already preps automatically,
requestApproval()andwaitForApproval()from@duereason/sdk(or the no-code webhook recipe if you would rather not write a backend) replace the point where Moxo's agent assembled the request and routed it to the approver. - Replace whatever reads the request's approved status back into the rest of your process with a check of
decided.statusand a verification ofdecided.grantbefore the step that actually acts - the system doing the work should check the grant, not just the portal's recorded decision.
What has no direct equivalent
DueReason has no branded client portal, no document-version and e-signature thread, and no forward-deployed engineering team shaping a bespoke workspace to your operation - it is not a portal replacement and does not try to be. If the value you get from Moxo is the ongoing, multi-request relationship with a client or vendor living in one shared space, keep Moxo for that and add DueReason around the specific decisions that need a signed, independently verifiable grant rather than expecting a native replacement for the portal itself.
Questions
- Does moving to DueReason mean giving up our client portal?
- No, and DueReason does not offer one to replace it with. Keep Moxo (or any portal) for the ongoing, branded workspace shared with a client or vendor, and point the specific decisions inside it that need a signed, verifiable grant at DueReason instead.
- Can an outside client or vendor still approve without a DueReason account?
- Yes, with a guest response: a named outside approver gets a signed, single-use link for one specific request and decides with no account and no login, the same one-click reach as Moxo's magic links - scoped to that one decision rather than a standing, persistent portal.
- What does Moxo cost, compared to DueReason?
- Moxo's entry Business plan is priced from $99/month billed monthly (about $80/month billed annually) for a limited number of workflows, with custom pricing above that; verify the current figure directly with Moxo before relying on it. DueReason is free today for one organization with up to five members, all core features included.
- Does DueReason do AI-prepped requests the way Moxo's agents do?
- DueReason does not ship a built-in agent that drafts a request for you. What it adds once a request exists - from any agent, pipeline or person - is the decision itself: a signed, payload-bound grant and a hash-chained ledger entry, reachable the same way whether the request was prepared by a Moxo-style agent, a script, or someone typing into the console form.
- Can I self-host instead of using the hosted product?
- Yes. Self-hosting runs on one Postgres database and one pre-built image started with Docker Compose, with no portal, document store or e-signature module of its own - the same actions, grants and ledger work the same way whether you use the hosted product or run it yourself.
Move one decision out of the portal to DueReason
Keep your client or vendor portal for the ongoing relationship - point requestApproval() and waitForApproval(), a guest response, or the console request form at the one decision that needs a signed, verifiable grant.
Create your accountSources
- Moxo: AI approval workflow software
- Moxo: Human-AI workflow automation for business operations
- @duereason/sdk: requestApproval and waitForApproval reference
This guide explains the regulation as we read it; it is not legal advice. Check the official text and your national law, which may add obligations.