Revenue and marketing operations, designed and built by me
I design revenue and marketing operations for B2B companies and build them myself: the CRM, scoring, routing and attribution, the automation that keeps it accurate, and reporting the board can trust. HubSpot is my core platform, and the work runs well past it, into Salesforce, n8n, Clay, Power BI and the AI layer on top.
- HubSpot architect, all hubs
- Salesforce, n8n, Clay, Power BI
- Remote, worldwide
- English, Bulgarian
- HubSpot Revenue Operations2026
- HubSpot Inbound2026 to 2028
- RevOps XL, HubSpot Solutions Partner
About
I started working in 2011 and have been in and around HubSpot since 2014. Operations has been most of my work since 2016, and revenue operations the focus since 2020. I have worked both as an in-house expert, owning the systems, and as an outside consultant, rebuilding or designing portals from scratch.
Most of my recent work has been in regulated financial services and enterprise consulting. Before that came an agency, iGaming and a global property portfolio. The job was much the same in each: keeping marketing and operations pulling in the same direction.
The part of the work I am most useful at is the whole picture. Operations work usually gets scoped to one team, then breaks where that team hands over to the next, so I treat marketing, sales, design, customer success and product as one system.
I like working directly with customers. Day to day that means CEOs, CFOs and other C-level owners, founders and boards, and the international teams under them.
I design and redesign the system, then onboard each team member who has to use it, and write all of it down.
- Education
- Bachelor's degree, Public Relations, Advertising and Applied Communication. Sofia University.
- Languages
- English, professional. Bulgarian, native. Russian and German, beginner.
- Working
- Remote, worldwide. European hours. A message first, then email or a call, whichever you prefer.
Certified and listed
- HubSpot Revenue Operations2026
- HubSpot Inbound2026 to 2028
- RevOps XL, HubSpot Solutions Partner
What I do
I build it myself, in whichever CRM the company runs: the properties, the pipelines, the workflows and the reports. The data model mapped to how a company actually sells. Pipeline stages that mean the same thing on a sales call and in a board report. Forecast logic that holds, reporting nobody has to caveat, and CRM migrations that arrive with their history intact.
I set up the scoring model, the routing rules and the attribution reports myself. Lifecycle stages, scoring that reflects real buying signal, and routing with an SLA so no lead sits in a queue. Campaign operations, attribution I can defend in a meeting, deliverability, and the data hygiene that makes the rest of it true.
708 contacts classified against a real ICPWho owns the lead at each handoff
The system that runs across sales, marketing, service, customer success, product and finance at once. What looks like a reporting problem is often a handoff nobody owned.
One number every team agreed onNobody owns the shape of the system
Stack rationalization, automation, access and permissions, vendor and contract work. Documentation is delivered with the build rather than promised for the end, so the system is never hostage to one person, including me.
Lead qualification that reasons, enrichment, classification, drafting. Built in where it earns its place, logged, with a person in the loop. I like automation that gives people their time back, and I am wary of the version bought to replace them.
The meeting that files itselfAugment your people, don't replace them
I design and redesign the system, then onboard each person who has to use it afterward, and document all of it. A CRM works when the people in it understand why it is shaped the way it is.
The practice
RevOps XL is the practice: the senior operator a B2B company brings in, embedded and part-time, to own the revenue engine without making a full-time hire. I scope the work and I build it. As it grows, others build alongside me, against the same documentation standard.
The site, the automation, the deploy pipeline and the search work behind revopsxl.com are all mine.
Visit the practice Brands
Work done for, or from inside, these. Some as an employee, some as a vendor, some as a client. The ones I cannot name are not here.
- International Finance Institute
Stack
Laid out the way it actually runs. Pick a node to see what is inside it. The label on each tool is what I can do unsupervised, not what I have logged into once.
Demand and ads Paid and organic acquisition
LinkedIn Ads Hands-on
The channel I have run longest.
- Google Ads Hands-on
- Meta Ads Working
- Brevo Working
Search and behavior Where the traffic comes from
Screaming Frog Hands-on
Technical crawls, cannibalization scans, redirect audits.
- Search Console and Bing Webmaster Hands-on
- SEMrush Hands-on
- Hotjar Working
- Microsoft Clarity Working
Data and enrichment Building the target list
Clay Hands-on
Enrichment waterfalls and list building, wired back into the CRM rather than left sitting in a spreadsheet.
- ZoomInfo Hands-on
Demandbase Hands-on
ABM targeting and intent data.
- LinkedIn Sales Navigator Hands-on
- Apollo.io Working
BuiltWith Working
Technographics, for building a target list from what a company already runs.
CRM The system of record
HubSpot Architect
All hubs. Architecture, admin, the data model, custom objects, workflows, migrations, and training the team that has to run it after I leave.
Certified
- HubSpot Revenue Operations passed 2026
- HubSpot Inbound 2026, valid to 2028
Salesforce Sales Cloud Hands-on
Objects, flows, reporting, and the HubSpot-to-Salesforce identity and sync work that decides which record wins.
Revenue Grid Hands-on
Activity capture and pipeline signal. Useful when the question is what the sales team actually did, not what they remembered to log.
- Pipedrive Working
Automation and AI Keeping it running
n8n Architect
My primary orchestration layer, self-hosted and cloud. Multi-workflow systems running in production, not demos.
AI-to-CRM orchestration Architect
Lead qualification that reasons, enrichment, and data governance. Every action logged, and a person in the loop wherever a wrong call costs something.
Claude Hands-on
The model I reach for in production workflows: qualification, enrichment, classification, drafting.
OpenAI and Gemini models Hands-on
Model picked per job, and weighed against what it costs to run.
Wippy Hands-on
Agentic AI runtime for workflows running inside Salesforce and other SaaS applications.
REST APIs and webhooks Hands-on
The fallback when no connector exists, which is more often than the vendors suggest.
- Make.com Working
- Zapier Working
Analytics Numbers you can defend
Power BI Hands-on
Revenue reporting from first touch to closed won, and the board dashboards sitting on top of it.
SQL and PostgreSQL Hands-on
Querying the warehouse directly when the dashboard will not answer the question.
Python Hands-on
Scrapers, data pipelines, reporting jobs, and one-off migrations.
- GA4 Hands-on
- Google Tag Manager Hands-on
- Looker Studio Hands-on
HockeyStack Working
B2B attribution and journey analytics, for the deals that never touch a form.
- Tableau Working
Delivery How the work is tracked
Jira Hands-on
Reporting and dashboards, and the ticket hygiene that feeds them.
- ClickUp Working
- Wrike Working
- Architect: design it, administer it, own it in production
- Hands-on: build and run it inside client work
- Working: used it on real projects, not my primary
- The tools marked + open.
For agencies
Agencies subcontract revenue operations builds to me, and the arrangement is deliberately dull. White-label under your name, or named on the project. Either way the client relationship stays yours, during and after, and an NDA is standard.
Written scope, agreed before anything starts, priced fixed or hourly. I scope the work and build it myself. The build comes back documented, so your team can carry it afterward. HubSpot across all hubs, Salesforce Sales Cloud hands-on, and the migration, lifecycle, attribution and automation work underneath.
Tell me what the project is. My first reply says whether it is mine to build.
Writing
| Piece | Topic | Published |
|---|---|---|
| Your sales team will not use the CRM, and what that is telling you | CRM adoption | Aug 2026 |
| The buying committee your attribution cannot see | Attribution | Aug 2026 |
| The dark funnel: why B2B deals look like they came from nowhere | Attribution | Aug 2026 |
| Spreadsheet to CRM: why the switch hurts when the software looks simple | CRM migration | Aug 2026 |
| Multi-touch attribution: a CEO's guide to when it pays off | Attribution | Jul 2026 |
| TAM, SAM, SOM: what they mean and how to calculate them | Market sizing | Jul 2026 |
Off the clock
I read plenty. What I keep coming back to is dystopian fiction, the classics and cozy crime novels. A long-time Kurt Vonnegut reader.
Trained in fine arts, mostly graphics. I enjoy research, for work and for pleasure, and I write long essays under an anonymous handle on Substack to work through it.
I like being outside and travelling, preferably near nature and animals. I like food too: on a trip I try to book one Michelin meal to mark it, and bring the people close to me along when I am not travelling solo.
Contact
Start with a message here or on LinkedIn. From there it runs by email or on a call, whichever you prefer.
- in/alexkokova
- The practice
- RevOps XL
