Scope note: the two passages below are fictional pricing and engagement discussions, covering communication, the organisation of information and the division of work only, not legal, financial or contractual judgement. Real pricing decisions follow your own operating data and professional advice.
When two people work together, friction tends to appear when one is already changing the tiers and the other is still working out how to raise it with regulars. This is rarely a matter of who is right, but of which kind of information each handles first. The division can be written down by duty and authority: who owns which part, who has the final signature. Writing it is more reliable than relying on rapport.
The three tiers: should the middle tier offer less value?
(Fictional scene.) One set of services splits into basic at 99, standard at 199, premium at 399. Early in the discussion someone proposes making 199 visibly poor value, adding only two trivial features over 99, so customers either stay at 99 or jump to 399. The other objects: regulars renewing at a single price are using something close to 199, and turning that into the bad-value tier tells them they have been overpaying for years.
Set the goal first, then the tiers. This time the goal is for most new customers to land on 199: 99 moves volume at thin margin, 399 is a high threshold for a new customer, and the team wants to test whether customers see 199 as good value. With that goal, 199 has to stand up: the added service needs a clear purpose and enough use to justify the price difference of 100; 399 exists as a reference, with clearly wider entitlements and a jump in price, so that 199 looks like the reasonable choice rather than the tier being pushed.
"Will customers move from 199 to 399, and why" is a hypothesis to be tested, known only from the choice distribution and renewal feedback after launch; it cannot be written into the design as a goal, and cannot be engineered by making the middle tier bad.
Both risks are real: a structure that is too clever will feel like a trick once customers see it; attending only to regulars' feelings may leave all three tiers untouched and the increase unrealised. The middle path is to make 199 solid while giving regulars a transition period with written conditions, rather than using the middle tier as both a decoy and the main product.
The check is an exploratory interview, not a vote: ask five or six regulars to look at two versions of the list, with and without 199, and say which they would choose, why, which entitlement they did not understand, and what is missing now. What is recorded is reasons and sticking points; there is no threshold of "if this many people mention it, add it", and a sample this small cannot justify cutting or adding a tier. The interviews inform the price list; they do not judge anyone's type.
A classmate's shop asks for pricing help: charge or not
(Fictional scene.) A university classmate has opened a small shop and asks you to look at the price list and the menu structure, saying several times "no rush, whenever you have time".
Either may simply produce a version, and either may ask about scope first. This is closer to a difference in task scope and relationship terms: whether there is time, whether this will recur, and how you and this classmate usually deal with each other all change the approach.
Put the same set of questions to both: how far does this help go, what is delivered, when is it needed, is there a fee, and does a later price change count as a new engagement. One more often checks whether a rule can be applied consistently — free this time, so is it free for the next person who asks; saying "one verbal opinion, implementation billed separately" saves both sides trouble. The other more often starts from the existing relationship — it is not easy for a classmate to ask, so hold the atmosphere first and find a moment to state the boundary. Both reasons can hold at once, and often appear in the same person.
A workable approach is layered: free this time, one verbal opinion, no documents; for implementation, a separate engagement with scope, deliverables, timing and fee written down.
Counterexamples worth remembering: some ENTPs will insist on a simple letter of engagement, and some ESFJs will take on three months of work with "we are classmates". Type does not decide who has better judgement about boundaries; whether the scope can be stated clearly depends on experience, the relationship and the situation. If the two take it on together, divide by who knows how, who has time and who is authorised to speak outward — not by four letters.