d.velop extension · Software development from Munich
Your d.velop can do more than file
d.velop reliably archives whatever you put into it. What happens to a document afterwards is usually still manual work. We build the AI-driven extension that automates that second step – directly inside your d.velop instance, in production.
d.velop standard
+ Codesymmetric extension
d.velop knows where a document lives. Our extension decides what happens next.
d.velop itself partners with AI vendors for generic document processing in its app store. We don’t build an app-store template – we build an extension with decision logic written for your actual process, wired into the systems next to it.
You get an honest assessment, even if it says: this isn’t worth it.
Data protection first: the AI runs in an EU data centre – and entirely on local hardware at your site when needed.
Progress Software partner since 2019 (NASDAQ: PRGS). d.velop extensions in production at a Munich property management company.
Use cases
What we automate in and around d.velop
Five patterns that come up whenever a document lands in d.velop and still triggers work afterwards.
Understanding
Understanding documents, not just filing them
An AI model reads what a document is actually about, even when badly scanned, and triggers the matching next step instead of just assigning metadata.
Reconciliation
Checking bank statements against the archive
Instead of looking up every account balance in the DMS by hand, the system searches the d.velop archive itself and only reports what doesn’t match.
Deadlines
Linking contracts and powers of attorney to deadlines
Contract numbers, terms and references to powers of attorney are recognised and linked to the right file automatically, instead of being searched for later.
Approval
Pre-sorting approval steps
The clear-cut part keeps moving through d.velop, the unusual part lands on a person’s desk with a reason attached – instead of treating every item the same.
Integration
Connecting d.velop to your own software
Connections to your ERP, property or line-of-business systems and custom databases that don’t exist out of the box, because your process isn’t a standard case.
Approach
Four steps, in this order
Each step decides whether the next one is worth doing at all – which is why you can walk away after two of them.
01
1 day · free
Process screening
We look at how documents currently move through your d.velop instance and work out where an extension pays off. You get an honest assessment, even if it says: this isn’t worth it.
02
1–2 weeks
Feasibility & interface check
We check your d.velop configuration, API access and the systems next to it. You get a solid statement on effect and cost before development starts, not after.
03
4–6 weeks
Prototype on the real process
The prototype runs on your real documents, alongside your existing d.velop instance. You see the accuracy before anything goes live.
04
ongoing
Production
Integration into your d.velop instance and the systems next to it, with monitoring, an escalation path and tests. The source code is yours.
↑ Exit points after 01 and after 02.
Difference
Why a software house, not an app-store plugin
Generic AI add-ins from the d.velop marketplace solve standard cases. A process that runs through several systems needs an extension someone actually operates and stands behind.
Built for your process, not everyone’s
No app-store template. The decision logic is written for your documents and your systems.
Inside your d.velop instance
Your archive, your workflows, your tagging stay in place. We build an extension that fits in, rather than rebuilding everything around it.
One team for the model and the software
ML engineers, backend developers and database architects from one house. No gap between the model and the production system.
Traceable, not just impressive
Every decision is logged with a confidence score and a reason, with a defined path for a human to step in.
EU data centre or fully local
An EU data centre is the default. If your documents can’t leave the building at all, the models run on your own hardware.
Proven
What came out of it
casavi
Automatic ticket creation
AI reads the inbox and creates tickets, instead of someone opening every email.
Munich property management company
Audit
Annual statements
Rule-based checks plus AI review, before a statement reaches the owner.
German billing services provider
9×
Response time & throughput
Performance audit of an existing web application.
Medical Protection · Medicine & insurance
R&S
Project management platform
Domain-driven design, full test coverage, performance across every layer.
Rohde & Schwarz · Electric engineering
Questions
What you probably want to ask
Do our documents have to leave our own infrastructure?
Only as far as necessary. The models run in an EU data centre; if documents must not leave your building at all, everything runs on hardware on your premises – a standard deployment option for us, not a special case.
Does this work with our d.velop version, cloud or on-premises?
The extension builds on d.velop’s existing interfaces, regardless of whether you run cloud or on-premises. We check which API paths are available in step 02, before any development cost is incurred.
Do we need the d.velop app store for this?
No. App-store add-ins are built for generic standard cases. We build a standalone extension that works against your d.velop instance and the systems around it, independent of what the app store offers.
What happens to our existing d.velop workflows?
They stay in place. The extension sits before or alongside your workflows instead of replacing them – it supplies the pre-decision or extra information your workflow then continues with.
Let’s look at what’s really happening in your d.velop instance
One day, free, no obligation. At the end you’ll know whether an extension is worth it for you – and if not, we’ll say so.