OmniStudio consulting from someone who has actually shipped it.
Nineteen years on the Salesforce platform. OmniStudio since the Vlocity days, including leading it at a global enterprise. Now available to drop into your OmniStudio or document generation project — as the architect who builds it, or the advisor who tells you whether you should.
- 19 years on Salesforce
- OmniStudio since Vlocity
- Enterprise-scale delivery
- No bench. No hand-offs.
Bring me in to build it — or to decide if you should.
Most OmniStudio problems fall into one of two buckets: you've committed and need it built right, or you haven't committed and need an honest answer first.
Build lead
I drop into brand-new OmniStudio or document generation projects as the hands-on architect and lead builder.
- Architecture, naming standards, and reuse patterns set from day one — not retrofitted in month six
- OmniScripts, FlexCards, DataRaptors, and Integration Procedures built to survive handoff
- Document generation pipelines with template governance that scales past the pilot
- Your admins and developers work alongside me, so the org stays maintainable after I leave
FIT: net-new implementations · doc-gen programs · rescues
Advisor
I help you work out whether OmniStudio belongs in your environment before you spend license money and a year finding out.
- Fit assessment: OmniStudio vs. Flow vs. custom code, mapped to your actual requirements
- Licensing and org-impact review before you sign anything
- Architecture review of an existing OmniStudio footprint that isn't working
- Roadmap and enablement plan your internal team can execute
FIT: pre-purchase diligence · struggling programs · platform strategy
OmniStudio is too niche for generalists — and too easy to build badly.
OmniStudio rewards deep, current, hands-on knowledge and punishes everything else. Most consultancies staff it from a bench: someone who did a Trailhead badge last quarter, backed by a partner who has never opened a DataRaptor.
This practice is the opposite of that. One senior specialist, nineteen years into the platform, who has led OmniStudio delivery inside a global enterprise — designing it, building it, and living with the consequences of every decision. The person on the sales call is the person in your org.
- Direct access to the person doing the work — no account layer, no juniors
- Patterns proven at enterprise scale, not copied from documentation
- Honest scoping: if Flow or code is the better tool, I'll tell you
- Knowledge transfer built into every engagement, not sold as an add-on
Three ways I can help, all of them OmniStudio.
OmniStudio Implementation
OmniScripts, FlexCards, DataRaptors, and Integration Procedures — architected and built to enterprise standards from the first commit.
Explore → SVC / 02Document Generation
Quote packs, contracts, statements — OmniStudio DocGen pipelines with template governance that survives version twelve.
Explore → SVC / 03Advisory & Fit Assessment
An evidence-based answer to "should we use OmniStudio here?" — before the licenses, not after.
Explore →Field notes from the OmniStudio trenches.
From Vlocity to OmniStudio: what actually changed
The acquisition, the renaming map, and what it all means for teams running the managed package today.
Read →A practical guide to your first DocGen project
Templates, token maps, and the governance decisions that determine whether document generation scales.
Read →OmniStudio vs. Flow: how to decide what belongs where
A working decision framework for the question every Salesforce architect eventually has to answer.
Read →Have an OmniStudio decision in front of you?
A 30-minute call is usually enough to tell you whether I'm the right fit — and if I'm not, I'll say so.