# Miller Heiman Blue Sheet in Pipedrive: which boxes become deal fields, and what the manager reads on Monday

https://salesbond.app/blog/miller-heiman-blue-sheet-pipedrive/
Published: 2026-10-15 · Updated: 2026-10-15

Keep the Miller Heiman Blue Sheet in Pipedrive as four or five things a manager can read without opening the sheet: the deal’s single objective, each buyer’s role on the deal, one red flag, the win-result for the main buyer, and the next step with a date. Everything else stays in a note or on paper. That is the Blue Sheet template we use in Pipedrive. The sheet has six blocks, and a small team does not need six blocks in the CRM; it needs the few that change what happens next week.

## A paper form in a CRM world

The first Blue Sheet I saw in a small company was a printout. The rep had filled it in by hand after a two-day course, it lived in a folder next to the proposal, and it was good. Four buyers named, two red flags, a real action plan. The manager had never seen it. He ran the Monday pipeline review from Pipedrive, where that same deal showed a title, a value, a stage and a single contact person. The sheet said the deal was in trouble. The CRM said nothing at all.

That gap is the whole problem with the Blue Sheet in a small team. The form is fine. Its in the wrong place. Our overview of [sales methodology for Pipedrive teams](https://salesbond.app/blog/sales-methodology-for-pipedrive-teams/) covers how to wire any method into deal fields; this post is about this one sheet.

## What the Blue Sheet actually asks

Strategic Selling is the Miller Heiman planning method, and the Blue Sheet is its worksheet. Korn Ferry now publishes it as its own opportunity management framework for complex sales ( [Korn Ferry on the Blue Sheet](https://www.kornferry.com/insights/featured-topics/sales-transformation/the-blue-sheet-history-and-evolution-of-an-industry-icon)). Its sibling, the Green Sheet, belongs to Conceptual Selling and plans a single meeting rather than the whole deal ( [Salesmotion on Miller Heiman](https://salesmotion.io/blog/miller-heimann)).

The sheet opens with one line, the single sales objective for the deal. Qwilr’s walkthrough of the process starts at the same place ( [Qwilr](https://qwilr.com/blog/miller-heiman-sales-process/)). Under it sit six blocks, which Salesmotion lists as buying influences, red flags and strengths, response modes, win-results, ideal-customer-profile alignment and an action plan ( [Salesmotion](https://salesmotion.io/blog/miller-heiman-blue-sheet)).

In plain words the sheet asks: who decides, who uses, who checks the spec, who is on your side; what could kill this deal and what is working for you; how each of those people feels about change; what each of them personally gets if you win; whether this customer looks like the ones you win; and what you will do next. Sybill names the four response modes as Growth, Trouble, Even Keel and Overconfident ( [Sybill](https://www.sybill.ai/blogs/miller-heiman)). They are useful in a conversation. They are a poor thing to put in a dropdown, and we will come back to why.

Salesmotion also makes the point that the sheet is meant to be re-read at every stage gate and used in pipeline reviews, not only in one-on-one coaching ( [Salesmotion](https://salesmotion.io/blog/miller-heiman-blue-sheet)). That is the clue. A sheet that gets re-read is a sheet someone other than the rep can see. In a small team that means the CRM, or it means nobody.

## A Blue Sheet template for Pipedrive: where each box goes

Our position: do not rebuild the sheet as thirty custom fields. Take each box, decide whether a manager will ever filter on it, and put it where it will be read. Here is the whole template, one line per box:

- Single sales objective: the deal title, written as “what, for whom, by when”.
- Buying influences: deal participants for the people, plus two text fields, Economic buyer and Coach.
- Red flags and strengths: a text field, Red flag, and a date field, Red flag since; strengths go in a note.
- Response modes: a note, if anywhere.
- Win-results: one text field, Win-result (economic buyer).
- Ideal customer profile alignment: not kept on the deal.
- Action plan: the next scheduled activity.

The title costs nothing. The sheet starts with one objective and a Pipedrive deal starts with one title, so make them the same sentence and the objective is on every deal card and in every list without a field.

Buying influences split in two because a deal has one linked person and participants add the rest ( [Pipedrive: participants](https://support.pipedrive.com/en/article/participants)). The participants list says who is on the deal. The two fields say who decides and who is yours, and a filter can test whether either is empty. Red flag follows the same logic: the manager needs the single worst thing on the deal and how long it has been there. Strengths are context for the rep, so they go where the rep reads.

Win-result is one sentence, in the deciding person’s words, about what they get personally if you win. If the rep cannot write it, that is the red flag.

Two boxes stay off the deal on purpose. A buyer’s attitude to change is a judgment that shifts between calls, and a dropdown with four values will be set once and never touched. Profile fit belongs to qualification before the deal exists, or to an organization field; on a live deal it only produces a box that reads “yes”. The action plan needs no field at all, because Pipedrive already has the object: activities are calls, meetings, tasks, deadlines or emails with a date, linked to the deal ( [Pipedrive: activities](https://support.pipedrive.com/en/article/activities)). A plan with no dated activity is a wish.

So the template is five fields: Economic buyer, Coach, Red flag, Red flag since, Win-result. Deal custom fields are created under Personal preferences > Data fields and show up in the deal detail view and as columns in the list view ( [Pipedrive: custom fields](https://support.pipedrive.com/en/article/custom-fields)). Put the five in one field group so they sit together in the detail view. On Growth and higher plans, each field can also carry a description; write the one-line instruction there ( [Pipedrive: data fields](https://support.pipedrive.com/en/article/data-fields-in-pipedrive)). If your account already carries a pile of fields nobody fills, clean that up first; we wrote about [which Pipedrive custom fields to keep](https://salesbond.app/blog/pipedrive-custom-fields-cleanup-data-fields/), and five more on top of forty dead ones will not get filled either.

A note on enforcement. On Growth and higher plans, Pipedrive can mark a field as important, which shows a reminder in the deal detail view when it is empty. On Premium and higher, a field can be required, which stops the deal from being saved until the field has a value, and you can apply it to specific pipelines or stages ( [Pipedrive: data fields](https://support.pipedrive.com/en/article/data-fields-in-pipedrive); [required fields](https://support.pipedrive.com/en/article/required-fields)). We would make Economic buyer required from the stage where you send a proposal and leave the rest important. A required Coach field produces invented coaches.

## Four buyers on one deal

Sybill lists the four buying influences as the economic buyer, who gives final approval; the user buyer, who lives with the result; the technical buyer, who screens against the spec; and the coach, the insider who guides your deal ( [Sybill](https://www.sybill.ai/blogs/miller-heiman)). MEDDIC borrows two of these as economic buyer and champion, and we covered that side as a qualification checklist in [MEDDIC for small sales teams in Pipedrive](https://salesbond.app/blog/meddic-small-sales-teams-pipedrive/); the Blue Sheet is the wider map, all four roles on one deal, for the whole life of the deal.

Here is how it looks on a deal. Open the detail view. The participants section shows four people from the customer side. The Economic buyer field holds one of those names. The Coach field holds another, or it is empty. That empty field is the most useful thing on teh page, because “no coach” in a text field is a fact a manager can see from the list view, while “we have a good relationship with the ops lead” in a call note is a feeling.

![Sketch of a deal view: five Blue Sheet fields with Coach empty, and four participants, one marked Economic buyer](https://salesbond.app/wp-content/uploads/2026/10/miller-heiman-blue-sheet-pipedrive-2.png)

Two things we have learned about those two fields. First, the name in Economic buyer must also be a participant. If the decider is not on the deal, the rep has a theory about who decides, not a contact. Second, the coach is a role the person earns, not a title you assign. We wrote more on that in [finding a champion on Pipedrive deals](https://salesbond.app/blog/sales-champion-pipedrive-deals/). The field should hold a name only after the person has done something for you that they did not have to do.

The user and technical buyers do not get fields. They are in the participants list, and in a small team’s deals that is enough. If you find yourself losing deals at the technical stage, add a third field then, not now.

## Red flags as a Monday filter

The manager does not read Blue Sheets on Monday. The manager reads saved filters: three that come straight from the sheet, and a fourth for deals with no next step. Pipedrive’s advanced filters take ALL and ANY condition groups, can be saved, shared with the team or kept private, and starred as favorites ( [Pipedrive: advanced filtering](https://support.pipedrive.com/en/article/filtering)). Text fields support an “is empty” condition ( [Pipedrive developers: filters](https://developers.pipedrive.com/tutorials/adding-filter-pipedrive-api)). That is all the machinery you need.

- Deals past the proposal stage where Economic buyer is empty. Nobody has met the person who signs. This list is short on a healthy pipeline and it should be read first.
- Deals in any stage where Coach is empty and the deal is older than your usual cycle for that stage. Early deals without a coach are normal. Old ones are a single-threaded deal with a nicer name.
- Deals where Red flag is not empty and Red flag since is older than two weeks, or whatever “too long” means for your cycle. The flag is not the problem; the flag nobody acted on is.
- Deals with no activity scheduled. Not a Blue Sheet item, but the action plan block lives here, and an empty next step makes the other three lists meaningless.

Share the filters with the team. A rep who sees the list on Friday fixes half of it before Monday which is the point: the lists exist to make the review about stuck deals, not about people.

## How the sheet dies

Hyperbound calls it the checkbox problem: the sheet gets filled in so the box is ticked, not so the deal is understood ( [Hyperbound](https://www.hyperbound.ai/blog/miller-heiman-blue-sheets-guide)). Supered puts it harder. The Blue Sheet, they write, is the original deal-inspection artifact, and a sheet filled in once and never revised is fiction ( [Supered](https://www.supered.io/blog/miller-heiman/)). Both are describing the same Tuesday. Training ends, every open deal gets a sheet, the sheets are good, and then the the deals move and the sheets do not.

A CRM does not fix that by itself. A field can be filled in once and ignored just as easily as a form. What a CRM changes is who sees the staleness. On paper, a red flag from six weeks ago looks exactly like one from this morning. In Pipedrive, Red flag since is a date, and the deal’s changelog tab shows every field change since the deal was created ( [Pipedrive: detail view](https://support.pipedrive.com/en/article/detail-view)). A manager who opens the changelog and sees that the Blue Sheet fields have not moved since the deal entered its current stage knows the sheet is dead without reading a word of it.

So the stage gate rule is small. When a deal moves stage, the rep touches the five fields. Not fills them, touches them: confirms the decider, confirms or removes the coach, replaces the red flag with the current worst thing, rewrites the win-result if it changed, and sets the next activity. Five minutes, once per stage. If a deal goes through two gates with the same red flag and the same date, that is the conversation on Monday.

We build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Deal Health checks every deal against more than 20 rules, including whether a deal is missing data and whether it has a next step, and shows which deals need attention and why. It does not know what a coach is, so the four lists above stay with you. It takes over the routine part, empty fields and deals with nothing scheduled, so the Monday review starts from the thin deals rather than the whole pipeline. [Check your CRM with SalesBond](https://salesbond.app/) if you want to see that list before you build the filters.

## The sheet is still worth filling in

None of this means the paper sheet goes away. The six-block version is still the best way we know to make a rep think about a deal for twenty minutes, and the parts we left out of Pipedrive, the response modes, the strengths, the profile fit, are exactly the parts that reward thinking over recording. Keep the sheet for the rep. Keep five fields and the Monday filters for the manager. The deal from the folder at the start of this post had a red flag written on it in pen, and the manager found out when the deal was lost. A date field would have told him in week two.