Frequently asked questions

Most projects are fixed-price once we’ve scoped the work: you know the price before anything starts. Longer engagements (maintenance, part-time IT lead, ongoing development) run as a monthly agreement. Hourly billing (60 €/h + VAT) is only for smaller changes and short consulting calls.

A website typically takes 1–14 days, a larger web app or SaaS build 8–12 weeks. Exact timelines depend on scope and how ready your content or design is at the start.

Fair question. Code, documentation and infrastructure access always stay under your own control, never locked to me personally. For larger projects we agree on a documented handover, and I can bring in a second developer as backup if needed. And leaving you without an answer is the last thing in my interest: my business runs on happy clients and their referrals.

You do. All code, licences and infrastructure access belong to the client: no hidden dependencies, no services registered under my name that your business would end up depending on.

Yes, as an option. Maintenance and SLA support run as a separate monthly service: security updates, backups and incident response. It’s not mandatory, but most clients choose it rather than monitoring things themselves.

When it matters, AI features are built on self-hosted models running on your own server or a chosen cloud: data never goes to a public third-party API. That’s a deliberate architectural choice, not a default assumption, and we discuss it at the start of every project.

Yes. Most communication already happens remotely: video calls, written documentation and asynchronous updates work fine across time zones. Estonia remains the core market, but geography isn’t a limitation.

On fixed-price projects, scope changes are a separate, explicit conversation: no surprise invoices. If I hit complexity that wasn’t visible at the start, we talk about it right away, not on the final bill.