Start small, get clarity fast, then scale.
Offers
Every offer has a defined scope, a clear outcome and named accountability. No pre-project for the pre-project.
Core: software & delivery
Keycloak & multi-tenant access
“Every customer needs its own permissions — and every exception ends up in code.”
Model tenants, SSO and permissions properly — instead of grown edge cases in every application.
- Format:
- 4–8 weeks, fixed-price frame after discovery
- Who it is for:
- SaaS and product teams with multiple tenants, organisations with fragmented user management
- Role, permission and tenant model, documented and implemented
- Keycloak setup or remediation incl. realms, clients, token design
- Self-service admin UI for user and permission management
Event modeling & adoption sprint
“We have been discussing requirements for months and nobody shares the same picture.”
Model the domain together before code exists — and clarify who owns it afterwards.
- Format:
- 2–4 weeks, remote-first with 2 on-site workshop days
- Who it is for:
- Initiatives before build start, or projects going in circles
- Event model of the core processes with commands, events and read models
- Slicing into deliverable increments incl. sequence and risks
- Ownership map: who decides, who operates, who explains
EventSourcingDB package
“We cannot reconstruct afterwards how a state came to be.”
Event-driven domain systems with a traceable history — built on EventSourcingDB by the native web.
- Format:
- Proof of value in 3 weeks, then iterative rollout
- Who it is for:
- Teams with audit requirements, regulated domain logic or complex history
- Assessment whether event sourcing actually fits — including honest pushback
- Reference implementation of one domain slice
- Integration into existing systems and read-model strategy
Platform & production readiness
“Every release is an event — and we notice failures when customers call.”
From “works on our machine” to reliable operations: calm deployments, visible failures, clear ownership.
- Format:
- 4–10 weeks depending on the starting point
- Who it is for:
- Teams that want to ship faster but get stuck in operations
- Kubernetes setup or clean-up, infrastructure as code
- CI/CD with reproducible builds and safe rollbacks
- Observability: logs, metrics, traces and meaningful alerts
Monolith modernisation
“Every change to the legacy system costs weeks and nobody dares to touch it.”
Relieve existing systems step by step, without stopping operations or rewriting everything.
- Format:
- Assessment in 2 weeks, delivery in iterations
- Who it is for:
- Organisations with a grown system and overdue modernisation
- Analysis of coupling, domain boundaries and risk hotspots
- Migration path with strangler steps instead of a big bang
- Test coverage and refactoring of the critical paths
Amplifiers: impact & adoption
Fractional tech leadership
“We are missing someone who makes technical decisions and owns them.”
Technical leadership on demand: make decisions, steer delivery, build the team — with clear accountability.
- Format:
- 1–3 days per week, from 3 months
- Who it is for:
- Companies without in-house technical leadership or in a transition phase
- Architecture and technology decisions, documented and justified
- Delivery steering with roadmap, priorities and quality standards
- Building internal roles and handing over leadership
Post go-live ownership setup
“Things get delivered, but nobody answers for the overall result.”
So that after rollout it is not an open question who actually carries the system.
- Format:
- 3–6 weeks alongside the rollout
- Who it is for:
- Projects shortly before or after go-live
- Role and responsibility model for operations, evolution and support
- Onboarding material and internal communication
- Operating routines: incidents, releases, feedback loops
GTM sparring for technical offers
“The product is good, but the market does not understand what it stands for.”
Positioning, packaging and narrative for IT products and services — understandable instead of generic.
- Format:
- 4 sessions across 4–6 weeks
- Who it is for:
- Software and IT service companies that want to sharpen their offer
- Positioning and target segments with clear boundaries
- Packaging and pricing logic for explanation-heavy services
- Sales narrative and objection handling
Not sure which package fits?
Describe your situation in a few lines. You get a first assessment and a suggestion for a sensible starting point.
Request a first assessment