Case studies
What it looks like once it is running.
What FloConnector customers connected, what they built on it, and what their metered call log actually shows. Real figures, read from production on a stated date.
The executive assistant he built across 14 tools, then handed to his team
Barry Minton runs a scaffolding company with a small crew and large commercial clients. He connected 14 tools, cleaned up years of scattered data, put his morning brief on a schedule and gave his admin a profile that reads his inbox. Six weeks and 5,475 calls later, this is what the log shows.
- 14 tools connected
- 6 profiles shared with his team
- None quotes retyped by hand
Barry Minton Owner, Elite Access Solutions 
+8 
More from FloConnector
Recent from the blog
The FloConnector connector: 14 tools, and one deliberate difference
We build connectors to other people's platforms. This one points at ours: fourteen tools that let your AI client write, revise and publish the skills your workspace runs on. It is an ordinary catalog row in every respect but one, and that one is the interesting part.
Skills over MCP: where your instructions should actually live
An Agent Skill is a folder on somebody's laptop. Fine for one person, a quiet disaster for a team: four copies, three of them stale, no history and no way to take one back. Here is what changes when the folder becomes a hosted object served down the same connection as your tools.
Ascora + AI: 46 tools, and the quote is how the job gets built
Ascora runs on a connector we build and maintain ourselves, with 46 tools across enquiries, customers, quotes, jobs, labour, timesheets, suppliers, bills and the accounting handoff. The interesting part is what we had to do about an API that says yes rather more often than it means it.