Revenue Operations, Built as a System.

I design and improve the systems behind B2B revenue: CRM architecture, lifecycle management, pipeline operations, automation, reporting, lead scoring, and GTM handoffs. My approach starts with the bottleneck, traces it to the underlying process, and builds a system people can actually operate.

Target role Revenue Operations | GTM Operations | CRM Operations

View RevOps Work Download Resume

I Look for the System Behind the Symptom.

A pipeline is full.

But nobody trusts it.

Leads are coming in.

But follow-up is inconsistent.

The CRM is populated.

But the data cannot support a reliable forecast.

A handoff exists.

But nobody knows who owns the next action.

That is where I work.

I don't start by asking who made the mistake.

I start by asking:

What system produced it?

That instinct started in customer operations and became the operating principle behind my work in Revenue Operations.

I Didn't Change Directions. I Went Deeper.

  1. Customer Operations

    I learned what broken processes feel like from the front line: escalations, SLAs, customer expectations, workload allocation, and the consequences of unclear ownership.

    At CCI Global, a ticket-queue problem initially looked like an agent-performance issue. The deeper problem was the allocation mechanism. I built a round-robin process to make assignment more predictable and fair.

    That was the first version of the question that still drives my work:

    What is the system producing this behavior?

  2. Revenue Operations

    At Zawaa Tech, that question moved into the revenue engine.

    I began with websites and digital products. Then I saw what happened underneath them: fragmented lead management, inconsistent follow-up, unclear handoffs, weak documentation, and CRM data that could not always be trusted.

    I moved into CRM architecture, GTM process design, automation, reporting, lead scoring, attribution, and operational documentation.

    This is the work I am pursuing professionally.

  3. Technical Systems

    I am now extending that systems discipline into the technical layer.

    AWS, Linux, Python, APIs, serverless architecture, Infrastructure as Code, and CI/CD are deepening my ability to understand what sits underneath the business systems I already work with.

    RevOps is the destination. Technical depth is the leverage.

I Build the Revenue Operating Layer.

CRM Architecture

  • HubSpot
  • Salesforce
  • Custom Fields
  • Object Design
  • Lifecycle Stages
  • Pipeline Architecture
  • Field Mapping
  • Data Governance
  • Lead-to-Revenue Attribution

The goal is not to create a sophisticated CRM. The goal is to create one the business can trust.

GTM Process Design

  • Lead Capture
  • Qualification
  • Routing
  • Sales Handoff
  • Opportunity Management
  • Customer Onboarding
  • Lifecycle Transitions
  • Cross-Functional Ownership

I look for the places where context disappears, responsibility becomes ambiguous, or the next action depends on someone's memory.

Automation

  • HubSpot Workflows
  • Salesforce Flow
  • Zapier

Lead management, lifecycle updates, task creation, handoffs, notifications, data movement, operational triggers.

First fix the process. Then automate it.

Pipeline & Reporting

  • Pipeline Hygiene
  • Forecasting Dashboards
  • Sales Reporting
  • Executive Reporting
  • Lifecycle Reporting
  • Lead-Source Visibility
  • Data-Quality Checks

I care less about how impressive a dashboard looks than whether a revenue leader can use it to answer: what is happening, why it's happening, and what needs attention next.

Lead Scoring & Prioritization

I design lead-scoring models using ordinal value scales and behavioral signals to help teams distinguish activity from actual buying readiness.

The purpose is not to produce another score. It is to help sales spend attention where it has the highest operational value.

GTM Documentation

  • SDR Prospecting
  • AE Handoffs
  • CRM Governance
  • Customer Success Onboarding
  • Process Documentation
  • GTM Playbooks

Using Notion and structured documentation, I work to move critical knowledge out of individual heads and into the operating system.

The Work Is the Proof.

Mission 01 — CCI Global

Before Revenue Operations, I Learned to Find the Mechanism.

Customer Success → Operational Systems

Cases were expected to remain unattended for roughly 60 minutes or less.

The instruction was simple: pick a ticket when you see one.

The process was not.

There was no clear mechanism for deciding who should take the next case. Workload felt uneven. Friction followed.

I built a round-robin allocation process that tracked assignments and rotated cases more predictably.

The important lesson was not the tool.

It was the diagnosis: a recurring performance problem may be a system-design problem.

Complex B2B inquiries / month
150+
CSAT
~95%
SLA compliance
~95%

That became the operating instinct I carried into RevOps.

Mission 02 — Zawaa Tech

I Started Building Websites. Then I Found the Revenue Problem Behind Them.

