---
name: verify-prerequisites-product-customers-content
description: "Check what you sell and the proof that it helps. Do this before you pay for ads."
category: Dollar a Day Campaigns
stage: Promote
definitive_article: /dad
status: complete
---

# Verify prerequisites (product, customers, content)

Ads help more people see what your business does. Before you spend, check that the offer helps people and that you have proof to share. This guide helps you find what is ready and what needs work.

**The path:** Real offer → customer proof → useful content → honest decision.

**Use this when:** Paid amplification is proposed for a business or offer, or a previous prerequisite gap has been repaired.

## Inputs
- Permitted evidence of real sales, delivery, customer response and unit economics; an actual business owner who can resolve missing facts.
- Source reviews/testimonials and reuse rights; recent organic posts and their available metrics.
- The proposed goal, audience and budget context; a tracker for the three findings and next owner.

## First-run prompt

> Check this offer, customer evidence and organic content before paid amplification. Link the evidence for each finding, mark missing facts unknown and give a clear ready, needs-work or hold decision. Do not create reviews, invent sales or treat a catalog status as permission to spend.

## Steps
1. Name the exact offer and buyer need. Read evidence of actual delivery and customer value, not only the owner’s pitch. A launch for a new offer needs that gap stated rather than borrowing another offer’s proof.
2. Check the product/service case with appropriate records: real purchases, fulfilled work, referrals or repeat use where relevant. A long-life service may not have repeat purchases within a short window; judge its actual buying cycle instead of forcing that sign.
3. Review the available margin and target acquisition cost with the business owner’s records. Keep gross revenue, margin and allowable ad cost separate. If the economics are not supplied, mark the financial premise unknown rather than inventing a target.
4. Collect at least three verifiable instances of positive customer experience for this source task’s proof check, when available. Verify the original review or testimonial and permission for reuse. Do not solicit only positive reviews, pay for praise or turn an anecdote into a fabricated endorsement.
5. Inspect the actual organic content and its useful signal. Use comparable recent posts, comments, shares and watch data. Strong content means evidence of relevance, not a polished video or a famous name alone.
6. Record each of the three prerequisites with linked evidence and a clear finding: ready, needs work, or unknown. A ready finding has a reason. If a needed premise is weak or unknown, the paid-launch step remains pending even though the inspection itself can be finished.
7. Route the exact gap: service/value to the operations owner, customer-proof verification to the evidence owner, or missing useful content to the content owner. Do not claim another skill will manufacture genuine customer delight.
8. When the required premises are supported, write the [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/) baseline and hand over to measurement/budget planning. Passing this inspection is not a spend authorization or proof that any campaign has run.

## Definition of done (QA checklist)

- [ ] The exact offer and business evidence support the product finding.
- [ ] Customer proof is verifiable, permissioned and not manufactured.
- [ ] Organic content has relevant source metrics or a stated gap.
- [ ] All three findings preserve unknowns and name the next owner.
- [ ] Readiness, budget authority and actual campaign outcome are separate states.

## Example(s)

**Fictional teaching example:** A repair shop has real completed jobs, three verified customer reviews and a seat-fix clip with useful questions. Its owner has not supplied the margin or target lead cost. The report marks product delivery and customer proof as supported, and the paid-cost premise as unknown. The operator can finish this inspection and route the missing economics to the owner. It does not invent a target to pass the gate or claim the clip has already brought paid customers.

## Handoff and Content Factory context

