Request a proposal
Tell us one workflow, one learning problem or one governance question. You will get back a point of view, a recommended first step and an indicative shape of the engagement — not a capability deck and not a discovery invoice.
1 · A working session
45–60 minutes with a practitioner, not an account manager. We ask about the work, not the org chart.
2 · A written point of view
Where we think value is, where it is not, and which workflow we would start with — sent before any commercial discussion.
3 · An indicative shape
Scope, duration, team shape and an indicative range. Detailed pricing comes after the point of view is agreed.
What should we prepare for?
The more concrete the problem, the more useful our first reply. If you are not sure what to prioritise, describe the business pressure instead — that is usually enough.
Cyberwisdom Group
34 Floor, 77 Robinson Road
Singapore 068896
Hong Kong SAR headquarters
Our enterprise learning business — LMS, TMS, custom courseware, CPD and compliance training — is headquartered in Hong Kong SAR.
If your situation does not match where we are strongest, we will say so and, where we can, point you to someone better suited. We would rather decline than take an engagement we cannot prove value in.
What happens after you write to us
No discovery phase that bills for three months before anyone says anything useful.
You send a note
One paragraph is enough. Tell us the industry, the training obligation you are trying to satisfy, and who would have to approve it.
We come back with questions
Within one business day. Not a qualification form — three or four questions designed to find out whether we are the right firm.
A working call
Forty-five minutes with a practitioner who has delivered in your sector. We will tell you if your sector is one we are not right for.
A written point of view
Two pages on your first obligation, what it would take, what it would measure, and what we would deliberately leave alone.
A proposal
Scoped in one workflow, with the operating model, the evidence requirements and the learning plan inside it.
How an engagement actually runs
Every client gets the same shape. The content changes by industry; the discipline does not.
Diagnose
We find the workflows that are already written down as policy — because those are the only ones that can be delegated safely.
Design
We design the operating model: who decides, who supervises, what the agent may not do, and what gets logged.
Build
One workflow goes into production. Not a pilot that never ships — a real one, with a trace and a named human approver.
Train
The people who will operate it are trained before go-live, and the training is recorded in the LMS as evidence.
Measure
Ninety days later we measure against a baseline you did not choose, and scope the next workflow from what we learned.
Questions we are usually asked first
How quickly will you respond?
Within two working days. The first reply is a written point of view on your situation from a practitioner, not a calendar link to an account manager.
Do we need to know exactly what we want?
No. Most engagements we are asked about start with a business pressure rather than a defined project. Describe the pressure and we will tell you where we think the leverage is — including if that is somewhere other than where you were looking.
What size of organisation do you work with?
Mostly enterprises. More than fifty of our delivered projects were large programmes, and we also work with mid-market organisations and public-sector bodies. The common requirement is a real operating function to work with, not a project office.
Do you take on small pieces of work?
Sometimes — usually a two-to-four week diagnostic or a focused piece of custom courseware. But the value is in the operating change, so we are candid when a small engagement will not reach the outcome you want.
What is your first engagement usually shaped like?
A four-week diagnostic that scores candidate workflows and produces a recommended starting point, or an audit of your current learning and compliance position. Both end with a written point of view you own, whether or not we continue.
Six things worth having ready before the call
None of these need to be perfect. Having them roughly written down is what lets us give you a useful answer rather than a discovery questionnaire.
- The name of the obligation, not the department. "Annual sanctions refresher", not "finance".
- Who currently does it, and how many people.
- Whether that work is written down as policy, or lives in people's heads.
- The metric you would use to prove it worked — and its current value.
- Who is accountable for the programme, and who signs off the evidence.
- What your risk function would need to see before you could ship it.
- Which partner or customer process would feel the effect first.
Four ways to reach us
The fastest route to a person. Use it for scoping questions, and for anything time-sensitive in your market.
Learn more →For briefs, RFPs, tender documents and anything that needs a paper trail you can forward internally.
Learn more →Group HQ
34 Floor, 77 Robinson Road, Singapore 068896 — platform engineering, content production and group operations.
Learn more →Learning HQ
The enterprise learning business — LMS, TMS, custom courseware, partner and workforce enablement.
Learn more →Where we are
| Office | Address | Focus | How to reach us |
|---|---|---|---|
| Group HQ — Singapore | 34 Floor, 77 Robinson Road, Singapore 068896 | Platform engineering, content production studio, group operations | consult@cyberwisdom.net · WhatsApp +852 5807 1796 |
| Learning HQ — Hong Kong SAR | Hong Kong SAR | LMS, TMS, custom courseware, academy, partner enablement | consult@cyberwisdom.net · WhatsApp +852 5807 1796 |
| Delivery — Asia Pacific | Across Singapore, Hong Kong SAR, Malaysia, Thailand, Indonesia, Vietnam, the Philippines and India | Regional project delivery and partner enablement | Via the group HQ or your account lead |
What changes in the room
The difference is not budget and not technology. It is whether your organisation's own judgement is written down, and whether the people operating it are trained.
- Platform licence, priced per seat
- A six-month discovery phase
- Success defined as adoption and sentiment
- Training offered as a separate upsell
- Value case built on a vendor benchmark
- Renewal conversation in month eleven
- One workflow in production inside a quarter
- Named human approver and a decision log
- Success defined on your metric, against your baseline
- Training and the LMS record included, not extra
- Evidence model reviewed by your risk function in week one
- Next workflow scoped from measured results