enaudo
Book

Less manual work

Custom software development for service businesses. Connect your tools and automate workflows.

Book an intro call Our services

Based in Berlin. Remote across Europe.

  • Inbox with reply draft

    AI can draft the reply, your team edits and sends it.

    Inbox with reply draft: Try itLearn more

  • Enquiries and payments at a glance

    From new enquiry to payment, with the calendar in view.

    Enquiries and payments at a glance: Try itLearn more

  • New contacts straight into the CRM

    From an e-mail, business card or chat into the CRM in one click.

    New contacts straight into the CRM: Try itLearn more

  • Capture and sort receipts

    Photo or file, check the details, ready for accounting.

    Capture and sort receipts: Try itLearn more

  • Review and approve documents

    Extract details, check the original, create a PDF from a template.

    Review and approve documents: Try itLearn more

  • Onboarding, step by step

    Documents, access and the first day in one process.

    Onboarding, step by step: Try itLearn more

AI can draft the reply, your team edits and sends it.

Examples built for this website with invented data: no client systems, no references, no AI running. The scope is defined per project.

Inbox with reply draft

Try it: click the icons, switch conversations, edit the text or have it rewritten. The variants are prepared, no AI is running here. Nothing is sent or saved.

  1. An enquiry arrives and appears as a conversation.
  2. In a real system, AI prepares a reply draft that your team can edit.
  3. The draft only goes out once someone on your team clicks “Send”.
See the enquiry workflow

Examples built for this website with invented data, not client systems or references. No AI runs in these examples and nothing is sent or saved. Features are defined per project.

Enquiries and payments at a glance

Try it: move enquiries on, then open the calendar and payments via the icons. Nothing is sent or saved.

  1. Every enquiry moves through clear steps.
  2. The calendar shows which days are booked.
  3. Open and overdue payments are always visible.
See custom business software

Examples built for this website with invented data, not client systems or references. No AI runs in these examples and nothing is sent or saved. Features are defined per project.

New contacts straight into the CRM

Try it: switch between e-mail, business card and chat, change the fields and add the contact. The details are prepared, no AI is running here. Nothing is saved.

  1. A new contact arrives by e-mail, on a business card or in a chat.
  2. In a real system, the details are read and prepared, and you check them.
  3. One click adds the contact. The same action is available via API and MCP.
See the CRM workflow

Examples built for this website with invented data, not client systems or references. No AI runs in these examples and nothing is sent or saved. Features are defined per project.

Capture and sort receipts

Try it: review the waiting receipt, change the details and filter the list. The reading is simulated, no camera is used and nothing is saved.

  1. In a real system, a receipt arrives as a photo or file and the details are read.
  2. You check the fields and correct anything that is wrong.
  3. In this example, the receipt only joins the list after your click.
See the receipts workflow

Examples built for this website with invented data, not client systems or references. No AI runs in these examples and nothing is sent or saved. Features are defined per project.

Review and approve documents

Try it: settle the quantity that differs between delivery note and order, accept or edit the suggestion, and approval unlocks. A preview of the PDF follows. The suggestion is prepared, no AI is running here. Nothing is saved or downloaded.

  1. In a real system, a scan is read and uncertain spots are flagged.
  2. In a real system, AI only suggests additions to entries that are too short; your team decides.
  3. In a real system, the finished PDF is created only after approval.
See document automation

Examples built for this website with invented data, not client systems or references. No AI runs in these examples and nothing is sent or saved. Features are defined per project.

Onboarding, step by step

Try it: tick tools under access and watch the preparation run by itself. Unticking reverts the run. You approve sending and activation yourself. Nothing is sent or saved and no access is created.

  1. Every new hire goes through the same steps.
  2. A tick starts the preparation: account, access, invitation. Activation and sending wait for your approval.
  3. The first day is planned and the welcome message is ready.
See the onboarding workflow

Examples built for this website with invented data, not client systems or references. No AI runs in these examples and nothing is sent or saved. Features are defined per project.

Business software built around your operations

enaudo builds custom software and automates processes for small and medium-sized service businesses (SMEs). Your existing tools, custom apps and accounting become one connected workflow with clear responsibilities and approvals.

Onboarding and offboarding also fit: bring documents, tasks and access together. Activation, sending and removal of access remain subject to approval. HR examples

Explore services and how to start

From enquiry to invoice draft

Try it: click through the steps, choose the quantity that was actually delivered and approve the draft. Nothing is sent, booked or saved in this example.

  1. An enquiry is taken over and prepared as a quote.
  2. The work that was actually done is recorded, even if it differs from the quote.
  3. An invoice draft follows from both. It only goes out after approval.
