Answers written by Bolun (Ben) Liu, Founder of RightClick:AI. If your question isn't here, email ben@3nm.io — you'll hear back within 24 hours.
RightClick:AI builds custom AI Operating Systems for service businesses in Singapore with 10 to 35 staff. The Foundation Build delivers a complete operating system in 6 weeks: an operational dashboard, workflow automation, an AI assistant, and a notification centre — all running on your real data, scoped specifically to how your business works.
It is built and run by Bolun (Ben) Liu, working solo with a tight specialist network. SGD 7,600 fixed scope. Day 7 MVP. SGD 200 back per day late. You own the code outright. No SaaS subscription, no lock-in, no platform you have to learn.
Bolun (Ben) Liu is the founder. I am a marketer and an AI operator based in Singapore, non-technical by training — my edge is process-first thinking and data discipline, not code. Before RightClick:AI, I built and ran AI workflows for a service-based SME, developed AI agents for my own company, and shipped automation systems for paying clients.
Sectors delivered: healthcare consulting · financial services · compliance workflows · family office operations · 3PL logistics · education consulting · marketing agencies · law firms. Contact: ben@3nm.io. Singapore (SGT, UTC+8). 24-hour response.
Yes. I work with partners who own the client relationship — agencies, consultancies, advisory firms, and operators with existing books of business. The engagement is signed in your name. Your client never sees a "RightClick:AI" invoice unless you want them to. I am the backend; you stay the brand.
Same offer, same pricing, same SLAs as a direct engagement. The Foundation Build is delivered to whatever brand or entity you specify, with documentation and code handover written for your team. If you want me on the call with your client, I am there. If you want me invisible, I stay invisible.
Service businesses in Singapore with 10 to 35 staff. Consulting firms, education companies, financial services, logistics operators, agencies, law firms, family offices. The common thread: complex enough to need real systems, not large enough to maintain an internal technology team.
You are a good fit if your workflows are still mostly manual, your data lives across email and spreadsheets and people's heads, you are spending several hundred dollars a month on SaaS tools that do not talk to each other, and growth currently means hiring rather than systematising. Poor fit: a business that hasn't started yet, a consumer-product idea, or a team that cannot give 48-hour feedback during the build.
Yes. Most of the founders I work with are non-technical. Being non-technical is not a barrier — it is the default. The discovery call and scoping process are designed to extract information from people who run workflows, not engineers who build them.
What I need from you is knowledge of your business: how your team works, what tools you use, where the friction is, what decisions you need to make faster. I handle everything technical. Every system delivered is designed for non-technical teams to use from day one — no new platform to learn, no complex onboarding, no ongoing maintenance burden on your staff.
The primary focus is Singapore. The 48-hour feedback loops during the build depend on timezone alignment with Singapore Standard Time (SGT, UTC+8), and the discovery and scoping conversations are most efficient in person or near-real-time.
For businesses in neighbouring markets — Malaysia, Indonesia, Hong Kong — I assess on a case-by-case basis depending on engagement size and ability to work within SGT. If you are outside Singapore and believe there is a strong fit, email ben@3nm.io with a brief description of your business and the problem you are trying to solve. You will hear back honestly about whether I can serve you well.
A 30-minute conversation. No pitch, no proposal. We talk about your business, the bottleneck you are hitting, and whether what we build is the right answer.
If we are not a fit, you hear it on the call and we move on. If both sides see a fit, we run a 1-hour audit of your current workflows — tools, data, manual processes. The audit is what the scope is built from.
If you decide to proceed after the audit, you commit — and the scope work begins. From there:
6 weeks from approved scope. Day 7: working MVP — your operational dashboard live on real data (revenue, pipeline, team capacity, client health). Weeks 2–6: iteration sprints on the four functions, with 48-hour feedback loops between us.
The 6-week SLA depends on 48-hour feedback from your side during the build. If feedback consistently runs longer, the SLA pauses for the duration of the delay. That clause exists because the timeline is two-sided — I cannot deliver in 6 weeks if I am waiting two weeks for sign-off on a question. SGD 200 back per day late on any committed milestone, regardless.
Not knowing exactly what you need is the normal starting point. The discovery call qualifies the engagement — and the 1-hour audit afterward is where we map your tools, your team, and your specific friction points. I build the picture from there. You do not need to arrive with a spec. You need to arrive with knowledge of how your business runs and where the friction is.
After the audit, if both sides want to proceed, you commit and the scope work begins. Within 48 hours: a complete written scope — deliverables, timeline, cost, assumptions. If the scope does not feel right at that point, cancel: 95% back.
Written into every agreement, not aspirational targets:
Every clause has money on it because soft promises are how trust dies. The 6-week SLA pauses if your side's feedback consistently runs longer than 48 hours — the timeline is two-sided, and I will say so up front rather than fail quietly.
Foundation Build: SGD 7,600 fixed scope. Four functions delivered in 6 weeks: operational dashboard, workflow automation, AI assistant, notification centre. Day 7 MVP. SGD 200 back per day late. The 30-minute discovery call and 1-hour workflow audit are free; pricing kicks in once you commit to proceed.
Function Cycles after Foundation: SGD 2,400 per cycle. One new capability at a time, scoped per cycle, queued at your pace. Stop anytime. Maintain Mode: annual subscription, opt-in.
For reference: hiring an operations manager in Singapore is SGD 80,000 to 120,000 a year plus CPF and tools. The Foundation Build is roughly 6 to 9 percent of that, delivered once, with no recurring headcount cost.
Yes, at any point. Three checkpoints:
All work delivered up to that point is yours regardless. No lock-in. The structure is in writing because soft cancellation policies are how engagements turn adversarial — and that does not serve either side.
Yes. You own the codebase, the architecture, and the deployment outright. Every deliverable is yours from the moment it is built. No SaaS subscription. No lock-in. Any developer anywhere can pick up the work and continue it — the system is documented and written to be understood by other engineers, not just by me.
Maintain Mode is opt-in: an annual subscription covering hosting, updates, AI refresh, and async support. If you prefer to take the codebase and maintain it in-house or with another developer, that is fine. Many founders continue with Maintain Mode because it is far cheaper than the SaaS tools the system replaces.
The Foundation Build is always Stage 1. SGD 7,600 fixed scope, 6 weeks, four functions delivered as one operating system: operational dashboard, workflow automation, AI assistant, notification centre. This is the operational core. Every business gets the same four functions — but each is scoped specifically to your data, your workflows, and your decisions.
Function Cycles are Stage 2 and beyond. SGD 2,400 per cycle, one new capability at a time. Scoped in 48 hours, MVP in 7 days, full delivery in 6 weeks. Queue as many as you need. Stop anytime. Function Cycles are how the system grows after Foundation — predictable per-capability pricing, no surprises, no annual contract.
Delivered: automated report generation pipelines (healthcare consulting — manual production eliminated; consultants drop a file, receive a formatted PDF). Compliance and approval workflow automation (financial services — 60% reduction in coordination work, error rate from 13% to near zero). OCR and portfolio intelligence layers (family office — parses statements across multiple banks, flags dependencies, generates AI-driven suggestions). Multi-retailer BI dashboards with AI analysis agents (3PL logistics — days-to-instant turnaround on performance data). Student management platforms (education consulting). Content fulfillment pipelines and campaign performance dashboards (marketing agencies). AI knowledge bases (law firms).
The four-function Foundation pattern fits all of them — the difference is what data each function runs on, and which workflow gets automated first.
You have the full operating system. From there, two paths — both opt-in, neither contractually required:
You can mix the two. You can stop both at any time and take the codebase elsewhere. You can pause for six months and come back. There is no annual contract, no auto-renewal, no escalating retainer. The economics are pay-as-you-go because that is the model that stays honest.
Yes — that is what Function Cycles are for. Most founders expand their system over time. The architecture is built to extend, not a closed box that requires rebuilding when needs change.
Each Function Cycle follows the same process as the original Foundation: 48-hour scope, Day 7 MVP, 6-week build, SGD 200 back per day late. There is no obligation to continue with RightClick:AI for expansions — the system and codebase are yours, and any developer can extend them. Most founders continue because the context is already built and the per-cycle economics are predictable.
Book a free 30-minute discovery call. No pitch, no proposal, no obligation. We talk about your business and answer everything directly.
ben@3nm.io · Singapore · Response within 24 hours