TreeSolid Systems GmbH TreeSolid Systems GmbH · Oberkrämer, Germany
A hand pinning a large process sheet to a workshop wall

FAQ · TreeSolid Systems GmbH

Questions buyers ask before projects begin

Processes drawn true, then built to run.

This page answers the questions German businesses ask most often before starting a software or automation project with TreeSolid Systems GmbH. The answers are short because the detail lives on the services, automation, consulting, and approach pages. If your question is not covered, send it to [email protected]. We would rather answer a specific question than publish a generic one.

Ask a question Read the answers

Am Siebgraben 14, 16727 Oberkrämer · Monday to Friday, 9:00 AM – 6:00 PM

The work in one line

What does TreeSolid Systems GmbH do?

We develop custom software and digital applications, automate business processes, connect existing systems, and provide IT consulting. The company is based at Am Siebgraben 14, 16727 Oberkrämer, Germany. Most projects combine two or three of those areas. A typical engagement starts with process modelling and ends with training and launch support. The aim is software your team can run in daily operations.

Terms, in plain words

What is the difference between RPA, workflow automation, and process orchestration?

Workflow automation controls tasks, approvals, and handoffs between people. RPA automates actions on screens, such as copying data into a legacy application. Process orchestration coordinates several systems and people as one end-to-end flow, with state kept at each step. The three approaches often appear in one project. The choice depends on the systems involved and the stability of the process.

Where to start

Which business processes are best suited for automation first?

Processes that are frequent, rule-based, and visible are the best first candidates. Invoice intake, customer onboarding, standard reporting, and address or master data changes fit that description in many firms. Clear inputs and outputs make testing straightforward. A narrow first project finishes faster and builds trust. Wider automation can follow once the team knows the method.

Hands tracing a workflow sheet on an oak bench

Evidence, not decoration

Modelling comes before building. When inputs, approvals, and handoffs are drawn and confirmed by the people who run them, the later automation work has something solid to test against — and you can see in the photograph above where that work happens: on paper first, at the bench, before any tool is chosen.

How do companies connect automation tools to ERP and CRM systems?

Connections use APIs, events, or controlled file exchange, depending on what each system supports. Master data rules decide which system owns a value when records conflict. Validation, duplicate handling, and error logging are defined per interface. Monitoring shows failures before users notice them. Our integration work covers the design, build, and documentation of those connections.

When is low-code enough, and when is custom software better?

Low-code is enough for contained internal tools, approval flows, and departmental apps, especially in Microsoft 365 environments. Custom software is better for complex logic, high volumes, strict performance needs, or long service lives. The comparison should include licence costs and maintenance skills, not only build time. We help clients draw that line during consulting, before a platform is chosen.

How do AI agents fit into enterprise process automation?

AI can read documents, classify messages, and draft text inside a defined flow. Agents that change records need limits, human approval, and logging of each decision. Data protection and accuracy checks belong in the design from the start. AI layered on an unclear process produces faster confusion. Our advice starts with process and data readiness, then considers models.

The workshop bench in low north light

What does a good automation consulting engagement include?

It includes needs analysis, a status-quo assessment, BPMN process modelling, tool and architecture comparison, interface planning, and an implementation roadmap. Testing, training, and launch support are planned as part of delivery. Each phase produces a document or a working result. That structure protects the client from buying a tool before understanding the process.

You can stop after the analysis. Consulting and modelling are priced separately from build work, so the decision to build is made with the model, the interface plan, and the effort in front of you — not before.

Documented phases, working results

A consultant testing a workflow on a laptop at the bench

Testing before sign-off, at the bench

Explore services Read our approach

Can you work with our existing systems?

Yes. We connect to ERP, CRM, accounting, and specialist systems through APIs or file exchange. Legacy systems without interfaces can be wrapped or bridged, including with RPA where that is the practical route. We do not require a system replacement to start. Modernisation, when needed, is planned in stages.

How long does a typical project take?

A focused automation or integration project often runs for a few months, depending on scope and the number of systems involved. Discovery and modelling usually take weeks, not days, because users must confirm the model. Larger programmes with several processes take longer and are released in phases. We give a timeframe after the assessment, with the assumptions stated. Estimates without an assessment are not worth much.

What does a project cost?

Cost depends on scope, systems, and the amount of custom logic. Consulting and modelling are priced separately from build work, so clients can stop after the analysis. We present options with effort and operating implications before asking for a decision. There are no licence bundles or hidden platform fees in our quote. The business case should be visible in operational terms: time saved, errors avoided, or capacity released.

The short version

Processes drawn true, then built to run.

Send a short description of your process, your systems, and the problem you want to solve. Use the contact page or write to [email protected]. We reply with focused questions and a proposal for a first assessment. No commitment is needed at that stage. The conversation should end with a clear next step, whichever direction you choose.

Contact us

TreeSolid Systems GmbH · Am Siebgraben 14, 16727 Oberkrämer · +49 33054 49763

Close crop of the traced enamel lane on the process sheet
The lane, traced by hand before it is built