I drop into orgs that are partially broken, mostly undocumented, and quietly distrusted by the people who use them every day — and rebuild trust one fix at a time.
METHOD
The first move is always an audit — not a slide deck, but a grounded read of what the system actually does: where data is unreliable, which automations are silently failing, and what the team has worked around instead of fixing.
From there the work is incremental. Fix what blocks the team today, document the parts that have to stay, retire the parts nobody trusts. Reporting and dashboards do double duty as adoption levers — when people can see their work in the system, they start using the system.
PHILOSOPHY
Three rules I don’t break
01.
Clean systems beat clever ones
A Flow another admin can read in five minutes is worth more than a clever Apex trigger only the original author understands. Boring is a feature.
02.
Adoption matters more than features
A perfectly designed object that nobody uses is a liability, not an asset. I would rather ship a smaller change the team actually adopts than a comprehensive redesign that sits unused.
03.
Process before automation
If the underlying process is unclear, automating it just makes the confusion faster. I push back on automation requests that paper over a process question nobody has answered yet.
CAREER
Where I’ve done it
9+ years of revenue systems work, mostly as the first or only Salesforce person on the team.
2025 – PRESENT
Independent Salesforce & RevOps
Self-employed
— Contract and full-time engagements across SaaS and services companies.
— CRM audits, targeted implementation, and ongoing operational ownership.
2022 – 2025
First Salesforce Hire · RevOps
SmithRx — pharmacy benefit manager
— Built revenue and service operations from zero for a 650k-member PBM.
— Member outreach, agent productivity, broker, and compliance infrastructure — HIPAA-constrained.
2020 – 2022
Salesforce Consultant / Delivery
Cadalys · Mirketa
— Owned end-to-end Salesforce delivery for enterprise clients across tech, edtech, and healthcare.
— Integrations, large-scale data migrations, contract and revenue infrastructure.
2019 – 2020
Business Technology Analyst
Deloitte (Google engagement)
— Led a Service Cloud migration of 700k+ support records for Google Maps.
— Case routing, entitlements, and data enrichment to a clean, validated go-live.
2014 – 2017
Systems / Application Engineer
Infosys · Accenture — India
— Financial-process automation, mainframe batch development, and RPA integrations for US banking operations.
— Foundation before an MS in Software Engineering at UC Irvine.
BOUNDARIES
What I’m not
Not an admin-for-hire working tickets. I do the work that moves a system from unreliable to trusted, not the request queue.
Not an architect who only draws diagrams. I build the thing. Diagrams are a byproduct, not the deliverable.
Not a sales engineer pretending to be RevOps. RevOps lives in the boring middle: data quality, process design, reporting infrastructure, change management. That’s where I work.
Want to talk about your revenue systems?
The fastest way to find out if I’m a fit is a short conversation.