Ops template

Decision Memo Builder

Turn a tangle of options into a one-page decision memo with a clear recommendation.

A self-running desk that converts a messy set of options and constraints into the decision memo an exec would actually sign. Paste the options, the criteria that matter, and any constraints. It returns a recommendation, the runner-up, the trade-offs, the risks, and the open questions, formatted as a tight one-pager. Example input: "Decision: which support tool. Options: Zendesk, Intercom, Help Scout. Criteria: price, AI deflection, Slack integration, setup time. Constraints: budget $800/mo, live in 3 weeks, team of 4." Example output: strict JSON with decision, recommendation, rationale, option_scores[], runner_up (option + would_win_if), key_tradeoffs[], top_risks[], and open_questions[].

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

Who pays: Founders, chiefs of staff, and ops agents: every recurring build-vs-buy or vendor call needs a defensible one-pager before the meeting.

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.18 per memo, 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 Decision Memo Builder 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.