Website builds, audits, and hourly advisory
I work two ways. A fixed price when the job has an end - a build, an audit, a rescue. Hours when what you need is one decision reviewed before you commit to it.
Some of the technology I build with
Website audit
I find the bugs, name what is making the site slow, and price every fix - written so you can decide what to fund without a developer translating it.
Website maintenance retainer
A fixed block of hours every month, held for your site - regressions caught before your customers find them, patches applied, and someone who already knows the codebase when something breaks.
AI-editable websites with a CMS
A headless CMS you pick - Sanity, Storyblok, or another platform - wired for schema-as-code and AI-agent access alongside your editors' visual editing.
Vibe-coded site rescue
Flat-fee diagnosis of a Lovable, Bolt or Replit project that stopped moving forward, then a stabilization plan and an honest repair-or-rebuild verdict.
AI-editable websites, no CMS
Markdown-native, git-based, edited directly by Claude Code or Cursor. Schemas and CI checks stand in for an editor's guardrails - schema discipline, not vibes.
General frontend consultancy
Hourly advisory on a frontend decision - architecture, a framework choice, a CMS schema call. Pick a platform below for the deepest fit, or start from a general question and I point you to the right one.
General CMS consultancy
Schema architecture, content modeling, and migration review for a headless CMS project on Prismic, Contentful, Tina CMS, Payload, Builder.io, or another platform outside Sanity and Storyblok - hourly, one decision at a time.
Sanity CMS consultancy
Multi-tenant dataset architecture, document-versus-field-level internationalization, schema construction, Media Library adoption, and codebase audits for a Sanity project - hourly, one decision at a time.
Storyblok CMS consultancy
Bloks structure, Visual Editor bridge, and space internationalization review for a Storyblok project - hourly, one decision at a time.
Agentic coding consultancy
Architecture review, code review, and performance debugging for teams shipping production sites, plus the rules and docs a coding agent needs before it gets wider access.
Next.js consultancy
Caching, the App Router server/client boundary, and edge middleware review for a Next.js project - hourly, one decision at a time.
Astro consultancy
Islands architecture, SSR adapter choice, and content collections review for an Astro project - hourly, one decision at a time.
The exceptions
Two exceptions worth knowing before you pick one
When do you skip the CMS?
Only when a developer or a technically comfortable founder is already the one touching content, and pages change in shape as often as they change in words. That is the exception, not the default - most teams need editors to build and rearrange sections themselves, on their own schedule, without a pull request in the loop, and that is a CMS case. I quote the CMS build unless your team is fully technical.
When are you the wrong person to hire?
When you need a long design process upfront and a very bespoke design. I work at Bejamas day to day. Bejamas has a dedicated team of UI/UX specialists for exactly that.
In practice
The process
You send the brief
A build, an audit, a rescue, or the one decision you want reviewed. One paragraph is enough - I read what you send before I quote anything.
You get a fixed number in writing
A fixed price and a deliverables list for a build, audit, or rescue. A fixed hour estimate for advisory. Either way, the number is set before work starts, not adjusted after.
Work ships on that number
No retainer running in the background, no scope drifting past what was quoted. If something outside the brief comes up, that becomes a new quote, not a surprise on the invoice.
Client feedback
What clients say after the work ships
01 / 05
Get in touch
Tell me what is going on
Four fields. I reply with the right service, or a straight answer that none of them fit.