Accounts and Team

A SaaS opportunity needs a clear customer account before anyone discusses its value. The account holds the customer name, account code, contact name, address and eligibility note. Its organization link keeps that customer in the right operating scope. A Relationship Owner selects the account when opening an opportunity, so later activities and renewal reviews lead back to the same commercial relationship.

The App Administrator maintains this foundation. The account’s active setting tells the team which customers belong in the current working list. Organization records carry a time zone and reporting currency. Team membership connects the person doing the work to that organization and to their user identity. Commercial ownership sits on the opportunity, where the Relationship Owner remains visible throughout the sale.

• Customer identity. Keep the account code stable and record the contact the team actually works with. Use the eligibility note to explain a material constraint before the owner prepares a proposal. An address correction belongs on the customer account so later work uses the same reference.
• Organization scope. Match the account and opportunity to the organization responsible for the relationship. Review the organization’s active setting, time zone and currency during setup. A familiar customer name alone is insufficient when separate operating organizations deal with similar names.
• Team membership. Link each team member to the correct user and organization. The role name describes their operating responsibility; approval authority still follows the assigned permissions and independent review rules. Review membership when someone leaves or responsibility changes.

Agree who maintains account codes and how the team checks for a duplicate before creating a customer. Decide what the eligibility note must explain for your sales process. Keep it useful to the Relationship Owner: for example, which operating entity is in scope or which commercial restriction must be resolved before proceeding.

Confirm the time zone used to interpret a renewal date and an expected close date. Agree the currency basis for recurring monthly values before comparing them across customers. Assign the Sales Manager who can independently review an owner’s work. Administrative access alone must not make someone the approver of a commercial outcome.

Use an illustrative customer, Cedar Analytics, with an account code and a named contact. The App Administrator checks its organization and eligibility note, then confirms the owner’s membership. The Relationship Owner opens an opportunity against that account and records the expected close date. The Sales Manager should be able to trace the customer through the opportunity without asking which similarly named account the owner intended.

Repeat the exercise with a team member who has moved to a different organization. Check that the operating scope is corrected before that person participates in the next review. Retain the earlier opportunity and decision evidence so an Auditor can still explain the original relationship. This rehearsal catches identity mistakes before they become ambiguous approval requests.

• Active Accounts — Current customer accounts with the contact and eligibility context needed to open an opportunity.
• Active Team Members — Organization membership and user links for checking who can take part in the work.

Continue with account setup and qualification, then use the implementation sequence to rehearse membership and access.