Real example: the AI income experiment guide on this site was authored, connected to the training and blog pages, checked, published through GitHub and Railway, and verified on the live site. The steps below turn that pattern into a reusable website workflow. They do not claim a measured time saving or commercial result.
Step 1 · Human + product lead
Brief the job
Write the audience, visitor problem, one primary action, required content, exclusions and definition of done. For a service page, define what a visitor must understand before contacting you.
Leave with: A one-page brief with acceptance criteria.
Review before continuing: Can someone describe the purpose without seeing a mockup?
Step 2 · Research + developer
Inspect what already exists
Read the current site and source before changing anything. Map the existing navigation, forms, content sources and deployment path. Record what to reuse.
Leave with: A current-state note and a bounded change list.
Review before continuing: Are you editing the source that generates the page, rather than an output that the next build overwrites?
Step 3 · Designer + content worker
Design one journey
Sketch the path from headline to evidence to action. Use Figma if a visual prototype will resolve a question. Prepare realistic content and an image brief. Keep text out of images when it needs to remain selectable.
Leave with: A page outline or prototype and reviewed copy.
Review before continuing: Can users find the offer, understand the next step and use it on a small screen?
Step 4 · Development worker
Build a reviewable version
Give the builder the approved brief and existing design rules. Ask for the smallest change set, meaningful error states and accessible controls. Keep credentials out of public code.
Leave with: A preview or branch with an explanation of the changes.
Review before continuing: Do links, forms, keyboard focus and empty states work? Does the page preserve existing behavior?
Step 5 · QA + human approver
Review and publish
Run relevant build and link checks. Inspect the actual page, including mobile layout. Confirm the intended audience and deployment target before publishing. Keep a known prior version for rollback.
Leave with: A reviewed release and live URL.
Review before continuing: Does the live URL contain the intended version and serve its images and downloads? A successful build alone is not live verification.
Step 6 · Measurement worker + human
Observe and improve
Choose one meaningful action such as a completed inquiry. Record visits and qualified actions, with consent-aware analytics where configured. Ask users where they hesitate.
Leave with: An observation log and one next improvement.
Review before continuing: Do not call a page successful because it is live. Missing evidence remains unknown.
Copy the starter prompt
Use this approved website brief and the existing project files. First identify the content source and current user journey. Propose the smallest implementation. Return changed files, checks run, unresolved issues and publication steps. Do not invent testimonials, results or unavailable features. Ask before actions outside the approved scope.
Where this workflow can break
A polished screenshot can hide a broken form. Agents can also edit generated files, replace valid links or add unsupported claims. Require source-level changes, functional checks and a live read-back.
Your practice assignment
Create one offer page or improve one existing page. Stop when the intended visitor can understand the offer and complete the primary action. Do not expand into a complete application to finish this exercise.
Get the brief, handoff and review templates
Keep a useful result log
Record what you attempted, what you accepted, corrections, cash spent, total human time and the next decision. A published output or completed lesson is an artifact; demand, learner performance and business results require separate evidence.
Explore the other workflows
Create a useful course with an agent team · Research and test an income idea with agents