Clear answers
before we start.
Practical answers on pricing logic, scope, timeline, compliance, and post-launch ownership.
Why do you build custom websites instead of WordPress or Webflow?
Voiceless builds from scratch with frameworks like Next.js or Nuxt because plugin chains increase security and maintenance risk. Custom code removes plugin attack surface, performs faster, and gives full ownership for long-term product evolution.
What is your typical project timeline?
Direction Sprint projects run in about 2 weeks, Signature Sites in 5-8 weeks, MVP builds in 8-12 weeks, and larger platform builds in 3-6 months. Final timing depends on scope depth, integrations, and stakeholder response speed.
How much does a project cost?
Projects start at the equivalent of EUR 18,000 and scale with complexity. Final pricing depends on scope, integrations, and delivery roadmap. The pricing page shows starting points for each engagement tier.
How are payments structured?
Standard engagements follow a phased model: 20% deposit, 40% after design sign-off, and 40% at launch. Projects under the equivalent of EUR 20,000 use a 50/50 structure.
Can you work under NDA and confidential delivery constraints?
Yes. NDA-constrained delivery is standard. Public case notes are written to protect confidential product and business details where required.
Do you include SEO, accessibility, and performance work?
Yes. Every build targets Core Web Vitals, semantic structure, metadata quality, and WCAG 2.2 AA implementation. We treat performance and accessibility as revenue and risk controls, not optional polish.
What happens after launch?
You can continue through a retainer for iteration, experiments, new feature delivery, and ongoing performance and accessibility hardening. Launch is version 1.0, not the end state.
What do you need from us to start?
One clear decision-maker, business goals, realistic budget range, and response discipline. Faster approvals and clear ownership reduce delivery risk and protect timeline quality.