Saltar al contenido
Chandler Nguyen
Volver a todas las plantillas

Plantilla

AI Builder Reality Check para marketers

Decide si estás listo para construir una primera parte útil de producto con IA, e identifica qué se romperá primero si empiezas ahora.

Ideal paraMarketers que usan Claude Code, Codex, v0, Replit o herramientas parecidas, pero no lanzan con consistencia · Operators con prototipos pero sin camino real de usuario · Senior marketers decidiendo si seguir como power users de IA o convertirse en builders · Consultores que convierten conocimiento de dominio en un pequeño producto o herramienta interna

Campos de la plantilla

  • User and painful job
  • First useful slice
  • Proof that someone wants it
  • Current artifact or prototype
  • Weakest assumption
  • Data or workflow dependency
  • Review standard
  • Launch risk
  • Next 14-day build commitment

Ejemplo trabajado

A marketer trying to build an internal campaign QA assistant.

Los ejemplos completados de abajo están en inglés.

Versión débil vs versión sólida

Versión débil

User
Marketing team
First useful slice
AI assistant for campaign QA
Proof
Everyone says QA is annoying
Weakest assumption
Need better prompts
Launch risk
Bugs
14-day commitment
Build MVP

Por qué falla

  • "Marketing team" is not a user.
  • "AI assistant" is too broad.
  • The proof is hearsay, not behavior.
  • The weakest assumption ignores source data, approval rules, and workflow ownership.
  • "Build MVP" is not a commitment.

Versión sólida

User
Paid media manager checking campaign launch settings before client approval
First useful slice
A checklist reviewer that compares campaign setup notes against required client launch rules
Proof
Two managers already use a manual spreadsheet before every launch; mistakes still reach strategist review
Current artifact
One sample launch checklist, three anonymized campaign setup notes, and one failed QA example
Weakest assumption
The checklist rules are explicit enough for AI to evaluate without platform access
Data/workflow dependency
Client launch rules, platform screenshots, naming conventions, approval owner
Review standard
Flag missing budget, geo, naming, tracking, claim, and approval evidence; never approve launch automatically
Launch risk
False confidence before a client-visible campaign goes live
14-day commitment
Build a reviewer for one client and one platform, then test against five past launch packets

Por qué funciona

  • The user is specific.
  • The first slice is constrained.
  • Proof comes from an existing workflow.
  • Launch risk is clear.
  • The commitment creates evidence, not just more code.

Qué revisar en tu versión

  • Whether the first useful slice is still too large
  • Whether the user is real or imagined
  • Whether there is proof beyond personal excitement
  • Whether the artifact standard exists before the build starts
  • Whether the hard part is product judgment, data access, approval, or implementation
  • Whether the next step should be reality check, build brief, build plan, execution lane, or launch gate

Siguiente paso

¿Creaste una herramienta de IA en tu portátil? Repasa lo que necesita antes de que tu equipo dependa de ella.

Disponible en English, Tiếng Việt, 日本語, 简体中文, 繁體中文

Empezar el camino gratis