Skip to Content
Custom Pack · ERP tailored to your business

When your operations don't fit a standard solution, we design the system around your business.

The Custom Pack tailors an ERP to your SME’s operations. We start with a functional analysis commissioned as a separate phase, then define the processes, integrations, automations and dashboards to implement in stages.

Speak to an advisor Explore the possible scope
Initial functional analysis Written, phased scope All the users you need, at no extra per-user cost
// CUSTOM PROJECTUnderstand → implement
01Current processesAssessment
02Target processDesign
03Architecture and phasesPlan
04Tailored configurationSystem
05Automations and integrationsConnection
06Testing and acceptanceValidation
07Launch and measurementControl

We don't start by developing software. First, we understand what the system needs to solve, what data it requires and which risks must be managed.

Business-specific operations

Industry-specific or unique processes that do not fit a standard workflow.

Essential integrations

Verified connections to the applications your business depends on.

Roles and approvals

Tailored permissions, validation steps, documents and responsibilities.

Tailored oversight

Metrics, calculations and dashboards designed around your operations.

Finding the right fit

The Custom Pack is for businesses whose operations require more than adapting a standard process.

We recommend it when your business depends on multiple companies or locations, unique processes, critical integrations, complex data or rules that need to be designed specifically.

Especially suitable if…

Your business structure, rules or systems make a standard implementation insufficient.

The aim is to build a manageable, scalable solution around your actual processes, without forcing your company to work in a way that does not suit its operations.

  • You operate multiple companies, branches, locations or business models.
  • You have industry-specific processes that do not fit standard workflows.
  • Your operations depend on essential integrations with external applications.
  • You need advanced inventory, logistics or traceability.
  • You require custom portals, permissions, approvals or documents.
  • You need to migrate complex historical data or information from multiple systems.
  • Your automations involve multiple rules, exceptions or services.
  • Management needs business-specific dashboards and calculations.
  • Specific components need to be developed.
Not every difference calls for a Custom Pack

First, we check whether Pro, an add-on or a limited adaptation meets the need.

Choosing Custom only makes sense when the unique requirement affects the core process design, critical data or several areas of the business.

  • Small adjustments within a standard workflow are often covered by Pro.
  • A clearly defined need can be solved with Pro plus an add-on.
  • A limited, non-essential integration may be possible without redesigning the whole system.
  • If you only need customer management, quotations, invoicing and payments, Standard may be sufficient.
  • Without a decision-maker, available data and the ability to validate decisions, the project is not yet ready.
  • When exceptions dominate the workflow, we assess Custom or recommend organising operations before implementing anything.
The change we aim for

From adapting your business to a tool to building a system that meets your operational needs.

Customisation is not about adding unlimited features. It means designing specific processes, data, rules and controls without losing clarity, traceability or room to evolve.

Before

The business is forced into a standard process

The target process drives system design
Before

Each company or branch works in isolation

A shared architecture defines what is common and what differs
Before

Critical integrations are improvised

Feasibility is verified before committing to scope
Before

Permissions and approvals are generic

Each role accesses, approves and acts according to defined rules
Before

Changes are tested on real operational data

A test environment allows validation before going live
Before

The project grows without control

Each phase has a defined scope, tests and acceptance criteria
How it starts

We don't commit to a fixed scope before understanding processes, data, integrations and risks.

The Custom Pack starts with an initial functional analysis, commissioned as a separate phase. This turns a general need into a verifiable architecture, scope and implementation plan.

What we analyse

The entire operation before deciding what to configure, integrate or develop.

  • Objectives, current processes, bottlenecks and dependencies on individuals.
  • People, roles, permissions, approvals and responsibilities.
  • Available data, quality, historical records and migration needs.
  • External applications, technical access and integration criticality.
  • Business-specific rules, exceptions, documents and calculations.
  • Metrics and dashboards needed for management.
  • Risks, priorities and dependencies between phases.
What you receive after the analysis

A functional specification that enables informed decisions before implementation.

Functional map and target process

How information should flow, who is involved and what triggers each step.

Architecture and phased roadmap

What is implemented first, what depends on what and how the system can evolve.

Integration and migration feasibility

What can be connected or transferred, under which conditions and with which risks.

Scope and acceptance criteria

What each phase includes, how it is tested and when it is considered complete.

The analysis prevents blind estimates and reduces the risk of turning a complex need into an open-ended project.
Pack scope

