FAQ
Straight answers.
What we build, which AI models we use, what happens to your data, how we price work, and what happens if you are not satisfied. If your question is not here, ask it directly.
About Vuewer
Who is behind Vuewer?
Vuewer is a boutique engineering studio run by Alexander (Sander) van Hooff, its founder, designer and web engineer. You work with him directly, from the first call through to handover. Our clients are predominantly other development companies, marketing agencies, and businesses that need help with their digital projects.
Where are you based?
We are based in the Alicante region of Spain and work with clients across Europe, mostly in the Netherlands, Belgium and Spain. Everything is set up to work remotely, and has been since 2015.
Which languages do you work in?
English, Dutch and Spanish. Projects, documentation and code review can be run in any of the three.
AI
What kind of AI features can you actually build?
Retrieval-augmented search over your own content, document and email extraction, generation and summarisation inside existing workflows, and multi-step agents that complete real tasks. In practice that means a support assistant that answers from your documentation, a pipeline that turns incoming invoices into structured data, or an agent that drafts work and hands it to a human to approve.
Which AI models do you use?
Mostly OpenAI and Anthropic models, chosen per task rather than per project. Some work runs better and cheaper on a small open model, and we will tell you when that is the case. We build so the model can be swapped without rewriting the feature, because the best option changes every few months.
What happens to our data?
Your data stays in your infrastructure and is sent to a model provider only for the specific request that needs it. We use business API tiers where the provider contractually does not train on your data, and we can run entirely on self-hosted models if your compliance requirements demand it.
How do you stop it from making things up?
By grounding answers in your own data, citing the source of every claim in the interface, and building an eval set before building the feature. The eval set is a list of real questions with correct answers that runs on every change, so accuracy becomes something you can measure rather than something you hope for.
When is AI the wrong answer?
When a deterministic rule would do the job, when there is no data to ground the model in, or when the cost per request does not work at your volume. We would rather tell you that in the first call than six weeks into a build.
How long does an AI feature take to build?
Three to six weeks from first call to a feature your users can use, for a well-scoped first feature. Week one is discovery and building the eval set, week two is the build, week three is hardening and shipping. Larger or more integrated work takes longer, and we will say so before you commit.
Working together
How do we start?
One call, then a written scope with a fixed price. If the scope is unclear we will suggest a short paid discovery to make it clear, rather than guessing at an estimate that neither of us can trust.
How do you communicate during a project?
A single direct channel with Sander, weekly progress on a staging URL you can click through, and a video call whenever something needs discussing rather than typing. No ticket queue, no account manager relaying messages.
What if I'm not satisfied?
Then we keep working until you are. We have a one hundred percent satisfaction guarantee, and in ten years we have never needed to argue about it. Weekly delivery is what makes that possible: problems surface in week one, not at the end.
Do you do design as well as development?
Yes. Interface and interaction design are done in-house, which is why nothing gets lost in a handover between a design agency and a developer.
Can you take over an existing codebase?
Yes, and it is a large part of what we do. We start with a paid audit: what state it is in, what it would cost to stabilise, and whether it is worth keeping. You get that assessment in writing whether or not you continue with us.
Pricing
Why not just hire a full-time developer?
Because a full-time senior engineer costs far more than the salary and takes months to find. With Vuewer there is no recruitment, no onboarding cost, no sick leave, no holiday cover, and no commitment beyond the current piece of work.
What does it cost?
Hourly work is €95 per hour. Websites start at €1.499, custom web applications at €4.999, and a three-week AI feature sprint at €7.500. Ongoing retainers start at €1.950 per month. Every project gets a fixed price in writing before it starts.
Do you work on a fixed price?
Yes, for anything with a clear scope. If the scope is not clear yet, we do a short paid discovery first and then fix the price, which is a better outcome for both of us than an estimate that quietly doubles.
Technical
What technology do you build with?
Laravel and PHP on the back end, with Livewire, Alpine.js and Tailwind CSS on the front end. For AI work, the OpenAI and Anthropic APIs, plus Postgres or a dedicated vector store for retrieval. We choose a short list we know deeply over a long list we know slightly.
Where do you host?
Laravel Cloud, Hetzner or your own infrastructure, depending on requirements and where your data has to live. European hosting is the default.
Who owns the code?
You do, in full, on final payment. It lives in your repository, with documentation good enough for another engineer to pick it up. We do not build in dependencies on ourselves.
Do you handle maintenance after launch?
Yes, on an optional monthly retainer that covers dependency and security updates, monitoring, backups and a set amount of development time. Without a retainer we are still available hourly, just not on a guaranteed response time.
Get in touch
We'd love to hear from you.
Do you have a question or need help with a website or web application? Whether you are starting from scratch, refining what you already have, or stuck on something complex.
Fill in the form and we'll get back to you as soon as possible.