RevOps

Scale revenue,
not operational
complexity.

I help your revenue teams put AI to work across the customer journey, connecting systems, improving data quality and automating workflows so you can grow without adding operational overhead.

Let’s talk

01 The opportunity

Make your
revenue workflows
actually flow.

Replace manual handoffs, scattered signals and repetitive admin with AI workflows built around how your revenue team actually operates.

AI-native RevOps

63%

of AI-native RevOps teams report 20%+ productivity gains.

Everstage × UserEvidence, State of AI in RevOps 2026, n=424

AI at scale

~2×

Companies that embed AI across multiple functions generate nearly twice the profit margins of peers using AI in only a few departments.

McKinsey, Operational Excellence Survey 2026, n=1,000

AI-powered customer operations

5–8%

revenue uplift from AI-powered customer orchestration, through lower churn and stronger cross-sell and upsell.

McKinsey, Next Best Experience, 2025

02 What I Bring

Make more of what you already have.

The best revenue teams aren’t buying more AI. They’re getting more value from the tools, data and processes they already have.
I connect and automate workflows across your revenue operations, making existing systems work better together without replacing what already works.

  1. 01

    Map the operating model

    I map the workflows across your customer journey, including the work that falls between teams and nobody owns end to end. We define the process, ownership, handoffs and context before automating anything.

  2. 02

    Strengthen the foundations

    I make sure the data and tools underneath those workflows can support them. That means fixing critical data gaps, simplifying the stack and connecting the systems you actually need.

  3. 03

    Build the automation

    I build the workflows, agents and integrations around your real processes and business rules, inside the stack you already run. Your team focuses on revenue. I focus on making the system around them work.

Give your revenue teams the freedom to focus on growth.I automate the operational work around them so their time goes where it creates the most value: winning, retaining and expanding customers.

03 Day to day

Built for the
outcome,
not the activity.

AI works behind the scenes, inside the tools your teams already use. It brings the right information forward, flags what needs attention and automates the routine work. Your teams stay in control, and you measure success by business results, not the number of tasks automated.

What your teams see

Revenue agent Mon 09:12
#cs-new-customers

Northwind is ready for handoff.

Brief’s done: deal goals, stakeholders, promised integrations. Three open questions to confirm before kickoff.

Revenue agent Tue 14:40
#cs-onboarding

Acme onboarding at risk.

Kickoff’s in 3 days and there’s still no technical owner. They also mentioned an IT freeze on the last call. Worth locking both down first.

Revenue agent Thu 08:05
#renewals

Globex renewal looks shaky.

Renews in 94 days. Usage is down 31% since the reorg, and nobody’s met the new VP yet. I’d set up an exec check-in this month.

Illustrative example. Company names are fictional.

What the business sees

  • Quota retirement (comes in faster)

    Renewal and expansion quota closes earlier in the period. Agents surface risk and upsell signals months ahead, so the team works the right accounts first.

    Renewals, expansion signals

  • Capacity per CSM (goes up)

    Each CSM can carry more accounts without dropping the ball. Handoff briefs, onboarding follow-ups and account admin move to agents, so their hours go to customers.

    Handoffs, onboarding

  • Net revenue retention (goes up)

    Where it all adds up: revenue kept and grown from your existing customers. Retention and expansion compound instead of depending on individual heroics.

    Retention and expansion, end to end

Metrics are agreed per engagement and measured against your own baseline.

04 How an engagement runs

From diagnosis
to production.

  1. Diagnostic

    A fixed-scope review of your revenue workflows. You get a prioritised view of where revenue leaks, the first workflow to fix, and a scoped proposal.

    Fixed scope, fixed price

  2. Build

    The first workflow goes into production in your stack, measured against a baseline we agree on up front. Timeline committed in the proposal.

    Weeks, not quarters

  3. Run or hand over

    I run and extend it to the next workflow, or your team takes it over with full documentation.

    Your choice

05 What you own

No new licence.
No lock-in.

Everything runs in your CRM, your Slack and your data. If I leave, it keeps working.

  • Runs in your existing stack
  • Open-source components
  • Full documentation and handover
  • Your data stays in your systems
Portrait of Zsuzsanna Tamas

06 Why me

Senior-led.
Hands-on.

The person you meet in the first call is the person who leads your build. No hand-off to a junior team once the contract is signed.

  1. 0110+ years building products and teams, including AI/ML and personalisation at Amazon Music.
  2. 02When the build needs more hands, I bring vetted forward-deployed engineers and lead them myself. You keep one point of accountability.
  3. 03I own the workflow across teams: build, alignment, enablement and adoption.

07 FAQ

Good questions.

What happens if you leave?

The solutions are built to be yours, not to depend on me. They run within your existing systems wherever possible, with clear documentation and ownership. Your team can take over, or I can stay involved to maintain and improve them.

Which tools do you work with?

I work with your existing tools, whether that's Salesforce, HubSpot, Gainsight, Planhat, Gong, Clari, Outreach, Slack or other platforms in your stack. I'm tool-agnostic: I connect what you already use and introduce new components only where they add clear value. No unnecessary platforms or subscriptions.

How do you handle data and EU compliance?

I design around your security, privacy and compliance requirements from the start. That includes where data is processed, who can access it, and how AI actions are monitored and logged. I work with your IT, security and legal teams to align the solution with applicable GDPR and EU AI Act requirements.

How long does a build take?

I start with one clearly defined workflow rather than a large transformation project. Many implementations can be delivered in weeks, depending on the complexity of your systems, data and approvals. You'll have a clear scope, timeline and deliverables before we start.

How is it priced?

We start with a fixed-price Diagnostic to identify and prioritize the opportunities. Implementation is then scoped and priced per workflow, with clear deliverables and agreed costs. Any additional work is discussed and approved before it begins. No unexpected bills.