We build what we recommend.
Microsoft 365, WordPress and WooCommerce, ERP implementation, cloud telephony, n8n automation, mandatory e-invoicing — we do the building. No hand-offs to an implementation partner, no losses between the concept and the code.
Implementation
with the concept
in its bones.
Building without understanding first is like building without a plan. Possible, but risky.
We build the way we would have designed it — including when the concept came from another consultant. In practice: we question before we build. We say so when we think a concept will not hold up in the detail. And we document so that a successor can carry on without us.
That makes working with us slower than plain click-and-go. It also makes the result hold.
Six areas we know in depth.
Microsoft 365 and cloud identity
Tenant setup, migration from legacy systems (Exchange, Google Workspace, on-premises), structuring Teams, SharePoint and OneDrive. Multi-tenant strategies for corporate groups, consolidation of tenant landscapes that grew as they went.
On the identity side: OAuth and SSO integration, Azure app registration for in-house applications, GDAP partnerships for external client access without employee accounts of your own.
A frequent trigger: consolidating several Microsoft 365 tenants after an acquisition or a merger.
WordPress and WooCommerce
Theme and plugin architecture, custom layouts, B2B extensions, configuration for the German market, filtering and search structures, content portals.
We build WordPress setups with substance, not page-builder improvisation on sand. Stack: Astra Pro, Spectra, Gutenberg block patterns, ACF Pro, FacetWP, German Market.
A frequent trigger: modernising the platform of a WooCommerce shop that grew as it went.
ERP implementation and migration
Selection, design, roll-out and migration of ERP systems for small and mid-sized businesses. We advise vendor-neutrally and implement with the system that suits your business — not our commission plan.
Specialised topics: multi-company setups, batch tracking, core charges, generating ZUGFeRD and XRechnung documents, DATEV interfaces, migration off legacy systems.
A frequent trigger: a legacy system that no longer carries the growth and blocks further digitalisation.
Cloud telephony and CRM integration
Connecting cloud phone systems (Yeastar P-Series, for example) to CRM and ERP through webhook-based workflows. Incoming calls find the contact in the CRM, call events trigger tasks — with no manual upkeep.
Available as a standardised package: connecting a phone system to a CRM or ERP as a repeatable implementation.
Process automation with n8n
Our own n8n instance as the switchboard. Typical workflows: CRM synchronisation, marketing automation, ERP-to-shop synchronisation, lead enrichment, telephony and ticket workflows.
We favour n8n because it can be self-hosted and the data does not have to sit with US providers — which fits our line on sovereignty.
E-invoicing and GoBD implementation
XRechnung CIUS, ZUGFeRD 2.x, KoSIT validation, archiving that satisfies the German GoBD rules, PEPPOL connectivity. Putting the e-invoicing obligation into practice — not as marketing advice, but as an implementation that works.
We have taken clients through the German e-invoicing obligation of 2025 and 2026 and know where it usually trips people up.
We use AI
ourselves before
we sell it.
We use Claude Code, agentic workflows and structured automation throughout our delivery chain. That makes us faster and more consistent than classic consultancies — with the same team effort or less.
For you as a client that means we have real experience with AI implementation, because we run it ourselves. If you want to bring AI into your processes, we talk about specific applications — not about buzzwords.
And, just as honestly: where a plain interface will do, we do not recommend AI. We know when the effort pays off.
How an implementation project works with us.
Getting clear
If the design did not come from us: a short familiarisation phase. We read what is there. We ask about what is unclear. We name what worries us.
Delivering in slices
We do not build in waterfall phases. We deliver in slices: a first working piece that creates value straight away. Then the next one.
Documenting reproducibly
What we build, we document so that a successor can carry on without us. Architecture description, setup instructions, context files for agentic follow-up work.
Handover and readiness to escalate
We stay reachable after the project ends. If something goes wrong weeks or months later, we are the people to call. Even when nothing is formally running.
What clients often ask about implementation projects.
Can you take over what someone else started?
Yes, in many cases. We do a short familiarisation first — we read the code, examine the architecture, talk to the people originally responsible. Then we say honestly whether taking it over will work or whether starting again is cheaper.
What size of company do you work with?
Owner-run SMEs, typically five to a hundred employees. Corporate projects with large implementation teams are not our business.
How many projects can you run at once?
Deliberately few. We do not take every project that comes to us. When our capacity is used up, we say so up front — and name another dependable partner where we can.
What if the system you recommend causes trouble later?
We remain your point of contact, including after the project ends. If a tool turns out to be a dead end, we help with the move away from it. We take no commission from vendors, so we have no interest in keeping you on a platform that is going nowhere.
How much do you travel?
We spend a lot of time on site with clients, mainly in German-speaking countries. Travel costs are stated transparently in every proposal. Much of the work can be done remotely — workshop phases are typically on site.
You have something planned — or a problem that could turn into one?
Talk to us. Thirty minutes, free of charge, no obligation. We work out with you what you actually need — and say whether that is a fit for us.