Grabbit Client Capture Workflow Handoff (Onboarding)
A handoff with 7 steps: Provision the API key and confirm CLI login.
By InnovaAI ResearchPublished Updated
What are the steps?
Grabbit Client Capture Workflow Handoff (Onboarding)
- 01
Provision the API key and confirm CLI login
Create the key in the Grabbit dashboard, then run `npx grabbit.live login` on the delivery machine so the agent runtime (Claude Code, Codex, OpenClaw, or Cursor) inherits the credential. Store the key in the agency's secret manager, not in a client-facing doc.
- 02
Send one test POST /grabs against a client URL
Confirm pixel-perfect output, cookie-banner dismissal, and full-page capture before any client URL is added to the production queue. A failed test here costs minutes; a failed test after handoff costs a retainer conversation.
- 03
Map target URLs and capture parameters
For each client URL record full_page, width, format, selector, and wait time. Selector-targeted crops are the parameter most likely to break when a client redesigns, so note the selector owner on the client side.
- 04
Validate webhook signatures and delivery destination
Point async grabs at the client's storage or email endpoint and verify the signed webhook lands. If the client has no endpoint, deliver to branded cdn.grabbit.live URLs and hand over the URL list instead.
- 05
Size the grab volume against the plan
The Annual tier covers 25,000 live grabs per year; Scale tops up 50,000 for $100 or 125,000 for $250. Usage-based grabs run $0.002 each, so a client capturing 40,000 pages a month needs a volume conversation before onboarding, not after the first invoice.
- 06
Write the client-facing runbook
Document which URLs are captured, on what schedule, where images land, and who to contact when a capture fails. Include the idempotent and SSRF-guarded behavior so the client's security reviewer has an answer without a call.
- 07
Hand off to the delivery owner with a 14-day check
Assign one named operator, log the handoff date, and schedule a check at day 14 to review failed grabs and selector drift. Agencies that skip this step discover broken captures when the client does.
More on Grabbit
- StrategyWhy Grabbit Turns Screenshot Capture Into Agency Retainer Infrastructure
- ConceptGrabbit Grab-Volume Margin Curve
- Evaluation RuleWhen to Adopt Grabbit: Usage Volume Must Clear the $0.002/Grab Math Before You Resell It
- Decision FrameworkGrabbit: Buy vs Skip (Agent Screenshot Capture for Client Deliverables)
- Failure PatternThe Grabbit Per-Grab Margin Trap: Why Agencies Fail With Usage-Based Screenshot Pricing
- Implementation BlueprintGrabbit Managed Screenshot Service Build (7-10 days)