App catalogue Sales and service

Key account review

Runs the quarterly review of each key account on live orders, quotes, credit and returns, with the account team, the sales director and the executive sponsor on their own levels.

HIERARCHY · KEY ACCOUNT REVIEWAccount teamL1: account managerscreen · usersL2: sales directorscreen · usersServiceL1: service leadscreen · usersFinanceL1: credit controllerscreen · usersExecutiveL1: executive sponsorscreen · usersa person created at a level is assigned their parent-level and child-level users at the same timeTrigger and flow criteriaThe review cycle starts on the first working day of each quarter for every account on the key-account list, or…
The hierarchy: functions, levels, and the criterion that starts the flow. Each level carries a screen and its people.
5 days
of configuration to a production-grade version
estimate
5
screens, desktop and mobile
catalogue
5
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
2
clocks with escalation
catalogue
What it does

Today, and with the app

Today the account manager builds a deck the week before the review from CRM reports, ERP extracts and a note from credit control, and the figures are 3 weeks old when the executive sponsor sees them. The commitments made in the meeting live in the deck.

The app starts a review for every account on the key-account list at the start of each quarter, with the live figures already in place: orders and revenue for the last 4 quarters against the plan, open quotes and their value, credit exposure and days to pay, and returns by reason. The account manager writes the assessment and the plan for the next quarter, the service lead adds the open issues, credit control adds the payment picture, and the sales director signs the plan. The executive sponsor sees a 1-page view before the customer meeting and records the commitments made there. The plan and the commitments are written to the account in the CRM, and the next review starts from them.

Who takes part

Collaborative app: levels first, then screens per level, then people, then the flow and trigger criteria

FunctionLevelDoes
Account teamLevel 1: account managerwrites the assessment, the plan and the actions
Account teamLevel 2: sales directorreviews and signs the plan
ServiceLevel 1: service leadadds open issues, returns and their status
FinanceLevel 1: credit controlleradds exposure, overdue and days to pay
ExecutiveLevel 1: executive sponsorreads the 1-page view, meets the customer, records commitments
Screens

5 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Account overviewchart of revenue and orders by quarter against plan, open quotes, exposure and days to pay, returns by reason; last review's actions with status
S02 Assessment and planassessment fields by theme, next-quarter targets, actions with owner and date; submit for sign-off
S03 Service and finance inputopen issues and returns with status; exposure, overdue and payment behaviour; confirm
S04 Sponsor page1-page view: the 5 figures that matter, the plan, the asks for the meeting; commitment field
S05 Review trackeraccounts by review stage, sign-offs, commitments open and closed, revenue trend
Data handlers

5 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Customer masterthe account, its sales organisation and termsSalesforce · S/4HANA · Snowflake · Databricks
Sales order lineorders and revenue by quarterSalesforce · S/4HANA · Snowflake · Databricks
Quotationopen quotes and their valueSalesforce · S/4HANA · Snowflake · Databricks
Credit profileexposure, overdue and risk classSalesforce · S/4HANA · Snowflake · Databricks
Return orderreturns by reason and quantitySalesforce · S/4HANA · Snowflake · Databricks

Written back

ObjectWhat changes
Customer masteraccount plan summary, next-quarter targets and the commitments recorded at the meeting written to the account record in the CRM
The flow

From the trigger to the last write

THE FLOW · KEY ACCOUNT REVIEW1Review openedfigures loaded per account;account manager, servicelead and credit controllernotified2Inputs completeassessment, service issuesand payment picture allpresent by working day 103Plan signedsales director signs, orreturns the plan with anote4Customer meetingexecutive sponsor recordsthe commitments made; eachgets an owner and a date5Written to the CRMplan and commitmentswritten to the account;tracker updated; actionstracked to the next review
Each step and the criterion that moves it.

Start: The review cycle starts on the first working day of each quarter for every account on the key-account list, or when the sales director opens one early.

StepMoves when
Review openedfigures loaded per account; account manager, service lead and credit controller notified
Inputs completeassessment, service issues and payment picture all present by working day 10
Plan signedsales director signs, or returns the plan with a note
Customer meetingexecutive sponsor records the commitments made; each gets an owner and a date
Written to the CRMplan and commitments written to the account; tracker updated; actions tracked to the next review
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
cht_revenueon load → read orders and revenue for 4 quarters and the plan → draw the trend, colour the quarters below plan
btn_submit_planon click → check that every theme has an assessment and every action an owner → open S04 for the sponsor, notify the sales director
btn_sign_planon click → lock the plan → write the plan summary to the account in the CRM, store the record ID
btn_record_commitmenton click → save the commitment with owner and date → write it to the account, add it to S05

Clocks

StepTime limit and escalation
Inputsworking day 10 of the quarter, then the sales director is told which accounts wait for which input
Commitmentits due date, then the owner is reminded and the sponsor is copied

Measures

reviews completed by working day 15revenue against plan per accountcommitments closed on timeopen issues older than 30 days per account
A day with the app

Illustrative

Names, places and figures are illustrative; the pattern is the catalogue's.

On 2 April at 08:00 the app opened 38 reviews for the region, and Hannah, the account manager for a telecom operator in Stockholm, found the overview already filled: revenue 12 percent below plan, 2 open quotes worth 900,000, and 4 returns with the same reason code. She wrote the plan by 11:30, the service lead added the returns issue that afternoon, and the sales director signed on day 4. The executive sponsor met the customer on 15 April with the 1-page view, recorded 2 commitments at 15:20, and both appeared on the account in the CRM before the taxi left.

illustrative scenario · Key account review
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

Key accountA customer on the list the sales director keeps, reviewed every quarter with an executive sponsor.
Executive sponsorThe senior person who owns the relationship with the customer's leadership.
CommitmentA promise made to the customer at the meeting, with an owner and a date.
Questions

How long does it take to have this running?

About 30 minutes to a first running screen on your live rows, and 5 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.

Which system does it run on?

Any of Salesforce, SAP S/4HANA, Snowflake, Databricks, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.

Who takes part from outside the company?

Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.