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.
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.
| Function | Level | Does |
|---|---|---|
| Account team | Level 1: account manager | writes the assessment, the plan and the actions |
| Account team | Level 2: sales director | reviews and signs the plan |
| Service | Level 1: service lead | adds open issues, returns and their status |
| Finance | Level 1: credit controller | adds exposure, overdue and days to pay |
| Executive | Level 1: executive sponsor | reads the 1-page view, meets the customer, records commitments |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Account overview | chart 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 plan | assessment fields by theme, next-quarter targets, actions with owner and date; submit for sign-off |
| S03 Service and finance input | open issues and returns with status; exposure, overdue and payment behaviour; confirm |
| S04 Sponsor page | 1-page view: the 5 figures that matter, the plan, the asks for the meeting; commitment field |
| S05 Review tracker | accounts by review stage, sign-offs, commitments open and closed, revenue trend |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Customer master | the account, its sales organisation and terms | Salesforce · S/4HANA · Snowflake · Databricks |
| Sales order line | orders and revenue by quarter | Salesforce · S/4HANA · Snowflake · Databricks |
| Quotation | open quotes and their value | Salesforce · S/4HANA · Snowflake · Databricks |
| Credit profile | exposure, overdue and risk class | Salesforce · S/4HANA · Snowflake · Databricks |
| Return order | returns by reason and quantity | Salesforce · S/4HANA · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Customer master | account plan summary, next-quarter targets and the commitments recorded at the meeting written to the account record in the CRM |
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.
| Step | Moves when |
|---|---|
| Review opened | figures loaded per account; account manager, service lead and credit controller notified |
| Inputs complete | assessment, service issues and payment picture all present by working day 10 |
| Plan signed | sales director signs, or returns the plan with a note |
| Customer meeting | executive sponsor records the commitments made; each gets an owner and a date |
| Written to the CRM | plan and commitments written to the account; tracker updated; actions tracked to the next review |
| Component | Trigger → action → outcome |
|---|---|
| cht_revenue | on load → read orders and revenue for 4 quarters and the plan → draw the trend, colour the quarters below plan |
| btn_submit_plan | on click → check that every theme has an assessment and every action an owner → open S04 for the sponsor, notify the sales director |
| btn_sign_plan | on click → lock the plan → write the plan summary to the account in the CRM, store the record ID |
| btn_record_commitment | on click → save the commitment with owner and date → write it to the account, add it to S05 |
| Step | Time limit and escalation |
|---|---|
| Inputs | working day 10 of the quarter, then the sales director is told which accounts wait for which input |
| Commitment | its due date, then the owner is reminded and the sponsor is copied |
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.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Customer master read from Account; CRM.
Open the Salesforce page →Customer master read from KNA1 · KNB1 · KNVV; also on SAP ECC.
Open the S/4HANA page →Customer master read from CONFORMED.CUSTOMER; lakehouse.
Open the Snowflake page →Customer master read from silver.customer; lakehouse.
Open the Databricks page →Other systems connect through the same handlers; see how SmartApps connect.
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.
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.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
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.