Three services, one person responsible
Each one starts with the same conversation about what should change in your work. Below you will find the scope, the time, and what stays with you once we finish.
AI adoption
I connect your tools to language models through n8n: email replies, product copy, reports from raw data. We start with the process that eats the most of your time — so that is the time you get back first.
- →An audit of one process and where automation actually pays
- →An n8n flow wired to a model and your tools
- →Prompts in the repository, with change history and a test set
- →A decision log: what the model did, what a human approved
MVP, quickly
You get a working version of the idea in weeks, on Astro with SSR. Exactly enough features to put it in front of first users and learn something real before you spend more.
- →Scope cut down to a single use case
- →An Astro app with SSR, deployed on your domain
- →One way to sign in, and database access for you
- →Feedback collection built in from day one
Websites
Sites and shops on Astro or WordPress — fast, built around what is meant to happen on them, and editable by you, without an invoice for every small change.
- →Structure and copy agreed before the first pixel
- →Astro or WordPress — chosen by who will be editing
- →Performance and SEO checked before launch, not after
- →Handover with a recorded editing walkthrough
Four steps, always the same — you always know where you stand
A conversation
Thirty minutes about what should change. I ask four questions and say plainly if this is not a project for me.
Scope in writing
A feature list, a date and a price range in one document. Nothing starts until you accept it.
Delivery in iterations
You see a working version every week, not at the end. Changes are cheaper once there is something to look at.
Handover
Access, documentation and a recorded walkthrough of the editing. Maintenance only if you want it.