LIVE RHIZ PAGEOWNED BY WERHIZMOVING: PRICINGUPDATED 2026-07-05RHZ-26A-8EWFA-X

Pricing

Choose the first surface that matches the work.

The homepage asks what you are trying to move. Pricing keeps the same question visible: one page, connected pages, a repeated workflow, or a larger coordination system.

What are you moving

Pick the path that matches the work. You can change or grow later.

01PageSingle surfaceOne public surface for an ask, offer, or identity.Open Page02SiteConnected surfacesConnected pages for story, proof, and offers.Open Site03WorkflowRepeated loopOne repeatable loop with intake and follow-through.Scope a Workflow04ConveneOrganization scopeOrganization-paid coordination across a network.Open Convene

Route packet

Start here
01PageSingle surfaceOne public identity surface, one ask, one action path.02SiteConnected surfacesConnected pages when the story, proof, and offers need room.03WorkflowRepeated loopOne repeated loop with intake, routing, QA, and follow-through.04ConveneOrganization scopeOrganization-paid coordination across members, requests, and outcomes.

Pricing boundary

Enterprise stays proposal-led. Launch ladder pricing stays on Launch.

This surface runs intent routing for teams deciding what shape to launch first. Public self-serve prices and checkout belong on Launch surfaces. Enterprise starts with scope and proposal, then coordinates through one operating surface.

Instead of a stack

  • Intent diagnostic to classify launch shape
  • Live path into Page, Site, Workflow, or Convene
  • Partner Scope lane for managed build requests
  • Proposal-first path for institution-grade deployments

The route keeps self-serve and enterprise pricing boundaries intact while preserving one system.

See the operating model

01 / Single surface

Page

One public identity surface, one ask, one action path.

Start with Pages

02 / Connected surfaces

Site

Connected pages when the story, proof, and offers need room.

Open Sites

03 / Repeated loop

Workflow

One repeated loop with intake, routing, QA, and follow-through.

Open Workflows

04 / Organization scope

Convene

Organization-paid coordination across members, requests, and outcomes.

See Convene

Next steps

Start in the lane that matches current scope.

Use this routing surface to choose the first shape. Launch handles self-serve checkout and tier specifics. Enterprise lanes begin with scope and partner conversation.

Enterprise lane

Convene

Organization-paid coordination for member pages, requests, routing, and outcomes.

See Convene

Managed build

Partner Scope

Custom infrastructure, integrations, operating support, or white-label work when the loop is bigger than one launch.

Open Partner Scope