Expert knowledge for digital decisions
What can your product not do – what would you advise against?
Short answer
What is not offered here
| Area | Reason |
|---|---|
| Approved medical products | Conformity assessment according to Regulation (EU) 2017/745 with a notified body, QM according to ISO 13485 – a separate operational mode, not an add-on module |
| Cash register systems | § 146a AO requires a certified technical security device; additionally, there is a notification obligation to the tax office according to § 146a Abs. 4 AO |
| Payment services | Anyone providing payment services commercially needs permission from BaFin (§ 10 ZAG) |
| Financial accounting, payroll | There are mature standard software solutions for this; a replication would be worse and more expensive |
| High-risk AI according to Annex III of the AI Regulation | Conformity assessment, risk management, and registration, obligations from August 2, 2026 |
This is not a convenience. In each of these fields, success is not determined by programming, but by an approval or supervisory procedure.
What is advised against, although it would be feasible
Replicating good standard software. Accounting, word processing, payroll, video conferencing. Anyone building anew here pays for ten years of product development of others again – and gets less.
Projects without a decision-making contact person. The biggest cost factor in software projects is waiting for decisions, not programming hours.
Migration without prior data cleansing. Duplicates and half-empty records do not improve through the move, only become more visible – and more expensive.
"Everything at once." A project whose first usable version only comes after many months loses user feedback along the way. Without this feedback, development occurs in the wrong areas.
Projects below a sensible minimum size. With very small budgets, the costs of concept, coordination, testing, and handover exceed the benefits. The threshold here: no minimum amount – we review every inquiry.
Limits of our products
Ouhud CRM covers customer, offer, and sales processes. It is not a substitute for the forecasting, territory, and commission mechanics of large corporate sales. Anyone wanting to depict a multi-tier international sales organization with deep forecasting logic is better served with an established product.
Ouhud E-Invoice generates and receives invoices according to EN 16931. It is not accounting and does not replace chart of accounts or tax advisors. The timeline is dictated by law: obligation to receive since January 1, 2025, obligation to send from January 1, 2027, for companies with more than 800,000 euros in previous year's revenue, from January 1, 2028, for all (§ 27 Abs. 38 UStG).
Ouhud QR manages dynamic QR codes with evaluation. It is not a marketing suite and does not replace a web analytics tool.
HealthFusion is a research and development project without approval. It is not a medical product and is not offered as a diagnostic or therapeutic system.
What speaks against a young provider
Ouhud GmbH was founded in 2025. This leads to three points that a customer should know before making a decision:
- No long certification history. Tenders requiring ISO 27001 or multiple comparable references from the last five years formally exclude a company of this age. This cannot be argued away.
- Small teams have a failure risk factor. Anyone becoming dependent on this should contractually secure source code deposit, complete documentation, and a right to data export in an open format – with every service provider, not just this one.
- No 24/7 operation on its own. Anyone needing on-call availability around the clock must explicitly agree to this and pay for it; a standard maintenance contract does not cover this.
When a standard solution is the better choice
When the process is industry-standard, when there are several mature products available, and when no competitive advantage depends on how exactly the process looks. Custom development is worthwhile where a process is essential for the business and standard software only represents it with detours – not because a custom solution would be nicer.
Key facts
- Legal basis
- Electronic recording systems require a certified technical security device according to § 146a AO; § 146a Abs. 4 AO additionally requires notification to the tax office.
- Legal basis
- The commercial provision of payment services requires permission from BaFin according to § 10 ZAG.
- Legal basis
- Approved medical products require a conformity procedure according to Regulation (EU) 2017/745; HealthFusion has not undergone such a procedure.
- Legal basis
- The e-invoice sending obligation applies from January 1, 2027, for companies with over 800,000 euros in previous year's revenue and from January 1, 2028, for all (§ 27 Abs. 38 UStG).
- Legal basis
- The obligations for high-risk AI systems according to Annex III of the AI Regulation (EU) 2024/1689 apply from August 2, 2026.
Sources
All external claims are backed by traceable sources.-
01
§ 146a AO – Ordnungsvorschrift für elektronische Aufzeichnungssysteme Bundesministerium der Justiz
-
02
§ 10 ZAG – Erlaubnis für das Erbringen von Zahlungsdiensten Bundesministerium der Justiz
-
03
§ 27 Abs. 38 UStG – Übergangsregelung zur E-Rechnung Bundesministerium der Justiz
- 04
- 05