Anti-patterns
Designs that feel tidy and then break.
They work while the portal is small. They fail when a second team, a second brand, or a second year arrives.
Leave this out
- One pipeline per rep. Reporting dies and stages drift.
- A property for every idea. The record becomes a form nobody finishes.
- Lifecycle as a mood. Two definitions of opportunity, and the automation fights both teams.
- A shared super admin. Everyone can see everything, so permissions are never designed.
Use this instead
- One pipeline and an owner on the deal.
- A property group, or an object, when the thing is real.
- One written definition of each lifecycle stage.
- A permission set named for the role, checked with a user who should be blocked.
Tidy on day one is not the test.The test is the portal after the second team joins.
A shared login hides the design.You never learn who was allowed to see the deal.