Skip to content

We built ReferOn because
nothing else did the job

Before this was a platform, it was a Google Sheets CRM, built by people who’d spent years fighting affiliate software that fought back. Two years on, we still ship from the same operator instinct: what would we have wanted, the tenth time we exported the same report by hand?

Book a demo

It started in a spreadsheet

I’ve spent years running affiliate programs on legacy platforms. The dashboards contradicted each other. The reports never showed what he actually needed. The reward math required a side-PDF and a calculator. So I built our own CRM in Google Sheets

Vlad Bondarenko Head of Product

It wasn’t elegant.
It was lazy in the right way

Open the sheet, press one button, see this week’s top affiliates. Same sheet, another button: what deal to offer next. Same sheet again: launch a new partner with a tracking link and a reward plan already wired up. The principle has a name now. We call it lazy intelligence, and every workflow on ReferOn traces back to it.

The other lesson came from the opposite side. Across his career, Vlad migrated programs off three different legacy platforms. Each migration taught the same thing in a different way: contract lock-in disguised as integration, useful features quietly hidden behind enterprise tiers, support tickets routed through people who’d never touched the codebase. We built ReferOn as the inverse of those systems.

The team

These are the
people building it.

We grew up wanting to be a lot of things. None of them were “affiliate platform engineer”. We arrived here through different paths and ended up in the same place: building the system we wished existed in our previous lives.

Alex Bukin Alex Bukin

Alex Bukin

CEO

This is the one making the big-boss decisions now

David Harris David Harris

David Harris

COO

This is who’s scaling our operations at high speed

Vlad Bondarenko Vlad Bondarenko

Vlad Bondarenko

CPO

This is who’s building the future of affiliate tech

Camila Beatriz da Silva Camila Beatriz da Silva

Camila Beatriz da Silva

Senior Sales Manager

This is who’s closing all the big deals

Hristiana Stefanova Hristiana Stefanova

Hristiana Stefanova

Head of Partnerships

This is who’s making sure every partner is happy and heard

What we believe

Five rules
we don’t break.

These aren’t aspirations. They’re constraints. When a feature design conflicts with one of them,
the feature changes — not the rule.

1. Clarity

Clarity over complexity.

If a feature isn’t usable on Tuesday morning by a tired affiliate manager, it doesn’t ship. Most “advanced settings” are admissions that the default is wrong.

2. Automation

Automation with control.

Smart defaults handle the common case. The edge cases stay reachable in the same screen. We don’t make you choose between magic and manual; you get both.

3. Real-time

Real-time by default.

If you have to wait for a report to refresh, the platform is already failing you. Live data isn’t a premium feature, it’s the floor.

4. Logic

Logic over buttons.

Every “what about X” question should have a structural answer, not another toggle. Adding settings is the lazy fix; rethinking the model is the right one.

5. Open

Built in the open

We migrate alongside you. New features ship to all clients at once. The engineer who fixed your bug is in your Slack channel.

Affiliate operations,
finally under control

Book a demo