fastbrowse Client Workflow Handoff (Delivery)

fastbrowse Client Workflow Handoff (Delivery)

1. 01

   Confirm the client's named scoped secrets are registered against the permitted origin before any run is scheduled

   Secrets are passed by name and resolved only on the permitted origin, so the value never enters a model prompt. Verify each credential resolves on the exact domain the workflow targets, not a wildcard.

2. 02

   Write the task instruction as natural language plus an optional starting URL, and attach an output schema

   Use a Pydantic or Zod schema so the returned answer is validated structurally. The instruction should name the workflow outcome, not the click path, since fastbrowse indexes page controls and selects actions itself.

3. 03

   Run the workflow once on the Free plan against a public practice site to confirm control indexing works

   Free covers 1 run at a time with 7 day history. Use this pass to catch pages where controls are not indexed as expected before the client sees anything.

4. 04

   Review the step trace and verbatim quotes before reporting the task complete

   Answers cite quoted page text that is checked before a task is reported complete. If a quote does not support the answer, rewrite the instruction rather than accepting the run.

5. 05

   Confirm irreversible actions pause for authorization and decide who on the agency side approves them

   Actions classified as irreversible halt for authorization. Name a single approver per client so checkout or submission steps never sit waiting during a delivery window.

6. 06

   Move the client to Starter at $29 monthly for 5 concurrent runs, 30 day history, secrets, profiles, schedules, and webhooks

   Schedules and webhooks are what turn a one-off run into a retainer deliverable. Wire the webhook to the client's results dashboard so cited answers land without manual export.

7. 07

   Hand the client a run log showing step count, model cost, and session recordings where the plan includes them

   Session recordings and the audit log sit on Pro at $199 monthly with 25 concurrent runs and 90 day history. Quote model spend per run so the retainer conversation is anchored to measured cost.

8. 08

   Document the workflow in the agency runbook with the instruction text, schema, secret names, and approver

   The next operator should be able to re-run or fork the workflow without reading the original build notes. Record which plan tier the client sits on so history retention expectations are explicit.