Salesforce CPQ
Product catalogue design, pricing rules, quote lifecycle, contract generation, and renewal automation across the classic Sales Cloud path.
CPQ Administrator certified
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. My Salesforce certifications back the platform side; the integration side is where I get to be most senior.
My own product
Salesforce ISV Partner
Configra — a Salesforce ISV Partner solution for Revenue Cloud
Out of this Revenue Cloud work, I'm building Configra: a Revenue Lifecycle Management managed package that lets sales reps create deal-specific product configurations directly on a quote — without polluting the catalog. It's on AppExchange as a managed package and currently going through Security Review.
Proof: Configra on the Salesforce AppExchange — managed package, in Security Review. Click an image to enlarge.
What I build
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 ten external systems — Stripe (HMAC-SHA256-verified webhooks), Sendcloud/DHL, JIRA, Slack, DocuSign, Notion, SAP S/4HANA, Twilio WhatsApp, plus the German finance stack lexoffice and DATEV.
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.
Credentials backing this
My active Salesforce certifications cluster around Revenue Cloud and its supporting stack.
Salesforce Certified OmniStudio Consultant
Industry Solutions · Jun 2025
Salesforce Certified OmniStudio Developer
Industry Solutions · Jun 2025
Salesforce Certified Industries CPQ Developer
Industry Solutions · May 2025
Salesforce Certified Platform App Builder
Platform · Apr 2025
Salesforce Certified CPQ Administrator
Sales Cloud · Mar 2025
Salesforce Certified Platform Developer II
Platform · Dec 2024
Salesforce Certified Platform Developer I
Platform · Nov 2024
Salesforce Certified Administrator
Platform · Oct 2024
Community
I run the Salesforce Revenue Cloud | Germany community on LinkedIn
A focused group of practitioners — Salesforce developers, consultants, and architects working with Revenue Cloud in the DACH region. I founded it in early 2025 to give the niche a place of its own.
- Members
- 303
- LinkedIn followers
- 13,264
Where this shows up in my work
The reference architecture is real, not hypothetical. Two projects implement different slices of it.