Ga naar inhoud
Onafhankelijke software engineering voor intelligente producten

Bouw de softwarelaagdie je workflow mist.

RMedia-IT is een eenmanspraktijk voor klanten die meer nodig hebben dan een nette website. Ik bouw AI tools die echt werk doen, builder systemen die content schaalbaar maken, dashboards die operatie zichtbaar maken en browser-native software die snel genoeg voelt voor dagelijks gebruik.

Maatwerk softwareAI operationsWebsite buildersAutomationDashboardsBrowser games
AI
assistants, agents en review workflows
BUILD
website systemen en product dashboards
PLAY
browser software en game mechanics
solo.engineer.boot
brief: workflow frictie, databronnen, gebruikersrollen
compose: AI laag, interface systeem, automation logica
output: bruikbare software, gebouwd door een aanspreekbare engineer

Instapaanbod

Concrete builds om mee te starten

RMedia-IT werkt het best wanneer de eerste mijlpaal concreet is. Deze vormen maken van een ruwe softwarevraag een gerichte build met een engineer die direct verantwoordelijk is.

AI workflow prototype

Voor repetitieve intake, documenten, support of operationeel werk waar snel een bruikbare AI laag nodig is.

/Workflow map
/AI interactiestroom
/Prototype interface
/Review checkpoints
Eerste prototyperichting in 10-14 dagen
agent.workflow -> human.review

Custom dashboard MVP

Voor bedrijven die een helder controlepaneel nodig hebben voor taken, KPI's, alerts, queues of interne operatie.

/Datamodel
/Dashboard UI
/Filters en states
/Launch-ready MVP
Gerichte MVP in 2-4 weken
metrics.sync(live_state)

Website builder systeem

Voor merken die herbruikbare paginablokken, contentcontrole en een websitefundament nodig hebben dat als software werkt.

/Bloksysteem
/Contentregels
/Preview states
/Herbruikbare layouts
Builder fundament in 3-5 weken
blocks.render(brand_safe)

Browser tool of game prototype

Voor interactieve ideeen die responsieve input, state, feedback, progressie of een browser-native software shell nodig hebben.

/Game/tool loop
/Interactiemodel
/UI shell
/Prototype build
Speelbaar prototype in 2-3 weken
input -> state -> feedback

Proof patterns

Real proof and system examples

A live RMedia IT powered website now sits next to prototype directions, so visitors can see both shipped work and the kind of systems a focused solo engineer can design next.

Live project example

Balans en Opvoeden

system preview

Problem

A coaching practice needs a calm public website that helps parents find the right path: toddler parenting support, child coaching, methods, reviews, and contact.

Build

A content-focused website with clear navigation, service routes, personal positioning, review content, and direct contact paths for Dutch parents.

Result

A warm, structured web presence that turns sensitive service information into a clear visitor journey.

Public websiteService pagesReview contentContact flow
live_site -> service_routes -> contact

System example

AI Intake Console

system preview

Problem

Incoming requests, documents, and notes are scattered across tools, making triage slow and inconsistent.

Build

A review-first AI interface that extracts structured data, proposes next actions, and keeps human approval visible.

Result

A clearer intake flow where repetitive interpretation is automated and judgment stays with the operator.

Next.jsTypeScriptOpenAIReview UI
extract -> classify -> approve

Prototype direction

Brand Page Builder

system preview

Problem

A growing brand needs to publish quickly without breaking layout rules, tone, or visual consistency.

Build

A modular website system with reusable content blocks, schema-driven sections, preview states, and branded constraints.

Result

Publishing becomes faster while the site still feels engineered, controlled, and visually consistent.

App RouterCMS LogicBlock SystemTailwind
content.schema -> page.blocks

Build pattern

Operations Dashboard

system preview

Problem

Important work is hidden across spreadsheets, inboxes, browser tabs, and manual status checks.

Build

A dashboard MVP with queues, filters, status language, alerts, and terminal-style audit details for key actions.

Result

Operators get one control surface for decisions, follow-up, and visibility into what changed.

ReactData ModelAutomationDashboard UI
events -> queue -> decision
/Direct communication with the engineer
/No agency handoff or hidden production layer
/Architecture and interface decisions stay connected
/Prototype thinking before overbuilding

