Objective vendor comparison
Units-Master vs. leikom
Regional Austria focus with solid accounting features.
Executive Summary
leikom serves the Austrian market regionally with solid accounting and banking features. Scaling, portals and AI features are minimal.
Feature comparison in detail
| Feature | ⚡ Units-Master | leikom |
|---|---|---|
| Process Ticketing | Built-in | Partial |
| Visual Workflow Engine | Built-in | Not available |
| Voice AI (Phone) | Built-in | Not available |
| In-App AI Chat | Built-in | Not available |
| In-App Team Chat | Built-in | Not available |
| Owner / Tenant Portal | In development | Partial |
| Auditor Portal | In development | Not available |
| Accounting & Reports | In development | Built-in |
| GoBD / BAO Archiving | Built-in | Built-in |
| Service Directory | Built-in | Not available |
| Banking / SEPA & EBICS | Not available | Built-in |
| WEG Voting & Assembly | Not available | Not available |
| Meter & Heating DB | Not available | Built-in |
Legend
- Built-in
- Fully part of the vendor's own product, developed and maintained in-house. No extra contract, no data sync, one support line.
- In development
- Not yet usable, but on the active engineering roadmap with a confirmed release window. Relevant for multi-month rollouts that can plan around it.
- External vendor
- Delivered by a separate vendor via integration, add-on or sync. Expect additional licence fees, a second support relationship, and data flowing across two systems.
- Partial
- The feature technically exists, but only at checkbox level: enough to tick the requirement, rarely enough to solve the underlying day-to-day workflow.
- Not available
- Not part of the product. No integration, no roadmap commitment — the workflow has to happen outside the platform.
Strengths of leikom
- Native accounting, banking and meter database
- Regional roots in Austria
- GoBD/BAO archiving
Weaknesses of leikom
- No AI layer, no voice agent
- Ticketing only basic, no workflow engine
- No auditor portal, no tradesperson directory
Operational differences
01
Process-driven workflows instead of static inboxes
Every ticket in Units-Master triggers an executable, multi-step Standard Operating Procedure (SOP) — no manual tag assignment, no ping-pong between staff members.
02
Native voice AI agent, not a third-party tool
Inbound phone calls are handled entirely by the native voice AI agent: emergency dispatch, intake and ticket creation — autonomously, 24/7.
03
In-app copilot Werner AI: contextual and action-capable
Werner AI is not a generic chatbot. It knows property history, summarises units, prepares accounting data and executes actions directly.
04
Embedded service directory, wired into workflows
The /directory connects local tradespeople, plumbers, HVAC technicians and auditors directly to the automated ticket workflows — no media breaks, no manual coordination.
When each fits
Choose Units-Master when…
- You plan cross-regional growth across DACH
- AI and automated processes are strategically relevant
Choose leikom when…
- Purely regional focus on Austria with no scaling ambition
- Basic bookkeeping is sufficient, no process automation needed
Last reviewed and updated: 15 August 2026
All information without guarantee. Feature scope may change through product updates from the vendors listed.