Operations & Revenue Operations · Warsaw 🇵🇱 · EU citizen
I lead a 50+ agent operation across 14 regulated European markets, on KPIs tied directly to revenue, reporting straight to department leadership. Six years before that in finance and operations at SAP and Dell — collections, accounts receivable, order-to-cash — including 100% of revenue and collection targets across North America two years running.
What sets me apart from most operators is that I don't just run the operation — I build the software it runs on. When the off-the-shelf tools didn't give the operation the visibility it needed, I started building my own, in natural language with AI assistance.
The ecosystem below is where that goes furthest: I rebuilt the idea from scratch, on synthetic data, as one connected system — to show how I think about a business end to end, not as separate departments but as a single chain where every decision feeds the next.
Six single-file control surfaces that follow one decision down the whole chain — from the shift being covered to the cash being collected. Not six separate demos: one company seen from six functions, on the same hubs, the same markets and the same data universe, with data flowing between the tools.
| Stage | Tool | The question it answers | |
|---|---|---|---|
| Capacity | Shift Planner | Is the shift covered? | live · repo |
| Workflow | Ticket Triage | Who takes what, without collisions? | live · repo |
| Productivity | Performance Tracker | Is the team performing? | live · repo |
| Retention | Customer Cockpit | Does the base retain & grow? | live · repo |
| Revenue | Revenue Cockpit | Are we going to make the number? | live · repo |
| Cash | AR Cockpit | Did the money actually land? | live · repo |
▶ Start at the ecosystem hub →
The chain isn't just a narrative — data moves across it. Each export is shaped to be the next tool's import:
- Performance Tracker → Customer Cockpit. Export QA by operation; account health re-scores from real support quality. The support floor's performance drives the retention read.
- Customer Cockpit → Revenue Cockpit. Export the retained + expanded base as the installed revenue new deals build on.
- Revenue Cockpit → AR Cockpit. Export closed-won deals as invoices; the same money becomes a receivable to collect.
That's the thing I care about most as an operator: not six dashboards, but one money trail you can follow from a covered shift to landed cash.
Every tool is a single index.html — no backend, no build step, no framework — deployable to GitHub Pages as-is and opening instantly with zero setup. Vanilla JavaScript for the models and logic, Chart.js for visuals, PapaParse for CSV. Each ships with a seeded synthetic dataset (mulberry32) so the demo always works, and a column-mapping uploader that takes a real export — handling European or US number and date formats, mixed separators and encodings, reporting skipped rows rather than dropping them silently.
Everything is synthetic and everything stays in the browser. No real customers, agents, deals or company names anywhere. No credentials, no data leaving the page.
I'm not a software engineer — I'm an operations person who builds the tools the operation runs on. The first ones I built were for a real team, in natural language with AI assistance; this ecosystem takes what that taught me and rebuilds it as one coherent system, on synthetic data, to show how I think about an operation rather than to ship a product.
Six years in finance and operations — collections, accounts receivable, order-to-cash at SAP and Dell, including 100% of collection and revenue targets across North America for two consecutive years. Now leading a 50+ agent operation across 14 regulated European markets.
Focus: Revenue Operations · Finance Operations · Business Operations · Internal Tools — fintech, payments, tech & marketplace.
📫 LinkedIn · Warsaw, open to remote-first across the EU