Supported premises go to [set up digital plumbing pixels tracking](https://local-service-spotlight.github.io/task-library/?task=set-up-digital-plumbing-pixels-tracking#task-set-up-digital-plumbing-pixels-tracking) and [identify signals worth amplifying](https://local-service-spotlight.github.io/task-library/?task=identify-signals-worth-amplifying#task-identify-signals-worth-amplifying). The actual business, evidence or content owner receives each named gap before the affected paid step proceeds.

This task is in Promote within the [Content Factory](https://blitzmetrics.com/content-factory/). Produce gathers real source material; Process makes useful assets; Post places and checks them; Promote distributes suitable work within its own scope. Use the proof and checked posts from earlier stages; a Promote task does not automatically redo all four stages. Use the actual next step above; catalog neighbors are not prerequisites.

## When this runs

Run before a new paid-amplification plan and after meaningful offer or evidence changes. Recheck a prior gap when new proof arrives. This is not a mandatory new recurring schedule.

## First-run setup and continuity

Open the supplied task file and its linked source. Verify the project’s real inputs, account, access and output folder before work. This Markdown file is a guide; it does not install an app, connect an account, supply a subscription or create a schedule. Carry out work already authorized; do not ask for the same approval again. Keep any unsupplied destination or new action outside that scope clearly pending.

Save source IDs, versions, decisions, checked outputs and next owner in the project tracker. Before a retry, check the saved state and other workers’ changes. A model name does not guarantee memory or a running timer. Repeated work needs an actual configured trigger and durable state; one-off work can be started by the prompt above.

Keep agent media muted with volume zero before playback. If mute cannot be verified, use captions, metadata or still frames. State the limit: silent visual checks do not prove spoken-word accuracy or audio quality. Do not start sound through the user’s speakers unless explicitly asked.

## Write up the real run

For every actual attempt, [write its meta article](https://blitzmetrics.com/meta-article-prompt/) with this recipe and revision, trigger, steps performed, output evidence, measured result, gaps and next owner. Failed, blocked and partial attempts also get a written record. A draft can satisfy writing; publishing it follows the existing job scope.

Keep one stable execution ID across retries and edits. A separately scoped child task may have its own ID linked to its parent. Writing the parent’s meta record is part of that run, not an endless new chain. The [recipe and meta-article guide](https://localservicespotlight.com/meta-articles/) explains this distinction. Teaching examples are not real executions and must not enter the run count.


<!-- factory-layer:start -->

## Factory chain (do not treat this as isolated)

- **Phase:** Promote
- **Importance:** 5/5 `●●●●●` — frequency 3, revenue 5, gating 5 (ads/revenue path; unblocks a chain (access/plumbing))
- **Suggested previous station:** —
- **Suggested next station:** —
These stations are generated neighbors, not verified prerequisites or handoffs. Follow the task’s actual Inputs and Handoff sections.
- **Handoff:** Organic metrics CSV (or Ads Manager export), pixel ID, creative filenames, kill/scale log. Next week's ranking starts from this file.

## Model routing (same factory, any engine)

- **This task's lane:** `computer` — Logged-in UI (Meta Ads Manager, Descript, GSC, wp-admin when REST is blocked). Requires a supported browser tool and the right account access.
- **Single-engine path:** Use the capable AI app you already have. Check its required tools and access before starting. Pass the actual result and proof to the next task.
- **Optional multi-engine:** A tested local model may draft; a stronger model may review facts and voice. Use supported tools for approved actions. Pick models from observed quality and cost; a model name does not prove it can run this task.
- **Never** store the working state in one vendor's memory. Files in the Content Library are the bridge.

<!-- factory-layer:end -->
## Definitive article & links

- Maintained method: https://blitzmetrics.com/dollar-a-day/
- Source mapping needs reconciliation: the preserved `definitive_article: /dad` points to the coaching program. The method page above is `/dollar-a-day/`; this record does not certify the coaching page as a task recipe.
- Exact task: [Verify prerequisites (product, customers, content)](https://local-service-spotlight.github.io/task-library/?task=verify-prerequisites-product-customers-content#task-verify-prerequisites-product-customers-content)
- Writing standard: [Article Guidelines](https://localservicespotlight.com/article-guidelines/)
- [Dollar-a-Day method](https://blitzmetrics.com/dollar-a-day/)
- [Goals, Content, and Targeting](https://blitzmetrics.com/gct-business-strategy/)
- [One-minute video guide](https://blitzmetrics.com/one-minute-video-guide/)
- [Content Factory](https://blitzmetrics.com/content-factory/)

## Review and evidence still needed

The source contributor status is preserved. It is not certification of this draft or proof of account access, completed work or a live outcome. The worked example teaches the method and is explicitly fictional.
- No actual sales records, customer permissions or financial target is supplied here.
- Three examples support a source checklist; they do not prove universal customer satisfaction or a future paid result.