Connect the plans your business keeps in separate tools.
KEZEL Integrated Planning puts services, materials, distribution, finance and margin planning on one backbone in your own deployment. Each plan reads the records it depends on, so a change to a forecast, a project or a price reaches the plans that follow from it.
A 14-week data platform deal moves to 60% probability in the sales pipeline.
- Demand3,730 hours of role demand from week 6, weighted to 2,240
- CapacityData engineers 2.4 FTE short in weeks 6 to 12
- FinancePipeline-weighted revenue up $186k for the quarter
- DeliveryHeld as role placeholders until the deal is won
Planning areas that read the same records.
Start with the area that hurts most and add others as the cycle needs them. The figure above draws four lanes to stay readable; a deployment carries as many plans as its business runs.
Services and projects
Capacity, bookings and staffing requests built from VIA projects and logged time. Utilisation, estimate at completion, rate cards, revenue recognition by contract type, hiring plans and practice P&L.
In KEZEL, as viaPlan
Materials (MRP)
Time-phased material requirements with lot sizing, exceptions, pegging to the demand behind each order, what-if runs and a month-end roll-forward.
Reference model
Distribution and replenishment (DRP)
Daily replenishment by warehouse and item across a two-tier network, with the reason behind each order, the arrival chain and planner overrides.
Reference model
Financial planning (FP&A)
Driver-based budget and latest estimate, make versus buy, a consolidated P&L and variance with commentary, kept as named versions.
Reference model
Price, volume and mix
Why revenue and margin moved between two versions, split into quantity, mix, local price, FX and new or discontinued lines, with a price simulator.
Reference model
Demand forecasting
Time-series forecasts from the Prophet and ARIMA model families, run against your own tables and read under policy.
In KEZEL, as Insights Studio
Reference models are working applications on the KEZEL stack, each with its own worked dataset. We run them with our design partner group.
Run one area on its own, or several as a group.
Each planning area is a module. Start with one beside the source systems you have, and add others when the cycle needs them. KEZEL modules run inside your deployment, next to the data they read.
Standalone
Pick one area and run it on the systems you already use. It reads from your ERP, data warehouse, HR system or spreadsheets, and nothing else in your stack has to change.
One module, switched on for one organisation.
As a group
Add areas on the shared backbone. They read one another's records, so a forecast change reaches supply, finance and margin without an integration project between them.
Modules added one at a time, on the same records.
Where the plans read from
Databases and warehouses
Snowflake, BigQuery, Redshift and operational databases, with change data capture
Business applications
Salesforce, HubSpot, Zendesk and custom systems through connectors
Files
CSV import with preview and row-level errors for people, rates, calendars, leave and budgets
KEZEL VIA
projects, tasks, estimates and logged time, read directly
Source data is read where it lives through the orchestration engine, under your policies. Direct planning feeds from HR systems and CRMs are on the roadmap below.
Open any number to see how it was reached.
Each figure carries its formula, the values put into it and the records those values came from. A reviewer can check a margin or a planned order without asking for the spreadsheet behind it.
- The price-volume-mix bridge closes without a residual bucket, so every unit of variance is assigned to a cause.
- Each planned material order is pegged to the demand that raised it, and each exception says which rule fired.
- Utilisation states its denominator. A missing rate is raised as a data-quality issue and the figure stays unpriced instead of being costed at zero.
Formula, burn-rate method
EAC = actual + remaining estimate × (actual ÷ earned)
Substituted
1,904 + 1,168 × (1,904 ÷ 1,632) = 3,267 h
| Input | Value | Source |
|---|---|---|
| actual to date | 1,904 h | 412 approved time entries |
| earned to date | 1,632 h | Σ estimate × progress, 38 tasks |
| remaining estimate | 1,168 h | 21 open tasks |
| budget | 2,800 h | version Budget FY27 |
467 h over budget (16.7%)Flagged: hours over budget
Try a change before anyone acts on it.
Versions, scenarios and simulations sit on the same records as the live plan, so a what-if is calculated with the formulas of the plan it may replace.
Versions
Budget, latest estimate and forecast are stored as versions of the same plan, so variance is a difference between two saved versions.
Scenarios
Copy the live plan, change it and compare the two side by side. In services planning, promotion is refused if the live plan moved after the scenario was evaluated.
Simulation
Test a price change against an elasticity, a make-or-buy switch from a chosen month, or a what-if run on material supply, without touching the live plan.
Exceptions and alerts
Material plans raise expedite, defer and cancel exceptions. Project plans flag burn ahead of progress, margin below target and unstaffed demand.
Services planning runs on the delivery records in VIA.
viaPlan is the planning part of the VIA suite. It reads projects, phases, tasks, estimates, assignees and logged time from VIA and stores only what VIA does not hold, such as calendars, rates and opportunities.
Capacity
Working calendars, public holidays, approved leave and part-time schedules give each person's available hours by day. Bookings are tentative or confirmed, and work can be staffed by role before anyone is named. Skills and proficiency produce a fit score for each open request.
Demand
Opportunities carry demand by role and a stage probability, and capacity views can show the pipeline as excluded, weighted or in full. Staffing requests pass an approval before they become bookings.
Finance
Rate cards by role, grade, location and client price the plan, with loaded cost and exchange rates. Revenue is recognised for time and materials, capped, fixed fee, retainer, milestone and internal work. Closed months can be locked, and practice P&L is published as account lines for finance.
Delivery
Bookings can be published back to VIA as the task's assignee, so planning and delivery show the same person.
Cost and margin are visible only to roles cleared for them. Where a role may not see money, the field arrives empty from the database and the screen hides the column.
| Role | Sees |
|---|---|
| Consultant | their own schedule and utilisation |
| Resource manager | people, bookings and capacity, with money fields empty |
| Project lead | the plans of projects they manage in VIA |
| Finance | cost, bill rates, revenue and margin |
| Administrator | salary-level cost, as a separate permission |
Plan changes are written to an audit trail with the person who made them.
See the VIA suiteWork through the models with people who plan for a living.
We are forming a small design partner group of planners and model builders. You work through the reference models and tell us where they part from how planning happens in your firm, and you can shape a use case of your own. The datasets are ours; you bring your judgement.
Roadmap
Connectors for HR systems and CRMs, actuals from ERP and the general ledger, and time captured by the viaDesk desktop companion are planned. Today people, rates, holidays, leave and budgets import from CSV, opportunities are entered in KEZEL and time is logged in VIA.
Bring the planning cycle you run on spreadsheets.
Show us how your business plans demand, supply, people or margin today. We will walk through it in KEZEL on sample data, then scope a pilot on your own records.