What the Custom Pack can include.

The content is designed based on the functional analysis. Not every element is automatically enabled: only what is necessary is included, and everything is defined in writing.

Process flow and functional map

We design the target process with roles, statuses, deadlines, rules, alerts, exceptions and completion criteria. The ERP is configured around that design, not the other way around.

Solution architecture and phases

We define components, dependencies, priorities and a roadmap for progressively implementing and validating the solution.

Required standard components

We use standard capabilities wherever they already address part of the process, avoiding unnecessary development and reducing complexity.

Custom fields, views and permissions

We adapt visible information, forms, access rights and available actions for each role in the company.

Custom workflows, approvals and documents

We configure approval workflows, statuses, templates and documents that match your actual operating rules.

Defined automations and integrations

We connect tasks, departments or applications once technical feasibility has been verified and the objective, rules and expected outcome are clearly defined.

Test environment and validation protocol

We test real-world scenarios outside the production environment and establish who validates each scenario before activating a phase.

Agreed data migration

We transfer explicitly agreed data, with the structure, format, transformations and checks defined in the scope.

Role-based training

Management, administration and operational users receive the training they need to carry out their part of the process and access the relevant information.

Custom dashboards

We design business-specific metrics and calculations when the required data can be recorded and maintained reliably.

Documentation and phase acceptance

Each phase includes documentation of how it works, its limitations, the tests performed and the criteria for accepting delivery.

Fundamental rule: Custom does not mean “everything included”. It means the scope is individually designed, divided into phases, validated and accepted in writing.
Controlled customisation

A tailored solution must be testable, acceptable and able to evolve without becoming an endless project.

That is why we divide implementation into functional phases. Each phase addresses a specific objective, has known dependencies and ends with validation.

How each phase is controlled

Objective, scope, testing and acceptance.

Before a phase begins, we define the problem it solves and the conditions that must be met before moving on.

  • Functional objective and assigned ownersSCOPE
  • Data, access and dependencies availableINPUT
  • Configuration and integrations in a test environmentPREPARE
  • Real-world scenarios and validation protocolTEST
  • Training and operating documentationADOPT
  • Acceptance before starting the next phaseCLOSE
Areas that can be customised

Only what the process needs and the scope defines.

Customisation may affect different layers of the solution, always guided by clear functional and technical criteria.

ProcessesStatuses, roles, rules and exceptions
InformationFields, views, documents and calculations
AccessRoles, permissions and approvals
IntegrationsApplications, services and external data
AutomationsAlerts, tasks, documents and practical AI
ControlBusiness-specific metrics and dashboards
StructureCompanies, branches, locations and operations
ExperienceCustom portals, forms and screens
Customisation does not eliminate the need for standardisation. First, we simplify the process. Then we configure what is needed and only develop custom functionality when the standard system does not solve a real need.
Invoicing and VeriFactu

When the project includes invoicing, VeriFactu is addressed in the scope.

Customisation must not compromise compliance in the invoicing workflow. We define which parts are standard, what documentation is required and which elements cannot be changed without validation.

Clear responsibilities

Implementation and documentation tied to the delivered system.

We configure the invoicing workflow included in the project, perform the agreed tests and provide the relevant documentation. The declaration of responsibility comes from the system producer and covers its version. Extensions to the invoicing system need their producer’s declaration.

01

Define the workflow

Numbering series, documents, statuses, responsibilities and connections with the rest of the process.

02

Implement and validate

We test the included scenarios without altering regulated elements beyond the verified scope.

03

Deliver the documentation

You receive the declarations of responsibility and information about the installed version and extensions.

Source: AEAT · Declarations and system extensions (in Spanish).

Project boundaries

What is not included by default and what can be added within the agreed scope.

In a custom project, clear boundaries are part of the solution. Everything implemented must be defined, feasible and have acceptance criteria.

Not included by default

Custom does not mean unlimited availability or changes.

These needs require a scope change, a new phase or a separately contracted service.

  • Anything requested during the project without changing and approving the scope.
  • Integrations whose technical feasibility has not been verified.
  • Unlimited data cleansing or manual correction of historical records.
  • Permanent availability or support not specifically agreed.
  • Tax, employment, legal or other regulated professional services.
  • Guarantees of financial results that cannot be measured or depend on the client’s actions.
  • Features planned for later phases that have not yet been approved.
