Transfer data automatically. Less manual data entry.

Planfold connects your tools to import customer enquiries and create follow-up tasks automatically. We work with you to identify which recurring tasks can be automated.

Example: one enquiry, two ways of working.

Manually

4 manual actions
  1. Email
  2. CRM
  3. Task
  4. Team
1 / 4
Open enquiry
New customer enquiry

You move the enquiry from one tool to the next.

Four manual actions: open the enquiry, copy contact details, create a task and notify the team.

With Planfold

1 prepared handoff
Email
CRM
Task
Planfold prepares the handoff
Handle customer enquiry
Details transferredTask created
Time for the customerHandle the enquiry personally
Planfold transfers the data, creates the task and notifies the team. Your staff then handle the customer enquiry personally.

Your time back

How much time could you save?

Enter how often the task occurs and how long it takes now and with automation.

Example calculation · Adjust the values
Estimate the human work still needed.
Today5 hrs / week
With automation1 hrs / week
4hours freed up each week

An estimate based on your inputs; actual effort depends on the workflow.

What does that mean in euros?

Enter all three amounts to see the cost scenario; zero is allowed.

Time freed up has a calculated value; it is not a guaranteed cash saving.

View calculation

Tasks × minutes ÷ 60 = hours per week. The difference is the time saved. Monthly time value: time saved × 52 ÷ 12 × hourly value, less running costs. Setup ÷ positive monthly time value gives the notional payback period.

Where does work repeat itself?

Choose an example workflow.

  1. Input
    Email or form
  2. Processing
    Assign details
  3. Result
    CRM & team

The enquiry and contact details reach the responsible person.

When something is unclear

Clarify missing information.

We check which tools can connect based on their interfaces and access.

How we set up your workflow

Together we define what runs automatically and where your team decides.

  1. Map the workflow

    You show a typical task. We define the applications, rules and exceptions.

    An agreed scope
  2. Connect & check

    We connect the systems and check complete, missing and duplicate inputs.

    A checked workflow
  3. Hand over & support

    Your team gets documentation and guidance. Ongoing support is agreed as needed.

    A documented handoff
Technology and handoffs in detail

How we connect systems, constrain AI and handle failures.

n8n coordinates the workflow
Webhooks, schedules and APIs connect the systems involved. Field mapping, conditions and responsibilities are defined in the workflow. We add custom functions where an integration requires them.
AI with a defined task
AI can classify free text or extract details from documents. Required fields and allowed values are then validated. Unclear results go to follow-up or approval.
Handle failed tasks
Retries, duplicate-processing protection and a review queue are configured for each target system. Logs and agreed notifications make failed handoffs visible.
Hand over your workflows
You receive workflow exports, custom code and integration documentation. Hosting, access and external services are agreed up front, so another provider can take over maintenance.

What goes into your proposal.

Implementation and ongoing services are agreed separately.

One-time implementation

The project price reflects the agreed workflow.

  • Connect applications
  • Rules & exceptions
  • Checks & handoff

Ongoing operations

Choose the level of support your business needs.

  • Hosting & services
  • Monitoring & updates
  • Support & changes

What determines the work involved

The systems involved, data processing and support determine the work. We document which services are included.

Discuss my project

Your website and workflow maintenance

You can commission a website, a workflow or maintenance for existing systems. We check which connections the work needs.

One example: from photo to website entry

A photo and a message start the workflow through to website publication. The homepage shows how an incoming message becomes a checked entry.

View the website example

Questions before your first automation

Integrations, decisions and everyday maintenance.

Can we keep our existing software?

Usually, if suitable APIs, webhooks or exports are available. We check integration options before quoting. If a system does not support reliable data exchange, we explain the limitation and possible alternatives.

Does every workflow need AI?

No. Fixed rules are enough for many handoffs. We use AI for specific tasks such as classifying free text or structuring information. Delivery and approvals follow the rules agreed with your team.

What happens when data is missing or a system fails?

For each workflow, we define when to retry, ask for more information or hand over to a responsible person. Incomplete cases should remain visible. Notifications and ownership are agreed before launch.

Which data reaches external services?

That depends on your connected tools and the selected AI processing. We document data flows, permissions and providers during the project. Which data may reach a service is agreed before implementation.

How are the costs determined?

We first define the workflow and applications involved. The proposal describes implementation, checks and ongoing services with their respective scope. Additional changes are agreed separately.

How is the workflow implemented?

We map the existing process, check integrations and agree on scope. Then we build and test the workflows with your team. Documentation, training and the agreed support arrangements are part of the handover.

Can another provider maintain the workflows?

You receive the n8n workflow exports, custom code and documentation. Workflows can run on another suitable n8n instance. External services and their contracts still need to be considered.

Automation in practice

This project example shows how n8n automates and monitors recurring internal operations and back-office tasks.

Automating recurring internal operations with n8n

n8n connects ticket handling, identity-based access setup during onboarding and follow-up tasks from monitoring. Incoming emails are converted into business data for further processing.

View implementation story

What does your team keep typing in again?

Bring one concrete example and the names of the tools involved. We will identify which handoffs can be automated and where your team should make the decision.

Review my workflow