Services

01
Services

What I build, in full: the plain claim, the brief behind it, and the constraints, decisions, and tradeoffs. The same detail on every screen, not hidden behind a hover.

  • 01

    Web apps & SaaS

    A custom web application that's yours to own, built end-to-end from data model to interface. Type-safe throughout.

    You get the repository, the documentation, and the deployment, all in your accounts and under your name. I work in TypeScript end to end, and the range I can build in runs wider than my default stack: React or Vue/Nuxt in front, Node.js, Go, or C#/.NET behind it, SQL underneath. I've built and maintained SaaS platform features in a team setting (Appsemble, 2023–2024) and refactored a legacy Go microservices codebase (ART-IE, 2024–2025).

    What you get
    • The source-code repository, in your own account
    • Documentation for what was built
    • A live deployment, in your own hosting account
    Promo visual
    Technical schematic
    Constraint
    I define the data model before any UI work begins.
    Tradeoff
    Higher upfront technical planning, in exchange for faster long-term iteration.
  • 02

    E-commerce

    Online stores that take payment reliably and don't fight you at checkout. Built to sell, not to impress other developers.

    My secondary education was e-commerce (2012–2017); the point hasn't moved since: the store has to take money reliably. I build the catalogue, the checkout, and the payment integration, and I write automated tests (Playwright, Vitest) for the exact paths where a failed step costs you an order.

    What you get
    • A working catalogue and checkout
    • A payment integration through an established processor (Stripe or Mollie)
    • Automated tests (Playwright, Vitest) on the checkout paths that cost you an order
    Promo visual
    Technical schematic
    Constraint
    Payments go through an established processor (Stripe or Mollie, chosen for your market); I never hand-roll payment handling.
    Tradeoff
    Processor fees, in exchange for the processor carrying PCI compliance and fraud handling.
  • 03

    Booking sites

    Let clients see your availability and book it themselves. Fewer emails, fewer no-shows.

    Clients book themselves and you read the result in one place instead of reconstructing it from your inbox. I build availability, booking, and confirmation: a data model, a calendar view, and email that fires when a booking is made or changed.

    What you get
    • A booking data model and calendar view
    • Automated confirmation email when a booking is made or changed
    • One source of truth for availability (your calendar, or one I build)
    Promo visual
    Technical schematic
    Constraint
    Availability needs one source of truth: your existing calendar or one I build, never both.
    Tradeoff
    Payments go through an established processor (Stripe or Mollie); no custom payment gateways.
  • 04

    Get online

    No site, no presence, no idea where to start? I get you legitimate online, domain to launch, without the agency runaround.

    I set up the whole chain and hand it over with the accounts in your name, not mine: domain, hosting, the site itself, the legal lines Dutch law requires on a business site, and a mailbox on your own domain.

    What you get
    • A domain registered in your name
    • Hosting and the site itself
    • The legal lines Dutch law requires on a business site
    • A mailbox on your own domain
    Promo visual
    Technical schematic
    Constraint
    The domain is registered in your name, not mine. You own your address from day one.
    Tradeoff
    Less drag-and-drop freedom than a site builder, in exchange for a site you own outright and that loads fast.
  • 05

    Email & automation

    Transactional and campaign email that actually lands, wired to fire on the events that matter.

    Transactional email wired to events in your system: an order, a booking, a password reset. I set up the sending domain (SPF, DKIM), the templates, and the triggers, and I test deliverability instead of assuming it.

    What you get
    • Sending-domain authentication (SPF, DKIM)
    • Email templates for your transactional events
    • Triggers wired to the events that matter (an order, a booking, a password reset)
    • Deliverability testing, not an assumption
    Promo visual
    Technical schematic
    Constraint
    Sending starts only after authentication is set up (SPF, DKIM, DMARC); unauthenticated mail lands in spam.
    Tradeoff
    Deliverability discipline over blast volume: fewer, better-targeted sends.
  • 06

    Content management

    Edit your own site without calling a developer. Structured content you control, not a pile of HTML.

    I set up structured content: pages, posts, and products as fields you edit, not markup you can break. Headless CMS or a plain admin panel, matched to how much you actually publish, not to what a platform wants to sell you.

    What you get
    • Structured content fields for pages, posts, or products
    • A CMS or admin panel matched to how much you publish
    • Editing access with no markup to break
    Promo visual
    Technical schematic
    Decision
    Structured content with defined fields, not a freeform page builder.
    Tradeoff
    Less freeform layout freedom, in exchange for pages that cannot be accidentally broken.
  • 07

    SEO groundwork

    The technical foundation so search engines can find, read, and rank you. Measured, not promised.

    Semantic HTML, metadata, sitemaps, redirects, and page-speed work: the part of SEO that is engineering. I measure before and after (Lighthouse and search console data). Rankings are the search engine's decision, so I don't promise them.

    What you get
    • Semantic HTML, metadata, and sitemaps
    • Redirects and page-speed fixes
    • Before-and-after measurement (Lighthouse, search console data)
    Promo visual
    Technical schematic
    Constraint
    No ranking guarantees. Rankings are the search engine's decision, so I don't promise them.
    Decision
    Technical foundation first: crawlability, structure, and speed, before any content play.
    Tradeoff
    Measured groundwork over promised outcomes; results are reported, not predicted.
  • 08

    Anything else

    Odd problem, weird integration, something no template covers? Bring it. Full-stack means I don't hand you off.

    The range is the point of a one-operator studio. I've assembled printed circuit boards in a cleanroom (Prodrive Technologies, 2021–2022) and refactored an EU-funded federated-learning platform in Go with Cassandra and microservices (ART-IE, 2024–2025). An odd integration or a problem without a template still lands on one desk: mine.

    What you get
    • A written feasibility report scoped to your specific problem
    • The same one-desk accountability as every other service
    • A written answer you can take elsewhere, even if I don't end up building it
    Promo visual
    Technical schematic
    Constraint
    The feasibility report applies double here: it's a paid service, but if I can't build it well it says so up front, so you spend a fraction of the build to learn that, not the whole thing.
    Tradeoff
    Odd problems take longer to scope, in exchange for a written answer you can take elsewhere.

What I don't do

  • 01 · Web apps & SaaS

    I define the data model before any UI work begins.

  • 02 · E-commerce

    Payments go through an established processor (Stripe or Mollie, chosen for your market); I never hand-roll payment handling.

  • 04 · Get online

    The domain is registered in your name, not mine. You own your address from day one.

  • 07 · SEO groundwork

    No ranking guarantees. Rankings are the search engine's decision, so I don't promise them.

Not sure it's even possible? That's what the first conversation is for.

You get a written feasibility report and an honest cost before you commit to the build. src: How I work · step 03

Start the conversation