Illustrative scenario

German SME: a CRM that finally talks to accounting

A German Mittelstand supplier usually has excellent products, loyal customers and a sales process that lives in Outlook folders, Word quotes and one very important Excel file. This scenario shows how such a company could move to a custom CRM that is connected to its accounting, its Steuerberater's DATEV workflow and its support inbox — with GDPR and works-council expectations built in from the start.

Illustrative scenario (anonymised)

Manufacturing & industrial supply (Germany)

A mid-sized industrial components supplier in southern Germany with field and inside sales, invoicing in lexoffice, a Steuerberater working with DATEV exports, and a sales pipeline that lives in Outlook folders and one Excel file.

Everyone knows the customer; nobody can see the pipeline

The company supplies machined components to industrial customers across Germany and neighbouring countries. Two field sales staff and an inside sales team handle enquiries by email, write quotes in Word from an old template, and log the status in a shared Excel file that is honest only on the day it was last updated. Invoicing runs in lexoffice; the Steuerberater receives DATEV exports monthly. Support requests arrive in a shared mailbox and are forwarded by hand.

Quotes go unfollowed because nobody owns the reminder. The same customer is contacted twice with different prices. Management asks for a pipeline figure and receives a spreadsheet that three people disagree with. When a sales colleague is on holiday, their customers wait. Data-protection questions from customers are answered by searching mailboxes.

Interactive demonstration

Before

  • Enquiries handled from personal Outlook folders
  • Quotes written in Word from an old template
  • Pipeline status kept in one shared Excel file
  • Invoices typed into lexoffice from the quote
  • Support requests forwarded by hand from a shared mailbox

After

  • One customer record with sites, contacts, articles and opportunities
  • Quotes generated from the CRM; follow-ups scheduled by n8n
  • Pipeline dashboard read by management and sales alike
  • Won deals create lexoffice invoice drafts; payment status flows back
  • Support emails become tickets linked to the account

Implementation process

  1. Audit

    Trace an enquiry to a paid invoice

    We follow several enquiries through Outlook, Word, Excel and lexoffice, list every hand-off and agree the scope with sales, accounting and the works council.

  2. Design

    Data model, GDPR fields and integration map

    Accounts, sites, contacts, opportunities and consent fields are designed; the map of lexoffice, DATEV export and mailbox integrations is reviewed as clickable prototypes.

  3. Build

    CRM core, then quotes and n8n, then integrations

    The CRM core goes live first, quote generation and follow-up automation follow, then the lexoffice and support-inbox integrations.

  4. Migrate & train

    Import from Excel and mailboxes, training in German

    Customers, open opportunities and recent activities are cleaned and imported; sales and accounting are trained on their own screens in German.

  5. Go-live & improve

    Parallel run, switch, quarterly review

    The CRM runs alongside the Excel file for a short period, then replaces it; quarterly reviews add reports and refine the automations.

This is an illustrative, anonymised scenario composed from typical situations in this kind of business — not a published client result.

What AutoProbaho builds

  • Custom CRM with accounts, contacts and opportunities

    One record per customer with sites, contacts, machines or articles supplied, open opportunities and their stages, activities and documents — accessible by role, hosted on infrastructure in the EU that the company controls.

  • Quote generation and follow-up automation

    Quotes are generated from the CRM with the current price list and article data, sent as PDF, and n8n schedules follow-up reminders and status changes so no quote goes silent.

  • Integration with lexoffice, DATEV export and the support inbox

    Won opportunities create the invoice draft in lexoffice via API, payment status flows back to the CRM, the DATEV export for the Steuerberater keeps working unchanged, and support emails become tickets linked to the account.

  • GDPR-conscious design and management reporting

    Consent and retention fields per contact, deletion and export routines, activity logging agreed with the works council, and a pipeline dashboard for management that replaces the Excel debate.

Expected business outcomes

  • One pipeline that management and sales agree on

    Opportunities, stages and values are read from the same record rather than from a spreadsheet.

  • No quote without a follow-up

    Reminders and status changes are automated; people spend their time on the conversation, not the calendar.

  • Accounting sees sales, sales sees payments

    Won deals become invoices without re-typing, and payment status is visible to the account owner.

  • Data-protection questions answered from the system

    Consent, retention and deletion are handled by routine, not by mailbox search.

Frequently asked questions

In this scenario the company wants its customer data on infrastructure it controls in the EU, a data model built around sites and supplied articles, no per-user licence for occasional users such as service technicians, and integrations with lexoffice and DATEV that behave exactly as its Steuerberater expects. Where a SaaS CRM fits, we say so in the audit.

Is your pipeline an Excel file that only one person trusts?

Book a free consultation. We will trace one enquiry from first email to paid invoice through your current tools and tell you honestly which link to fix first.