Revenue Cloud

Revenue Cloud is my core. Quote-to-Cash from product catalogue to settlement, orchestrated end-to-end.

I work across the full Revenue Cloud surface — Salesforce CPQ, Industries CPQ, Revenue Lifecycle Management, Contract Lifecycle Management — and own the integration layer that ties it all together. Six certifications back the Salesforce side; the integration side is where I get to be most senior.

What I build

Salesforce CPQ
Product catalogue design, pricing rules, quote lifecycle, contract generation, and renewal automation across the classic Sales Cloud path.
CPQ Administrator certified
Industries CPQ
Attribute-based pricing, context rules, account-context catalogues, and bundle configuration — the Vlocity-era stack used across communications, energy, and manufacturing.
Industries CPQ Developer certified
Revenue Lifecycle Management
Modern Revenue Cloud (post-Vlocity rebranding) — subscription products, usage-based pricing, ramp deals, amendments, and the new product-management surface.
Contract Lifecycle Management
DocuSign envelope flow, Connect webhook landing on a Salesforce Site, Platform Event indirection to escape Guest User FLS limits, and Asset creation on signature.
Quote-to-Cash architecture
End-to-end orchestration via MuleSoft Anypoint across seven external systems — Stripe with HMAC-SHA256 webhook verification, Sendcloud/DHL, JIRA, Slack, DocuSign, Notion.
OmniStudio
DataRaptors, Integration Procedures, OmniScripts, and FlexCards — the OmniStudio surface that sits on top of Industries CPQ for guided sales and partner experiences.
OmniStudio Developer + Consultant certified

Revenue Cloud

The Quote-to-Cash lifecycle I implement

How a deal moves from the catalogue to settlement in the TechnoStore reference architecture — concrete, not theoretical.

01
Product & Catalogue
Industries CPQ attribute-based catalogue with account-context filtering. Products grouped into bundles; pricing tied to attributes (volume, region, channel).
02
Quote & Configure
Bundle configuration, attribute-driven pricing, DACH-specific 19% VAT formulas, and an approval chain. Quote artefacts ready for signature in one click.
03
Order
On activation, OrderTriggerHandler fans out in parallel to five downstream systems: JIRA (inventory ticket), Slack #warehouse (Platform Event → MuleSoft), DocuSign (envelope), Stripe (payment), branded invoice email.
04
Contract
DocuSign Connect webhook lands on a Salesforce Site, publishes a Platform Event (escapes Guest User FLS), and an autolaunched Flow creates the Asset on signature.
05
Asset & Subscription
Asset created on contract signature drives the subscription state machine: active, paused, amended, renewed. License keys generated for digital products via the same fulfilment router.
06
Billing & Settlement
Stripe checkout via MuleSoft; HMAC-SHA256 webhook verified at the Mule edge, then scattered back to Salesforce (mark Paid), Slack #payments-team, and a Choice router for fulfilment — Sendcloud/DHL for physical, license-key generation for digital.