Account scope

A technology opportunity belongs to a customer or prospect account inside an operating organization. App Administrator maintains the account code, contact name, address and eligibility note. Relationship Owner uses that account context when preparing the opportunity and deciding what evidence to gather next.

The account’s active flag helps the team distinguish current operating scope from accounts that need attention before new work proceeds. Team membership provides similar context for the person responsible for the opportunity. The member’s user reference connects business ownership with the identity acting in the app, while the organization identifies the scope in which that person works.

• Account eligibility. App Administrator records the reason an account is eligible for the team’s sales process. The contact and address help Relationship Owner identify the right customer context before logging a discussion or preparing a proposal.
• Opportunity ownership. Each opportunity names its owner and account. Sales Manager can follow that responsibility when reviewing the submitted revision. Keep the existing activity evidence when responsibility changes so the reviewer can follow the customer discussion.
• Operating organization. The organization holds its time zone and currency settings. Opportunity expected values are recorded in USD, so the team agrees how those estimates relate to its commercial reporting during setup.

Choose account codes that the sales team can recognize and decide how to distinguish similarly named customer entities. Agree who maintains eligibility notes and what makes an account active for the pilot. If the same customer works with different operating organizations, make the intended account relationship explicit before assigning an opportunity.

Agree how App Administrator will review team membership when people join, change responsibility or leave. Admin handles technical user access, while Sales Manager retains the separate independent business decision. An administrative change should not grant someone the ability to approve an opportunity they prepared. Check the operating time zone used for due dates and expected closing discussions.

Use a pilot opportunity for a software evaluation at a customer with similarly named regional entities. App Administrator confirms the correct account code, contact and organization. Relationship Owner opens the opportunity against that account and records the expected closing date.

Ask Sales Manager to identify the account and responsible person using the opportunity alone. Then try the same action with a team member from another organization and with an inactive member. Resolve the scope before the opportunity advances. Finally, change the customer contact information and confirm that the account remains identifiable without rewriting the opportunity’s earlier activity history. The team should be able to explain who can prepare the next action and who can independently review it.

• Active Accounts — Eligible operating accounts with their contact and organization context.
• Active Team Members — Active membership and user references for assigning responsibility.
• My Open Opportunities — The Relationship Owner’s current sales work and expected closing dates.

Continue with qualification and activity, then proposal and negotiation.