Core services

Engineering voor intelligente digitale producten

RMedia-IT is een solo engineering praktijk voor software met een duidelijke taak: systemen die tijd besparen, bruikbare data tonen, repetitief werk automatiseren en een merk technisch sterker maken.

Software development

Voor founders, operators en hands-on ondernemers die een werkend systeem nodig hebben in plaats van een statische pagina. Ik bouw typed web apps, interne platformen, workflow tools en productinterfaces met onderhoudbare architectuur vanaf de start.

Product UIAdmin toolsInterne workflows
next build --typed --scalable
Bekijk pagina

Website builder systemen

Voor merken die vaak publiceren en controle nodig hebben. Herbruikbare paginablokken, visual editing flows, contentregels, preview states en brand-safe templates die een website laten werken als software.

Herbruikbare blokkenCMS logicaPreview flows
blocks.map(render)
Bekijk pagina

AI tools

Voor workflows waar AI gestructureerd werk moet doen, niet alleen praten. Assistants, agent flows, document parsing, extractie pipelines en review interfaces worden ontworpen rond traceerbare output.

AssistantsExtractieReview queues
agent.tools.verify()
Bekijk pagina

Automation

Voor repetitief werk dat aandacht opslokt. Apps koppelen, notificaties triggeren, browsertaken uitvoeren, data transformeren en approvals zichtbaar houden waar menselijk oordeel nodig blijft.

IntegratiesBrowsertakenAudit trails
queue -> action -> audit
Bekijk pagina

Dashboards

Voor bedrijven die willen zien wat er gebeurt zonder vijf tools te openen. Heldere datamodellen, statustaal, alerts, filters en beslisklare views voor dagelijks werk.

KPI'sQueuesControl rooms
metrics.live.sync
Bekijk pagina

Browser software

Voor producten die in de browser leven en direct moeten voelen. Utilities, extension-style workflows, interactieve tools en game-adjacent systemen met responsieve input en schone state.

ExtensionsToolsGame loops
runtime: browser-native
Bekijk pagina

Stack

Modern tools, tuned for serious builds

A focused solo stack for fast frontend systems, reliable backend patterns, AI APIs, browser automation, and visual polish.

Next.js
TypeScript
React
Tailwind CSS
Node.js
OpenAI
Python
Supabase
PostgreSQL
Playwright
Framer Motion
Three.js

AI Lab

AI that plugs into the work, not the hype cycle

My AI Lab work focuses on applied systems: extracting structured information, routing decisions, reducing manual steps, and keeping the operator in control when accuracy matters.

ai-lab.pipeline
ingest docs, forms, tasks --normalize --index
compose agent tools: browser, data, dashboard, notifications
return verified actions, traces, and operator controls

Agent Workflows

Tool-enabled assistants that route tasks, call internal systems, produce structured output, and pause for approval when a decision needs human judgment.

Best for: intake, triage, scheduling, reporting

Knowledge Systems

Searchable company memory, document intelligence, retrieval layers, and normalized source handling so AI products answer from useful context instead of guesswork.

Best for: documents, SOPs, product data, CRM notes

AI Interfaces

Review screens, confidence signals, audit trails, correction flows, and operator controls that make model-powered work inspectable before it affects the business.

Best for: approvals, QA, dashboards, copilots

Games & systems

Browser-native systems that feel alive

This lane covers game systems, custom tools, dashboards, and product surfaces where interaction quality is part of the value. It is one-engineer software with feedback, state, and momentum.

Browser Games

Fast-loading mechanics, score systems, upgrade loops, responsive input, and interface layers that feel immediate in the browser. Useful for branded games, training flows, product demos, and playful tools.

input -> state -> feedback

Web Platforms

Admin portals, builder platforms, SaaS-style tools, and custom control rooms designed for repeated use. The goal is a product surface people can scan, operate, and trust daily.

portal.control.surface

Custom Utilities

Small but powerful systems: extensions, calculators, workflow panels, data utilities, and focused products that remove daily friction without becoming bloated platforms.

utility.solve(friction)