See the enquiry workflow

Examples built for this website with invented data, not client systems or references. No AI runs in these examples and nothing is sent or saved. Features are defined per project.

Your own app that connects your existing tools

Try it: connect the tools one after another and watch the data arrive in the workspace. The tools are invented, nothing is really connected or saved.

  1. You connect the tools your business already uses.
  2. The data for one case comes together in one workspace.
  3. SSO, API and MCP are building blocks of the connection in this example. What a real tool allows is checked per tool.
See custom business software

Examples built for this website with invented data, not client systems or references. No AI runs in these examples and nothing is sent or saved. Features are defined per project.

Review and approve documents

Try it: settle the quantity that differs between delivery note and order, accept or edit the suggestion, and approval unlocks. A preview of the PDF follows. The suggestion is prepared, no AI is running here. Nothing is saved or downloaded.

  1. In a real system, a scan is read and uncertain spots are flagged.
  2. In a real system, AI only suggests additions to entries that are too short; your team decides.
  3. In a real system, the finished PDF is created only after approval.
See document automation

Examples built for this website with invented data, not client systems or references. No AI runs in these examples and nothing is sent or saved. Features are defined per project.

Built openly, run in Europe

We run the systems we build for you, or they run on your own infrastructure.

More on sovereignty and open systems

  1. API and MCP in the tools we build

    What we build ourselves usually comes with an API and can be reached by AI assistants through MCP, the Model Context Protocol, the open standard for connecting assistants to tools. We connect third-party programs through the interfaces they already have.

  2. Central login for the tools we build

    Where single sign-on is set up, one login covers the tools we build ourselves instead of a new password for each. Whether third-party programs can join is checked one by one.

  3. Servers in the EU

    Our systems run almost exclusively on servers in the EU. We name exceptions before the project starts.

  4. Open source or custom code

    Almost exclusively open source or code we write ourselves, so usually no subscription for third-party software.

On site in Europe

We prefer to meet at your site, because that is where we see the process as it really runs. For larger projects we come to you in Germany, across the rest of the EU and in the UK, and in Berlin we also meet at The Delta Campus in Neukölln. Remotely we work across Europe.

What does custom software or automation cost?

As a guide, smaller projects are up to €6,000; more comprehensive systems start from €6,000. A small, clearly scoped component can be the first step towards a more comprehensive business solution.

Smaller projects

up to €6,000

A defined workflow, an integration or a focused app. We agree on the goal and scope before building.

More comprehensive systems

from €6,000

Several connected workflows, a custom working interface and integrations with your tools. The specific scope determines the budget.

Operations

from €150 per month

If we run it for you, you pay a monthly flat fee, from about €150 net for smaller projects. Operation, backups and maintenance are included. Availability and response times are set out in the contract. Alternatively, the system can run on your own infrastructure.

Non-binding budget guidance for businesses, all amounts in euros and excluding VAT. Data migration, roles, integrations, exceptions and testing determine the specific quote. Operations and further development are agreed to suit the project. If the system runs on your own infrastructure, the quote sets out the costs and usage rights for that.

Book an intro call

Short answers

Do we have to replace our existing applications?

That depends on the process. Existing applications can remain in use and be connected. If an application lacks the required interfaces or permissions, we clarify a limited handover or an appropriate alternative before agreeing the implementation.

Can we start small and expand later?

Yes, if a useful first component can be defined. We discuss early on which later steps should be considered. Additional functions, costs and dependencies are agreed before each extension.

Who looks after the software after handover?

Operation and maintenance are explicitly agreed. Options include managed operation or a handover with designated owners. Updates, support and new features need a clear scope; they are not automatically included without limits.

Do we need a finished concept?

No. A concrete description of today’s process, the applications involved and your goal is enough to start. Scope and possible implementation are then discussed together.

All questions

Tell us about your project

Which task takes up time, which tools do you use, and what should work better? A short description is enough to get started.

Project enquiry

Three details are enough. Everything else is optional.

More details (optional)

We will reply by email.

Controller: Leonardo Scharl (enaudo). We process your details to handle your enquiry; we use the optional information on how you heard about us to evaluate our contact channels. Legal bases, service providers and your rights, such as access, erasure and objection, are set out in the privacy policy.

Book an intro call

The calendar is loaded from Cal.com (USA). To book the appointment and diagnose errors, technical data such as your IP address and diagnostic data go to Cal.com and its service providers in the USA; cookies are possible. No connection to Cal.com is made before you confirm. You can withdraw your consent at any time: close the window and reload the page. Details in the privacy policy

Use the enquiry form instead info@enaudo.de