AI that runs
without you

Questions

What people ask

• How do we start?

  Start by email. For a low-risk first step, discuss the €900 AI-visibility audit — fixed scope, delivered in 5–10 business days. For a larger project, four short questions prepare your email draft. After you send it, the engineer replies in writing within one business day. Questions, proposal, scope and agreement are handled by correspondence. A signed contract and NDA precede work beyond the audit; the public-source audit needs neither.

• How does payment work?

  Fixed prices, split into milestones — typically 30/40/30 — so your prepayment never exceeds one milestone. Payment by bank transfer against an invoice; the account details and the currency are on the invoice. Invoices carry no VAT — EU and UK clients self-account for it under the reverse charge, with your VAT ID on the invoice; other jurisdictions owe none, and your finance team already knows this pattern. Monthly retainers are invoiced monthly and can be cancelled any month.

• How long do projects take?

  The audit: 5–10 business days. A RAG assistant pilot: three weeks. A website: three to five weeks. A self-hosted AI deployment: four to six weeks. The date is written into the contract next to the price — and if a date moves for a reason on my side, you hear about it before it moves, not after.

• What about revisions and change requests?

  Every package states its scope up front, so 'is this included?' has a written answer before it's ever asked. Anything beyond the written scope gets a quote before the work happens — never a surprise line on the invoice. Fixed price only works when the scope is honest in both directions.

• What if I'm not happy with the result?

  Each rung has its own answer, in writing. The audit: if the report shows you nothing you can act on, you don't pay. The RAG pilot: we define an acceptance test together before work starts — fail it, and the final milestone isn't due. Websites: the Lighthouse target is contractual. Everything ships with a 30-day post-launch warranty, and milestone payments mean you never paid ahead beyond one step.

• Who owns the code, the model and the data?

  You do — all of it, in full, on final payment. The stack is deliberately standard and open (Astro, llama.cpp or vLLM, pgvector or Qdrant), the server is registered in your name, and the handover pack — documentation, runbook, credentials in your vault — is part of the deliverable, not an extra. Your data stays on infrastructure you control — that is the architecture, not a promise. What access I hold to it, and for how long, is a separate matter and it is agreed in writing before the work starts, rather than left to be inferred from that sentence.

• You're one person. What happens if you're unavailable?

  The honest answer has two parts. Day to day: I reply within one business day in EU hours, in writing — a promise one engineer can actually keep, unlike a badge that promises more than any one person can deliver. Long term: every system is documented, runbook'd and built on standard components precisely so your own IT can take it over at any moment. The systems are designed to run when I can't be there — that has been the engineering rule here for a decade.

• Do you work European hours? Where are you?

  Gyumri, Armenia — GMT+4. My working afternoon overlaps EU and UK business hours. Briefs, questions, deliverables, scope and approval move through correspondence. Cross-border contracts have an English-law option; invoices carry no VAT under the published terms, and communication is in writing.

• Is VKVstudio a real business — and is it an agency?

  A registered sole proprietorship in Armenia since February 2026, with full registration and tax details in every contract and invoice. Not an agency — one engineer, on purpose: the person you talk to is the person who builds, and nothing is subcontracted behind your back. The Trust & Process page spells out the paperwork, the payment mechanics and the liability cap in advance.