Your workflows.
Built on ElbDesk.

ElbDesk is the foundation on which we develop your software. ElbDesk provides sign-in, permissions, documents and collaboration. We add your screens and business rules, and ERP modules when you need them.

Sample view · values for illustration

An ElbDesk window: on the left the areas overview, purchasing, warehouse, sales and accounts, below them “Your part” with designer and the open production area. On the right a production order created from the designer, with four materials and quantities; at the bottom the scheduling at the cutting station with material reserved.

An illustrative view

Your workspace. Your business rules.

Lists, detailed views and next steps belong together. This illustrates how a custom workspace on ElbDesk could look.

Workflow illustration · fictional example data
  1. See your records
  2. View details in the same workspace
  3. Prepare the next step

In practice

ElbDesk in use

  • Built with ElbDesk

    Auction house

    Auction platform

    Workflow illustration · fictional example data

    ElbDesk as an auction platform - lot numbers, catalogue and settlement in one system.

    • Lot number entry
    • Cataloguing of objects
    • Settlement of auctions
  • Built with ElbDesk

    Prepress business

    Replacing an old system in a production business

    At Carl Ostermann Erben, an ERP on ElbDesk replaces an old system that could no longer be extended - on a clean data model and connected to the production software in real time.

    • Production steps directly in the ERP
    • Room to extend on the ElbDesk Core
    • Real-time connection to the production software

„Durch die enge und partnerschaftliche Zusammenarbeit entwickeln wir ein ERP-System, das genau auf unsere Bedürfnisse zugeschnitten ist.“

Holger Ostermann · Managing Director, Carl Ostermann Erben GmbH

Why ElbDesk is different

Which foundation fits your project?

Standard software, a standalone custom application and ElbDesk have different strengths. Your workflows, existing systems and the effort needed for rollout and operation determine the choice.

CriterionStandard softwareStandalone developmentWith ElbDesk
Sign-in, permissions, documentsIncludedHave to be developed as wellProvided by ElbDesk
Warehouse, invoicing, accountingIncluded, the way the vendor designed themHave to be developed or connectedAs modules, when you need them
Your special rulesOnly within the settings, the rest runs alongsideDeveloped for youDeveloped for you, directly in the system
Later changesDepends on what the vendor allowsAs you need themAs you need them

ElbDesk is not automatically the right choice for a pure integration or a standalone app. We clarify that before implementation.

Structure

One foundation. Modules as needed. Your process on top.

  1. The foundation

    What every application needs and nobody should build twice: sign-in and permissions, workspaces, collaboration, documents and search - in the office, in the browser and on the phone.

  2. ERP modules

    Ordering, warehouse, invoicing or accounts are added only if you need them. If you have an ERP, it stays. Accounts and warehouse keep running there, and we connect it where possible, so nothing is maintained twice.

  3. Your part

    We build your costing, approvals or production steps with custom screens and rules. The scope follows your actual workflows.

Ways to use it

As a foundation, alongside your system or as an ERP

Which way fits depends on what your current system does well.

Option 1

As the foundation for your application

Customer portal, field app, approvals: ElbDesk already brings sign-in, permissions and master data. The scope of custom development depends on your task.

Option 2

Alongside your existing ERP

Processes your system does not cover run in ElbDesk and are, where possible, connected. We assess any required changes to the existing ERP in advance.

Option 3

As the ERP for your company

When the existing system reaches its limits, we plan its replacement with ElbDesk. For each area we assess data migration, parallel operation and cut-over dates.

Rollout

Your process first.
Then one area at a time.

Whether ElbDesk fits your process shows in the first area - not in a presentation.

  1. Record the process

    We look at how your business works and what your current system does - and check whether ElbDesk fits.

  2. Build the first area

    We build your workflows on ElbDesk, and your team tests them on real transactions. Your current system keeps running, connected where possible.

  3. Carry on once it proves itself

    Further areas follow at your pace. What can stay, stays.

AI in the system

Ask your ERP in your own words

ElbDesk answers questions like these straight from your data. AI assistants access it through a dedicated interface (Model Context Protocol, MCP) - what they may read is decided by the permissions in the system.

Which orders are overdue?

Show me all customers in Hamburg.

Contact

Does ElbDesk fit your project?

We discuss your workflows and show you what ElbDesk provides, what would need custom development and what a first step could look like.

Tobias Kietzmann

Managing Director · Your permanent point of contact

Send an enquiry

Tell us briefly where things are stuck. We will get back to you personally.

A short description is enough. We will work out the details together.

Guides on this topic

Answers to the questions we are asked most often before a project - in detail, to read at your own pace.

All articles