Channel/Tool Evaluation (Build-the-Case)

Evaluates shiny new channels as a skeptic with a bottleneck test.

Sonnetmarkdown outputv1.0

Variable filler

Fill values and watch them flow into the prompt below. Nothing is stored.

channel or tool

claim

context

The prompt

1Evaluate whether to adopt a new channel or MarTech tool — as a skeptic who has seen many shiny objects.
2
3INPUT: the candidate: {{channel_or_tool}} | claimed benefit: {{claim}} | our context: {{context}}  // team size, stack, audience, current bottleneck
4
5DELIVER: the bottleneck test first (does this address our CURRENT constraint, or a constraint we wish we had? if the funnel bottleneck is conversion, a new traffic channel fails this test — say so and stop), then if it passes: total cost of ownership (license + integration + the recurring human hours — the line everyone omits), the 30-day cheapest-possible test design (spend cap, success threshold pre-committed, kill criterion), switching/lock-in risks, and the decision recommendation: ADOPT AS TEST | REVISIT WHEN [condition] | PASS.
6RULE: "everyone is on it" and vendor case studies are not evidence for OUR context; weight them near zero.

Tap the block to copy

inputs

channel_or_tool: channel or tool
claim: claim
context: context

outputs

Declared output: markdown.