Founder → Revenue Operations

Zawaa began with websites, e-commerce, and digital products.

Then I started seeing the machinery behind the front end.

Leads came through multiple channels. Follow-up varied. Ownership was unclear. Handoffs lost context. Documentation was inconsistent. CRM data could become difficult to trust.

The bottleneck was often not lead generation.

It was everything that happened after the lead arrived.

So I moved into the operating layer.

I diagnosed GTM and pipeline bottlenecks. Built Zawaa's HubSpot CRM from scratch. Worked across HubSpot and Salesforce architecture. Designed lifecycle structures, field mapping, workflow automation, reporting, lead scoring, attribution models, and GTM playbooks.

I also conducted 500+ outbound touchpoints and discovery conversations with SaaS founders and operators, using those conversations to sharpen positioning and understand the operational problems businesses were actually experiencing.

This is the work I want to do next, professionally: Revenue Operations.

Mission 03 — Technical Depth

I Am Going Deeper Into the Technology Behind the Revenue System.

RevOps → Technical Systems

My cloud work is not a second career competing with RevOps.

It is an extension of the same systems discipline.

I'm building practical capability across AWS, Linux, Python, APIs, serverless architecture, infrastructure, and CI/CD because modern revenue systems increasingly depend on technical systems underneath them.

I am still developing this layer.

That distinction matters.

I am not presenting cloud as a completed mastery claim. I am deliberately building deeper technical fluency so I can understand more of the stack behind the systems I design and operate.

  • AWS
  • Linux
  • Python
  • APIs
  • Serverless
  • Infrastructure as Code
  • CI/CD

The more of the system I understand, the better decisions I can make at the operating layer.

My Workflow Is Simple. The Problems Usually Aren't.

  1. Diagnose

    Find the bottleneck. Separate symptoms from causes. Identify where information, ownership, or process breaks.

  2. Model

    Define the lifecycle. Map the handoffs. Clarify ownership. Make the process explicit.

  3. Architect

    Design the CRM structure. Define fields, stages, workflows, reporting, and governance.

  4. Automate

    Remove repetitive work. Connect systems. Create operational triggers.

  5. Measure

    Build visibility. Check data quality. Track pipeline health. Find the next bottleneck.

  6. Improve

    The first architecture is not the final architecture. I keep investigating.

The Role I Am Building Toward Is Clear.

I want to work in Revenue Operations because it sits at the intersection I have been moving toward for years: customers + process + data + technology + revenue.

I understand the customer-facing consequences of bad systems.

I have built and structured CRM and GTM systems.

I have worked on automation, reporting, lead scoring, documentation, and operational audits.

And I am developing deeper technical fluency in the infrastructure underneath modern business systems.

I am not looking for a title that lets me stay close to technology.

I am looking for a role where I can help make the revenue engine more visible, more reliable, and easier to operate.

What I Bring Into a RevOps Team

CRM Architecture

  • HubSpot
  • Salesforce
  • Data Structure
  • Lifecycle Design
  • Pipeline Architecture

Revenue Operations

  • GTM Processes
  • Lead Management
  • Handoffs
  • Lead-to-Revenue Attribution
  • Data Governance

Automation

  • HubSpot Workflows
  • Salesforce Flow
  • Zapier
  • Operational Triggers

Reporting

  • Pipeline Hygiene
  • Forecasting
  • Executive Reporting
  • Sales Performance
  • Excel

Enablement

  • Notion
  • GTM Playbooks
  • SOPs
  • CRM Governance
  • Customer Success Onboarding

Emerging Technical Depth

  • AWS
  • Linux
  • Python
  • APIs
  • Serverless
  • Infrastructure as Code
  • CI/CD

Still Building. Deliberately.

I am polishing the parts of RevOps I already practice while deepening the parts I am still learning. That means:

  • Getting better at architecture.
  • Getting sharper at diagnosis.
  • Making reporting more useful.
  • Understanding attribution more deeply.
  • Designing cleaner automations.
  • Building stronger operating documentation.
  • Extending my technical understanding into cloud infrastructure and application architecture.

I would rather show the work than claim mastery.

The systems can speak for themselves.

Hiring for RevOps? Start Here.

If you are building a revenue organization and need someone who can work across CRM, GTM processes, automation, reporting, and operational systems, I want to talk.

I am looking for a Revenue Operations / GTM Operations / CRM Operations role where I can contribute immediately, deepen my craft, and take on increasingly complex systems.

Review My RevOps Experience View My Resume

Good revenue systems don't happen by accident. They are designed.