FAQ
Questions people ask before a first call.
Short answers. If yours isn’t here, ask it in the brief.
About the studio
What is SIMONVILSTECH?
An independent digital experience and growth engineering studio founded by SIMONVILDONELOHIM. We design and build websites and digital products, including real-time graphics in WebGL, and the systems around them that bring and convert customers: search, local presence, ads, calls, booking, analytics and automation.
Who do you usually work with?
Companies with something that takes explaining (technology and product companies, studios and professional firms), local businesses that win customers by search, phone and booking, and agencies that need a WebGL or frontend developer for a project.
Why are there no client logos?
Because we haven’t published any client work yet, and we won’t imply that we have. Everything under Work was built by the studio itself: its own products, prototypes and demo builds for fictional brands. Each page gives the project’s status and says what is a demo.
The projects show how we design and build, recorded from the running code. They don’t show business results, and we don’t present them as if they did.
How big is the studio?
An independent studio with no large team behind the name, and no pretence of one. The founder directs every project and is accountable for what ships. AI agents carry much of the research, building and testing under that direction, which is why the studio moves faster than its size suggests. When a project needs other skills (copywriting, 3D modelling, a specialist back end), specialists join for that part and are named in the proposal.
Services
What do you actually deliver?
Designs and working code. Depending on the project that can include the sitemap and page templates, the interface and motion design, a design system, the frontend build, WebGL scenes, CMS integration and the launch. Services has the detail.
Can you just design, or just build?
Yes, either. If we build from your designs, we’ll point out anything that will be slow, inaccessible or hard to maintain before it’s built, not after.
Do you work for agencies?
Yes. You bring the client and the concept, we build the WebGL, motion and frontend, under your name or ours, as agreed in writing.
Do you build AI agents?
Yes, inside systems with clear limits. The AI receptionist answers calls from information you approve, review replies and content are drafted for a person to approve, and in automation a language model handles the steps that need judgement while a person reviews what it is unsure about.
None of it has run for a client yet, and we say so. A first project is a small pilot with a fixed scope.
Projects
How big or small a project do you take?
Anything from one launch page to a full company site or an interactive product page. Small fixes are usually quicker for your own team. Very large platform builds may need a bigger partner, and we’ll tell you early.
Do we need a full redesign?
Often not. A short audit (content, structure, speed, accessibility, the code) shows what is worth keeping. See website redesign.
Process
How does a project run?
In six phases: discover, define, design, engineer, launch, evolve. Each one ends with something you review and approve. Approach describes them.
What happens after I send a brief?
We read it, ask about anything missing, and if it looks like a fit we suggest a call to scope it. If we’re not the right studio, we say so and, where we can, suggest who might be.
How much of our time will it take?
Most at the start and at each review. Between reviews it’s our job. One person on your side who can make decisions saves more time than anything else.
Timeline and price
How long does a website take?
It depends on the scope, and even more on whether the content is ready. The studio works in short cycles: AI agents take on much of the research, building and testing, and a person reviews every step, so a working version comes early and improves from there instead of arriving after months of documents.
We give a dated plan once the scope is agreed, not before, and we do not promise a date the scope cannot support.
We have a fixed date. Can you hit it?
Tell us the date in the brief. If the scope fits, we plan backwards from it. If it doesn’t, we’ll say what can realistically go live by then.
How much does it cost?
We quote after scoping, against a written scope. There is no price list because two “websites” can differ by a factor of ten. The brief asks for a rough budget so the proposal fits it; “not sure yet” is a fine answer.
Fixed price or day rate?
Fixed price when the scope is clear. Time and materials for open-ended work such as prototypes or ongoing iteration. The proposal says which and why.
Technology
Which technologies do you use?
HTML and CSS first, then JavaScript or TypeScript, static generation where we can, and WebGL (Three.js or our own GLSL) and GSAP when real-time graphics or motion are worth their weight. Technology explains the choices.
Can we edit the site ourselves?
Yes, if you need to. Some sites are best kept as content in code (this one is); others need a headless CMS. We recommend one after seeing who edits what, and how often.
Won’t WebGL make the site slow?
It can, which is why it loads after the content, draws less on weaker devices, stops when it is off screen and becomes a still image for people who prefer reduced motion. The page works without it. How we budget for it.
Will the site rank well?
Nobody can promise rankings. What we can do is build the parts we control properly: content in the HTML, one clear topic per page, structured data that matches the page, internal links, redirects from old URLs, and fast pages.
Is accessibility included?
Yes, it’s part of every project. We work to WCAG 2.2 AA and test with automated checks, the keyboard and a screen reader.
Hosting and security
Where will the site be hosted?
Wherever suits you. We usually recommend static hosting on an edge network such as Cloudflare Pages, Vercel or Netlify, but we can deploy to your own infrastructure.
How do you handle security?
Mostly by keeping the surface small: static pages, few third-party scripts, current dependencies, security headers, validated form endpoints, and only the access we need to your accounts.
After launch
Who owns the code and designs?
You do, once the project is paid for, as the contract sets out. Open-source libraries keep their own licences, which we list at handover.
What happens after launch?
We watch the first weeks closely, fix what comes up, then improve from what visitors actually do. Ongoing work can be a retainer or per request. Either way the code is documented, so another team could take over.
Do you offer ongoing support?
Yes, scoped per project: content and dependency updates, performance and accessibility checks, new pages or features. The terms are in the proposal.
Working remotely
Do you work with companies abroad?
Yes. We work remotely, in English or French, with written updates and scheduled calls that suit both time zones.
Can you build a multilingual site?
Yes. That means language-specific URLs, translated metadata, hreflang tags and a content workflow per language, so we plan for it from the sitemap onwards.
Growth
Do you guarantee rankings, leads or AI citations?
No. Search engines, ad platforms and AI assistants decide what they show, and anyone who guarantees a position is guessing or buying something they shouldn’t. We build what we control properly, measure what happens with stated methods, and report it, including when it doesn’t work.
Whose accounts do you use?
Yours. Your Google Business Profile, ad account, Search Console, phone numbers and data stay in your name, and we get access you can remove at any time. Some connections also need an approval from the platform (Google reviews API access to Business Profiles, for example); until then the same work is done by hand, from the same rules.
Can you get us more Google reviews?
We can make sure every customer is asked, once, with a reminder, at the right moment, which is what most businesses don’t do. We never buy reviews, write them, offer anything in exchange, or ask only the happy customers: Google forbids all of it, and Canadian law treats fake reviews as deceptive marketing.
What is AEO?
Answer-engine optimization: making a business easy for AI assistants (ChatGPT, Gemini, Perplexity, Google’s AI answers) to understand and quote. It is mostly strict structure: a plain definition, services and areas named consistently, questions answered directly, and structured data. The audit scores it on any site.
Will you change our ad budget?
Never without your approval. The budget, its cap and every change are approved by you and written in a change log with the reason. The ad account and the media spend are yours; we don’t buy media on your behalf or mark it up.
Will callers know they are talking to an AI?
Yes. The receptionist says so at the start, says that the call is recorded and why, and offers a person or a callback. It answers in French first, then in the caller’s language. It does not make outbound sales calls.
Is it legal to record calls?
In Canada a call can be recorded with the consent of one party, but a business recording customer calls must say so at the start, explain why, and offer an alternative. Under Québec’s Law 25 the recording is personal information: we keep it only as long as you decide, and delete it on request.
How do you prevent double bookings?
The slot is held for a few minutes while the customer confirms, and checked again against your real calendar just before the booking is written. Holds for the same calendar are processed one at a time, so two people cannot take the same slot.
Does tracking mean cookies and pixels everywhere?
No. The event model is first-party and carries no personal data; this site uses no cookies and no third-party tags. Advertising platforms only receive what you choose to send them, with the visitor’s consent where the law requires it.
Still have a question?
Ask it in the brief — there is no obligation attached.


