Partners

We know the engine, and you know the market.

Partnerships usually take one of two shapes, though we're open to others.

Reseller

You find the customer, keep the relationship and the renewal, and share in the income. The licence itself is between TVM and the customer, and you or the customer run it. We're the wholesaler and you're the face.

White-label

You contract with the customer, set your own price, host and give first-line support. You hold the source under a white-label licence, we agree the wholesale terms between us, and your customers never see the source or us. Each of your customers is a tenant in your one installation rather than a separate install, so serving your twentieth customer costs you close to nothing. One thing to know up front: our interface doesn't carry your branding yet (see below).

What we ask of a partner

  • Knows the market and its legislation
  • Brings the local rules as configuration
  • Can demonstrate the product themselves
  • Runs first-line support in the white-label shape
Know the business, whatever your stack

The partner on a different stack

Over the years we've worked with some very good payments and banking consultancies. They knew their market inside out, and more than once we sat down to talk about them partnering on our software. It usually stalled on the same thing: their people worked on a different technology stack, and taking on someone else's engine in an unfamiliar language and framework was a big ask.

That problem has largely gone away. The AI, the skills and the rules ship with the source, so a partner who knows the business can describe a change in business terms and have it built inside the same guard rails we use, without first becoming expert in our stack. And the stack itself is no longer set in stone. We moved our own front end from Blazor to React in days, and with the decision records and tests in place, swapping out a database, a framework or a user interface is a project rather than a rewrite. The consultancy that couldn't partner with us a few years ago is now exactly the partner we're looking for.

Your brand on it

Statements carry the operating entity's branding today, but the interface doesn't yet.

For now a white-label partner puts its own interface in front of the engine using the API, which is how a fintech uses it too. Branding our interface per customer, with your logo, name and colours, isn't built yet. It's a configuration surface we can add and it's on the list, so if it's the thing you need first, tell us and it moves up.

What we do not know

We know the South African, European and ISO rules, but we don't know yours.

Local credit law, statement rules, regulatory returns and payment schemes are all configuration, and the partner who lives in that market is the right person to write them. That's the whole point of making them configuration.

How big is a new country? The UK is our worked example. Its calendar, identification, addresses, legal forms and local rules came as a folder of configuration, with no code change. The payment schemes are the bigger piece, because each new rail needs its own file formats built, and that's development work, though it's exactly the kind the AI and the skills handle well. The UK layer →

Working out what a country's law actually asks of the engine is quicker than you'd think. Auditing the South African legislation, the National Credit Act, FICA and the credit bureau rules, against the engine took a single working session with the AI, and what it found is written up, gaps included, on our standards page.

We've done this before. New Zealand was our third market, served through a joint venture in Auckland, with finance companies including Instant Finance, UDC, Numeria Finance and Hopscotch. The local knowledge came from people in Auckland rather than from Cape Town, and the New Zealanders were some of the friendliest customers we've ever had.

The rules we hold ourselves to

No conflict of interest

A partner doesn't compete with the customers it serves.

Terms agreed up front

Whatever the commercial model, it's clear and agreed before the first customer.

Full visibility of end customers

Every tenant is disclosed to us under a non-disclosure agreement, because white-label doesn't mean invisible.

A step-in right

So that no customer is ever left stranded.

Exclusivity has to be earned

If a partner wants exclusivity, it comes with a commitment and an end date.

Contact

Talk to us about your market.

jrich@tvm.co.za