A ticket says “add a field.” A requirement says why the field exists, who reads it, what decision it feeds, and what happens if it is wrong. When Salesforce requirements arrive as tickets, that second layer never gets written — and the backlog quietly becomes your CRM strategy.
How ticket-driven delivery drifts
Each ticket is small and reasonable. Approved one at a time, they accumulate into an org nobody designed: five fields capturing versions of the same data, automations that fight each other, page layouts shaped by whoever asked most recently.
No single ticket caused it. The absence of business analysis did.
What senior BA practice actually does
A senior business analyst turns requests into decisions. That means requirements workshops that surface the process behind the ask, stakeholder alignment so competing requests are resolved before they hit the backlog, and written requirements that state intent — not just configuration.
It also means saying no with a reason: some requests cost more in complexity than they return in value, and someone senior has to be able to show that math.
You may not need a full-time hire
Most mid-market Salesforce teams do not have enough requirements flow to justify a full-time senior BA — but they have far too much to have none. Fractional BA leadership, one to three days a week, covers the workshops, the alignment, and the backlog discipline without new headcount.
One manufacturing client took exactly that route: weekly senior BA cadence, no hire, and a structured review that identified roughly $100K in annual license and process savings along the way.
The test
Open your backlog and pick five tickets at random. If you cannot tell from the ticket why the business needs it, requirements are not being written — they are being skipped. That is the gap a senior BA closes.