Systems that have never been connected to each other. We connect them.
We build the software your systems are missing: custom modules, integrations, and the middleware that keeps their data consistent. We start by mapping what you already run.
The map before the code.
Most integration projects fail before a line of code is written, because nobody agreed on what the landscape actually looks like. So we always start with the map.
See what you actually run
We map the systems and the integrations between them, then hand you the picture and a prioritised list of what to fix first.
- Systems and interfaces mapping
- Findings and risk register
- Prioritised improvement plan
Decide once, written down
Target architecture, data ownership and system boundaries, drawn as flowcharts and specified interface by interface.
- Target architecture document
- Interface specifications
- Phased roadmap
Develop the missing parts
Custom modules, middleware and integrations, written to be handed over: documented, tested, and readable by whoever maintains them next.
- Modules and extensions
- Integrations and middleware
- Handover and documentation
Six systems wired to each other is up to fifteen interfaces.
Route them through one agreed contract and it is six. Finding that shape means knowing what you actually have, and nobody has mapped it.
Every stage stands on its own.
A short first step, and something useful in your hands within weeks.
Conversation
One call. What you run, what hurts, what you have already tried. It is also where we size the work, because the price follows the size of your systems.
Systems mapping
Two to four weeks. We map your systems and interfaces, then hand over the findings and the fix list.
Architecture and specification
The target design as flowcharts, with the trade-offs written down. Hand it to us or to anyone else.
Development and handover
Delivery in phases, each one shippable. Documentation is part of the scope, not an invoice at the end.
Three ways to start.
Nothing here has a list price. What the work costs follows the size of your systems, and the first call is where we find that out.
Systems Mapping
The map of your landscape, the risks in it, and a prioritised plan. Yours whether we build the next step or someone else does.
Development Project
Custom development with the outcome agreed up front. That might be two systems that exchange data with each other, without anyone reconciling them by hand.
Development Partner
A long term arrangement for companies that need extra development capacity. The work runs month to month and the design decisions stay straight.
Rasmus Spiegel.
The background is custom software development and integration between business critical systems: CRM, inventory, purchasing and sales. Since 2023 in manufacturing, construction, wholesale, logistics and e-commerce.
Custom software and integrations
Interfaces between business critical systems: CRM, inventory, purchasing and sales. The larger engagements run for years, the smaller ones for weeks.
Custom ERP development
Modules and extensions the standard package does not cover: business logic, reporting and interfaces to the rest of the systems. Work where the rule has to be exactly right in code.
Architecture
Architecture diagrams, interface and data flow drawings, and the system built from them. The same person draws it and builds it, so the diagram and the code never drift apart.
Tell us what you run.
We will tell you what we would do.
A first call costs nothing and takes thirty minutes. By the end you know what needs to be done and how big the work is. If this is not our work, we will say so straight away.
Book a call →