Our process
We turn a real business workflow into a working Claw.
Island Workflow does not start with generic AI. We start with the place work is already leaking: missed calls, slow follow-up, scattered customer context, repetitive questions, website forms that do not hand off cleanly, or decisions that need human approval before anything moves.
New to AI agents? Learn the shape first.
If you are still getting oriented, start with the short Google Cloud explainer now embedded near the top of our homepage, then use the AI Guides to match the idea to a real business pressure point. The paid process begins when we map your actual tools, channels, approvals, handoffs, and launch path.
Education
Understand the agent idea first
The homepage video gives a quick, non-Island-Workflow explanation of what an AI agent is before we talk about a Claw.
Watch on the homepageFit
Choose the workflow that hurts most
The AI Guides explain common front desk, follow-up, property, clinic admin, and Vancouver Island business automation paths.
Open the AI GuidesFirst paid step
Map before building
A Claw Readiness Session turns the pressure point into a practical scope, boundary map, and launch recommendation.
Book readinessDiscovery and fit check
Usually 20–30 minutes before the call
We collect enough context to avoid a vague sales conversation. The goal is to understand the business, the current tools, the website or intake path, and the workflow that is costing time, revenue, or trust.
- Business profile, team structure, service area, and offers
- Current tools, website, phone/message channels, documents, and access requirements
- Lead sources, customer touchpoints, and handoff points
- The first pressure point worth solving instead of every possible automation idea
Claw Readiness Session
Typically 60–90 minutes
This is the safest first paid step. We map the real workflow into build material: what the Claw should notice, say, summarize, ask, route, and never do without approval. By the end of Readiness we also know which setup path fits — and you have not committed to anything bigger than the session itself.
- Walk through the customer journey from first inquiry to finished work
- Identify the first useful workflows instead of overbuilding the system
- Capture tone, escalation rules, sensitive boundaries, and approval requirements
- Produce the build brief, integration map, open questions, and a recommended setup path
Choose the setup path that fits the work
Decided with you at the end of Readiness
Not every business needs a dedicated private system on day one. Some need to clean up one painful intake leak; some need a steadier office loop; some are ready for a deeper owned build. Readiness ends with a clear recommendation — and the three options share the same Claw thinking, just with different reach and ownership.
Basic organizes the mess. Pro keeps things moving. Full Build supports the whole workflow.
Cloud-Hosted Basic
Get the front door under control
One main intake channel becomes a clean, organized stream: approved questions answered, requests captured with the details you actually need, weekly summaries that make the leak visible. A managed hosted starting point — small enough to say yes to, useful within the first month.
Cloud-Hosted Pro
Keep the office loop steady
Two or three channels, routing rules, reminders, light scoped integrations, and daily visibility so quotes, follow-up, and handoffs stop depending on someone remembering to check. Still hosted and bounded — for teams whose pain is the loop, not the platform.
Self-Hosted / Full Build
Own the operation end-to-end
A dedicated private Claw built around your business — deeper integrations, custom workflows, stronger privacy and control, approved self-hosted hardware where included, and long-term ownership. The right choice when the Claw is becoming part of how the office actually runs.
If you are not sure which path fits, the answer is almost always: start with Readiness and let the workflow tell us. Moving up later is straightforward; building too much too soon is the expensive mistake.
Pair the required Runtime
Selected alongside the setup path; minimum 12-month term
Every Claw needs a Runtime package, whichever setup path you pick. Runtime is the working capacity your Claw uses to read incoming requests, reason through context, summarize what staff need to see, prepare handoffs, and keep approved follow-up moving. It is metered and managed separately from setup and Cloud hosting so pricing stays honest about what each piece is actually paying for.
- Setup builds and configures the Claw to your business
- Cloud hosting (Basic/Pro) keeps the Claw online, backed up, monitored, and available
- Runtime is the working capacity behind every read, reason, summary, handoff, and follow-up the Claw performs
- We choose the Runtime tier with you based on volume, channels, and how active the Claw needs to be
Build, launch, and team walkthrough
Cloud setups launch in days to a few weeks; Full Builds plan around a month, including any hardware shipping
We build the Claw against the Readiness brief, prepare the launch environment, run real business scenarios end to end, and bring your team through it together. Nothing goes live until your team has seen the Claw handle real examples and signed off on the escalation and approval rules.
- Agent identity, approved knowledge, boundaries, prompts, and workflows configured
- Connections to approved tools, channels, website forms, calendars, documents, and inboxes verified
- For Full Builds: approved hardware received, inspected, prepared, and shipped where included
- Live walkthrough so the team sees how the Claw handles routine, urgent, and out-of-scope cases
- Launch acceptance checklist, backups, and immediate follow-up notes
Tune, support, and grow
Ongoing, as the business changes
After launch there are two ongoing needs: keeping the Claw running cleanly, and improving the workflow as the business changes. Runtime stays paired with the Claw for at least 12 months. Remote Support is there when something needs tuning, a new FAQ added, a workflow reviewed, or a small new capability scoped.
- Runtime keeps the Claw’s working capacity available for the approved workflows
- Remote Support starts with a CAD 300 two-hour assessment, then CAD 150/hr for additional time
- Urgent or after-hours support is quoted separately when needed
- Seasonal updates, website changes, new channels, and deeper integrations get scoped as follow-on work
Strategy call question spine
The questions we script around
These questions are designed to produce a better Claw build, not a vague sales conversation.
- What would feel different 90 days from now if this Claw worked perfectly?
- Where do leads, messages, approvals, or tasks usually slip through the cracks?
- What software, website forms, phones, inboxes, calendars, documents, or spreadsheets does the workflow already depend on?
- What do customers repeatedly ask, wait for, misunderstand, or complain about?
- Which steps must always stay human-approved?
- If we only built three useful workflows first, which three would remove the most stress or protect the most revenue?
- Does the website itself need to change before the Claw can capture leads or hand off cleanly?
Required pairing
Every Claw needs a Runtime package.
During Readiness we choose the Claw depth and the Runtime package together. The Claw setup builds the system. Cloud hosting keeps it online. Runtime is the working capacity it uses to read, reason, summarize, hand off, and follow up. Runtime is required for a minimum 12-month term for Cloud and Full Build setups.
Ready to map the first Claw?
Start with the Readiness Session if you want the safest first step. If the website, lead capture, or forms are the first blocker, we can include that in the same discovery path before recommending a Full Build.
Book a Claw Readiness Session
Island Workflow