Realtime Interaction

Stateful interfaces with crisp feedback, motion discipline, keyboard-ready controls, and visual language that keeps users oriented as data, scores, or actions change.

motion supports meaning

Process

A practical path from rough idea to working system

The process is built to reduce ambiguity early. Every phase produces a concrete artifact, so the work moves from business signal to product logic to usable software.

01

Map

Pin down the business outcome, user roles, workflow bottlenecks, data sources, and the smallest system that can create leverage.

Output: scope map, system boundaries, risk notes
02

Prototype

Turn the idea into a clickable technical model: core screens, data movement, AI behavior, automation rules, and failure states.

Output: interface flow, data model, feature sequence
03

Engineer

Build the production surface with typed components, clear state, resilient integrations, and code that can survive iteration.

Output: working product, integrations, reusable modules
04

Refine

Test the flows, sharpen accessibility, tune performance, polish motion, and prepare the system for real users.

Output: QA pass, launch polish, next roadmap

Projects

Product directions with a clear technical spine

RMedia-IT is strongest where interface, logic, automation, and brand experience meet. These concepts show the kind of systems one focused engineer can design, build, and extend.

Live Website

Balans en Opvoeden

A public website for a Dutch opvoedcoach and kindercoach, structured around service routes, personal trust, review content, and direct contact paths.

Shows how a sensitive service brand can become clear, calm, and easy to navigate online.

balansenopvoeden.nl -> powered_by_rmedia_it
AI Automation

Ops Command Center

A control-room dashboard for monitoring AI tasks, alerts, queue health, browser automations, and human approval checkpoints.

Turns scattered operational work into visible queues, traceable AI actions, and cleaner decision moments.

events.stream -> approval.queue
Builder System

Modular Site Engine

A component-driven website engine with reusable sections, content rules, preview states, and layouts that stay on-brand as pages scale.

Gives a brand the speed of a builder without giving up design consistency or engineering control.

schema.blocks.render(site)
Browser Software

Interactive Game Toolkit

A browser-first toolkit for mini-games, gamified portals, progression systems, and responsive interfaces with a polished software shell.

Creates product experiences where interaction, feedback, and progression make the tool more engaging to use.

loop.tick(input, state)

Trust model

The one-man show is the advantage

RMedia-IT is intentionally direct: one accountable engineer, practical scope, connected technical decisions, and no agency handoff between strategy, interface, and implementation.

Direct Engineer Contact

You speak with the person who designs the architecture, writes the code, and makes the implementation decisions.

no handoff layer

Scope Before Build

The first milestone is shaped around the smallest useful system, known risks, and the decisions needed before production work expands.

scope.map -> milestone

Practical Technical Standards

Typed interfaces, reusable components, responsive layouts, clear states, and build verification stay part of the work from the start.

typed + tested + usable

One Accountable Builder

Architecture, interface, automation logic, and delivery stay connected because one engineer owns the thread from idea to launch.

one thread, less drift
trust.protocol
client.talks_to = engineer
scope.before_build = true
handoff.layers = 0

Working Style

/Clear written direction before implementation
/Fast technical decisions without committee drag
/Prototype first when uncertainty is high
/No fake proof, no inflated team language
/Build notes that explain tradeoffs and next steps
/Premium interface polish tied to real software behavior

Technische intake

Vraag een technisch bouwplan aan

Gebruik deze korte brief composer om het probleem scherp te maken voor het eerste bericht. Je werkt direct met de engineer die dit vertaalt naar scope, architectuur, interface en bouwvolgorde.

contact.sequence
accepted: ai_tool, dashboard, site_builder, automation, browser_game
brief.required = outcome + users + data + friction
reply: architecture direction, build phases, first milestone

Een beter eerste bericht.

De briefing hoeft niet perfect te zijn. Er moet alleen genoeg signaal in zitten om de eerste mijlpaal, de risicovolle onbekenden en de kleinste bruikbare build te vinden.

/Beschrijf de uitkomst, niet alleen de feature
/Noem wie het systeem gebruikt en hoe vaak
/Voeg databronnen, tools en randvoorwaarden toe
/Vraag om de eerste praktische bouwvolgorde