An honest answer to “should we use OmniStudio here?”
Independent fit assessment and advisory — before you buy licenses, before you commit a roadmap, or after a build that isn't delivering what the slideware promised.
What the advisory covers
- Fit assessment: your use cases mapped against OmniStudio, Flow, and custom development — with evidence, not vibes
- Licensing and commercial review: what OmniStudio actually costs in your context, including the org impact
- Architecture review of existing OmniStudio: component design, performance, and upgrade readiness
- Vendor and partner proposal review — a second opinion from someone with no stake in the license sale
- Roadmap and sequencing: what to build first, what to defer, what to never build
- Enablement planning: the skills and standards your internal team needs before the first OmniScript
How an assessment runs
Frame
Define the decision on the table — new purchase, expansion, or rescue — and the criteria that will settle it.
Investigate
Requirements review, stakeholder interviews, and hands-on inspection of your org and any existing OmniStudio assets.
Recommend
A written assessment with a clear position: fit by use case, risks, costs, and a sequenced plan.
Decide together
A working session with your architects and leadership to pressure-test the recommendation until you own it.
Signals you need this
- A vendor is proposing OmniStudio and you have nobody independent to sanity-check it
- You're choosing between OmniStudio and Flow for a major program and the internet's answers all contradict each other
- You inherited an OmniStudio org and don't know if it's salvageable
- Leadership wants a defensible platform decision, not a preference
Asked on most first calls
What does a fit assessment actually produce?
A written, evidence-based recommendation: which of your use cases suit OmniStudio, which belong in Flow or code, licensing and org-impact implications, and a sequenced roadmap. It's designed to be defensible in front of your architecture board.
Will you just recommend OmniStudio because it's your specialty?
No — and my model depends on not doing that. A meaningful share of assessments end with 'use Flow for this' or 'your incumbent tool is fine.' An honest no is what makes the yes worth anything.
How long does an assessment take?
Typically two to four weeks depending on scope: requirements review, stakeholder interviews, a look at your org and any existing OmniStudio assets, then the written recommendation and a working session to walk it through.
Can this include a review of OmniStudio we've already built?
Yes. Architecture reviews of existing footprints are half my advisory work — assessing component design, performance, upgrade posture, and maintainability, with a prioritized remediation plan.
Need an independent read before you commit?
Assessments are fixed-scope and fixed-fee — you'll know the cost of the answer before you ask the question.