See how it works

One data loop. From an ERP file to a board decision — and back to the sales rep.

This is what a week with SoldCalc looks like: who does what, what happens automatically and where the value is created along the way. No magic — step by step.

1 · Admin loads the data→ 2 · The system computes itself→ 3 · The rep plans→ 4 · Work in the field→ 5 · Manager and director see the whole picture→ 6 · The loop closes
1ADMINISTRATOR

Data enters the system

Getting started requires no integration and no IT project. The administrator loads data from an Excel file exported from the sales system — SoldCalc recognises the columns itself (customers, products, sales, price lists) and cleans up date or name formats. On a full licence you can connect the database directly instead of files.

  • Excel import with automatic column mapping — no data retyping
  • On a full licence: connection to PostgreSQL / Microsoft Dataverse / SAP — strictly read-only
  • Automatic sync schedule: the data refreshes itself
Excel from ERPor CRM (read-only)
import →
SoldCalc API + databasea server inside the buyer's company
⇄ sync
SoldCalc appthe team's computers
Every user's app synchronises 18 data types incrementally and keeps a local copy — so it also works without internet, e.g. in the field.
2SYSTEM — AUTOMATIC

Sales and margin analysis computes itself

From the first sync SoldCalc works in the background: it aggregates sales, classifies customers (ABC and behaviour patterns), detects margin leaks and calculates forecasts. Nobody has to "run the analysis" — the results are simply waiting for people.

  • ABC classification of customers and products plus behaviour profiles (growing, declining, price-shopping…)
  • 19 Margin Recovery rules scan sales for margin leaks
  • Quarterly forecasts: history + seasonality + the reps' knowledge
KPI dashboard fed automatically
The engines' output: a KPI dashboard ready without manual work — click to enlarge
Customer briefing before the visit — history, forecast and next actions
Customer briefing — what is known about the customer, the forecast and the next actions
ABC classification of customers
ABC classification — which customers and products carry the result
3SALES REP

Sales visit planning — on a map, not in a notebook

The rep opens the map: customers colour-coded by importance (ABC classes), plus a visit calendar and route planning. Priorities come from the feed — a list of actions derived from data, not gut feeling.

  • Customer map with pins by ABC class and turnover, filtered by region and industry
  • Visit calendar with route optimisation
  • "Actions for today": whom to visit and why — with the opportunity amount
Visit map with ABC pins
Visit map — the day's plan in the field — click to enlarge
Actions for today — the rep's data-driven priorities
"Actions for today" — the day's priorities driven by data, not gut feeling
4SALES REP — IN THE FIELD

At the customer: offer, competitive interview, notes — all in one, offline too

On site the rep has the customer card (offline!): purchase history, product proposals for this specific customer, prices and margins calculated live. They build the offer, and when a deeper discount is needed — the request goes to the manager and comes back with a decision before the coffee is finished. Along the way they note competitors' prices.

  • An offer with an automatic price cascade and a PDF e-mailed on the spot
  • Discount request → manager's decision in real time (push notifications)
  • Competitive interview: what the customer buys elsewhere and for how much
  • Everything saves locally and syncs to the API once back in coverage
  • The manager’s suggested price shows up directly in the offer — together with the note explaining it
  • An offer status on every line: price OK, too high, wants a sample, staying with the competitor — plus the competitor price and a note
Customer card and offer with product proposals
Customer card: product proposals, live prices and margins — click to enlarge
Competitive interview form in the field
Competitive interview — field knowledge becomes comparable data
Manager's real-time discount decision — push notification
The discount request at the manager's desk: full customer context and post-discount margin — a one-click decision
KO/DR suggested price — the manager records a target price, the rep sees it in the offer
KO/DR suggested price — the manager records a target price, the rep sees it in the offer
5MANAGERDIRECTOR

Profitability, competition and forecasts — the company picture for managers and directors

What the reps collected — sales, offers, interviews, visits — flows into the API and is aggregated by role. The manager gets the team's priorities and discount requests to decide. The director sees the cockpits: profitability, competition, price-change impact — with amounts, not decorative charts.

  • Manager: customer pipeline with alerts, discount approvals, rep support
  • Director: profitability cockpit with "Where you lose / Why / What to do" cards
  • Competition cockpit: how much is leaking and where — based on field interviews
  • Everyone sees exactly what their role allows: rep → manager → director
  • The change in turnover and margin broken down by cause: price, quantity, new products, dropped products, free goods — per company and per rep
  • Client profitability simulator: what happens to the margin if you change a price or the make-up of the basket
Profitability cockpit for the board
Profitability cockpit (Margin Recovery) — field findings turned into amounts — click to enlarge
Customer pipeline for the sales manager
Pipeline for the manager — which customers need action and why
19 Margin Recovery rules in the cockpit
The 19 rules at work — every leak with an amount and a plan
Price · Volume · Mix — the change in turnover by cause, with a management comment
Price · Volume · Mix — the change in turnover by cause, with a management comment
6THE LOOP CLOSES

The next morning the rep's feed already knows what happened yesterday.

The manager's decisions, new interviews, ABC class changes, detected leaks — everything comes back into "Actions for today" as concrete, prioritised tasks. And at month-end the board sees which actions really translated into sales and margin. No collecting reports, no "prepare me a summary for Monday".

data→ analysis→ action→ result→ data again
Proof of Value · 30 / 60 / 90 dni

Want to see this loop on your company's data?

The pilot programme follows exactly this path — from loading your Excel to the "how much SoldCalc found" report.

Book a Proof of Value →