Pricing & inclusions

Know what you are buying before you buy it.

Small, clearly defined tasks have package prices. Larger projects receive a written proposal before any paid work begins. Nothing below is a hidden retainer.

Please note: the figures on this page are proposed prices while the practice establishes its Finnish pricing. They are confirmed in writing before any work starts.

Connect

Connect a workflow

Proposed €250, one-off

Included

  • Assessment of one workflow across up to two systems.
  • A written description of the technical next step.
  • A clear statement of what a full connection would require.

Not included

  • Building the connection itself.
  • Licences or subscriptions for third-party services.
Enquire about this →
Understand

Get a useful report

Proposed €350, one-off

Included

  • Improvement of one existing ERPNext report.
  • Agreed columns, filters and totals.
  • A short handover note so the report can be changed later.

Not included

  • New doctypes or data that does not exist yet.
  • A full reporting suite or dashboard programme.
Enquire about this →
Implement

Plan your ERP

From a proposed €3,500

Included

  • ERP operational starter: configuration of core sales, purchasing and inventory.
  • Data import within agreed volume limits.
  • Testing of real workflows and training for your team.

Not included

  • Manufacturing, payroll or healthcare modules unless scoped.
  • Custom development, integrations and hosting — quoted separately.
Enquire about this →

What always needs a separate quote

The costs people forget to ask about.

ItemHow it is handled
HostingQuoted as a recurring cost, with who holds the server access stated in writing.
SupportAgreed as a separate arrangement — response expectations stated, not implied.
Data migrationScoped by volume and by who is responsible for cleaning the data.
IntegrationsQuoted after the API assessment, because that is when the real cost is known.
Custom developmentQuoted per defined requirement, never open-ended.
TrainingIncluded in implementation scope; additional sessions quoted separately.

Before you compare quotes

What actually drives ERP cost.

  • How much data moves, and how clean it is. Migration is usually underestimated more than configuration.
  • How many workflows change at once. A phased first step finishes; a full rollout often stalls.
  • How many systems must stay connected. Each integration is its own project with its own failure modes.
  • How much training the team needs. Software nobody was trained on becomes a side spreadsheet.
  • Who runs it afterwards. Hosting and support are ongoing costs, and they belong in the first conversation.

Want a figure for your actual situation?

Describe the workflow and you will get a written scope with the assumptions spelled out.

Request a scope