Questions before we build anything.

One messy workflow, turned into a system the team can run. We clarify the process, write the rules, build it, and hand it over.

SME owners and operators who already know where work is breaking: follow-ups, document checks, reporting, handoffs, internal knowledge. If it still lives in people's heads, that is usually a fit.

Paid one-month discovery. One workflow, mapped as it actually runs, then a go / no-go. If we stop, you keep the written scope, the deployment definition, and the resource plan.

Guide your people starts from RM 3,000 / month after paid discovery. Do it for you is quoted after discovery. The free 30-minute call is not the paid month.

Discovery is one month. If we continue with your team, the aim is one workflow live and in use by the end of Month 4, with a mid-point checkpoint where we can still stop. Done-for-you follows the scope we quote. I don't publish a single calendar for that path.

You bring the tools and the access. On a guided engagement that means a named owner, protected hours, and whatever you already run: n8n or Make, API keys, data, permissions.

The contact form collects your name, email, and the note you write. The privacy policy covers that, plus device data, cookies, and analytics. Client work stays in the systems you already use and grant access to. Privacy policy.

On Guide your people, your owner builds and I coach. On Do it for you, a delivery partner builds and I stay on it. I don't build the guided engagement alone.

After the paid month, go or no-go, you keep the written scope, the deployment definition, and the resource plan. After a build, handover is the logic, the owner, and the docs. Your people run it.

No. The call is 30 minutes. It is not Month 1. Paid discovery is a separate yes. I'll say if the workflow sounds like a fit for discovery.