Answers to your questions
How a project runs, what it costs, how long it takes and what happens after launch. If your question isn't here, ask it and we'll reply within a working day.
What we do
If a template genuinely fits, use one, and we’ll tell you if we think that’s your situation. What you’re paying for here is the part a template can’t do: working out what your site needs to say, and building it so it stays fast and editable as you grow.
Yes. If you have guidelines we work inside them rather than quietly redesigning your brand halfway through. If we think something in them is working against you, we’ll say so and let you decide.
Yes, that’s a normal way to work. We’ll want to look at the files early and flag anything that’ll be expensive or fragile to build before you finalise the design, which usually saves everyone a round.
Both, including multilingual sites where the CMS carries two locales.
Yes: illustration, motion, 3D and ad creative. Useful when you need something on-brand and don’t have the time or the in-house resource. It’s the same team, so it doesn’t need briefing twice.
Yes. If part of your business runs on manual copy-paste, we’ll look at what’s actually available, test it against how you really work, and give you an honest read on whether it’s worth it before building anything. Sometimes the answer is that your current process is fine.
For straightforward catalogues, yes. For anything with complex inventory, subscriptions or heavy fulfilment we’ll usually point you at a dedicated platform and build the front end around it, which is a better outcome than bending Webflow into something it isn’t. We’ll tell you which one you need before you commit.
We can, in English and Dutch. Most projects land somewhere in between. You know your business and we know what a page needs to do, so we usually shape it together rather than one of us handing the other a finished draft. If you’d rather write it all yourself, we’ll tell you what each page needs and roughly how long it should be.
Yes, it’s one of the most common things we’re asked for. We rebuild in Webflow rather than auto-converting, because a straight port carries all the old problems across. You come out with a site your team can edit without a developer, and no plugin stack to maintain.
It can, and it’s good at parts of it. But a site that carries your brand and your business goals still needs judgement: what to say, what to cut, what to fix before launch. We use AI every day. We just don’t let it do the thinking.
Yes. Every site ships with solid technical SEO, performance work and a content structure search engines can read, and that AI assistants like ChatGPT and Perplexity can cite. Deeper SEO and structured data work when a project calls for it.
Webflow gives you the best balance of design freedom, speed and control. Distinctive sites that load fast, and a CMS your team can update without a developer. If Webflow is the wrong fit for your project, we’ll tell you before we start.
Working with us
More people doesn’t mean more attention. On a bigger team the senior people pitch and the junior people build. Here they’re the same people.
We agree what the site is for before we design it: more enquiries, better-qualified ones, fewer support emails, whatever actually matters to you. Analytics are set up to measure that specific thing, so after launch you can tell whether it worked instead of guessing.
Ask, and we’ll show you what’s closest and be straight about where it isn’t a match. Work in your exact sector matters less than whether we’ve solved the same problem: a booking flow, a complex catalogue, a site that has to explain something difficult.
You’ll see the site as it’s built, on a live link, rather than getting a status report about it. There’s one senior contact and they get in touch when something needs you, not to fill a weekly slot.
The people you meet. It’s a small senior team with a single point of contact: no account managers, and nobody hands your project down to a junior after the pitch.
Then we haven’t understood something yet, and it’s better to find that out at v1 than at launch. We go back through it with you in detail and rework it. The first version exists precisely so this conversation happens early.
Real content, as early as we can get it. Lorem ipsum makes everything look fine and hides the problems: headlines that are twice as long as the design assumed, sections with nothing to say. If your content isn’t ready we’ll work with a realistic stand-in rather than filler.
It’s the single most common reason projects slip, so we plan for it rather than pretend it won’t happen. We’ll tell you what’s needed and when, and design around real structure so late content doesn’t stall the build. If it slips far enough to move the launch date, we’ll say so early rather than absorb it quietly and miss the date together.
Content, brand assets if you have them, and feedback when it’s asked for. The last one matters most, because projects slip on feedback far more often than they slip on build time. We’ll tell you up front where the decision points are so you can plan around them.
A short call, then a proposal. The call is mostly us asking questions about your customers, your goals, and what’s not working now. The proposal comes back with a defined scope, a fixed fee and a date. You’re not committed to anything until you sign it.
Cost & scope
Yes. The work is remote either way, and we’re in Amsterdam and happy to meet in person when it helps.
A kickoff, then a review at each design stage. A few hours across the whole project, concentrated at the start and at each round of feedback. You won’t be sitting in weekly status calls.
Two structured rounds, one on the first design and one on the full build, plus the small corrections at the end. That’s what the fixed fee is scoped against. If a round turns into a change of direction rather than feedback, we’ll say so and re-scope rather than quietly absorb it.
Fixing one part of a site you already like is a normal piece of work, not a favour. If it’s genuinely too small to be worth either of our time, we’ll say so and point you somewhere better.
We’ll price it and tell you before doing it. The fee is fixed against a defined scope, so a new requirement is a decision you make with a number in front of you, not something that turns up on an invoice later.
One part of a site you already like is usually one to three weeks. A full build from brand upwards runs eight to twelve. What sets the actual date is your deadline: a launch, an event, a funding round. We scope the work to fit it. You get the timeline in writing with the proposal, before anything starts, and we hold it. If the date you need isn’t realistic for what you’re asking for, we’ll tell you then rather than let you find out in week six.
Every project is different, so we don’t pull a number out of thin air. After a short call you get a proposal with a defined scope, a fixed fee and an honest timeline. No open-ended agency meter, no surprises halfway through.
Technical
Analytics and cookie consent are set up as part of the build and configured to be compliant by default, rather than retrofitted after someone’s legal team asks.
We build to sensible standards, including proper heading structure, keyboard navigation, colour contrast that passes and alt text on everything. If you need formal WCAG compliance to a specific level, tell us at the start: it changes some design decisions.
Yes, and it’s part of the build rather than something we optimise afterwards. Image handling, font loading and script weight get decided while the site is being made, because that’s when they’re cheap to get right.
Webflow hosting is billed by Webflow, not by us, and depends on the plan your site needs. We’ll tell you which plan and what it costs before launch so it isn’t a surprise afterwards.
Yours, in your own account, registered to you. If it currently sits with someone else we’ll help you move it. A domain you don’t control is the thing that makes leaving a supplier expensive, and it shouldn’t be.
You do. The design, the content and the Webflow project. You’re not renting your website from us, and you don’t need our permission to leave.
After launch
Yes, and you won’t need us to do it. The project sits in your account, so moving to another team or bringing it in-house is a permissions change, not a rebuild. We’d rather you stayed because the work is good.
Tell us and we’ll look at it. There’s a retainer for ongoing support, or we quote the job. Either way you’re not stuck waiting on a proposal to get a broken page working again.
Yes, before handover, on the actual site rather than a generic Webflow tutorial. The aim is that adding a page or updating a case study is something your team does in ten minutes without calling anyone.
Only if you want to be. Every site is handed over with your team trained on the CMS, so you can run it yourselves. If you’d rather not, there’s a retainer covering hosting, updates, new pages and the small fixes.