πŸš€ Visma Apps

← All roles

πŸ“ˆ Sales Manager

Runs the sales team β€” performance and pipeline.

What it does β€” 6 skills

βœ“ Team performance review β€” Check each team member’s performance daily and flag who needs support.βœ“ Analyze / read / write management reports β€” Read, analyse and produce monthly management reports. Learned the hard way, and the most important lesson first: a management report is a GOOGLE DRIVE DOCUMENT / PRESENTATION β€” the one the Managing Director writes their commentary in β€” NOT just data-lake numbers. So the real skill is (1) FIND the right report in Google Drive: search by company name + "management report", and verify the document actually belongs to that company and month before reading it β€” don't grab the most-recently-edited file globally (a classic wrong-doc mistake). (2) READ THE ACTUAL DOCUMENT (open the doc/slides, digest the text and any charts) to capture the MD's narrative β€” what happened, why, what's at risk, and what actions are planned β€” because that written analysis is the whole point and appears nowhere in the raw numbers. (3) Use the data lake only to CROSS-CHECK the figures, minding its traps: ARR-type metrics live under source "product" (not "financial"), a company-KPI-period is the SUM of component rows (never dedupe β€” that reads ARR as ~554K instead of ~56M), and the latest month is PROVISIONAL so trust actuals only through the last closed month. Then report BOTH the MD's narrative and the verified numbers β€” the story and its evidence together.βœ“ Lead & pipeline analysis β€” Track lead statistics and how much the pipeline is worth.βœ“ Schedule oversight β€” Watch team schedules and flag changes needed.βœ“ Forecasting β€” Forecast the quarter/year and flag risk early.βœ“ Data lake β€” Query the financial data warehouse (the "data lake") for ARR, margins, KPIs and trends. Hard-won learnings baked in: the true grain is (unit, source, KPI, year, period, Gr1, R12, reporting-year, date-key) β€” always SUM the components, never pick one row. NUMERIC values come back as big.js objects, not plain numbers, so a naive value-handler silently yields null β€” coerce with String(). Never diagnose a shocking swing as "duplicate double-counting": double-counting inflates, while a collapse toward zero is almost always an un-summed component or the provisional latest month. Verify against pfdw before trusting anything surprising. How to run it (the `lake` CLI, plus the analysis tools built on top): β€’ lake explore --company Acubiz β€” list the KPIs, sources and periods available for a company β€’ lake series ARR --company Acubiz --source product --chart β€” the ARR time-series (correctly SUMmed), ready to plot β€’ lake growth ARR --company Acubiz β€” period-over-period and YoY growth β€’ lake forecast ARR --company Acubiz β€” projection that prefers the forecast value for the provisional month β€’ lake validate --company Acubiz β€” flag genuine double-loads and mark the provisional latest month β€’ benchmark ARR β€” compare one KPI across the whole portfolio β€’ portfolio β€” the fleet-wide KPI snapshot; waterfall / scenario / explain for bridges, what-ifs and drill-downs β€’ lake manual β€” the deep guide (grain, provisional months, big.js NUMERIC) baked into the tool itself