Lexware D!VE Offers
An IT service partner of Deutsche Telekom used Lexware as their order and quotation system, but Telekom required every quotation to reach its systems in a specific format — D!VE XML, the data…
View Case Study →Backend systems, data models, desktop tools — and the business logic that makes them yours
Software that fits the way your business actually works.
We design and build software around your processes, not the other way around. Backend systems, data architecture, desktop and server applications, and the business rules that make them yours, on a Microsoft stack proven in mid-market and enterprise environments. Built to be run for a decade by whoever comes after us, not demoed once.
Off-the-shelf fits until your business does something it was not built for.
Generic platforms are the right answer for generic problems. The trouble starts where your business is specific: a regulatory label format the product does not know, an order system that has to speak a partner's data model, a catalogue too large for a plugin architecture to carry, a group structure with more legal entities than the licence allows. Then every workaround adds friction, every integration is a compromise, and the software you rely on quietly works against you.
Custom software is not a bigger, more expensive version of that. It is software written for your specific situation, from the data model up, with the hard parts of your business encoded once, correctly, and then enforced by the system instead of by people remembering.
What we build.
Typically .NET, C# and SQL Server, hosted where your data has to live: Azure, a private cloud, or a server in your own building. We choose the stack for the problem, not the other way round.
- Backend systems and business logic tailored to your processes: order handling, multi-entity finance, traceability, approvals, whatever your operation actually runs on
- Data architecture and modelling: the schema, the identifiers, the batch, lot and serial tracking that later reporting, compliance and integrations all depend on
- Line-of-business platforms such as multi-tenant ERP modules that go live one module at a time, with production running throughout
- Windows desktop and server applications where the job sits on a PC, a printer or a machine, not in a browser — labelling systems, format converters, operator tools
- REST APIs and integration points built to be documented and reused, so the system connects to what you already run and to what comes next
- Regulatory correctness by design: UDI and CE labelling, audit trails, role and approval models that produce the evidence an auditor asks for as a by-product of normal use
- Hosting and infrastructure choice made with you, on Azure, a private German cloud or on-premises, with the deployment pipeline set up from the first release
- Documentation, handover and long-term maintenance, so the system stays maintainable by people who never met us
Why exbisoft.
Written for your situation, not adapted from a template.
For an ISO 13485-certified medical device manufacturer we built a labelling system that generates UDI-compliant CE labels, warehouse bin labels and item labels from the Excel data they already maintain, prints straight to their label printers, and enforces the mandatory fields so a non-compliant label cannot be produced. No shop-floor tool does that out of the box; it had to be written.
The hard part of the business, encoded once.
A group of medical products companies runs a multi-tenant ERP we built on .NET and SQL Server: several legal entities, countries and currencies on one codebase, with batch, lot and serial traceability in every transaction. The modules went live one at a time while the earlier ones stayed in production.
Sometimes the answer is a small, exact tool.
An IT partner of a large telecoms provider needed quotations from their Lexware system in the provider's D!VE XML format. We built a Windows desktop application that converts them directly. Not every custom system is large; the point is that it fits exactly, and that we kept it fitting as the format evolved.
One team, start to finish.
The engineers who design your data model are the ones who build, deploy and support the system. There is no handoff between an architecture team and a delivery team, and the decisions made in week one are still explainable in year five.
Built to be maintained.
Clean architecture, documented code and a repeatable release path, so whoever inherits the system after us can actually work with it. Several of the systems we built are past their tenth year in production, still with us, still changing as the business does.
Have a system in mind?
Tell us what your business needs to run on and where the standard products stopped fitting. We will tell you honestly what it takes to build it, and whether building it is the right call.
Start a conversation