Common questions about what I build, pricing, and how a real engagement works.

It is the set of layers that lets AI agents work beside your people, on your data, on your say-so. There are six: context, operational data, AI agents, the workspace, the ledger and your admin panel. Your people set the rules and the agents do the legwork.

I start with the foundation, which is your context and operational data, built on your real records. The agents, the workspace, the ledger and your panel follow as later scopes.

The foundation: your records, how you decide and how you sound, kept where your own AI can read them. Your records are your operational data, cleaned up and kept in one well-maintained place. The wiki holds how you think and decide, what you’ve learned and where things stand. The skills turn your brand, tone and SOPs into instructions the agents follow.

I build it on your real data and hand it over with recorded walkthroughs and written SOPs. Everything exports as files.

I do. RightClick:AI is me. I take the call, scope the build, build it and hand it over, with no subcontractors on the core build and no account manager in between. You talk to the person doing the work, start to finish. I take three projects a month.

Owner-run businesses in Singapore with 5–25 staff. It fits if you’ve said “it lives in my head”, “it runs on spreadsheets”, “I’m the bottleneck” or “nothing talks to each other”.

It isn’t for a team that wants live training sessions, since handover is recorded walkthroughs and written SOPs, or for anyone after a SaaS subscription. If you want a custom app first, that is its own scope, after the foundation.

Yes. You give access and answers; I do the rest, from cleaning the data to connecting the apps. The mess is normal. Every business I’ve built for had spreadsheets that disagreed, and you don’t clean up before I start. Handover is recorded walkthroughs and written SOPs, and after it you never need me to use it.

Singapore is my focus. I’m based here and work in Singapore time (SGT, UTC+8). The build runs on your own accounts and keys, and handover is async: recorded walkthroughs and written SOPs. If your business is outside Singapore, raise it on the free call and I’ll tell you honestly whether I can serve you well.

A free 30-minute call, with no pitch and no proposal. Bring the one thing eating your week; I read every booking myself. You book on the site and it opens WhatsApp.

If it’s a fit, the next step is one scoping call, and after it you get a written scope and quote to approve. If your team wants to try agents first, ask on the call for the free two-hour workshop I run at your office.

About four weeks from the scoping call to a working first build, on your real data. The steps are the call, one scoping call, the build, handover, then an optional monthly. Momentum is two-sided: if feedback is slow, progress pauses.

For a sense of pace, a data build for a 3PL logistics firm in Singapore went from signed to live in 13 days: signed 17 June 2026, live 30 June.

Access to your accounts, answers when two numbers disagree, and your approval of the scope before I build. During the build, come to the working sessions and reply to feedback promptly; slow feedback pauses progress. Cleaning the data, writing the wiki, building the skills and recording the walkthroughs are my side of the work.

Quoted per client after the scoping call, and never published. Every business’s data is different, and I see yours on that call before I quote. The shape is a fixed setup fee, then an optional monthly you can cancel any time. The first call is free, and you see the written scope and quote before any build starts.

I build until what’s in the scope works. You get the result, not a refund.

The written scope sets the limit. If what’s in it isn’t working on the day I said it would be, I keep building until it does, at no extra cost. Anything outside the scope is a new scope. I don’t offer money back, because a refund guarantee attracts the buyer who is already looking for the exit.

No. Grant approval takes four to six months; the build takes about four weeks. Waiting on the paperwork would take longer than the work itself, so I don’t do PSG or EDG applications on this offer. The build starts once you approve the written scope and quote from the scoping call.

Yes, outright. The data, the wiki, the skills and the SOPs are yours, set up on your own accounts and keys. There is no SaaS subscription and no lock-in. Everything exports as files, so you can move it whenever you like. If you want to run it yourself after handover, everything works.

In your own tools, on your own accounts. I set this out in writing before I quote:

• Where it lives: your own workspaces, drives and databases, named tool by tool in the scope.
• Whose accounts and keys: yours. I get scoped access to build, and it is handed back or revoked at handover.
• Who changes things: you, after handover. You never need me to use it.
• Getting it out: everything exports as files, in no format only I can open.

The foundation runs on standard tools, not a custom-coded app, so there is less to secure.

No. Every agent has one job and a person it answers to. Agents draft and recommend; a person signs. Every hand-off goes in the ledger, with who did what and when, and you can read it, question it and undo it.

Nothing goes out in your name that you did not allow. The agents arrive after the foundation, as a later scope.

You have all of it, as files, and it works without me. If you want, an optional monthly keeps it current: I add new context, refresh it as the underlying models change, tune the skills, and give async support when something breaks. It is light by design, and it is not a retainer.

Yes, any time. Nothing shuts off when you cancel, because it all runs on your accounts and it is already yours. If you’d rather run it yourself after handover, everything keeps working. The monthly exists because keeping it current is useful, and clients ask for it.

Yes. After the foundation come the agents, the shared workspace, the ledger and your admin panel. Each gets its own written scope and quote, the same way the first build did, so you decide one piece at a time.

I don’t refuse custom apps either; a custom app is its own scope after the foundation. The foundation goes first because it makes every later piece cheap to add.