Prepare for the renewal conversation
Make a view of upcoming renewals with the fields your team uses to prepare. Define the time window, the account owner and the signals that deserve a closer look.
Flex for account managers
Know the account.
Lose the busywork.
Build a customer tool around the questions your team needs to answer. Bring renewals, activity and account context into a focused internal app, with access to data configured by engineering.
“Create a renewal view with account owner, renewal date and recent product activity. Show where each field comes from and use our approved reporting source.”
Working preview
A better start to an account review.
- Account view
- Owner and renewal date
- Useful context
- Recent product activity
- Source
- Approved reporting data
A new app, shaped around your team’s work.
Start somewhere useful
Small enough to start.
Useful enough to matter.
Build a customer briefing
Bring the approved facts for an account into a page you can review before a call. Ask for clear source labels and dates so the team can judge how current the information is.
Spot the follow-up
Create a focused list of accounts that meet your team’s criteria. Explain the criteria rather than relying on an unexplained score, and check the results against known accounts.
A practical way forward
From the first request
to a shared decision.
Start with one conversation
Describe what an account manager needs to know before a call or renewal. List the fields and explain where the team currently finds them.
Agree the data boundary
Engineering connects an approved source and chooses the credentials. Decide which customer information belongs in the tool and who should use it.
Review the working tool
Check a preview against familiar accounts. Refine the layout, labels and filters, then review data accuracy and access before rolling it out to the team.
How your team stays in control
Useful customer context, with clear boundaries.
Treat access to customer data as a design decision. Connect only what the workflow needs, use suitable database permissions and review how the finished app exposes information.
Explore Flex security- Use sources configured by your engineering team.
- Choose read-only credentials for account lookup and reporting.
- Validate the customer data shown in the finished app.
Before you start
Good questions.
Clear answers.
How do we connect customer data?
Use customer data available through a supported configured database source. For information held only in a CRM, work with engineering on the integration your workflow needs.
Can we bring together account and product data?
Design the tool around the approved sources your team makes available. Agree the join keys, freshness and access rules with engineering, then verify the output against known examples.
Can the tool update customer records?
That depends on its implementation and the permissions of the connected credentials. Begin with a read-only view where possible and separately review any workflow that writes data.
Start with your team’s next idea