Sales Theorem
Every engagement starts with a diagnosis. What changes is how far we take the work, and where it ends.
The same three modes apply to Go-to-Market, Sales Engine and Commerce Growth. Each domain page shows what they mean there; this page explains the model.
Strategy, Forward Deployment and Managed Services work the same way in every domain. Only the system they apply to changes.
Go-to-Market
We sharpen the ICP, positioning and channel plan, and hand you a brief. Your team executes it.
Sales Engine
We name the gaps and hand you a brief. Your team executes it.
Commerce Growth
We assess the opportunity and hand you a brief. Your team executes it.
Go-to-Market
We build them into your CRM, sequences and pages with your team, then hand over on a date agreed at the start.
Sales Engine
We install the system with your team, then hand it over on a date agreed at the start.
Commerce Growth
We configure the platform and bring in the first partners or advertisers with your team, then hand over on a date agreed at the start.
Go-to-Market
After the handover, we revisit ICP and positioning on a fixed cadence and report channel by channel.
Sales Engine
After the handover, we keep the system current and report on it every month.
Commerce Growth
After the handover, or on a platform already live, we run the network and report every month.
Sometimes the gap is a person, not a system. We place a senior operator inside your team, in a defined role, for a defined period, with an end date agreed at the start.
A senior sales, go-to-market or commerce operator, working inside your team on a role written down before they start.
The period and the end date are agreed at the start, with a handover to your team or to a permanent hire.
At each review we confirm or adjust the scope. Never open hours against an invoice.
A brief is written so your own team can execute it without us. Every brief follows the same structure; the target system changes with the domain.
What is missing or not working in the system, each point tied to evidence from your own history.
The system your team should be running, specified precisely enough to execute. Its contents depend on the domain.
Which tool fits, and why, chosen after the diagnosis. It can be one of ours or one from outside our portfolio.
What to change first, what can wait, and who on your team owns each part.
Ends with a brief
A structured read of the system as it runs today, against your real history. Two to three weeks.
The target system, reviewed with you.
A written brief your own team can execute. The engagement ends here.
Ends with a handover
The same diagnosis, as the starting point for the install.
The target system, reviewed with you before anything is built.
Built inside your actual tools and workflow, with your team.
A named date when the system is yours to run alone.
Continues on a fixed cadence
We keep the system current and report on it every month.
Scope and results reviewed on a fixed cadence, never an open-ended arrangement.
Every engagement is scoped before it starts. You know what you are getting and when, never open hours against an invoice.
The handover date is agreed when the engagement is scoped, not when the work runs out.
Until that date, we build and run the system alongside your team. We leave when your team can run it without us.
After the handover, the system is yours. If you want it kept current, Managed Services picks up from there.
The gap is named before a tool is picked. The tool a brief points to can be one of ours or one from outside our portfolio, never ours by default.
CRM & sales
HubSpot · Salesforce · Gong · Fireflies · Chorus
Affiliate & partnerships
Impact · Awin · Partnerize · CJ · Rakuten Advertising · Optimise · Involve Asia · PartnerBoost
Marketplaces & social commerce
Amazon · Shopee · Lazada · TikTok Shop
Paid media
Meta · Google · YouTube · TikTok
Strategy ends with a brief your team executes. Forward Deployment installs the system with your team and hands it over on a date agreed at the start. Managed Services keeps the system current after the handover, reviewed on a fixed cadence.
Yes. Strategy stands on its own and commits you to nothing further.
Only when they fit, and we say so when we do. Our Forward Deployment and Managed Services experience comes from running tools built within the group, one per domain: MLPLY for sales teams, Oderra for advertising, Orvik for affiliate programs. The tool is still chosen after the diagnosis: one of these, one from the platforms you already use, or none at all. Never ours by default.
Yes. An embedded operator joins your team in a defined role, for a defined period, with an end date agreed at the start and reviews on a fixed cadence.
We are based in Singapore and work across Southeast Asia.
Every engagement is scoped before it starts. You know what you are getting and when, never open hours against an invoice.
A diagnosis usually takes two to three weeks. Deployment timing is scoped after the diagnosis.
The date is agreed when the engagement is scoped. Before it, we build and run the system alongside your team; on it, the system is yours. If you want it kept current, Managed Services picks up from there.