Outbound to held call
Build an ICP list, publish proof, run controlled outreach and trace held calls back to the touch that caused them.
Newsletter
Futurebits: what the client expected to need and did not
Waiting for you to approve
The uncomfortable part of what the client expected to need and did not: The interesting part is what we did not build. No quoting platform, no migration, no training programme. The constraint was never the tooling. It was that nobody had written down where the time actually went. The part that matters here is Show the build log. An automation studio for mid-market operations teams in the UAE — that is the lens I read this through. What has your experience of this been?
Futurebits: how to find the two steps that matter
Waiting for you to approve
The uncomfortable part of how to find the two steps that matter: We mapped it before writing anything. Two of the seven steps accounted for most of the delay: pulling current supplier pricing, and getting an approval from whoever was not in a meeting. The part that matters here is Process mapping beats model choice. An automation studio for mid-market operations teams in the UAE — that is the lens I read this through. What has your experience of this been?
What we did not build: a quoting teardown
Approved, not scheduled
A services business in Sharjah was losing two days a week to quoting. Seven steps, four systems, one spreadsheet that three people edited at once. We mapped it before writing anything. Two of the seven steps accounted for most of the delay: pulling current supplier pricing, and getting an approval from whoever was not in a meeting. We automated those two. Everything else stayed exactly as it was. Quote turnaround went from 2.5 days to 4 hours, and the only new software anyone had to learn was a Slack approval button. The interesting part is what we did not build. No quoting platform, no migration, no training programme. The constraint was never the tooling. It was that nobody had written down where the time actually went.