HEINI · Enterprise · companies & groups
Software and AI colleagues across departments.
HEINI connects its own applications with agreed integrations: from CRM, marketing and product data to purchasing, manufacturing, finance preparation, financial control and forecasts. Separate data areas, responsibilities and approvals govern collaboration.
See HEINI on your own case Explore all enterprise capabilities ↓A dedicated customer environment can include multiple sites. Separate legal entities retain separate data spaces; shared work follows agreed permissions.
- Multiple sites
- Clear permissions
- Agreed operations
HEINI in your business
Your ERP stays authoritative. Work across sites becomes reviewable.
One case connects the sites, existing systems and responsible decision makers.
One site needs stock recorded at another site.
Nothing has been sent or changed yet.
- Required contextERP stock with timestamp · site ownership · transfer rule
Stock freshness and approval from the supplying site remain open.
The transfer option and its consequences are presented together for review.
Nothing has been sent or changed yet.
Opens a draft in the existing Bar. Nothing is sent until you send it.
What HEINI takes off your desk
What HEINI takes off your desk
- 01
Required context
ERP stock with timestamp · site ownership · transfer rule
HEINI Enterprise · The full picture
One colleague. The depth of your business.
103 capabilities and work areas: from customer request to production, from product data to company knowledge.
Same idea. Two operating models.
Choose how your AI models operate. We agree the business scope and required connections together.
| Difference | Enterprise SaaS | Own server · on-prem |
|---|---|---|
| AI models | Agreed model service in the SaaS setup. | Selected own language and GenAI models on customer-owned GPU hardware. |
| AI actions | 150,000 actions per month | Agree billing and capacity in the proposal; both depend on hardware, model and task. |
| Hardware | No customer-owned GPU hardware required. | Hardware, ownership, delivery and installation are specified in the individual proposal. |
| Data routes | Standard hosting: Hetzner Falkenstein. Models, permitted data and connected services are agreed. | Local inference; HEINI is not fully local as a result. Remaining platform and service connections are agreed. |
| Responsibilities | Service scope and operation under the SaaS agreement. | Explicitly agree responsibility for hardware, models, updates and failure behaviour. |
| Roles and approvals | Sources, access and human approval apply within the agreed scope. | The same business boundaries. Owning a server does not expand permissions or approvals. |
| Costs | SaaS plan with an agreed AI action allowance; additional services by proposal. | Hardware, software, onboarding and operation are separate. Agree billing schedule and scope in the proposal. |
| Availability | Review the initial scope and specific connections together. | Server offer distributed exclusively in Germany, Austria and Switzerland. Delivery and operation by proposal. |
What HEINI can take on for you.
Open the area that matters to your business. Plan, data, connections and permissions determine the agreed scope. Pilot areas and special requirements are identified directly.
Control, colleagues and inbox10
| Capability | Preparation and outcome | Scope |
|---|---|---|
| Susi orchestrates the team | First contact, specialist hand-offs, appointment and follow-up mail — all on approval. | — |
| Per-colleague permissions | Turn each role on or off — which tasks they take and what they can see. | — |
| Shared inbox | Bring together messages from supported, authorised channels for your business. | You authorise the agreed messaging channels |
| Inbox that thinks ahead | Reads along, sorts, suggests reply and appointment — sends only with your okay. | — |
| Message-type recognition | Inquiry, order, complaint, service — Heini suggests the right next step. | — |
| “Why?” explanation | What · because · source — traceable on every suggestion. | — |
| Source labelling | Private, team, company, general — you see where every answer comes from. | — |
| Read receipts and PDFs (OCR) | Order PDFs, delivery notes, invoices — line by line, form ready for approval. | — |
| Read images (nameplate, delivery note) | Photo of a nameplate or delivery note — Heini reads and matches. | — |
| Connections with clear permission | Agree what HEINI may read and which steps it may perform after approval before connecting. | You determine data, permissions and owners |
Product data and PIM4
| Capability | Preparation and outcome | Scope |
|---|---|---|
| PIM — product data management | Structured product data, attributes, languages. | — |
| DAM light | Images and documents per product. | — |
| Import product data from PDF | Read PDF documents, spot drift and suggest corrections. | — |
| Site-separated product data | Multiple plants and locations with separate disclosures. | — |
Variants, CIM, CPQ and BOMs2
| Capability | Preparation and outcome | Scope |
|---|---|---|
| CIM — variant configurator | Review required fields, dependencies and valid product combinations together. | — |
| CPQ and bill of materials (BOM) | Configurator-based quoting, multi-level BOMs. | — |
HeiniBar in the back office and in the shop6
| Capability | Preparation and outcome | Scope |
|---|---|---|
| Back-office HeiniBar | Cmd+K, type or speak. Heini finds, asks back, queues cases for approval — visible with source and rationale. | — |
| Shop guidance with the HeiniBar | Repeat customers describe what they need — Heini finds, knows contract prices and lead times, prepares up to an order. | — |
| Live variant resolution in the browser | Buyers see right away what can be combined — not at the end of checkout. | — |
| Shop connections | Connect products and guidance to your existing shop; verify supported connections and tasks first. | Agree the shop and available tasks together |
| Prepare repeat orders | Use confirmed previous orders as a basis for a new proposal that can be reviewed. | — |
| Multiple shops, one HeiniBar logic | One customer view per shop, one HeiniBar per platform — one role matrix, one traceable history. | — |
Quotes, orders, logistics10
| Capability | Preparation and outcome | Scope |
|---|---|---|
| Quotes and orders | Inquiries, quotes, confirmations. | — |
| Inquiries from the email inbox | Sales picks up incoming mails, Heini sorts. | — |
| CRM — customer relationships | Customer file, pipeline, deals and VAT ID check — in one place. | — |
| Wholesaler availability and sourcing | Prepare availability and suitable sourcing options from a connected source for your decision. | Agree supplier source and data freshness |
| Stock levels and movements | Inventory, inbound, outbound. | — |
| Shipping prep with connectors | Shipping docs, labels, tour prep. | — |
| Supplier and purchase-order workflow | Inquiries, POs, supplier master data. | — |
| Production planning | Prepare work steps, material needs and feedback; ERP expansion from January 2027, Factory as a pilot. | ERP from January 2027 |
| 3D printing and manufacturing handover | Prepare product requirements and documentation for a connected printing system or manufacturing partner. | Agree the production partner and permitted handover |
| Site-separated order and logistics view | Multiple plants and sites. | — |
Required fields and Digital Product Passport4
| Capability | Preparation and outcome | Scope |
|---|---|---|
| Required fields simple | Standard mandatory fields per product — structured, multilingual, exportable. | — |
| DPP preparation by industry | Combine product information and sources for the relevant product passport; review legal requirements separately. | — |
| Advanced DPP / ESPR flows | Repair history, recycling concept, CO₂ trace, supply-chain data — preparation at the case, from Operations. | — |
| Multi-site / deeper proofs | Site-separated DPP view, cross-site history for leadership. | — |
Marketing and external presence15
| Capability | Preparation and outcome | Scope |
|---|---|---|
| Marketing colleague — copy, SEO, newsletter | Product copy, posts and newsletters in your voice — multilingual, channel-aware, not off the shelf. | — |
| Product copy in multiple voices | Descriptions, short and long copy, bullet lists. | — |
| Voice-register control | Consistent language per brand and channel. | — |
| Content colleague — pipeline & approval | Texts and images from draft through review to the approval folder — live only on your word. | — |
| Prepare product data for multiple channels | Prepare product information for agreed target channels. Publish only after approval and with a verified connection. | Agree target channels and available steps together |
| Prepare multiple listings together | Review listings and missing required information together; agree available publishing steps for each channel separately. | Agree accounts and available publishing steps |
| Online shop and channel feeds | Product data toward shop and marketplaces — no export-import circus. | — |
| Editorial plan and posts | Heini suggests what appears when — planned, live only on your word. | — |
| Image descriptions for findability | Alt text and image descriptions for better findability — prepared for approval. | — |
| Create and fill website pages | Spot empty pages, build a draft, write copy — the first impression, finished on approval. | — |
| Set up shop step by step | Connect, make products visible, payment — each step waits for your okay. | — |
| Page and conversion improvement suggestions | Which page gets visits but rarely converts — Heini suggests what could work better. | — |
| Prepare product videos | Short product videos on suggestion — publish on approval. | — |
| Connect external media management | Use images and documents from an authorised media source; assess the connection separately. | Provide the media source and usage rights |
| Advanced content workflows | Multi-step approvals for copy and campaigns. | — |
Pre-accounting9
| Capability | Preparation and outcome | Scope |
|---|---|---|
| Accounting preparation and DATEV handover | HEINI prepares entries for approval; you or your tax adviser post them. Review connection and export scope. | Agree export scope with your tax adviser |
| Document flow from the email inbox | Incoming invoices are picked up. | — |
| Credit notes recognised | Credit notes are recognised and matched to the right case. | — |
| Three-way matching | Invoice, purchase order and delivery note — matched before posting. | — |
| Reuse confirmed classifications | Suggest classifications confirmed by you or your tax adviser for review on similar documents. No tax advice. | — |
| Receipts, open items, reminders and discounts | Identify open items and propose reminders for approval; send only after your approval. Payments require your approval. | — |
| Foreign currencies with a rate source | Prepare amounts for review using a connected rate source and visible data timestamp. | — |
| Cash-register view (preparatory) | POS receipt processing as a prep step. | — |
| Controlling reports | Across sites and departments. | — |
Approval and traceable history9
| Capability | Preparation and outcome | Scope |
|---|---|---|
| Approval required per case | Heini prepares, the human decides — no silent background run. | — |
| Traceable history as PDF | Provide the case, sources and approvals as documentation. Compliance also depends on your procedures. | — |
| Documentation for a second review | Compile sources and change history for independent review; agree the review procedure. | — |
| Document decisions | Keep proposals, participants and approved results traceable; agree the procedure. | — |
| Federation — sites and legal entities | Connect authorised information across company boundaries for a defined purpose. Separate data spaces remain separate. | Both companies agree purpose and access |
| Service cases and complaints | Intake, routing, handling. | — |
| Quality reporting | Complaints and inspection analytics. | — |
| Legal — disclosure check | Templates, compliance view (no substitute for legal counsel). | — |
| People overview — administration | Organise employees, roles and sites administratively. Off by default; no payroll or decisions about people. | Off by default |
Authenticity, ownership and collateral10
| Capability | Preparation and outcome | Scope |
|---|---|---|
| Digital authenticity and ownership evidence | Combine provenance, product information and documented assignments. Digital evidence does not guarantee legal title. | — |
| 3D printing and evidence | Check required product and authorisation evidence before the agreed manufacturing handover. | Agree printing system and manufacturing approval |
| Document ownership assignments | Keep required information, sources and approval traceable with the product. | — |
| Document a transfer | Record documentation and approvals for an agreed transfer. Legal title transfer is resolved separately. | — |
| Ownership-record inbox | Incoming records land in the inbox — link, create new or reject. | — |
| Hold many records at once | Many machines in one case — approve once, Heini works the list. | — |
| Ownership documentation for financing | Prepare product and ownership documents for external review. No guaranteed valuation, credit offer or own financing. | External review |
| Share data with partners and marketplaces | Hand over authorised product and evidence data to agreed recipients; assess each connection and scope. | Agree supported recipients and data scope |
| Material record on recycling | At end of life: materials and secondary raw materials documented to the recycler. | — |
| Site-specific ownership evidence | Maintain evidence by site; cross-site visibility requires appropriate permissions. | — |
Company memory and knowledge2
| Capability | Preparation and outcome | Scope |
|---|---|---|
| Company memory | What matters in your company, Heini keeps in mind — private, team, company, general. | — |
| Knowledge map | Shows at a glance what Heini knows about your company — with source per entry. | — |
Leadership, predictions, Factory and private AI operation22
| Capability | Preparation and outcome | Scope |
|---|---|---|
| Team lead and supervisor | Bound tasks, delegate to specialist colleagues and present important steps for human approval. | Agree roles |
| Specialist collaboration | Keep one case connected across sales, purchasing, stock and finance. | Agree scope |
| Demand and revenue predictions | Show future demand and revenue with a data timestamp and uncertainty as planning support. | Data required |
| Cash and cost predictions | Prepare future cash needs and cost risks for review. No automatic payment. | Data required |
| TimesFM connection | Connect a provisioned TimesFM runtime for suitable time series. | Optional runtime |
| Editable reports and spreadsheets | Provide results as working files that can be edited further. | Agree format |
| Presentations and drawings | Prepare working documents for meetings and technical discussion. | Agree format |
| HEINI ERP | Connect product, BOM, purchasing, production and invoice within the agreed scope. | From January 2027 |
| Material needs and production orders | Turn configuration and BOM into a reviewable material and order proposal. | ERP from January 2027 |
| Factory and machine connections | Connect read-only machine signals to an order, material and responsible role. No machine control. | Agreed pilot |
| Shop floor and shift handover | Combine shift knowledge and open tasks with the relevant case. | Factory pilot |
| Maintenance | Compile signals and documents for agreed maintenance planning. | Factory pilot |
| Waybill and shipping dossier | Combine shipment information, accompanying documents and open questions before handover. | Agree the shipping route and required documents |
| Compare freight costs | Prepare connected freight quotes and service terms for your decision. | Agree available quote sources together |
| Guided onboarding | Set up sources, connections, roles and a first real case step by step together. | Agree onboarding |
| Introduce HEINI during operation | Start with a bounded workflow; keep existing systems in use during introduction. | Agree migration |
| ERP and Odoo connection | Retain an authoritative ERP and connect agreed data and work to HEINI. | Agree ERP, data scope and permitted steps |
| Own language and GenAI models | Select permitted models for the task and data class. | Agree model profile |
| AI inference on your own server | Run selected model calls on customer-owned GPU hardware. Platform deployment is planned separately. | Optional in DACH |
| Model operation responsibilities | Define hardware, models, updates, data routes and failure behaviour in the proposal. | Agree operation |
| AI action overview | Review usage and agreed SaaS allowance; own server without AI action billing. | By operating model |
| Permissions between legal entities | Share information for a defined purpose and limited time; make missing permissions visible. | Agree federation |
Less duplicated work
Which software can go? The task decides.
Where HEINI demonstrably covers the same required scope, individual licences, side tools and spreadsheets can become unnecessary. We assess your workflow without a blanket replacement or savings promise.
| Previously separate | HEINI covers | What stays? | Check before cancelling |
|---|---|---|---|
| Shop extensions | Connect product data, configuration, approved SEO content and product-passport references. | Store, checkout, payment provider and extensions outside the accepted scope. | Accept supported versions, mapping, orders and operating scope; retire only the extensions actually replaced. |
| CRM and sales spreadsheets | Customers, requests, quotes and next steps in one case. | Connected communication and the imported customer history. | Review existing customer history, connections and migration. |
| Separate PIM upkeep | Maintain product data, attributes and languages together. | An external PIM for specialist requirements outside the agreed scope. | Review specialist requirements and data model; external PIM can remain connected. |
| Separate CPQ and configurators | Connect valid configuration, BOM and quote preparation. | Specialist engineering calculations and retained configurators. | Accept rules, variants and technical calculations on the product. |
| Basic media and document repositories | Keep images and documents with the product and case. | Specialist DAM, media licences and large archives. | Assess specialist DAM, media rights and large archives separately. |
| Feed and listing side tools | Prepare product data for agreed shops and channels. | Shop, marketplace and their ongoing channel fees. | Review supported channels and their publishing steps. |
| Separate chat and knowledge tools | Handle questions and work requests with sources in company context. | Agreed models, operation and required external knowledge sources. | Agree model, privacy, permissions and required tasks. |
| Content and editorial side tools | Prepare copy, posts and newsletters for approval. | Delivery service, consent records and publishing channels. | Review delivery, consent and publishing connections. |
| Excel trackers and handover sheets | Keep requests, responsibilities, material needs and the next open step together. | Specialist calculations and reports outside the accepted scope. | Assess specialist calculations and existing reports individually. |
| Individual workflow automations | Guide agreed handovers between departments and make them traceable. | External automations and system connections still needed. | Replace external automations only after connection review and business acceptance. |
| SEO tools | Prepare search-oriented website copy and metadata for editorial review. | External ranking and backlink data, Search Console and specialist audits where needed. | Compare required analytics and data functions individually; copy generation does not replace a ranking-data provider. |
| Standalone DPP tools | Bring together product data, provenance and approved evidence for a digital product passport. | Legal review, industry-specific standards and required external evidence. | Accept data coverage, export, updates and applicable requirements. A product passport does not guarantee legal compliance. |
Your authoritative ERP, shop, accounting/tax-adviser system and specialist software can remain connected. HEINI ERP is planned from January 2027; replacing an ERP is a separate migration project. Payroll, legal advice and specialist CAD or machine control are not promised as replacements here.
What could work together in your business?
We take one case, your existing software and the outcome you want. Then we establish what HEINI takes on and what stays.
Arrange an enterprise meeting ↗Work continues beyond the first draft
The next step is part of the job.
Illustrative workflows within your agreed scope. Sources, ownership and your decision stay with the case.
Purchasing through invoice review
Material missing → compare sources → approve purchase order → confirm receipt → match invoice.
You choose supplier and approve the order. A draft is not a purchase.
Explore the related work area →Shipping through delivery evidence
Shipment details → shipping dossier → approved label → carrier update.
A dossier does not book transport. A label does not confirm delivery. Agree the available shipping route together.
Explore the related work area →Returns through refund
Find the original order → review return → confirm receipt and stock → review credit note → approve refund separately.
Each step needs confirmation. A return status alone does not change stock or a bank balance.
Explore the related work area →Structured documents and EDI
Receive orders, delivery documents and invoices in agreed data formats → match details → resolve discrepancies.
E-invoice data and EDI are more than reading PDFs. Agree format, trading partner and supported transfer route first.
Explore the related work area →Appointments and ownership
Assign the message → identify the owner → prepare an appointment or follow-up → confirm changes.
Your business calendar is separate from this website’s demo booking. Calendar access and permitted steps are agreed.
Explore the related work area →Product and evidence across its lifecycle
Match product and sources → record approved changes → keep evidence for use, transfer or recycling together.
A product passport supports traceability. It does not guarantee legal title, finance or general compliance.
Explore the related work area →Customer service · an illustrative B2B example
Your customer asks. Your team need not start over.
The request, product knowledge and responsible people belong together. The answer starts with what is already known.
The customer asks.
“Which seal kit fits the pump you delivered?” The request and the relevant order provide the starting point.
Use the right customer information.
The responsible team uses only the permitted order and product information in this customer context. Missing details require a follow-up question.
Prepare the answer.
Relevant facts, open questions and ownership come together. The team reviews the proposed answer before making a commitment.
A person sends it.
The responsible person checks the recipient and content and sends through the agreed channel. A credit note or refund would be a separate decision.
Keep the reply with the case.
The confirmed customer reply helps establish whether the issue is resolved. Any proposed addition to company knowledge is reviewed and approved separately.
Three contexts. Clear boundaries.
- HEINI supports its customers.
- A problem with HEINI belongs with HEINI support. The case is classified and directed to the responsible team.
- The agency supports customer service.
- End-customer requests are handled within the agreed company context of the agency’s client. Data, sender account and responsibility stay tied to that context.
- Support access needs permission.
- Access is granted for a specific case, purpose and limited period. It does not grant general access or permission to make arbitrary changes.
Explore the workflow and further possibilities
How the work moves forward
From a first case to a suitable rollout
One case connects the sites, existing systems and responsible decision makers.
- 01
Start with one case
Choose a recurring workflow and check sources, roles and connections.
- 02
Clarify responsibility
Sites and companies receive the required access. Approvals remain traceable.
- 03
Assess the result in practice
Once the first workflow is accepted, expand in agreed steps.
What is already included
Operations that fit your organisation
01Your existing systems
An existing ERP can remain authoritative. For a new core, consider HEINI ERP from January 2027 or Odoo.
02Your own AI server · exclusive DACH distribution
Enquire now: run your own language and GenAI models on a GPU server at your premises, connected to HEINI. Scope and operations are agreed individually.
Explore your own AI server↗03Operational responsibility
Access, support, service scope and failure behaviour are specified in the proposal. Owning a model server does not automatically replace hosting for the HEINI platform.
Trust · human decision
Clear boundaries.
Standard hosting in Falkenstein, a dedicated customer environment and multiple sites as required. For an own AI server, data paths, models and operations are explicitly agreed.
- Dedicated customer environment
- Human approval
- Traceable history
- Still to clarify
- Stock freshness and approval from the supplying site remain open.
- Prepared for review
- The transfer option and its consequences are presented together for review.
FAQ
Questions about an enterprise start
Which software does HEINI bring with it?
HEINI brings its own applications for customer management, product data, configuration and multi-level parts lists. AI colleagues use them to prepare work across sales, marketing, purchasing, manufacturing, accounting preparation, financial control and forecasts. Plan, data, connections and approvals define the agreed scope.
Can partners see all company data?
No. Each company keeps its own data area. Information is shared only as approved for the task, purpose and period. Agencies and operators work under an explicit client mandate; Super HEINI does not automatically extend it to other client data.
Do I save software costs or working time?
Both are possible and reviewed separately. A bill disappears only after an actual cancellation. Recurring savings = total costs today minus total costs with HEINI. Account for setup, migration and parallel operation separately. Less searching, retyping and chasing creates time for customers; freed time is not an automatic cash saving.
Does each site need a separate environment?
No. A company can manage multiple sites in its customer environment. Separate entities and data spaces are connected according to responsibility and agreed access.
What is included?
The enterprise proposal defines functionality, integrations, migration, permissions and service. Hardware and additional services are explicitly itemised.
Can I use my own AI model?
Yes, a GPU server running agreed language or GenAI models can be connected to HEINI. HEINI distributes this server offer exclusively in Germany, Austria and Switzerland.
Your business. Your case.
Let’s start with your context.
30 minutes for goals, existing systems and a useful first use case.