01
NOBODY NAMES THE TASK
The team cannot say which piece of work should change first, or who owns the change. Ambition stays abstract, so nothing ships.
We help Hong Kong teams put AI into one workflow they already run, measure the difference, and keep what works. With a private, on‑premise path for data that cannot leave the building.
BOOK A WORKING SESSIONWORKING WITH TEAMS ACROSS HONG KONG
Proofs of concept impress in the demo, then never reach the daily work
/ THE PROBLEM
Most teams do not need another license or another training day. They need one task done a better way, clear rules for data, and proof that the new way beats the old one. Four things usually stand in the way.
01
The team cannot say which piece of work should change first, or who owns the change. Ambition stays abstract, so nothing ships.
02
No one wrote down how long the work took before. So no one can show what got better, and the budget dies at the next review.
03
Nobody says what may go into which tool. People paste too much into public models, or avoid AI completely. Both cost you.
04
A demo works in a sandbox and stalls before production. The gap between a pilot and daily use is where most AI budgets go to die.
That is why we start small: one task, the team that owns it, and a number to beat.
/ THE APPROACH
Every engagement runs the same way, from a two‑week first deployment to a private setup. Plain steps, a fixed price, and a written verdict at the end.
DAYS 1–2
Choose one task where a better way matters. Agree who uses AI, what data is off limits, and the number to beat.
DAYS 3–8
Set up the tools and the rules, then work on live cases together until the new way holds without us in the room.
DAYS 9–10
Put the new numbers next to the old ones and agree what happens next: expand, revise, or stop. If the case is weak, we will recommend stopping.
You keep the working setup, the rules, the training, and a written recommendation. THE BASELINE DECIDES, NOT THE DEMO.
/ PRIVATE AI
Most teams only need approved accounts and clear rules. When the data demands more, we add a gateway you control, or a model on hardware you own. Use the level of control the work actually requires.
FOR TEAMS THAT NEED APPROVED ACCESS FAST
Accounts in your name, written rules for safe use, staff training, and a plan for daily work.
FOR TEAMS THAT NEED MASKING AND LOGS
Your team reaches external models through one gate in your cloud account. It masks sensitive data, logs use, and caps spend.
FOR WORK THAT MUST STAY ON‑SITE
A private model on machines you own, tested on your real workload, with a written runbook for your team.
You keep the accounts, the keys, the logs, and the hardware. You can remove our access at any time.
/ PRICING
Almost nobody in this market prints a real price. We do. The fee is agreed before work begins, in writing. Software, cloud services, and hardware are billed separately unless the proposal says otherwise.
MOST TEAMS START HERE
From HK$120,000
TWO WEEKS · ONE TEAM, ONE TASK
AFTER PROOF
From HK$320,000
8–12 WEEKS · ONE TEAM
PRIVATE PATH
Setup: fixed HK$98,000
4–5 WEEKS · GATEWAY FROM HK$19,500/MO
/ ABOUT
No software to sell. No quota to hit. No handoff to a junior team after the pitch. The practice is led by Johannes Janousek: previously a data scientist at Massar Capital, an award‑winning New York macro hedge fund, with an MSc in Data Science from King’s College London and startup experience in Berlin, New York, and Hong Kong.
We work directly with your team, write everything down, and set up only what makes sense for your business. We run our own work the same way we advise clients to run theirs.
/ FAQ
Teams whose work is analysis, documents, operations, code, or client service. Not only engineers, and not only large companies.
Start with the First Deployment. It is a small test on your own work, measured against your old numbers. If the results are weak, we will say stop. The first deployment is the decision instrument, not the commitment.
We agree the rules in writing before we start: which tools are approved, what may go into a model, and who reviews the output. If your policy asks for more, the private AI options add masking, logs, and on‑site models.
If the numbers hold, most teams expand to a second task or move to Embedded Adoption, where we stay until the new way is routine and then hand everything over. Launching is not the finish line; sticking is.
Both. We are based in Hong Kong and work on site with local teams. For teams elsewhere, we do the same work remotely.
/ CONTACT
A short note is enough: what the team does and what you want to change. Kept confidential; no sensitive data is needed at this stage.