Skip to Content
Raydo

Choose a Starter by Goal

Match the expected result to a workflow template.

Start with the result you need to inspect or deliver. A product launch can involve preparing images, gathering research, or submitting a draft to an external site. Each uses a different workflow.

Expected resultTemplate to start withWhat to verify
One result from a capability and one deliverySingle StepOne test input reaches the selected capability and its output reaches delivery.
A decision before a consequential actionApproval Flow or Review before publishA person can see the draft before the action, or the branch clearly separates submit and revise.
A useful handoff after a failed runFailure to InboxRun details retain the failed-node error, and Inbox triage can surface eligible failures.
Three SKU images or a single cutoutProduct Image Batch or AI Cutout / White BackgroundThe provider supports the action, and each result can be matched to its source image.
A brief with sources, or a refreshed knowledge baseDaily AI Brief or Customer Knowledge UpdateSource scope and citations for the brief, or the actual knowledge base and a test question for an update.
A web submission with evidenceBrowser + Desktop Submission AuditAccount, form fields, attachment contents, approval, and a receipt paired with the browser and desktop evidence.
Follow-up, launch, onboarding, or escalationSales Follow-up, Campaign Launch Pack, Customer Onboarding Pack, or Support Escalation ResolutionThe matching lead, campaign, customer, or ticket data and the exact destinations for each action.
A packaged result or an inspectable local previewArtifact Flow or App Capsule deliveryThe artifact source, the output, and who can open the delivered result.

If the result will go to a real account or service, choose the review and evidence steps by risk before connecting the action. For a template close to your process, adapt the draft and verify one change at a time.

Choose a Starter by Goal