Pricing power is not what your price list says. It is what happens in the conversation when a prospect asks for a discount, a waived rush fee, a custom bundle, or a stretched payment term. Most founders never measure that gap, so they mistake a policy document for a system. The Founder's Pricing Exception Log measures the gap in one month, using nothing but a document and the honesty to write down every deal where the number moved.
Key takeaways
- For one month, log every deal where price, terms, or scope was adjusted, and record who asked, what justification they gave, and what rule you applied.
- Sort the entries into three buckets: patterned exceptions that can become a written rule with a threshold, judgment calls that require strategic context, and improvised yeses that happened simply because someone asked.
- The ratio between those buckets is a direct read on how much of your pricing is architecture and how much is improvisation with a price list attached.
- Each bucket has a different fix: a rule with an escalation path, a captured rationale your team can consult, or a written standard that replaces the in-the-moment yes.
Why your price list is not your pricing
A price list is a statement of intent. Your actual pricing is the sum of every exception you granted last month. If the only person who can grant an exception is you, price is not a policy — it is a dependency. Every discount conversation routes back through your calendar, your memory, and your mood on that particular afternoon. The log makes that dependency visible before you attempt to fix it, which is why it comes first.
The log: what to record for every exception
For one month, every time a deal closes with anything other than standard price, standard terms, and standard scope, add a row. Four fields, no more:
- The deal. Who it was, what was sold, what the standard number would have been.
- Who asked. The buyer's role and how the request arrived — inbound, in the proposal call, at the signature stage.
- The justification. Their stated reason, in their words.
- The rule you applied. The threshold, the policy, or the principle you used. If you applied none, write "none."
That last word is the most valuable data in the log. "None" is not a moral failure. It is a measurement.
The three buckets
Sort every row at the end of the month, in one sitting, with the deals in front of you. Three buckets only.
Bucket one: patterned exceptions
You will recognize these because the justification repeats. Same request, same framing, same stage of the deal, different buyer. A pattern is not a risk — it is an unwritten rule asking to be written. The output of this bucket is a rule with a threshold and an owner, expressed in units you already sell in: days, volume, contract length, payment window. Name who may approve inside the threshold and who it escalates to outside it. If the rule cannot survive that test, it is not a rule yet.
Bucket two: judgment calls
Some exceptions are not patterns. They involve a strategic relationship, a new market signal, a logo that opens a category, or terms you accepted to learn something you could not have bought otherwise. These are not failures; they are how a founder gathers intelligence. But they are worthless as intelligence if the reasoning lives only in your head. The output of this bucket is a context source: what signal you saw, what you traded away, what you expected in return, and what would have to be true for the same call to be correct again.
Bucket three: improvisations
No pattern. No strategy. Someone asked, and you said yes in the moment, and later you could not fully reconstruct why. This is the tax you pay for keeping pricing in your own nervous system. The output of this bucket is a written standard that replaces the in-the-moment yes — not a punishment, just a default that exists so the next conversation does not require you.
What the ratio tells you
| Bucket | What it signals | What it becomes |
|---|---|---|
| Patterned exceptions | An unwritten rule is already operating | A written decision right with a threshold and an escalation path |
| Judgment calls | You are learning, but the learning is trapped in you | A self-serve context source that captures the reasoning |
| Improvisations | Pricing is being decided by proximity to the founder | A written standard that removes the guesswork |
If bucket three is the largest, your pricing power is improvisation wearing a price list. If bucket two dominates, you are running a bespoke advisory disguised as a product business, and your team cannot quote without you. If bucket one dominates, you are close — the rules exist, they are just still stored in your head instead of your operating system.
From log to architecture
This is the work EXIUSS Intelligence is built for. The 14-day implementation architecture trial takes the log you just built and moves each row into the Workspace as a decision your team can execute without asking you.
Patterned exceptions become encoded decision rights: a written discount limit, a named approver, an escalation path, and a threshold that lives where the deal lives. Judgment calls become context sources — the reasoning captured once, in the open, so the next person facing a similar signal can see how you thought about it rather than interrupt you to ask. Improvisations become written standards that close the gap where the yes used to happen by default.
The trial includes the guided discovery journey, 95+ Founder Frameworks and the 10 Universal Laws translated into working architecture, and a personalized EXIUSS Protocol that surfaces the organizational patterns and blind spots driving your exceptions in the first place. The Workspace ships with the trial — funnels, CRM, and pipeline — so you load real deals and stand up your first initiatives rather than sketch them. Everything you build carries over when you upgrade. Real-time voice conversation with EXIUSS unlocks on the paid tier; the architecture itself is available to you from day one.
Your pricing stops being a series of one-off conversations with you when the exceptions are logged, sorted, and encoded. One month of data is enough to start.
Quick checklist
- Open a single document today and title it "Pricing Exception Log."
- Record the four fields for every non-standard deal this month: deal, who asked, justification, rule applied.
- Write "none" honestly when no rule was applied — that entry is the measurement.
- Sort every row into patterned, judgment, or improvisation at month end, in one sitting.
- Convert each patterned row into a threshold, an owner, and an escalation path.
- Move the whole log into your Workspace during the 14-day EXIUSS trial at https://trial.codebreakers.pro so it lives in your operating system, not your head.