Finance practice
Accounting and FP&A
How figures are defined, challenged, explained and signed off.
About Précis
Finance experience and systems thinking, brought together.
Précis brings together experience in EPM, accounting and FP&A, finance systems and solution architecture. We have seen both sides of the same problem: finance professionals working around the limits of current platforms, and architects connecting the systems those platforms leave apart.
- Finance practice
- EPM experience
- Systems architecture
- Professional judgement
Why Précis exists
The systems are not the problem. The work between them is.
The ERP records the transaction. The planning platform holds the plan. The warehouse and BI layer organise reporting. Excel carries the questions and models that do not fit anywhere else. Each system is precise within the scope it was built for.
The remaining work falls to finance: reconciling definitions, moving figures between systems, rebuilding the same comparisons and tracing a number when the business asks why. Précis is being built for that work in between.
A deliberately mixed discipline
Finance practice, platform experience and architecture in one room.
Planning platforms
EPM and planning
Where structured platforms work well and where changing questions outgrow configured workflows.
Operational reality
Finance systems
How ERP, warehouse, planning and spreadsheet processes meet in practice.
Technical foundation
Solution architecture
How identity, permissions, deployment and data boundaries turn useful software into a credible finance system.
The combination matters because this is neither only a data problem nor only a workflow problem. Financial meaning, system design and professional judgement have to hold together.
What follows from that experience
Built around the way finance remains accountable.
- Précis prepares; finance decides. The platform retrieves, reconciles and structures. Finance interprets, challenges and signs off.
- Definitions sit below the interface. Metrics, statements, hierarchies and scenarios are governed independently of the client asking the question.
- Figures come from structured operations. A language model can help with language and navigation; it does not generate the financial result.
- Existing systems keep their role. Précis is not an ERP, an EPM replacement or a campaign to remove Excel.
- Trust boundaries are explicit. Deployment, identity, access and evidence paths should be inspectable and explainable.
Building with design partners
Start with one consequential finance workflow.
Précis is pre-General Availability. We are working with a small number of design partners to test the platform against real reporting structures, governance requirements and analytical workflows.
The source-available Précis Finance MCP read engine can be self-hosted today. The full Précis platform adds the finance workflow around that governed core. For a design partnership, we begin with one recurring process and make the definition, evidence and review boundary explicit before expanding.
Bring us the workflow that still lives between systems.
We will tell you where Précis fits, what needs to be configured and what should remain with finance.