Skip to content
PERINGER Data Solutions, back to home

Back

Solution

The business tool built for you

A shared file has ended up carrying an entire process, and every edit puts that process at stake. Replacing it doesn’t mean rewriting everything: it means giving that process a database, permissions and a history.

From shared file to application

In practice

  • Taking over the existing file: columns, formulas and special cases catalogued before anything is rewritten
  • A database with constraints, rather than a sheet where everything is allowed
  • Roles and permissions: who enters, who approves, who sees only part of it
  • A full change history, readable without writing a query
  • Import and export in the formats already in use, so habits do not break overnight
  • Automated tests on the calculation rules, run on every change

Systems involved

  • Existing Excel and CSV files, both in and out
  • Accounting and ERP over APIs or exchange files
  • Microsoft 365 or Google Workspace for identity
  • Mail, for notifications and approvals
  • A BI tool, when the data also has to feed a dashboard

Service lineApplications and integration →

How it runs

  1. Survey

    We read the file as it stands, with the people who use it. The special cases written down nowhere surface at this point.

  2. Model

    The data takes shape: what is an entity, what is a field, and what was only a column of convenience.

  3. First version

    A usable application on a narrow scope, running alongside the file, long enough to compare the results.

  4. Switchover

    History migrated, the team trained, and the file goes read-only rather than into the bin.

Test the fit: The business tool built for you

Describe the context, constraints and decision you need to make. The first conversation qualifies scope, boundaries and the next useful step.

Describe the situation