← Back to site
Story · "It works — but my people will never adopt it"

"We're not a technical business." Thirty days later, they were using it daily.

Based on our engagement with Training Combined, a Sydney vocational training organisation. Shared with permission; operational details simplified.
30 days
from engagement start to first workflow live and in daily use
0
technical staff on the client side — trainers and admin, not engineers
Daily
use by the team within the first month — no mandate required

The belief

"I believe AI works — for tech companies. We're trainers. My people are on their feet all day with real equipment and real students. Nobody here writes code, and nobody has time to learn a platform." That's the internal false belief in its purest form: not doubting the vehicle, doubting themselves. It kills more AI projects than any technical failure, because it kills them before they start.

What actually happened

We didn't train anyone to be technical. We found the bottleneck — the repetitive drafting and admin load around courses, compliance paperwork and student communications — and built the workflow to meet the team where they already work. No new platform to learn. No prompt engineering course. The workflow does the drafting; the operator reads, corrects, approves. The judgement stays human — it just stops being spent on the typing.

Adoption isn't a training problem. If the workflow removes a task people hate, adoption is the default — resistance only appears when AI adds work instead of removing it.

Within 30 days the first workflow was live and being used daily — not because anyone mandated it, but because the alternative was going back to doing the tedious part by hand. That's the adoption test that matters: would the team riot if you took it away?

The point

"We're not technical" is an argument against buying a technical product. It is not an argument against a done-with-you workflow, built around your people, that they operate the way they operate email. The build is our job; the judgement is yours; the 30 days is in writing.

Your team doesn't need to be technical. That's the point.

First workflow live within 30 days of engagement start, or your fee back — and you keep everything we've built. The 30-Day Live Guarantee.

Request a conversation →