How to Write a Business Case in Salesforce

Salesforce has no business case object and no template for one.

So the business case for a deal usually lives in a slide deck, a rep's notes, or an email thread with the champion. None of that shows up in a report, and none of it stays behind when the rep leaves. It is also why a deal with no real reason to buy can sit in the pipeline for months before anyone spots it as a stuck deal.

To write a business case in Salesforce, you give it a home on the Opportunity: a few custom fields, a prompt on the Path to fill them in, a rule that stops a deal moving forward without them, and an email template that turns them into something the buyer can forward.

Here is how to set up each piece.

Decide what the business case holds

Keep it to five fields. Every extra field is one more thing reps skip.

• Business Problem (Long Text Area). The problem in the buyer's words, not yours.
• Cost of Inaction (Currency). What the problem costs the buyer per year if nothing changes.
• Expected Outcome (Long Text Area). What the buyer says will be measurably different after they buy.
• Economic Buyer (Lookup to Contact). The person who signs.
• Decision Date (Date). The date that forces a decision, such as a contract ending, a budget cycle or a go-live.

If you already run MEDDICC or a similar framework in Salesforce, check your existing fields first. Most of these probably exist under different names, and you can point every step below at those instead.

Create the fields on the Opportunity

1. Go to Setup, then Object Manager, then Opportunity.
2. Open Fields and Relationships and click New.
3. Choose the data type and enter the label. For Economic Buyer, choose Lookup Relationship and relate it to Contact.
4. For the two Long Text Area fields, set visible lines to four or five so the section stays compact.
5. On field-level security, make the fields visible and editable for your sales profiles.
6. On the last screen, untick the page layouts. You will place the fields in a section of their own in the next step.
7. Repeat for all five fields.

One limitation to know now: Long Text Area fields can't be used as report filters. That affects the report later in this guide.

Give it its own section on the record page

Go to Object Manager, Opportunity, Page Layouts, and open the layout your sales team uses.

Drag a new Section onto the layout, name it Business Case, and drag the five fields into it. Place it high on the page, near Stage and Close Date, rather than at the bottom next to the Description field.

If your org uses Dynamic Forms, do the same in Lightning App Builder with a Field Section component on the Opportunity record page.

Prompt reps on the Path

The Path is what reps look at when they move a deal, so that is where the prompt goes.

1. Go to Setup, then Path Settings, and click Enable if Path isn't on already.
2. Click New Path. Choose Opportunity as the object, then your record type and the Stage picklist.
3. For each stage, pick key fields. Put Business Problem and Economic Buyer on your discovery stage, and Cost of Inaction, Expected Outcome and Decision Date on the stage after it.
4. Add a line of Guidance for Success on those stages describing a good answer, for example: "Write the problem the way the buyer described it on the call."
5. Save and activate.

Key fields also appear on Kanban views for the same object, record type and picklist, so reps working from the board see the gaps without opening the record.

Require it before a deal moves forward

A validation rule makes the fields mandatory at the stage where they matter.

Go to Object Manager, Opportunity, Validation Rules, and click New. This formula blocks any stage change into Proposal or later while a business case field is empty. Replace the stage names with your own.

AND(
  ISCHANGED(StageName),
  CASE(StageName,
    "Proposal/Price Quote", 1,
    "Negotiation/Review", 1,
    "Closed Won", 1,
    0) = 1,
  OR(
    ISBLANK(Business_Problem__c),
    ISBLANK(Cost_of_Inaction__c),
    ISBLANK(Expected_Outcome__c),
    ISBLANK(Economic_Buyer__c),
    ISBLANK(Decision_Date__c)
  )
)

For the error message, use something like: "Complete the Business Case section before moving this deal to Proposal."

Salesforce shows validation messages at the top of the page even when you set them to appear next to a field, so write the message so it makes sense on its own.

The rule only fires on a stage change. Deals already past Proposal won't be blocked until they move again, and the report in the next section finds those.

Test it by moving a deal from the Path as well as from the edit form. When the rule fires on the Path, the rep has to fill in the fields before the stage will change, which is why they should already be key fields on the stage before your gate.

Find deals that don't have one

1. Create a new report on the Opportunities report type.
2. Filter to open opportunities in the stages your rule covers.
3. Add three filters: Cost of Inaction equals blank, Economic Buyer equals blank, and Decision Date equals blank. Set the filter logic so any one of them matches, for example 1 AND 2 AND (3 OR 4 OR 5).
4. Add Business Problem and Expected Outcome as columns.

The filters run on the three fields that can be filtered. If a rep filled those in but left the text fields empty, you'll see it in the columns.

Add the report to your sales dashboard, or subscribe managers to it so it lands before the weekly pipeline review.

Send it to the buyer

A business case is most useful when your champion forwards it inside their company. A Lightning email template turns the fields into a message they can forward without rewriting it.

1. Open the App Launcher, go to Email Templates, and click New Email Template.
2. Set Related Entity Type to Opportunity.
3. Write the body and insert fields with the merge field picker. Lightning templates use three curly braces, for example {{{Opportunity.Business_Problem__c}}}.
4. Save the template, then send it from the opportunity's Activity tab using Insert Template.

A simple structure works: the problem as they described it, what it costs them per year, what they expect to change, and the date they need it by. Leave Economic Buyer out, since that field is for your team.

Preview it on a real opportunity before sending. Blank fields render as nothing, so a half-filled business case produces a half-written email.