Two AI Service Walkthroughs: From Brief to Client-Ready Delivery
Follow a five-account research brief and a two-clip video pilot, with example outputs, copyable prompts, review checks, and delivery templates.
Start with a deliverable you can inspect and a buyer who can explain what makes it useful. These two practice walkthroughs show how to prepare a small research brief or video package, review it, and hand it over without promising income you have not earned.
Set up Cameron and the handoff rules
Select and copy the prompt. Replace the bracketed fields with your own information.
You are Cameron, the coordinator for this one workflow. Use only the context I supply or sources you can actually open. Tell me which tools and delegation features are available before starting. If you cannot create subagents, complete the roles sequentially and label each handoff. Do not imply a role prompt installed a persistent bot. Return: task ID, owner, input version, output, source references, unknowns, review status, and next action. Stop when essential information is missing. Keep client data limited to what this task needs. Do not send, publish, spend, create accounts, or change live systems without approval of the exact action. Use the run's stated time and cost limits. No invented sources, quotes, contacts, or results.
Example 1: deliver a five-account research brief
Imagine a freelance web designer wants to understand which local businesses match a new booking-page service. Your pilot deliverable is a researched shortlist. Selling a list of “guaranteed buyers” would promise something your research cannot establish.
1. Agree on the delivery before researching
You + Cameron
Write a one-paragraph scope. Confirm what the buyer needs to decide and which records should be excluded.
Ready to continue when: you and the buyer could use the same checklist to accept or reject a row.
Copy the step 1 prompt
Select and copy the prompt. Replace the bracketed fields with your own information.
Cameron: turn this buyer request [paste] into a small research-brief scope. Include fields, fit rules, sources allowed, exclusions, acceptance criteria, revision limit, and questions I must resolve first. Return a draft scope, not a contract or sales claim.
2. Build the brief with evidence attached
Cameron → Scout
Research one account first and review the row before asking for four more. Use real accessible sources when you run your own version; the row below is a structure example only.
Ready to continue when: the first row passes review and no unsupported fact is being repeated across the batch.
Copy the step 2 prompt
Select and copy the prompt. Replace the bracketed fields with your own information.
Scout: create one row using [source] and [approved fit criteria]. Show exact observations, source URL, date checked, and unknowns. Leave missing contact fields blank. Do not infer buying intent. Wait for my review before expanding to a maximum of five rows.
3. Check the sample as if you were the buyer
You + independent reviewer
Open every source. Recheck location, service category, duplicate records, and exclusions. A second role can review evidence, but you own the final judgment.
Ready to continue when: all accepted rows are supported and any unfinished portion is explicit.
Copy the step 3 prompt
Select and copy the prompt. Replace the bracketed fields with your own information.
Reviewer: audit each research row [paste] against the buyer checklist. Return pass, fail, or blocked with the exact evidence. Check duplicates and exclusions. Do not fill gaps from guesses. Cameron: summarize corrections and the current accepted-row count.
4. Deliver something the buyer can use
You → buyer; Gauge records
Package the approved rows as a readable sheet or document. Include the scope, checked date, unknowns, and what is outside the service. Agree on delivery and revisions before taking paid work.
Ready to continue when: the file opens, source links work, the scope matches, and the recipient knows how to request the agreed revision.
Copy the step 4 prompt
Select and copy the prompt. Replace the bracketed fields with your own information.
Cameron: prepare a delivery note for [approved file and scope]. List what is included, unresolved questions, and the agreed revision process. Gauge: record actual delivery time and costs. Keep a draft invoice, an unpaid invoice, and a collected payment in separate states.
Example 2: turn an owned video into two finished clips
Use a short source video that you own or have written permission to edit. Frame’s first output should be an edit plan. A transcript, timestamps, and captions are preparation; the deliverable is the actual exported video file.
1. Approve the clip plan before rendering
You → Frame
Give Frame the source file, target channel, audience, central point, and delivery format. Start with two clips rather than a large package.
Ready to continue when: the selected passages make sense on their own and preserve the speaker’s meaning.
Copy the step 1 prompt
Select and copy the prompt. Replace the bracketed fields with your own information.
Frame: inspect this permitted source [file/transcript] and propose two clips for [audience/channel]. Return timestamps, exact spoken excerpt, hook, closing beat, caption plan, and required files/tools. If you only have a transcript, say that the visual and audio review is still pending. Do not claim rendered clips exist.
2. Render and inspect the actual files
Frame → You
Use your configured editing tool to create the files. If the agent cannot render video, use the edit plan in your editor; do not label the plan a finished video.
Ready to continue when: both exported files play, meet the agreed format, and pass the content review.
Copy the step 2 prompt
Select and copy the prompt. Replace the bracketed fields with your own information.
Frame: render the two approved clips using [available tool]. Return the actual files, dimensions, duration, captions, and review checklist. If a tool or source file is missing, stop and list it. Do not substitute a storyboard for a rendered file or publish to social channels.
3. Package the pilot and record its cost
You + Gauge
Deliver the approved files, caption text, source references, and the agreed revision scope. Record the total effort, including setup and failed exports.
Ready to continue when: the buyer can open every file and the agreed revision process is clear.
Copy the step 3 prompt
Select and copy the prompt. Replace the bracketed fields with your own information.
Gauge: summarize this pilot’s actual setup, editing, review, correction, export, and handoff time plus tool costs. Record acceptance and payment only when supported. Cameron: suggest one improvement to scope or process before I repeat the service.
Set a price after you understand the work
For a practice calculation, suppose a two-clip pilot takes 2.5 hours including review, and direct costs are $10. At a chosen $30/hour labor allowance, the cost basis is $85 before other overhead and tax. A proposed $125 test price leaves $40 above that stated cost basis. Those figures are an illustration, not a market-rate recommendation or expected profit. Replace them with your own timing, costs, and buyer feedback.
Let Forge add one useful reviewer
For the research brief, add a source checker. For clips, add a caption checker. Keep the reviewer’s access limited to the accepted brief and output; a review role does not need payment access or permission to contact customers. If your platform cannot spawn agents, use the reviewer prompt as a separate pass.
Copy the reviewer setup prompt
Select and copy the prompt. Replace the bracketed fields with your own information.
Forge: propose one reviewer for [research brief or clips]. It must compare the accepted scope with the actual output, return pass/fail/blocked with evidence, and stop after one review. No child agents, sending, publishing, or spending. Test missing input, an intentionally incorrect claim, and a complete valid sample. Explain whether this host supports actual spawning or requires a manual review pass.
Watch the handoff, then try it
Read the animation instead
You set the goal; Cameron assigns bounded work; specialists return evidence and drafts; Cameron packages a decision; you approve the defined action; Gauge records what happened.
Try another worked example
- Shape an offer with Waymaker
- Build the Agency lead-to-booking workflow
- Run the Wealth Experiment cost-and-time review
By Ashley Kays Rabbitt. Updated November 18, 2026. The named specialist roles are workflow templates; available tools and automatic delegation depend on your chosen platform.