Your best people spend their week on work AI already handles.

We're a Sri Lanka based team working across the region, and claimability depends on where your entity sits and which programme you run. Tell us your setup on the scoping call and we'll be straight with you about what is and isn't claimable for your organisation, and how other clients have structured it. We would rather tell you no on a call than have you budget around a claim that doesn't apply.

Yes. Blueprint works best in a room, and we travel to KL and the surrounding Klang Valley for it. Transform runs online across eight weeks, which works better when a rollout spans multiple offices or departments.

Blueprint is priced per day for the room. Transform is priced per participant, per department, and scales with how many departments run in parallel. Both are quoted after a 20-minute scoping call, because the price depends on team size, how many departments are involved and whether you want post-engagement support. We will give you a number on that first call. We will also tell you if we think you should start with Blueprint instead of committing to a rollout, which happens more often than you would expect.

Then they are the right audience. Every build is visual and no-code. In the room we have had finance managers, recruiters and warehouse supervisors ship working automations on day one. What matters is knowing the work, not the tooling.

Yes. We don't take a standard curriculum and apply it to your team. Every engagement starts with the Automation Audit, which maps your team's specific workflows before a single tool is introduced. What gets built is built around your work.

Marketing and growth ops, HR and recruitment, finance, and general operations. Anywhere a team runs the same process on a schedule. Marketing typically sees the fastest result because so much of the week is reporting, repurposing and follow-up. Finance and HR tend to see the largest single time savings, because their repetitive work is higher volume and more rule-based. On a Transform rollout, departments run in parallel and each builds its own automations.

Most AI training teaches tools. People leave energised, then return to the same inbox because nothing was built while they were in the room. We invert it. Nobody watches a demo. Every session is hands on keyboards, building against a real task from that person's real week, and the automation is running in your tools before they leave. We measure one thing: what is still running a month later.

Every participant tracks time saved from week one. By the end of a Transform engagement you have a dashboard showing hours recovered per week, per person, per department. Blueprint participants leave with a 30-day plan tied to named workflows, so you know exactly what to track. Build the business case on hours, not licences. Take the hours recovered per person per week, multiply by the loaded hourly cost of that role, and annualise. Teams here typically recover four to six hours per person per week. That is the number your CFO will actually recognise, and it is why we make participants log it rather than estimating it for you.

Blueprint is a single day, so one day out of the calendar and nothing after it. Transform runs eight weeks with a weekly live session plus a small amount of build time in between, which lands at roughly three to five hours a week per participant. That time is spent on their own work, not on exercises, so most of it is not lost to the business. We schedule around your operating rhythm rather than the other way around.

We start with what you already run — Google Workspace, Microsoft 365, Slack, Notion, Airtable. Where an automation platform is needed we work with whatever your policy allows (Make, Zapier or n8n) and bring IT into the scoping call before anything is connected.

Training runs on synthetic and sample records. Live data only enters once your team switches an automation on, after your own review. Nothing we build lives on our infrastructure. Every automation is created inside your tenancy, under accounts your admins control, with an owner and an off switch from day one. Anything customer-facing is drafted by AI and approved by a person, and those approval gates are part of the build rather than something added later.

You do, completely. They are built in your environment, on your accounts, by your people. Every automation ships with a named internal owner, a written trigger log and a documented way to switch it off. This is the main reason we build with your team rather than for them. Work delivered by a consultant leaves when the consultant does. Work your own people built, they can change.

If you want twenty automations built and nothing else, hire someone to build them. That is a legitimate choice and it is faster. The problem shows up in month four, when a process changes and nobody internal can edit the thing that broke. You end up back on a retainer for maintenance on a system you don't understand. We build fewer automations, more slowly, with the people who own the work, so the capability stays in the building. The automations are the visible output. The people who can now build the next one are the actual deliverable.

No, and that is on purpose. A certificate proves attendance. It doesn't prove anything changed. What your team leaves with instead is five or more automations running in their real workflow and a dashboard showing hours recovered per person. That is what we would want to see if we were signing the invoice.

Blueprint works best with 10–40 in the room. Transform cohorts are structured by department, typically 15–20 people, so sessions stay focused and everyone actually builds something.

Below about ten people, Blueprint is usually the right call rather than a rollout. Small teams tend to have less process but more overload per person, so the hours recovered per head are often higher than in a large organisation. If you're under ten and unsure, say so on the call. Sometimes the honest answer is that two people should do the individual cohort instead, and we'll tell you that.

Both. In-person is preferred for Blueprint — building together in a room moves faster, and we travel to KL for it. Transform runs fully online across multiple weeks, with recordings and a shared channel between sessions.

Transform participants keep the shared channel and the template library, and each department has a named internal owner responsible for the automations that are running. Blueprint teams leave with a ranked 30-day build list, costed in hours saved, so there is a specific next thing to build rather than general enthusiasm. The follow-through is the part most training skips, and it is the single biggest reason training either sticks or quietly disappears.

Then you were going to lose them anyway, and you'll have lost them from a team that runs on manual work instead of one that doesn't. Practically: the automations stay because they live in your tenancy with a named owner and documentation, not in one person's head. That is a deliberate design choice in how we hand things over. The capability does not walk out with an individual.