What I do
Services
Two distinct engagements. The first plugs me into an existing programme; the second hands me a product to build and put in production. Both are billed transparently, with the scope agreed in writing before anything starts.
01 · What I do
Integration Engineering
Make systems talk that were never built to.
I connect enterprise platforms (Guidewire PolicyCenter, EMR and laboratory systems, CRMs, document management, payment providers) over REST, SOAP, messaging and standards like FHIR. Four years of production integration work across insurance, healthcare and public services, and three Guidewire certifications on the InsuranceSuite side.
Who it is for
- P&C insurers running a PolicyCenter programme who need integration capacity that already knows the platform
- Healthcare vendors who must exchange data between EMR, lab and imaging systems without rebuilding them
- Enterprises with a legacy system everyone depends on and nobody wants to touch
- Teams whose integration layer keeps failing in production and nobody can say why
What you get
- Integration architecture: systems inventory, flow mapping, contract and payload design
- REST and SOAP connectors, Apache Camel routes and JMS messaging, built and deployed
- Event capture and bidirectional mapping across the business lifecycle (issuance, endorsement, cancellation)
- Error handling that a human can act on: retries, dead letters, follow-up tasks, alerting
- An integration test suite that catches regressions before your QA team does
- Runbook, documentation and enablement so your team owns it after I leave
How it runs
01
Discovery
Two weeks inside your systems, with the people who actually run them. I come out with a map of what talks to what, a list of the places it breaks, and a short note on which constraints are real and which ones everybody simply inherited.
02
Architecture
Contracts, payload shapes and the error strategy, written down and agreed. Nothing gets coded before that document exists.
03
Build
One flow at a time, tested and deployed as it lands. You have integrations running in the first month rather than one big release six months out.
04
Handover
Runbook, documentation and working sessions until your team can debug the thing without calling me. That is the whole point.
Engagement
- Model
- Day rate, embedded in your team
- Typical duration
- 3 to 12 months
- Commitment
- Full-time or part-time
Tools I use for this
Proof
Engagements of this kind, already delivered
Insurance (P&C)
Guidewire PolicyCenter integrations: P&C insurer
REST and SOAP connectors built in Integration Gateway between PolicyCenter and payment, CRM and document-management systems, across the motor policy lifecycle.
Healthcare
Kapsiki: healthcare interoperability (EMR, Lab, Radiology, ERP)
FHIR-based architecture enabling secure data exchange between open-source healthcare applications: EMR, lab, DICOM radiology and ERP.
Municipal services
Evia Burger Portal: municipal services
Mobile application giving German citizens access to municipal services: dog registration, local-event sign-up, personalised information.
02 · What I do
Product Delivery
From an empty repository to production, shipped by one person.
I build complete web products end to end (data model, Spring Boot API, Angular or Next.js front end, authentication, payments, containers and CI/CD) and put them in production. No handoffs between three contractors and no grey zone between front and back: one person accountable for the whole chain.
Who it is for
- Founders who need a first real version in production, not another prototype
- SMBs replacing a spreadsheet, an access database or a tool nobody maintains any more
- Teams that need an internal platform but have no capacity to build it
- Anyone holding a half-finished agency build that never reached production
What you get
- Scoping: user flows, data model and a milestone plan you can hold me to
- Spring Boot API: domain model, business rules, documented OpenAPI contract
- Angular or Next.js front end, responsive, server-rendered where it matters for SEO
- Authentication and roles (OAuth2, Keycloak) and payments (Stripe, subscriptions included)
- Docker images and a CI/CD pipeline that deploys on merge
- Production deployment, backups, monitoring, plus the source, the documentation and full ownership
How it runs
01
Scoping
One working session. Out of it come a written scope, fixed milestones, and a price against each one.
02
Foundations
Data model, authentication and the deployment pipeline, all running in a real environment before the first week is out. The boring parts get done while they are still cheap to change.
03
Milestones
Features land in increments, each one demoed and deployed. You always have something you can click.
04
Launch
Production release, with backup and restore procedures tested rather than promised. After that the source, the documentation and the keys are yours.
Engagement
- Model
- Fixed scope, quoted per milestone
- Typical duration
- 6 to 14 weeks
- Commitment
- Solo, or alongside your team
Tools I use for this
Proof
Engagements of this kind, already delivered
SaaS (personal product)
SprintSense
Agile retrospectives SaaS built solo, from design to production. Angular 19 SSR, Spring Boot, PostgreSQL.
SaaS (personal product)
Fluentry
Language-learning web app with tiered subscriptions (Stripe). Full product lifecycle, from API to UX.
Logistics
Joe-Cargo: real-time freight and fleet tracking
A real-time tracking platform for shipments and fleet operations, from dispatch to delivery.
Not sure which one you need?
Most engagements start as one and turn out to be the other. Describe the problem and I will tell you which of the two it is, or that it is neither, if that is the honest answer.