Proposal · Confidential
We build and operate our own AI products — customer messaging, social publishing, and SEO — and build custom systems on the same infrastructure. This document maps what already exists against what a newly established company in Malaysia actually needs in its first eighteen months.
01 — The situation
The gap is not strategy. It is throughput. The three places it shows up first are the same everywhere:
None of these need a bigger team first. They need systems that already work, installed and operated by someone who has run them before.
02 — Who we are
ZhenheAI operates a portfolio of production AI products serving businesses in Taiwan — multi-channel customer service, social publishing, and SEO tooling. The same stack is what we deploy for clients. That means the answer to "can it do X" is verifiable, and the person configuring it is the person who wrote it.
Infrastructure runs on Cloudflare and Supabase with error monitoring, transactional email, and payment handling as shared internal services — so a client system is not a prototype held together for a demo.
03 — Capability map
Each system below is independently deployable. Nothing here requires buying the whole set.
Replybot
One dashboard for Facebook Messenger, Instagram DM, LINE, and an embeddable web chat widget. The AI answers from a knowledge base built by crawling your own website and documents, hands off to a human when it should, and keeps the full conversation history in one place.
Hermes
A private AI workspace on your own subdomain, isolated from other tenants, connected to LINE and your internal knowledge. Where Replybot handles inbound customers, Hermes is the assistant your team talks to — briefed on your business, available to everyone, without any data sitting in a shared consumer account.
Autopost
Plan, schedule and publish to Facebook Pages, Instagram and Threads from one calendar, then read post performance and follower movement back in the same place. Built for the case where marketing is one person's third job — the queue keeps running on the weeks they disappear.
SEOHelp
A site audit engine that checks the things that actually move rankings — metadata, canonical and indexing directives, structured data, social preview cards, sitemap and robots health, hreflang for multi-language sites, and Core Web Vitals — and returns a prioritised fix list. Available as a dashboard, a command-line tool, and an interface AI agents can query directly.
ThreadScout
Searches Threads for posts relevant to your keywords and drafts reply options for each one. By design you choose, edit, and post every reply yourself — the system finds and drafts, a human always decides. That constraint is deliberate and it is what keeps the account safe.
Custom builds
Multi-language websites, internal tools, customer portals, referral and commission tracking, payment and subscription flows, transactional email, and error monitoring. Delivered on the same infrastructure we run our own products on, and handed over with documentation rather than dependency.
Process automation
Quotations, order and payment notifications, lead routing, follow-up sequences, recurring reports. We map the two or three processes costing the most hours, then build them to run on their own and alert a person only when something needs a decision.
04 — Recommended starting points
Our recommendation is to start with one layer, prove it for a quarter, then extend. Companies that install everything at once tend to operate none of it.
| Stage | The bottleneck | Start with | Add next |
|---|---|---|---|
| Just launched | No inbound at all, and no presence to generate it | SEOHelp audit on a properly built site, plus Autopost to establish a publishing rhythm | ThreadScout, to join conversations instead of waiting to be found |
| Getting enquiries | Messages arrive faster than anyone can answer them | Replybot across every channel you are already on, with a knowledge base from your own site | Process automation for quotations, order notifications and follow-up |
| Growing team | Admin and repetition consuming people you hired to do other work | Process automation across the two or three heaviest manual jobs | Hermes as the internal assistant, plus reporting automation |
| Scaling | Systems exist but nothing connects to anything else | Custom build to join the pieces, with monitoring so failures surface before customers find them | Referral, subscription and commission infrastructure as the model requires |
05 — How we work
We map where enquiries arrive, what happens by hand every week, and which of those is costing the most. The output is a written scope, not a slide.
One system, one process, deployed to production and measured against how it worked before. Short enough that if we are wrong, it is cheap to have been wrong.
Once the pilot holds, the rest of that layer goes in. Channels, workflows, or content systems — whichever the pilot proved.
We run and tune it while your team learns it, then hand over with documentation. Ongoing operation is an option, not a lock-in.
06 — Scope, honestly
WhatsApp runs through SalesSmartly. Replybot covers Facebook, Instagram, LINE and web chat natively; WhatsApp is served by integrating SalesSmartly alongside it. Given how central WhatsApp is in Malaysia, we would scope that integration explicitly in the first conversation rather than leave it assumed.
Payments are region-specific. Our payment infrastructure includes a Taiwan-specific gateway and e-invoicing path that does not apply here; for Malaysia the route is Stripe, which we already run in production. Worth confirming early if payments are in scope.
ThreadScout will not auto-post. It searches and drafts; a person must approve and publish each reply. This is a product decision for platform-safety reasons and it is not configurable.
Our content systems were built Chinese-first. They handle English and multi-language sites, but for Malay-language content we would want a review pass on the first cycle rather than claiming it works untested.
07 — Next step
Tell us which of the three bottlenecks in section 01 is the one hurting now. We will come back with a specific first deployment, a timeline, and commercial terms for that scope.