May be included in scope

The ERP can adapt to the areas that make your business unique.

Each component is included only when it addresses an identified need and its scope can be precisely defined.

Multi-company, branches and locations

Shared structure, permissions, workflows and operational differences between units.

Industry-specific processes

Statuses, documents, approvals, calculations or rules specific to your activity.

Critical integrations

Connections with external applications, provided access and feasibility have been verified.

Advanced inventory, logistics or traceability

Specific operations that must be designed and validated beyond standard workflows.

Custom portals and experiences

Access, forms, documents and information tailored to customers, suppliers or staff.

Advanced automation and AI

Workflows with multiple rules, or AI where there is a useful, verifiable case with human oversight.

Custom dashboards and calculations

Metrics built on available, maintainable data and defined by management.

Every element needs an objective, scope, required data, a validation owner and acceptance criteria.
How we implement it

The project is delivered in phases, following a consistent method.

Configuration alone is not enough. The solution must be understood, tested, adopted and measured so the business can delegate and grow with control.

01 / UNDERSTAND

Understand the current situation

Objectives, current processes, people, data, integrations and problems.

02 / DESIGN

Define the target process

Owners, statuses, rules, alerts, exceptions and metrics.

03 / PREPARE

Build the phase

We configure the system, prepare data and implement what has been approved.

04 / VALIDATE

Test real-world scenarios

We carry out the test protocol and correct anything included in the agreed scope.

05 / TRAIN

Provide role-based training

Each person learns only what they need to perform their part of the process.

06 / LAUNCH

Go live

With an agreed date, owners, data migration and incident-handling procedure.

07 / MEASURE

Review adoption and improvements

We review metrics, usage, exceptions and priorities for the next phase.

For it to work, we will need a clear commitment from you.

  • Appoint a decision-maker responsible for the project.
  • Provide data and documentation in the agreed formats and by the agreed dates.
  • Provide technical access and coordinate with external suppliers.
  • Validate the target process, priorities and test scenarios.
  • Ensure the team attends its training.
  • Stop using parallel processes that duplicate information.
  • Keep the data feeding automations and metrics up to date.
  • Involve your accountant or other professionals when their validation is necessary.
Frequently asked questions

Questions to consider before choosing the Custom Pack.

Why don't you provide a fixed quote on the first call?

Because we first need to understand processes, data, integrations, people and risks. The project starts with a functional analysis that provides a sound basis for defining the architecture, phases, scope and acceptance criteria.

Does the Custom Pack mean everything is included?

No. It means the scope is designed specifically for your operations. Each phase states what is included, what is excluded, how it is validated and which changes require an extension.

Can you connect the applications we already use?

Integrations can be included when they are necessary and their feasibility has been verified. We need technical access, provider documentation and a clear definition of the data and actions to be exchanged.

Can it manage multiple companies, branches or locations?

Yes, this can form part of the scope. The analysis defines what information is shared, which operations differ, what permissions each unit requires and how oversight should be consolidated or kept separate.

Is historical data migration included?

Only the agreed migration is included. Sources, formats, transformations, quality and validation must be defined. Unlimited data cleansing or manual correction of historical records is not included by default.

Is everything tested before using real operational data?

The scope may include a test environment and a validation protocol. Real-world scenarios are reviewed before each phase goes live to reduce risks and confirm that the process works as defined.

Are automations and development unlimited?

No. Every automation or development needs a defined objective, rules, data, outcome, tests and limits. New needs are addressed through a scope change or a later phase.

What if the analysis shows that Pro is sufficient?

We will tell you. The purpose of the analysis is to recommend the right solution, not automatically turn every need into a Custom project.

Do I pay more to add users?

No. You can add all the users you need without paying an additional per-user fee.

How is VeriFactu handled if the project includes invoicing?

We implement the agreed invoicing workflow. The system producer provides its declaration of responsibility; extensions to the invoicing system require their producer’s declaration. We deliver the documentation for the installed version.

See all FAQs
Next step

Your business shouldn't have to squeeze into a standard solution.
It needs a system designed around your operations.

Speak with an advisor. We'll review your processes, data, people, integrations and risks to determine whether you really need the Custom Pack. If it fits, the next step is to define the functional analysis; if Pro solves the problem, we'll tell you.

Speak to an advisor Use the contact form
No blind promises · First we analyse, then we define