Browser Use Client Workspace Setup (Onboarding)

Browser Use Client Workspace Setup (Onboarding)

1. 01

   Create the client workspace and issue a scoped API key

   Generate a dedicated API key per client in the Browser Use dashboard so task initialization ($0.01 per task) and browser session hours ($0.02 per hour) can be attributed to that account rather than pooled across the agency.

2. 02

   Select the billing surface before the first run

   Choose Browsers at $0.02 monthly for client-owned agents the agency operates, or Browser Use Agents (custom pricing) when the client wants tasks submitted and run by the hosted agent. Enterprise adds custom concurrency, custom SLAs, custom data policy, and HIPAA support with zero data retention for regulated clients.

3. 03

   Configure stealth session settings for the target site

   Enable anti-detection and CAPTCHA handling on the browser profile, then confirm the target domain tolerates the session pattern before scheduling anything recurring.

4. 04

   Write the first task in natural language and validate output

   Describe the extraction or form-filling job as a plain-language task, run it once against the client's real target page, and diff the returned data against a manual pass before it touches a deliverable.

5. 05

   Capture the working interaction as a reusable skill

   Save the validated site interaction to the skills system so repeat runs do not re-derive navigation logic, which keeps token spend down on Claude Opus 5 output billed at $30 per 1M tokens.

6. 06

   Set the task schedule and failure alerting

   Attach the run cadence to the client's reporting cycle and route failure notifications to the delivery lead, with a 48 hour resolution window written into the retainer terms.

7. 07

   Hand the run log and cost baseline to the account owner

   Deliver the first month's task count, session hours, and token spend so the agency can set a pass-through rate before the retainer renews.