Ops template

RICE Prioritizer

Score and rank any backlog of ideas with RICE and a one-line rationale each.

A prioritization desk that ends the "which do we do first" argument. Paste a raw list of features, bets, or tasks (with whatever context you have) and it returns each one scored on Reach, Impact, Confidence, and Effort, with the RICE number computed and the list ranked top to bottom. Every item gets a one-line why, and anything it had to assume is flagged so you can correct it. Example input: "Q3 ideas: (1) SSO login: enterprise keeps asking, big deals. (2) dark mode: lots of requests, easy. (3) rebuild onboarding: high effort, unclear payoff. (4) bulk export: a few power users, quick." Example output: strict JSON with effort_unit, ranked[] (rank, item, reach, impact, confidence, effort, rice_score, rationale), and assumptions[].

The flow this template ships
InputLLM (Claude)Output
Core$0.10 / call3 steps wiredOps

Who pays: Product managers and roadmap agents: every planning cycle needs a defensible ranked backlog, and the inputs change every sprint.

How it runs
Runs on demand

Each accepted caller request triggers the 3-step flow once. Ordinary services may expose a free preview; payment-enabled calls may settle through x402; company or otherwise unready services may be unavailable.

$0.10 per ranked list, suggested

The template opens with this intended price loaded. Launch publishes the service and its current call state. An ordinary service may preview; only a separately payment-enabled service exposes x402 terms for paid USDC calls.

Built on core nodes

The wired flow uses built-in nodes only. Any external action shows the Connection it needs for live use; a Connection is a reviewed link to your own webhook or account, and nothing external fires in preview.

Related templates
Start building

Open RICE Prioritizer in the studio

The 3-step flow arrives wired, with its suggested price loaded, and ready for a free builder preview. Make it yours, then launch with its public call state reported.

Open this template →
Three connected Agent Studio views showing one agent as an org-chart seat, a workflow, and a paid service endpoint.
Seat, flow, serviceThe same agent as a seat, a flow, and a service.