Home / Guidance

Guidance makes the difference, not the software

You do not choose an ERP from a feature list. What decides the outcome is the quality of the people who help you put it in place, then keep it alive.

Talk about your project
What we believe

Everyone sells software. Far fewer sell guidance.

Hundreds of deployments have taught us that ERP projects almost never fail on the technical side. They fail when nobody takes the time to understand the trade, when teams are left alone after training, or when the budget slips because nothing was ever costed. We work the other way round.

Analysts who come to you

We immerse ourselves in your day-to-day before writing a single line of specification. Your real constraints, not those of a sector in general.

Someone who knows you

No anonymous help desk: the people who answer are the people who built your environment.

A budget costed before we start

What can be estimated is estimated. What is variable by nature runs on a retainer drawn down as actually used, with no renegotiation at every request.

An SME talking to an SME

DigiWall is the size of its customers. The same trade-offs, the same urgencies, the same need for quick decisions.

Two SMEs

Wallify was born at DigiWall, and DigiWall runs on Wallify

We do not sell software we would not use ourselves. Our quotes, orders, service calls and dashboards live in Wallify every single day.

DigiWall
Wallify

One SME that builds, one SME that produces. The same constraints, the same language.

Setup

A controlled setup, estimated in advance

Hundreds of deployments have taught us to price precisely what starting up an ERP involves. Setup tasks are therefore estimated before the project; other work, variable by nature, is covered by a retainer used on a time-and-materials basis.

Setup — against an estimate

Priced before the start, within a precisely defined budget.

  • DeploymentInstallation of your environment, on our Azure solution, your cloud or your servers.
  • ConfigurationSetting up the modules, roles, journals, commercial terms and basic templates.
  • TrainingYour teams get to grips with the software, right through to being self-sufficient in their own area.
  • Any integrationsAccounting, Peppol, e-commerce or your existing business tools.

Against a retainer, time and materials

Work on demand, used as actually needed against an agreed retainer.

  • Data importsMigration of your customers, items, history and stock from your current systems.
  • Question-and-answer sessions & change supportLong-term support for your teams, at the pace at which their skills grow.
  • Specific document templatesQuotes, invoices and delivery notes in your own style and in line with the practices of your trade.
  • Specific dashboards and KPIsIndicators and analyses tailored to how you run the business. See examples →
  • +And any other requestYour needs change: the retainer adapts, with no renegotiation every time.
How the project runs

From the first meeting to going live, with no nasty surprises

An ERP is not deployed in one go: it is built in stages, each one approved with you before moving on to the next. Here is how it works in practice.

1
Against an estimate

Analysis of your needs

Immersion in your trade, a clear specification, a precisely defined budget.

2
Against an estimate

Deployment and configuration

Environment installed, modules configured, roles and document templates in place.

3
Test environment

Testing, approval and training

A dedicated environment, separate from your production system: your teams practise and you put the solution through its paces with no risk at all.

4
Against a retainer

Migration of your data

Customers, items, stock and history imported, then checked in the test environment.

5
Go live

Going live

A calm switch-over: what was approved in testing becomes your everyday tool.

6
Ongoing

Support and further development

Support, question-and-answer sessions, new modules and KPIs at the pace of your growth.

Step 3 · in detail

A test environment, separate from your production system

We can build a second environment, a copy of your future ERP, dedicated to training and approval. Your teams practise in real conditions and you put every process to the test before the switch-over — without ever touching your production data.

Train without risk

Your staff make mistakes, start again and gain confidence. Nothing gets broken.

Put your processes to the test

Replay your trickiest real-life cases before switching over.

Approve the imports

Check the data migration before it becomes your master data.

Test new developments

Keep it after go live to approve every new feature.

Let’s talk about your project, not about our features

One first conversation is enough to tell whether we are the right partner for you.

Request a free demo