Two operators who cover each other.
Revenue and operations work is wide: CRM, reporting, integrations, automation, AI on top of it all. Companies usually buy it one of two ways. An agency brings a big team — and the overhead that comes with it: account managers, layers, prices built for enterprises. A freelancer is light and fast — but one person goes deep in one thing, and the rest of your stack waits.
RSOD is the third option. Two senior operators with different stacks and enough overlap to cover each other. You talk to the people who do the work — no account manager in the middle, no handoff to a junior. And everything you see on this site is work we did with our own hands, inside live businesses: we were there when the problem showed up, and we stayed until the system that fixed it ran on its own.
Where we come from
We met at university in Kraków, and both of our careers started the same way: inside Google's vendor operations — sales and support for Google products, on Google's own systems, to Google's own standards. That's where we learned how the world's most measured company actually runs: everything written down, everything counted, every process owned by someone.
A few years later we were working side by side at a telecom-automation company — Mark on business development, Anton on the product. We've tried more than one joint project since; RSOD is the one that stuck, because it's built on the work we're both best at. Three years now, building revenue and operations systems for companies across Europe and beyond.
Mark
Mark has spent ten years climbing every floor of the revenue machine.
He started on the phones — inside sales, one of the strongest sellers on his team. Then he led sales and support teams inside Google's operation, ran sales teams on the Microsoft account across Central and Eastern Europe, and moved to the systems side as a sales operations manager. Today he is Chief Commercial Officer of an international consumer business, with sales running across Latin America, Africa, Asia and the Middle East.
Ten years, every seat: agent, team lead, operations manager, CCO. That's the point of having Mark on your project: he designs processes for the people who have to live in them, because he has been every one of those people.
Anton
Anton's ten years are one theme with rising stakes: take a commercial process and turn it into a machine.
He also started inside Google's vendor operations, as an expert on Google Ads and Analytics. Then business development in cloud telephony — scraping, data mining, building the CRM before selling from it. Then four years at the telecom-automation company where our paths crossed again, growing from project manager to product manager for AI voice assistants to pre-sales team leader. Since then he has run sales at an AI data-extraction startup, led B2B revenue operations at an international marketplace, and today he is a senior consultant at a European cyber-threat-intelligence company, working with its leadership on process and operations.
His daily stack is the deep technical end: Make and n8n pipelines, custom scrapers, flows that move records out of a CRM, through GPT, and back as clean data. HubSpot and Pipedrive both. Lately — production tools built on Claude.
Before anything gets built, he maps how the work is actually done — where deals stall, which numbers the team trusts, which they quietly ignore. When we score sales calls with AI, he writes the criteria with the sales team, tunes the prompts, and validates the output against real outcomes, so a score means something instead of just looking precise. And he's hands-on with the tools himself.
Once we agree what the system must do, he makes it real and keeps it running — the parts that have to work at 3 a.m. with nobody watching.
The roles aren't walls — they switch from project to project. On one, Anton runs the scrapers and the data pipelines while Mark writes the SQL and rebuilds the database behind them. On the next, Mark sets up the CRM workflows and the ad campaigns while Anton works with the C-level and shapes the process. Both of us have built CRMs end to end; both of us talk to the client; both of us can hold either end of a project. The specifics are in the use cases.
So neither of us is a single point of failure — and your project doesn't stop because one of us is on a plane.
What working with us looks like
You get two professionals on your problem, start to finish. We scope the work together, one of us leads each piece, and both of us know where everything stands. Advice comes with implementation attached — we don't leave slide decks, we leave running systems.
When a project needs more hands — a developer, a designer, a marketer — we bring in people we've worked with on other projects and would vouch for. They join for the part they're best at; we stay responsible for the whole. It's how we stay two people and still deliver work that takes five.
We work remotely, with clients across Europe and worldwide.