Operating ProcedureExecution layer

BrowserAct Scraper Handoff to Client Delivery (Handoff)

A handoff with 7 steps: Confirm the pilot scraper's output schema in the BrowserAct dashboard before handoff.

By InnovaAI ResearchPublished

What are the steps?

handoff

BrowserAct Scraper Handoff to Client Delivery (Handoff)

  1. 01

    Confirm the pilot scraper's output schema in the BrowserAct dashboard before handoff

    Open the agent build used for the pilot client and verify the structured output fields (lead name, price, stock status) match what was agreed in the pilot brief. Any field the client asked for but the scraper does not emit gets fixed here, not after handoff.

  2. 02

    Lock proxy and CAPTCHA settings on the agent build

    Check that proxy rotation and CAPTCHA handling are enabled on the build so the client's scheduled runs do not fail silently. Note the static proxy count against the plan ceiling (up to 5 on Basic, up to 50 on Advanced) so the client knows how many concurrent targets the scraper can hold.

  3. 03

    Export the API key and integration credentials to the client's own workspace

    Enable API access in the account settings and issue a key scoped to the delivered scraper. If the client runs Make, n8n, or Zapier, connect the scraper to their instance rather than leaving it on the agency account, so the retainer ends cleanly at handoff.

  4. 04

    Run one live execution against the client's target site and capture the output

    Trigger a manual run and export the structured CSV or Google Sheets output. Compare row counts and field completeness against the pilot baseline; a drop in either signals selector drift that must be resolved before the client takes ownership.

  5. 05

    Write the scraper runbook for the client's operator

    Document the natural language prompt behind each scraper, the schedule, the credit burn per run, and what to do when a run returns empty. Keep it to the fields the client's team will actually touch.

  6. 06

    Walk the client operator through one rebuild from a prompt

    Have them edit the natural language prompt and regenerate the scraper in a live session. This is the step that decides whether the handoff holds, because selector drift is handled by prompt edits, not by code.

  7. 07

    Transfer credit ownership and close the agency-side billing line

    Move the client onto their own plan (Basic at $16/month for 10,000 credits, Essential at $70/month for 50,000 credits, or Advanced at $96/month for 100,000 credits) and remove the scraper from the agency account. Confirm the client's simultaneous task limit covers their run schedule before you decommission anything.