Which system should I start with?

Start where it hurts most: no traffic → social media ops; no storefront of your own → the site system; street sales running on legs and memory → field lead-gen; messages piling up unanswered → AI support; old customers going quiet → private-domain ops. Not sure? Book a demo — one conversation makes it clear.

Can I buy just one system?

Yes. Start with the single system that fixes your most painful stage, then add along the growth chain as you go.

Is it a subscription or a one-time purchase?

Most systems run as a monthly subscription; some, like the storefront, start as a project. We'll scope the right model for your case during the demo.

Are the listed prices final quotes?

They're starting anchors, not final totals. Category, market and what you already have in place differ for every business; the exact scope and quote come after the demo.

What does working together look like?

Three steps: book a demo and pin down your most painful stage; run a small pilot on that one stage and watch real results; once it works, sign and go live.

How soon can we go live?

It depends on the system and what you already have in place. We'll give you a timeline for your specific situation at the demo — no blanket promises.

What does "proven on our own brands first" actually mean?

Our own brands run these five systems on real business every day. What you see in a demo isn't a product page — it's a live system and the real content and conversations it produces. If it doesn't work, we don't sell it.

Is the chat bubble in the corner one of your systems?

Yes. The reception you're getting right now is System No. 4 — the AI Customer Service System — running for real. Buy it, and this is exactly what your customers get.

Do you guarantee results?

We don't promise blanket numbers — categories and starting points differ too much, and anyone guaranteeing you a uniform figure deserves suspicion. Our way: see the live systems at the demo, judge the pilot on your own data, then decide.

I'm not technical — can I run this?

Yes. We handle deployment and integration; you and your team make the business calls. During handover we onboard your people — what you need to know is your customers, not code.

We already have a team, or use other tools. Does that clash?

No. The systems enter one stage at a time, so one can take over a single stage and run side-by-side with what you do today. Same team — much bigger throughput.

Why systems instead of hiring more people?

Hiring adds hands; systems add scale. Publishing, reception and follow-up run around the clock, while people handle only the calls that need judgment. The usual pattern is your existing team running the systems for bigger output — not either-or.

Do you offer done-for-you management?

No. We sell systems, not outsourced labor — the system goes to you or your team and lets the same people produce far more. If you need managed services, that's not our business.

Which languages and markets do you support?

Traditional Chinese, English and Vietnamese out of the box, with multilingual reception and content, so one setup serves domestic and overseas customers at once. We'll confirm coverage for your target market at the demo.

Which channels and platforms can you plug into?

The customer service system handles website live chat, WhatsApp, Messenger, Instagram, LINE and Zalo in one place; the social media system turns one asset into native posts for up to nine platforms. We'll map it to your channel mix at the demo.

Where is my data stored?

Your data is encrypted and stays yours; we'll walk you through exactly where it lives and who can access it when we onboard you.

What happens after I submit the form?

Your details get briefed to a teammate so you never have to repeat yourself; we'll reach you through the contact you left to set a demo time.

What if I can't answer any of the five questions confidently?

Start at attract and work forward — that's usually the honest answer for a brand that's very early. Fix that stage first; the other four questions get easier to answer once there's actual traffic and leads moving through them.

What if two stages both fail the question?

Fix the earlier one first and re-run the check. A downstream stage often stops looking broken once the upstream leak is closed, because what looked like a conversion problem was really a volume problem.

Do I need analytics tools to make this diagnosis more accurate later?

Eventually, yes — proper tracking narrows the diagnosis and shows trends over time. But it's not a prerequisite for a first diagnosis, and waiting for it before acting is its own kind of leak.

How often should I re-run the five questions?

After any change meant to fix the stage that failed, and roughly monthly otherwise. The funnel moves — a stage that was healthy six months ago can quietly become the new bottleneck.

How to Tell Which Stage of Your Funnel Is Actually Leaking Without a Dashboard

Funnel-leak content is written for a team that already has clean data

Most of what ranks for this question comes from CRO agencies and analytics platforms, written for a specific reader: someone with a pixel on every page, a CRM logging every lead, and a dashboard that already separates the stages. For that reader, finding the leak is a matter of pulling the right report and reading a drop-off number.

That reader isn't most early cross-border teams. A brand running social content in one app, a storefront in another, field visits on paper or in a group chat, and customer messages split across several platforms doesn't have a single report that shows the whole funnel — building that tracking is itself a project, not a five-minute fix. Waiting for it before diagnosing anything just delays the diagnosis.

That's the gap this piece fills: a way to answer how to tell which stage of your funnel is actually leaking using only what's already observable — no pixel, no CRM, no export required — so the diagnosis can start today instead of after the next quarter's tooling project.

Five questions, one per stage, that don't need a dashboard to answer

The workaround is to replace the report with an observable proxy — one question per stage that a person close to the business can answer immediately, from memory or by glancing at one place, not by pulling a query.

Work through the stages in order: attract, capture, acquire, convert, retain. The first stage where the honest answer is 'no' or 'not sure' is where the leak sits — stop checking there rather than moving on to the rest, because everything downstream of a broken stage tends to look broken too, whether or not it actually is.

Attract: can you name the last channel a stranger used to find you?
Capture: can you say what a new visitor is supposed to do in their first few seconds?
Acquire: does anyone know if last week's leads got followed up, without checking chat history?
Convert: how old is the oldest unanswered message on your slowest channel, right now?
Retain: can you name five past buyers who never came back, and has anyone reached out to them?

Checking out of order gives you the wrong answer, not just a slower one

It's tempting to jump straight to whichever stage feels most painful — usually convert or retain, because that's where a missed sale is most visible. But a downstream stage can look broken for reasons that have nothing to do with that stage. If almost nobody is finding the brand in the first place, the message backlog looks calm and repeat buyers look nonexistent — not because retention is broken, but because there's barely anyone to retain yet.

Checking in order avoids that trap. An upstream failure masks or distorts everything after it, so fixing a downstream stage before confirming the upstream ones are clean usually means fixing the wrong thing, or fixing something that didn't need fixing yet.

This is also why the five questions are framed as a sequence rather than a scorecard. A scorecard invites averaging — decent marks on four stages and a weak one on retain can still read as 'mostly healthy.' A sequence forces a stop at the first failure, which is closer to how funnels actually behave: one broken stage caps everything that comes after it, no matter how strong the rest looks.

The stage that fails points to what to fix first, not what to rebuild

Each of the five questions maps to one specific gap, not a general 'do more marketing' verdict. A failed attract question means the content or distribution isn't reaching anyone yet. A failed capture question means whatever a stranger lands on doesn't tell them what to do next. A failed acquire question means leads exist but aren't tracked into a pipeline. A failed convert question means messages are arriving faster than anyone can answer them. A failed retain question means past buyers are being let go quietly instead of deliberately followed up.

None of those are fixed by touching the other four. The point of running the check in order is to stop the instinct to rebuild everything at once — find the one stage that's actually leaking, put the effort there, then run the same five questions again in a month to see if the leak moved.