Scattered enquiries
WhatsApp, spreadsheets, and forms all run separately.
AI Business Consultant | 14+ years in IT delivery and workflow implementation
Fix the workflow first. Then make AI work.
Larry locks onto the one workflow hurting revenue or operations most, then clarifies ownership, SOP, and tracking within 30 days — CRM, AI, or automation only when justified.
Built for Hong Kong training, course, and professional-service teams of 3–30 people

Pain points
WhatsApp, spreadsheets, and forms all run separately.
People need to search, ask, and wait.
No one knows clearly who owns the next step.
One person on leave and the workflow stalls.
If one person takes leave and the process stops, that is not a process. That is a hostage situation.
Approach
One workflow at a time — not a company-wide digital transformation.
Step 1
Lock onto the revenue or operations bottleneck worth fixing first.
Step 2
Deliver process map, owners, SOP, tracking points, and one executable quick win.
Step 3
Help the team use it. Review missed follow-ups, quote time, and handoff completion on Day 30 / 60 / 90. Add CRM, AI, or automation only when needed.
BNI flash-card tool
Enter your industry and offerings to get 10 upstream, 10 parallel, and 10 downstream examples plus 5 Power Team ideas. AI / workflow-related items are marked for InnovateXP collaboration.
Main programs
Start by validating one workflow in 30 days, then expand to 3 / 6 / 12 months. Tool trials stay on secondary pages.
Not selling you a system first — diagnosis, implementation, adoption, and KPI review until one revenue-blocking workflow actually runs.
Recommended start
HK$6,800
Validate one workflow that affects revenue or operations.
Scoped by SOP complexity
Land 1–2 workflows, SOP v1, monthly checkpoints, one team training.
Scoped by SOP complexity
One department / 3–4 workflows, adoption tracking, up to two workshops.
Scoped by SOP complexity
Annual roadmap, SOP governance, management reviews.
Service areas
Find leakage in follow-up, slow quotations, and unclear handoffs.
Turn scattered enquiries into a traceable follow-up workflow.
Handle repetitive enquiries, data sorting, and admin work.
Turn event attendees into visible sales opportunities.
Help the team use AI safely and practically inside existing SOPs.
Industry examples
Anonymous scenarios (Before → 30-day approach → After → observable metric). No unverified ROI claims.
Training / courses
Before
Enquiry, trial class, enrolment, and payment lived in different chats and sheets; leave days broke continuity.
30-day approach
Locked onto enquiry → trial → enrolment; clarified owners, follow-up nodes, and a simple status board.
After
Every enquiry has an owner and next step; the owner stops chasing daily updates.
Observable metric
Fewer missed follow-ups; enrolment conversion visible on one page.
Professional services
Before
Quotes waited on missing data; each colleague had a different “latest” version; reminders exposed missed follow-ups.
30-day approach
Clarified quote inputs, ownership, and approval nodes; one trackable checklist.
After
Quotes follow a standard rhythm; handoffs are no longer verbal-only.
Observable metric
Shorter average quote time; fewer repeat data requests.
Studio industry (method example)
Before
Coaches tracked classes, unpaid students, and commissions differently; admins firefought daily.
30-day approach
Applied the same “fix workflow, then tools” method: ownership, status, reminders, export reconciliation.
After
Schedule, student status, and payment reminders live in one place — memory no longer runs the studio.
Observable metric
Unpaid follow-up has reminders; attendance / commission export is possible.
Why Larry
Contrast for client benefit — not internal product strategy language.
| Management consultants (report and leave) | I build, connect, and help the team adopt |
| SaaS vendors (sell licences) | I can tell you not to buy |
| Automation / AI freelancers (take jobs) | I ask the business question before naming tools |
| Large IT firms (six-figure projects) | HK$6,800 to try one workflow — low risk |
If you do not need a system, I will tell you directly.

About Larry
After more than a decade in IT delivery, the failure I saw most was not bad builds — it was perfect delivery that nobody used.
The same people kept using WhatsApp and Excel, and nobody said so out loud.
Looking back, the problem was rarely the tool — the workflow itself had never been clarified. The SOP lived only in the owner’s head, so one leave day broke everything.
So I changed the approach: fix one workflow first until it works and the team actually uses it — then talk about AI or systems.
I am the consultant who may tell you not to buy yet.
Not every team should start with AI immediately. Start with one workflow and decide based on real operational value.
Not always. Ownership, handoff clarity, and follow-up rhythm usually come before buying a new system.
Usually by focusing on one workflow first. We do not start with a company-wide overhaul.
Adoption matters as much as the tool. The workflow and handoff design must fit how the team actually works.
We focus on one workflow, identify leakage and ownership gaps, and decide what is worth fixing first.
Yes, especially when one absence can stall the whole workflow. The main path starts at HK$6,800 for a 30-day Sprint.
Step by step: 30-day Discovery Sprint (HK$6,800) 3-month Foundation (scoped by SOP complexity) 6-month Accelerator (scoped by SOP complexity) 12-month Partnership (scoped by SOP complexity) (Note: we focus on real operating problems. Tool trials are not the homepage headline.)
Book a 30-minute workflow diagnosis and find the one process most likely to leak leads, slow quotes, or stall handoffs.