Your ERP does 80%.
You compete in the other 20%.

No. Most of our clients haven't. That's exactly why our process exists, to guide companies whose expertise is in their product, not in software development. You don't need a technical team or a software background. You need people who understand your daily operations and can describe what's not working. We handle the rest.

Discovery exists specifically so you never have to guess what's next. Every phase has a defined deliverable, a fixed timeline, and a clear decision point where you choose whether to continue.

That's the first thing we figure out together. During Discovery, we map your actual workflows against what your current systems can do. Sometimes the answer is configuration, not custom code. If that's the case, we'll tell you, and you'll have spent 1–2 days getting clarity instead of six months building something unnecessary.

Custom solution makes sense when your business process is your competitive advantage and no off-the-shelf tool models it accurately. If your team is working around your ERP rather than with it, that's usually the signal.

ERP customization means modifying a system within its own constraints, you're limited by what the platform allows and every upgrade can break your changes. Custom software is an independent layer built specifically for your process. It connects to your ERP via APIs, reads and writes data in real time, but isn't dependent on or limited by the ERP's architecture.

The practical difference: ERP customization is faster for simple changes but becomes expensive and fragile at scale. Custom software is more flexible, fully owned by you, and survives ERP upgrades without rework.

It depends on complexity, but here's a general range for a typical mid-market integration project: Discovery takes 1–2 days on-site. The Proof of Concept typically runs 2–4 weeks. MVP development takes 6–10 weeks. Alpha refinement is another 4–6 weeks. And final V1.0 production launch takes 2–4 weeks. Total: typically 4–6 months from Discovery to production.

These are working estimates. Discovery gives you the actual timeline — specific to your systems, your complexity, and your team's availability.

We come to your site for 1–2 days. We sit with the people who actually use your systems, not just management, but operators, sales staff, warehouse teams, whoever touches the process. We observe workflows, we map the equipment that you are using and the software, including all the plugins and tools. We ask questions, and document gaps between what your software does and what your business actually needs.

You don't need to prepare technical documentation. You need to make the right people available for couple of hours per day. The ones who know the workarounds, the frustrations, and the "we've always done it this way" processes. They're our most valuable source. You walk away with a Discovery Report that includes scope definition, architecture recommendation, realistic timeline, and a fixed-price proposal for the next phase.

Any system with an API or a database we can connect to. In practice, for DACH-region companies, this most commonly means SAP (S/4HANA, ECC, Business One), Microsoft Dynamics, Sage, proALPHA, and abas for ERP systems. For CRM: Salesforce, HubSpot, Microsoft Dynamics 365, and Pipedrive. We also integrate with warehouse management, MES, document management, BI tools, and proprietary legacy applications.

If your system is older and doesn't have a modern API, that's not a disqualifier. We've integrated with legacy systems that predate the internet. We assess feasibility during the Proof of Concept - before you've committed significant budget.

Your team logs in once, using their existing company credentials (Active Directory, Azure AD, Google Workspace, or any SAML/OAuth2 identity provider). From there, they access the custom solution and all connected systems without additional logins. For the end user, it feels like one system. Behind the scenes, the software authenticates against each connected platform securely and in real time.

Your choice. We build for both. Many DACH-region clients prefer on-premise or private cloud hosting for data sovereignty and compliance reasons — and we fully support that. The software runs on your infrastructure, under your control. No data leaves your environment unless you explicitly want it to. No dependency on our servers. If you prefer cloud hosting, we deploy on your chosen provider (AWS, Azure, or any EU-based cloud).

Data sovereignty is an architectural decision we make on day one. The software is designed to be GDPR-native and NIS2-ready: data stays within your defined infrastructure boundaries, all integrations use encrypted connections, access controls and audit logging are built in from the start. No external dependencies that create compliance exposure. Full documentation for your compliance and IT security teams.

We're technology-agnostic — we choose the stack that fits your environment, your team's capabilities, and the problem being solved. For typical integration solutions, we commonly work with .NET, Java, Node.js, or Python on the backend; React, Angular, or Vue.js on the frontend; REST APIs, GraphQL, SOAP, and message queues for integration; Docker, Kubernetes, and CI/CD for infrastructure. Technology decisions are made during Discovery and documented transparently.

Because the custom solution connects to your ERP via APIs rather than modifying the ERP internally, it's largely independent of ERP upgrades. When your ERP version changes, we update the integration layer — not the entire application. If you're planning a full ERP replacement (e.g., migrating from SAP ECC to S/4HANA), we can design the custom solution to be ERP-agnostic from the start, so the transition requires minimal rework.

Every phase has a fixed price and a defined deliverable. You pay when the deliverable is completed and accepted — not before. No hourly billing. No timesheets. No invoices for "work in progress." Discovery has a fixed price, paid upon delivery of the Discovery Report. The Proof of Concept has a fixed price, paid upon successful technical validation. And so on through MVP, Alpha, and V1.0. If we don't deliver what was agreed, you don't pay.

Yes. Every phase is designed to be independently valuable. You can stop after Discovery and walk away with a comprehensive report. You can stop after the Proof of Concept and have validated whether the integration is technically feasible. At any exit point, you own everything we've built: code, documentation, architecture decisions, all of it. There is no lock-in. There is no penalty for stopping.

They happen in every project. The question is whether you have a process for them. Our approach: any scope change goes through a structured evaluation. We assess impact on timeline and cost, present you with options, and you decide. No change is implemented without your explicit approval. The Discovery phase and MVP testing significantly reduce surprise scope changes because we validate assumptions early.

You have three options: We maintain it with an ongoing support agreement and defined SLAs. Your team maintains it, we hand over fully documented code and provide training. Or a hybrid approach where your team handles day-to-day and we handle complex changes. The software is built to be maintainable by any competent development team, not just us. You're never locked into working with us. You choose to because it makes sense.

You can. But consider: hiring experienced integration engineers in the DACH region takes 4–6 months. Onboarding and aligning them takes another 3. You're looking at nearly a year before a single line of production code is written, and you'll be managing a software team, which is not your core competency. We bring a team that's already built this type of solution more than a decade, with established processes and proven architecture patterns. You get to production faster, at lower risk, without permanently increasing your headcount.

Five things: Pay-on-delivery pricing, you pay for delivered milestones, not hours. Discovery-first process: we invest 1–2 days understanding your business before proposing anything, which kills 30–40% of initial assumptions that would have become expensive mistakes. Team continuity: under 5% of critical personel turnover; the engineer who starts your project finishes it. Data sovereignty by default: on-premise, GDPR-native, NIS2-ready. And domain expertise — we understand product companies, ERP integrations, and how to speak to your end customers. We don't need six weeks to learn your industry.

Our primary market is the DACH region and Western Europe. We work in English and German and our delivery teams operate in Central European time zones. If you're based elsewhere but your requirements align with our expertise, we're open to the conversation.

A 30-minute conversation. No pitch. No slides. We ask about your current systems, your pain points, and what you're trying to achieve. You ask us anything. By the end, we'll both know whether this is worth exploring further — and if it is, we'll propose Discovery as the next step.

That's exactly what Discovery is for. It's a low-commitment, fixed-price engagement designed to give you clarity. You'll know what's possible, what it costs, and what the timeline looks like — whether you move forward with us or not. The worst-case outcome of Discovery is that you have a professional assessment of your systems and a clear recommendation. Most clients find that valuable regardless of what they decide next.