Trustless Campaigns
Trustless Campaigns is Gecko transforms brand-creator deals
Last verified:
What is Trustless Campaigns?
Trustless Campaigns is Gecko is an AI-powered founder review board that runs inside Claude Code, designed to stress‑test startup ideas before any code is written. It orchestrates a five‑agent panel that debates your concept, evaluates market fit, and produces a clear verdict—build, narrow, pivot, or kill—along with a fundable product requirements document (PRD) stored directly in your repo. The tool is aimed at technical founders, senior engineers, and AI‑native builders who already use coding agents but lack a disciplined pre-build review process, so they can avoid shipping products nobody wants.
Trustless Campaigns pricing
Pricing model: Freemium
Preview tier is free for one lightweight idea roast, letting you see how the panel pushes back before funding full runs. Validation runs cost 9–19 dollars per run and include a full adversarial debate, verdict, cited research, and a build/narrow/pivot/kill signal. PRD + ship runs cost 29–49 dollars per run and add a fundable PRD, MVP scope, GTM angle, landing narrative, and first implementation tasks. A founder workspace plan is in development at 99 dollars per month, offering saved projects, repeat validation, export/scaffold workflows, and workspace budget controls. When using optional gecko_route, there is roughly a 10 percent markup on routed agent calls, with per‑call receipts printed in‑terminal and applied to the same workspace budget.
Trustless Campaigns pros
- Adversarial five‑agent panel pushes back on weak ideas
- Delivers a crisp build/narrow/pivot/kill verdict in minutes
- Cited market research and concrete comparables in each run
- Structured PRD artifact stored directly in your repo
- Defined MVP scope with explicit non‑goals and Scope Cop checks
- Clear ICP and wedge statement for early‑stage positioning
- Built‑in personas that enforce product judgment, not chat bot fluff
- Flows naturally into Claude Code workflows without leaving the IDE
- Transparency via per‑call receipts when using routed execution
- Cost‑efficient routing that can reduce agent compute spend vs default paths
- Encourages validate‑first, build‑later discipline for AI‑native teams
- Provides fundable‑style PRD that can be shared with investors or teammates
- Re‑usable workflow for hackathons and MVP studios
- Tight integration with frames.ag wallet and stablecoin‑based agent payments
- Removes need to hand‑write prompts for validation personas
Trustless Campaigns cons
- Claude Code only; no native support for ChatGPT or other IDEs
- Requires familiarity with terminal and CLI‑style workflows
- Stablecoin/workspace setup adds friction for non‑crypto users
- Pricing model based on per‑run validation can add up for frequent use
- Limited governance or Jira‑style issue‑linking for enterprises
- Early‑stage product with some features still coming (e.g., founder workspace)
- Deeply tied to one stack opinion (Next.js + Tailwind + Supabase) that may not fit all projects
- Verdicts and PRDs are only as good as the initial prompt and repo context
- No GUI dashboard; most UX is in‑terminal and in‑repo
- Still relatively niche community and fewer integrations compared to mainstream tools
Frequently asked questions about Trustless Campaigns
What is Gecko and how does it work inside Claude Code?
Gecko is an AI founder review board that runs as an MCP skill inside Claude Code, activating a five‑agent panel to debate your idea, validate product and market fit, and produce a clear verdict and structured PRD before you write code. After installing the tool via a one‑liner script and pasting the skill URL, you can paste an idea into Claude Code and trigger a validation run that streams the adversarial debate into your editor context, then writes the verdict and PRD under .gecko/ in your repo. Workspace funding via frames.ag (email plus USDC) lets agents pay per task under the hood, while the main UX stays in‑terminal and in‑repo, minimizing context switching for builders.
Who is Gecko designed for?
Gecko targets technical founders, senior engineers, and AI‑native builders already paying for coding agents in Claude Code who worry about building the wrong thing too fast. It is especially suited for MVP studios, hackathon teams, and AI‑first builders who want repeatable product‑validation artifacts and a disciplined pre‑build review process instead of relying on chat bots that overwhelmingly agree. The tool is less suited for pure crypto tourists, OpenRouter‑only cost optimizers, or large enterprises that need heavy‑weight Jira governance on day one, since it starts with a validation‑first, lightweight workflow rather than a governance‑first stack.
What does a validation run include?
A validation run includes a five‑agent adversarial debate that produces a verdict (build, narrow, pivot, or kill), cited market research, TAM and comparable analysis, and a clear explanation of why the idea might succeed or fail. It also outputs a structured PRD with ICP definition, wedge line, market risks, MVP scope including acceptance criteria and non‑goals, success metrics, and a product narrative a teammate or investor can read cold. The run ends with ordered implementation tasks that can be pasted directly into Claude Code, and the entire artifact is stored in‑repo under .gecko/ so you can version and share it alongside your code.
How does the adversarial panel work?
The panel consists of five specialized personas: a research analyst that surveys TAM and concrete comparables with citations, a market validator that pushes back on weak demand signals, a technical architect that proposes a concrete V1 stack (typically Next.js + Tailwind + Supabase with Solana when on‑chain primitives are needed), a scope cop that flags V2 features hiding in MVP scope, and a builder that scaffolds implementation tasks aligned with the PRD. Together they simulate a critical founder review board inside your editor, forcing sharper wedge lines, tighter scope, and more realistic assumptions before you commit to building. The output is a single settlement per run, along with a transcript and PRD that stay in your repo for reference.
Can I use Gecko without knowing crypto or stablecoins?
You interact with stablecoins and wallet concepts mainly through frames.ag, which handles email‑based onboarding and workspace funding, so you do not need to be a crypto expert to use Gecko. The tool hides the complexity of on‑chain settlement and per‑task payments behind a simple workspace budget model, focusing your UX on the product‑judgment questions (build/narrow/pivot/kill) rather than the payment rails. Stablecoins are the infrastructure for agent settlements, but you still see only a funded workspace, receipts, and policy limits, not a crypto‑first product narrative.
How does routing and cost‑aware execution work?
When you opt into gecko_route, your Claude Code subagent calls are routed through a task‑hint matrix that aims to lower compute costs compared to default agent paths by selecting more efficient models or routes per call. The workspace budget funds these calls, and per‑call receipts print next to each line in‑terminal, so you can see how much each call costs versus a naive default baseline. There is roughly a 10 percent markup on routed calls, but this is surfaced transparently in‑terminal rather than buried in marketing fine print, and the goal is to keep execution costs lower while still enforcing the product‑judgment decisions made during validation.
What are the current pricing tiers and what do they cover?
Gecko offers a free preview tier that lets you run one lightweight idea roast to see how the panel pushes back before committing to paid runs. Validation runs cost 9–19 dollars per run and include full adversarial validation, verdict, cited research, and a build/narrow/pivot/kill signal. PRD + ship runs cost 29–49 dollars per run and bundle validation with a fundable PRD, MVP scope, GTM angle, landing narrative, and first implementation tasks. A founder workspace plan is planned at 99 dollars per month, providing saved projects, repeat validation, export/scaffold workflows, and workspace budget controls, while optional routed execution adds a small markup on top of the same workspace budget.
How does Gecko integrate with my existing repo and workflow?
Gecko installs via a one‑liner script that adds configuration and agents into your Claude Code workspace, placing personas under .claude/agents/ and artifacts under .gecko/ so everything stays in version‑controlled source. After a validation run, the PRD, MVP scope, and next tasks land in‑repo, and you can paste the implementation tasks directly into your Claude Code session to scaffold the project. The tool is designed to sit alongside your usual build loop rather than replace it, so you keep using your preferred stack and tools while anchoring decisions in the validation artifacts generated by Gecko.
Does Gecko support other agents or IDEs like ChatGPT or VS Code?
Gecko is currently built specifically for Claude Code and Claude Code–style workflows, not for ChatGPT or generic web chat interfaces. It uses the MCP skill mechanism and frames.ag integration to control agent behavior and workspace budgets, which are tied to Claude Code’s environment. While you can copy and adapt PRDs or task lists into other tools, the validation debates, personas, and routing are deeply integrated into Claude Code, so the full experience is not ported to other IDEs or chat agents at this time.
What are the limitations or risks of relying on Gecko for product decisions?
Gecko’s advice is only as good as the quality of your initial prompt, the context you provide, and the information available to the agents; it cannot replace deep domain expertise or user interviews. The tool enforces scope discipline and cited research, but it still operates in a simulated environment and may miss nuanced local market dynamics or regulatory constraints that real‑world founders must navigate. Additionally, because it is still early‑stage and tied to a specific stack opinion and workflow, it may not fit every project or team culture, and some teams may need to adapt or supplement its outputs with additional validation from human stakeholders or external data sources.