Booking window open: two project slots remain for the current quarter, starting late October.

Check availability
Fern Notch Iris Vandeleur Start a project brief
A working desk lit from a window, with an open laptop, notebook and a cup of coffee

Independent practice · Design & front-end

Small teams, shipped websites, no agency in the middle.

I'm Iris Vandeleur. I design and build the public-facing pages that founders, studios and independent operators actually need — scoped in weeks, written in plain HTML and CSS, handed over so your team can keep editing it.

How I work
Solo, contract-based. You brief me directly and I do the work — nothing is passed to a junior.
Working hours
Weekdays, 09:00–17:00 CET, with a standing review call each Thursday.
Current capacity
One sprint and one retainer seat. Build-outs are quoting for the new year.

01 — What I take on

Three kinds of work, scoped before anything starts.

Every engagement begins with a written scope: what ships, what it depends on from you, and what is explicitly out. If a request doesn't fit one of these lanes, I'll say so rather than stretch it.

S / 01

Marketing site design & build

A complete public site: structure, copy shaping, layout, and a hand-written front end. Built as static pages or wired into the CMS your team already pays for, so editing doesn't route back through me.

  • Sitemap
  • Page design
  • HTML / CSS build
  • CMS wiring
  • Handover doc

Typical shape5–8 pages over four to six weeks, with two review rounds built into the schedule.

S / 02

Landing pages and launch sprints

One page, one job — a product launch, a hiring push, a waitlist. I write the layout around the single action you need, then instrument nothing you can't read in your own analytics.

  • Offer framing
  • Single-page design
  • Form wiring
  • Responsive QA

Typical shapeTwo weeks from kickoff, including one round of revisions after the first build.

S / 03

Front-end repair and accessibility passes

For sites that already exist and have drifted: broken responsive breakpoints, unreadable contrast, keyboard traps, pages that weigh more than they should. You get a written findings list first, then the fixes in priority order.

  • Audit notes
  • Contrast & focus fixes
  • Breakpoint repair
  • Asset trimming

Typical shapeFindings in week one; fixes billed against an agreed block of hours.


02 — Selected work

Three recent projects, and the constraint each one had.

Names are shortened at the clients' request. What matters here is the shape of the problem — most briefs I receive look like one of these.

An open printed publication showing a two-page editorial layout
Independent publisher

A quarterly journal that had outgrown its single scrolling page

Split one long page into an issue index, an article template and a subscribe page, then handed the editor a short guide for publishing each issue without me.

Constraint
No developer on staff — everything had to stay editable in their existing CMS.
A notebook, pen and laptop arranged on a light wooden desk during a planning session
Two-person consultancy

A services site that finally explained what they actually sell

Rewrote the structure around three named engagements with the scope and timeline on the page, so enquiries arrived with a budget range already in mind.

Constraint
Four weeks, fixed fee, launched before a conference date.
Colleagues reviewing charts and notes together around a shared worktable
Workshop studio

A course page repaired for keyboard and small screens

An accessibility and breakpoint pass: focus order rebuilt, contrast lifted to pass at every text size, and the booking panel made usable at 390px where it previously overflowed.

Constraint
Existing codebase, no redesign — fixes only, in priority order.

03 — Engagement models

Pick the arrangement, then we scope the work.

Most people arrive unsure whether they need a project or a standing arrangement. This is the honest comparison I'd give you on a first call.

Comparing the three ways I contract
Model Sprint Retainer Build-out
Best for One defined page or feature with a date attached. Teams shipping changes every month who need a steady hand. A full site replacement or a first site from scratch.
How it runs Two weeks, fixed scope, one revision round. A reserved block of days each month, planned at the start of it. Four to six weeks in stages, each signed off before the next.
You supply Copy and assets before kickoff day. A prioritised list by the first working day of the month. One decision-maker and access to your CMS or repository.
You get The built page, source files and a short handover note. A monthly summary of what changed and what's queued. The full front end, a component reference and a training call.
Not included Ongoing edits after handover. Unused days rolling into the next month. Brand identity, photography or copywriting from blank.

04 — How the work runs

Four stages, and what each one asks of you.

01

Brief and scope

You send the form below. I reply with questions, then a written scope covering deliverables, dates and what sits outside the work. Nothing starts until you've agreed it.

02

Structure first

Before any visual design, we settle the page order and what each section has to do. This is the cheapest stage to change your mind in, so I push hard on it.

03

Design into build

Layouts go straight into a working front end rather than a static mockup, so you review the real thing at real sizes. Reviews happen on the standing Thursday call.

04

Handover

You receive the source, a plain-language note on how to edit each part, and two weeks of follow-up for anything that surfaces after launch.

Two people working side by side over laptops during a review session

05 — Studio note

A practice of one, on purpose.

Fern Notch has stayed a single desk for six years. It means I take fewer projects than an agency would, and it means the person you brief is the person writing the markup. These are the principles I hold to on every engagement.

  • Plain front endHand-written HTML and CSS. No build step you'd need me to maintain, and no framework you didn't ask for.
  • Works without JSEvery page reads and functions with scripts disabled. Motion and niceties layer on top.
  • Accessible by defaultContrast, focus order and touch targets are checked before a page is called done, not after a complaint.
  • Written scopeIf it isn't in the scope document, it isn't in the project — and adding it is a conversation, not a surprise invoice.
  • You keep the keysSource files, accounts and domains stay in your name throughout.

06 — Start a brief

Tell me what you're trying to ship.

A few sentences is plenty. If it isn't a fit, I'll say so quickly rather than leave you waiting.

  • Replies go out within two working days.
  • First response includes questions and a rough shape, not a hard quote.
  • No call is required before a written scope exists.
  • Everything you send stays between us.

Include a date if you have one — it's the fastest way for me to tell you whether the work fits.