Skip to content
Gallucci One Finance

How it works

6 steps.The last one goes back to the first.

Understand the business. Connect what it already runs. Configure only what it needs. Remove the repetitive work. Turn the data into something people can act on. Then change it all again, because the business will.

The sequence

  1. 01Understand
  2. 02Connect
  3. 03Configure
  4. 04Automate
  5. 05Understand
  6. 06Evolve
  7. ↻Back to 01

  1. 01

    Understand

    G1 maps the business before it changes anything.

    What you actually do, in what order, and where the friction is. Not a requirements document — a map of the business as it runs today, including the parts that only work because someone remembers them.

    • Where data is created, and where it gets re-entered
    • Which systems earn their place and which are habit
    • The decisions people need to make, and what they lack
    • The controls that exist, and the ones that only exist on paper

  2. 02

    Connect

    Systems and data are connected — not replaced for the sake of it.

    The systems worth keeping stay. Their data comes into G1 so the numbers stop diverging, and the manual bridges between the rest are removed rather than automated.

    • History and opening balances brought across and agreed
    • Bank statements and spreadsheets imported with validation
    • Master data deduplicated into one record per customer and supplier
    • A defined system of record for each kind of data

  3. 03

    Configure

    The modules and workflows the business needs are switched on.

    Chart of accounts, dimensions, approval rules, periods, roles. Configured to how this business works, not to a template — then the same structure is reused for the next site, entity or country.

    • One chart of accounts and dimension structure, used everywhere
    • Approval thresholds by document type, amount and role
    • Fiscal calendar, period control and close checklist
    • Only the modules that earn their place, to start with

  4. 04

    Automate

    Repetitive work is removed, not moved to someone else.

    Schedules post themselves. Matching proposes rather than waits. Approvals route by rule. The judgement calls stay with people, because those are the parts that are worth paying for.

    • Recurring journals, accruals and prepayments release on schedule
    • Statement lines matched by rule, confirmed by a person
    • Payment runs assembled from due bills, not from a spreadsheet
    • Approvals routed and escalated automatically

  5. 05

    Understand

    G1 turns business data into something you can act on.

    The second Understand is the point of the first four. Once the data is clean, current and in one place, the system can tell you what it is saying — and people can stand behind the analysis.

    • Dashboards and reports built on posted, reconciled data
    • Observations raised proactively, against your own history
    • Drivers explained, not just movements reported
    • Human review in front of anything that reaches a board

  6. 06

    Evolve

    The system changes as the business changes. It is never finished.

    A business that stays the same does not need this. Adding a module, an entity, a country or a capability should be configuration — which is why the architecture is built the way it is.

    • Add modules when the business needs them, not up front
    • New entities and sites are configuration, not projects
    • Capabilities that do not exist yet have somewhere to go
    • Remove what stops being useful

  7. And then back to 01

    G1 should never feel finished.

    A business that stays the same does not need any of this. Every time something changes — a new entity, a new country, a department that has outgrown its spreadsheet — the sequence starts again at Understand. That is not a failure of the implementation. It is the implementation.

An evolving system

What exists, what is being built, and the space left for what isn't.

Adding a module, an industry or a kind of agent is a content operation, not a release. That is the whole point of building it this way.

See the catalogue
  1. Today

    Finance, working

    The finance product that exists and is in use.

    • General ledger and the posting engine
    • Payables, receivables and banking
    • Tax, fixed assets and expenses
    • Reporting, management accounting and consolidation
    • Approvals, period locks and audit trail
    • Market intelligence

    15 modules in the catalogue: Accounting, Accounts payable, Accounts receivable, Cash flow and 11 more.

  2. Tomorrow

    Beyond finance

    Operations, commercial and documents on the same data.

    • Workflow and processes
    • Procurement
    • Projects
    • Documents
    • Customers

    6 modules in the catalogue: Workflow, Processes, Procurement, Projects and 2 more.

  3. Next

    Agents and prediction

    The system reading its own data, and doing the repetitive parts.

    • AI assistants and agents
    • Automated analysis
    • Forecasting and scenarios
    • Ranked recommendations

    5 modules in the catalogue: AI assistants, Automated analysis, Forecasting, Recommendations and 1 more.

  4. Whatever comes next

    The capacity to add

    The part we are not going to pretend to have specified.

    • New modules as content, not as releases
    • New industries without a new site
    • New agents without a new product
    • Capabilities that do not have a name yet

    Room left on purpose

The human layer

Technology when you need it.Expertise when you need it.

Software on an old process buys very little. The human layer exists because businesses sometimes need someone to actually help them make it work.

How we work
Build Your G1Meet the human layer

Start anywhere

The first step is understanding the business. Start by describing yours.

Build a G1 in a couple of minutes, or talk to someone who has done this before.

Build Your G1Talk to G1