Client names are kept confidential — these are described by industry and result. Full technical detail is available under NDA on request.
A data-center SaaS provider was running renewals through a legacy billing platform that couldn't keep pace with their product and pricing complexity. They needed a full Revenue Cloud Advanced implementation — and someone to own it as both architect and project lead.
Designed the complete model: products, bundles, and pricing procedures; approval routing; and a document workflow via PandaDoc. The centrepiece was a WHMCS-to-Revenue-Cloud renewal migration that moved an existing recurring-revenue book onto the new platform without dropping renewals in transit.
A manufacturing and distribution business needed B2B buyers to check out and pay online — but the payment flows weren't clearing, and gateway provisioning had stalled the rollout. Both checkout card payments and invoice-based Pay Now had to work reliably.
Diagnosed the gateway provisioning issue, moved the checkout to the native Salesforce Payments component, and set up the correct permissions and webhook plumbing. Confirmed both card checkout and authenticated Pay Now clearing cleanly through to the processor, and set up the sandbox as a production-ready reference.
The same business wanted a portal assistant that could help authenticated users self-serve — without ever exposing data the user shouldn't see. An agent is only safe if its guardrails are designed in from the start, not bolted on.
Architected the full agent: a topology of ten subagents, custom flows, and clear action-to-flow bindings for every capability the agent offered. A central verification gate governs the entire security model — the agent can only act once the user's identity is confirmed.
An analytics SaaS company was quietly losing revenue on amendments — mid-term changes weren't prorating correctly, but nobody could point to why. The gap was real money, spread thin enough to be hard to see.
Ran a revenue-leakage analysis that traced the gap through the amendment logic to the exact configuration objects responsible, then staged a recovery path for the team to review and approve — no silent writebacks. This engagement became the basis for the Logicrux leakage-forensics methodology.
Revenue configuration, pricing logic, and security models are commercially sensitive. Client names and specifics stay confidential by default — described here only by industry and outcome. In a scoping conversation, and under NDA, I'm happy to walk through the technical detail of any engagement above.
Reach out and I'll walk you through the architecture, the decisions, and what it would take for your org.