ConvertSail had ample tools. What it lacked was a dependable authority path between them: an assistant could inspect the wrong connection, report that a live account was disconnected and lose the team's trust in a single response.
Evidence at publication: six configured agents, 25 bindings and active Caddy, Command Center, Claw3D, billing-proxy and OpenClaw services were verified on 30 May 2026. The source does not retain a measured adoption or commercial result, so this case remains built with adoption evidence pending.
The company
Alex Momeni runs ConvertSail, an agency and e-commerce growth operation. Client delivery crosses Meta Ads, Google Workspace, QuickBooks, Calendly, Fathom, Slack, Discord, email, landing pages and internal command views.
Each surface contains a different piece of the work. Fathom holds meeting context. Calendly holds booking state. Meta holds acquisition performance. Team channels hold current instructions. QuickBooks covers a finance lane. A useful operator has to know not only how to reach those systems, but which route is authoritative for each one.
The constraint
Context and action were separated. If the system checked Composio for a Meta account already connected through a native wrapper, it could produce a false disconnection. If it asked for Google Docs authorization through Composio when Google Workspace already used gws-auth, it added friction instead of removing it.
Communication created a second constraint. The assistant needed to respond when an authorized teammate moved delivery forward, yet remain quiet during ordinary Slack conversation. A system that misses real work is unreliable; one that interrupts every message is unusable.
Why existing tools were not enough
The providers could each perform their own function, but none of them supplied the routing policy between systems. A generic assistant also could not safely collapse ad analysis, content production, finance checks, outreach and landing-page quality assurance into one undifferentiated role.
ConvertSail needed departmental separation, explicit source authority and channel etiquette encoded at the operating layer. It also needed visual work to end in inspection, not a text response claiming a page had been improved.
Transformation map
Before
Meta | Workspace | Fathom | Calendly | QuickBooks | team channels -> Alex resolves source and context -> work proceeds
After
Authorized request -> role router -> authoritative provider path -> specialist work -> visual or human check -> team-visible output
The important change is not the number of agents. It is that each agent inherits a deterministic rule for where truth should come from.
One workflow, end to end
- Input: An authorized client-delivery request arrives in Discord or as a direct Slack mention.
- Context: The system reads the permitted recent channel history and retrieves relevant meeting context through the Fathom helper.
- Routing: Main sends the task to Ads, Content, Pipeline, Strategy or Outreach according to the required operating mode.
- Authority: A Meta audit uses the native Meta path; Workspace work uses
gws-auth; finance work that belongs in QuickBooks follows its Tool Router route. - Production: The specialist prepares the analysis, message, asset or landing-page change. For a page, the workflow includes a deployed-page inspection and before/after screenshots.
- Control: External sends, publishing and consequential account changes remain subject to the team's approval.
- Record: The output returns to the relevant team surface, while session guards and cleanup reduce stale context accumulating behind it.
What changed
- Built: Six roles - Main, Ads, Content, Pipeline, Strategy and Outreach - plus provider wrappers, landing-page and conversion-site skills, session guards and cleanup automation.
- Connected: Native paths were established for Meta Ads and Google Workspace, with helpers for Calendly, Fathom and read-only Discord history; QuickBooks and selected finance tools use Composio Tool Router.
- Tested: Meta account audit rules, client-email context, landing-page QA, prompt-bank checks, provider selection and authorized Discord response behavior were hardened against known failure modes.
- Verified: On 30 May 2026, six agents, 25 bindings and the core runtime services were observed active.
- Actively used: The retained documents do not quantify routine team usage or completed client outcomes. Runtime activity is not presented as adoption proof.
- Remaining dependencies: Consequential external actions still require approval, and broader operational adoption needs a retained use record before this case can be described as verified live.
- Financial result reported by client: None retained.
Proof
- Agent receipt: Six specialist roles configured around agency delivery.
- Routing receipt: 25 bindings at the verification point.
- Runtime receipt: Caddy, Command Center, Claw3D, billing proxy and OpenClaw services active on 30 May 2026.
- Authority receipt: Written provider rules distinguish native Meta,
gws-auth, Tool Router and read-only Discord history paths. - Claim boundary: No time saving, revenue lift or adoption volume is inferred from the technical deployment.
Technology - revealed last
The deployment runs OpenClaw 2026.5.6 on a VPS with Discord, Slack, a billing proxy, gbrain-style context, native Meta Ads tooling, gws-auth, QuickBooks through Composio Tool Router, Calendly and Fathom helpers, a read-only Discord history wrapper, Command Center, Claw3D, Caddy and conversion-site tooling. Stale cron jobs were patched, large Discord sessions received cleanup automation and demanding design/content routes could use a higher-capability model where required.
Client quote
No source-backed verbatim client quote is published for this case. The deployment record supports architecture and runtime claims; it does not authorize RECAST to manufacture testimonial language.
Next transformation
See how Scaling Webinars coordinated eight specialist departments through one shared command center. Both systems solve cross-tool agency coordination, with different provider and approval boundaries.
Get your AI blueprint
If your assistant keeps asking for connections you already have, the bottleneck is not another integration. It is source authority. Book a free AI audit to map the correct provider, operator and approval boundary for each recurring workflow.
Source record
OPENCLAW-DEEP-CLIENT-CASE-STUDIES.pdf, page 10.RECAST_CASE_STUDIES_2026_UPDATED.pdf, page 6, documentRA-CASES-001, version 2.0.RECAST_WEBSITE_MASTER_BLUEPRINT.md, sections 10.4, 11 and 58.