The scoping call
The first step is a one-hour call. You describe what you need. We ask about the workflows you want to automate, which tools are involved, how you want approvals to work, and what a good outcome looks like.
By the end of the call, we have a defined scope: which workflows, which integrations, which agent configurations, and what the approval thresholds should be. Nothing is built until that scope is agreed.
You do not need credentials, admin access, or technical preparation before this call. It is a conversation about how your business works — not a technical handoff. Access comes later, once the scope is agreed.
What we configure
Once the scope is signed off, configuration work begins. This covers:
Agent setup
We create the agent configurations, write the system context for each workflow, and set the monitoring logic for the triggers you have approved.
Integrations
We connect to your tools — Gmail, Slack, Notion, Xero, or whichever are in scope — and configure each with the minimum permissions required.
Trigger logic
We define what conditions cause the agent to produce a draft: email patterns, invoice states, CRM field changes, time windows.
Draft templates
We write the base draft templates for each workflow — the starting point the agent adapts for each specific situation.
Approval flows
We configure the approval thresholds, set which actions require double confirmation, and test the full flow end to end.
Your time in the process
A standard implementation requires roughly three hours of your time:
| Your involvement | Time |
|---|---|
| Scoping call | 60 min |
| Review session | 60 min |
| Final sign-off and go-live | 30 min |
The rest — configuration, integration, testing — is done by us. You are not in the details of the build. You review the output.
You describe what needs doing. We build it. You review before it goes live.
Handoff
At the end of the engagement, you have a working setup and the keys to it. The handoff includes a usage guide — what triggers what, how to approve drafts in Slack, how to adjust thresholds — and a channel to request configuration changes or add new workflows.
The system is yours to run. We are not a required dependency after handoff. Ongoing support and additional workflows are available, but not the baseline expectation.
What's out of scope
ClawBuilt handles the OpenClaw configuration. We do not manage your IT infrastructure or server provisioning, write custom integrations for tools outside the supported list, or scope and build workflows that were not agreed on the initial call.
If your needs go beyond the standard scope — non-standard integrations, complex multi-agent setups, regulated-environment requirements — we discuss that on the scoping call and price it separately.