Skip to content
427
All products

Custom

Custom Automation

Dedicated automation for a workflow that doesn't fit a standard product.

If your workflow does not fit one of our standard products, we can scope and build a dedicated automation around it. You bring a specific, repetitive process. We define clear rules and a fixed scope, build the automation, test it with you and hand it over.

Input
Your workflow
Output
Dedicated automation
Project price
From €3,000
Founding Client Pricing

What it does

Custom Automation is for a specific business process that involves repetitive manual work: transferring information, handling documents or emails, routing work internally, updating databases or preparing the same reports again and again.

We start from how the process works today, identify the steps that can be automated reliably and agree the scope and rules in writing. The result is a practical automation built for that one workflow, not an open-ended consulting project. Steps that need human judgment can stay with a person, with the automation preparing the work for them.

A good fit when

  • The process repeats regularly and follows recognizable rules
  • Inputs and outputs can be clearly described
  • Time goes into manual transfer, checking or routing
  • No standard product covers the workflow

What you receive

  • A written scope with agreed rules and outputs
  • A working automation for the agreed workflow
  • Testing with your own data and cases
  • Deployment into your environment, with handover documentation

Works on its own

Custom Automation is scoped and delivered on its own. If one of our standard products covers part of the workflow, we will point that out, but you decide what to buy.

The problem it solves

Many repetitive processes are specific to one company. Standard software does not cover them, so they are handled by hand, with spreadsheets, copy-and-paste and email.

  • The same manual steps repeated every day or every week
  • Information moved by hand between emails, documents and systems
  • Work routed through inboxes and chat messages instead of a clear process
  • Recurring reports put together manually from several sources

How it works

  1. 1

    Understand the current process

    We go through how the workflow runs today: inputs, steps, people, systems and exceptions.

  2. 2

    Identify what to automate

    We point out which steps can be automated reliably and which should stay with a person.

  3. 3

    Define scope and rules

    Inputs, outputs, business rules and review steps are agreed in a written scope.

  4. 4

    Build the automation

    The automation is built for the agreed scope, using technology that suits the workflow.

  5. 5

    Test with you

    The automation is tested with your real data and cases until the agreed scope is accepted.

  6. 6

    Deploy and hand over

    The automation is deployed into your environment and handed over with documentation.

Example workflow

A company receives order change requests from customers by email. Each request is checked by hand, entered into an internal spreadsheet and forwarded to the responsible team for approval.

  1. 01We review the current process and the typical types of change request
  2. 02The scope defines which requests are handled, which fields are captured and who approves what
  3. 03Incoming requests are captured, and the relevant details are entered into a structured record
  4. 04Each request is routed to the responsible team for approval
  5. 05Approved changes are logged, and unclear requests are flagged for a person to handle

Typical use cases

  • Repetitive data entry

    Entering the same information into spreadsheets, databases or internal tools.

  • Document processing

    Extracting and organizing information from recurring business documents.

  • Email-driven processes

    Processes that start with an incoming email and follow a predictable path.

  • Internal workflow routing

    Sending work to the right person or team based on clear rules.

  • Approval workflows

    Structured request, review and approval steps with a clear record.

  • Data transfer between systems

    Moving information between tools that do not talk to each other.

  • Operational reporting

    Preparing recurring reports from data that is collected by hand today.

  • Administrative tasks

    Recurring administrative work that follows the same steps each time.

Expected business impact

  • Reduce repetitive manual work in the automated process
  • Reduce time spent transferring information between systems
  • Make the workflow and its review steps clearer
  • Keep information in a consistent, structured form

The actual effect depends on the workflow, its volumes and the agreed scope. We discuss realistic expectations during scoping.

Customization & scoping

Scoped around one specific workflow.

Every Custom Automation project starts with a defined scope. Not every process is a good candidate for automation, and we will say so during scoping if that is the case.

  • Which steps of the workflow are automated
  • Inputs, outputs and data structure
  • Business rules and exceptions
  • Review and approval steps
  • Integrations with your existing systems, where technically possible
  • How and where the automation is deployed

Ownership & deployment

Custom Automation follows the same ownership model as our standard products. Where technically appropriate, the automation runs on accounts and infrastructure that your organization owns.

  • Your repository, database and deployment, where the project needs them
  • Your business data and your API and external service accounts
  • Developer access only during the project, removed by you after delivery
  • Keeps running without our accounts or servers
Ownership & deployment
Code repositoryIn your GitHub organization, where the automation includes code
DatabaseIn your own account, if the automation stores data
Hosting and deploymentIn your own account, if the automation needs to run as a service
API and service accountsSuch as AI, email or office services, only where the workflow uses them

The infrastructure depends on the project. Technology is chosen to suit the workflow and agreed in the scope.

How ownership and handover work

Pricing

Project price

From €3,000

A custom solution built after we discuss your specific problem. Pricing depends on workflow complexity, integrations and the systems involved. You receive a written scope and a fixed project price before any work starts.

Founding Client PricingIntroductory pricing for our first 3 client projects.

Prices exclude VAT where applicable.

After successful delivery, we may ask for permission to use anonymized results or a case study. This is always your choice.

Included in the project

  • Review of the current process and a written scope
  • Building the automation for the agreed scope
  • Testing with your own data and cases
  • Deployment, handover and documentation

What affects the final price

  • Complexity of the workflow
  • Number of inputs and outputs
  • Required integrations
  • Number and complexity of business rules
  • Review and approval requirements
  • Overall implementation scope

Running costs of services in your own accounts (hosting, database, AI API usage) are billed to you directly by those providers.

How to order

Every product is ordered the same way:

  1. 1Contact
  2. 2Requirements
  3. 3Scope & quote
  4. 4Customization
  5. 5Implementation
  6. 6Testing
  7. 7Delivery

Talk to us about Custom Automation

Send a short description of your current workflow. We will reply with questions for scoping and the next steps.