Everything below is ours and on our servers. Nothing follows you to another site.
Who
How we work
Rebuild
WHITE LABEL · HOW IT WORKS
Most partnership processes are written to make every enquiry feel like progress, right up until a contract nobody actually wanted lands on the table. This one is built the other way: two of the six steps exist specifically to end things early if the fit is not real, before either side has spent real money finding out.
Most enquiries stop at step two. That is the process working, not failing.
FIRST CONVERSATION TO LAUNCH
The same six steps for every platform and every territory, adjusted for platform-specific configuration time.
Which platform, which territory, and what you already run there. Twenty minutes, and we will tell you on the call if it is obviously not a fit. This is the first of two points where the honest answer is often no.
We study market size, how money moves in that sector locally, regulation and payment rails, at no charge to you. Most proposals fail here. We would rather decline early than build something that cannot work in your country, which is the second point where the answer is often no.
Territory boundaries, ongoing arrangement, exit terms and notice period. All of it in writing before either side commits anything.
Your domain, your identity, your languages, local payment and delivery integrations, and your data migrated if you have existing records.
A controlled group first, so problems surface with people who forgive them. You get direct access to the engineer running your instance.
You sell. We monitor, patch and improve. Every platform update reaches your instance without you asking or paying for it.
THE TWO DECLINE POINTS
A partnership that should not have started is more expensive to end later than to decline now.
If the platform genuinely does not fit the territory, or the person on the call is looking for something this is not, a franchise, a passive investment, full source code, we say so on the call. Neither side gains anything from a polite maybe that both people already know is a no.
We study market size, money flow, regulation and payment rails before committing engineering time or our own operating standard to a territory. If the research does not support it, we tell you that directly, at no charge, rather than build something that cannot work in your country and call it your problem later.
Both of these protect the partner as much as us. A territory that cannot actually support the platform is a bad outcome for whoever licenses it, not just for the platform's reputation.
STRAIGHT ANSWERS
What each step actually involves, in more detail than the six-line summary above.
Twenty minutes, usually the same week you reach out. Bring the platform you are interested in, the territory you have in mind, and what you already run there today. We will tell you on the call if it is obviously not a fit, rather than let a process run for weeks toward an answer we already know.
Market size, how money actually moves in that sector locally, regulation and payment rails. Two weeks is enough time to check these properly rather than skim them. We are deciding whether to commit engineering time and our own operating standard to a territory, so this step is genuinely diligent, not a formality before an inevitable yes.
Territory boundaries, the ongoing arrangement, exit terms and the notice period, all specific to the platform and market discussed in the first two steps. Nothing is agreed verbally and confirmed in writing later. It is written first, and both sides sign the same document.
Yes, at step five: a soft launch with a controlled first group of customers, before opening more broadly. Problems surface with people who will forgive them, and you have direct access to the engineer running your instance during that period, not a support ticket queue.
Twenty minutes on a call, then two weeks of research at our cost. If your market does not support it, we will tell you that instead of selling you a licence.
One tap, then your app opens with it written.