Skip to content

Services

Three kinds of engagement, and the parts I build inside them. Each sheet lists what you receive at the end.

drawing
Scope of work
sheet
02 of 07
rev
A
date
2026-10-13

Engagements

Custom software

Web applications and platforms built end to end: data model, back end, front end and deployment.

you receive
  • Written specification and estimate
  • Working software, released in phases
  • Source code, infrastructure configuration and documentation
  • A handover session, or continued support
typical for
A new product, an internal tool, or a platform that has outgrown its first version.

Contract engineering

I join your team as a contract engineer and work inside your process, tools and review rules.

you receive
  • Tickets taken from your backlog and shipped through your reviews
  • Pull requests in your repository
  • Attendance at your stand-ups, planning and retros
  • Part-time or full-time commitment, agreed per month
typical for
A team with more roadmap than people.

Technical consultancy

An outside view on architecture, scaling, AI and legacy decisions, before you commit budget to them.

you receive
  • Code and architecture review
  • Written report with prioritised recommendations
  • Estimates for the work you decide to do
  • Optional follow-up implementation
typical for
A decision that is expensive to reverse.

Parts

Microservices and event-driven systems

Distributed back ends that stay consistent under load: event-driven messaging, service-to-service APIs and actor-based concurrency.

you receive
  • Kafka or RabbitMQ messaging with the transactional outbox pattern, so events are not lost
  • gRPC or GraphQL contracts between services
  • Microsoft Orleans for high-concurrency state, where it fits
  • Unit, integration and load tests (xUnit, JMeter) before go-live
typical for
A monolith that has to scale, or services that drop messages under load.

AI and LLM engineering

Features built on language models, with the evaluation, cost limits and monitoring they need in production.

you receive
  • Secure MCP servers that give AI agents controlled access to your data
  • RAG and semantic search on Qdrant embeddings
  • Knowledge graphs in Neo4j where relationships matter
  • Workflow automation with n8n
  • Evaluation sets, cost and latency limits, with monitoring
typical for
Support assistants, document processing, internal search, reconciliation and reporting.

Websites and technical SEO

Fast, accessible websites with the technical groundwork search engines reward.

you receive
  • Static or server-rendered pages tuned for Core Web Vitals
  • Metadata, sitemaps, structured data and link previews
  • Multilingual setup with hreflang, as on this site
  • Search Console setup and a list of what to fix next
typical for
A business that wants its website to bring in customers from search.

Mobile apps

Cross-platform iOS and Android apps in React Native, published to the App Store and Google Play.

you receive
  • Store-ready builds and release setup
  • A shared API with your web product
  • Push notifications, payments and offline support where needed
typical for
A companion app for an existing service, or a mobile-first product.

Legacy migrations

Moving .NET Framework services, spreadsheets, macros and desktop software to systems you can maintain.

you receive
  • An inventory of the rules the old system enforces
  • .NET Framework to .NET 10 migrations, containerised
  • Parallel runs that compare results with the old system
  • Data migration and a staged cut-over plan
typical for
A business that runs on a workbook nobody wants to touch, or a .NET Framework service nobody wants to deploy.

Hosting and DevOps

Infrastructure you can understand and afford, on a cloud provider or your own server.

you receive
  • Docker and Kubernetes deployments with ArgoCD
  • CI/CD pipelines
  • Monitoring, logs and alerts in Grafana, Kibana or Dynatrace
  • Backups with tested restores
typical for
Manual deploys, no staging environment, or a server nobody dares to restart.

Maintenance retainers

Ongoing care after launch, on a fixed monthly plan.

you receive
  • Security and dependency updates
  • Bug fixes and small features
  • Uptime monitoring
  • A monthly summary of what changed
typical for
Software that has to keep working after the project ends.

Send me a spec, or just the problem.

Tell me what you're building and where it's stuck. I read every request and reply by email.

drawing
Project request
sheet
06 of 07
next stepRequest a project