Skip to content
arthova

Frequently asked questions

Honest answers to the questions everyone asks.

Proposals, duration, ownership, operations — here is what you would otherwise ask in the intro call.

We only need a website or a small project. Is that a fit?

Yes. A website, a landing page or a clearly scoped workflow can be a standalone engagement. We agree the outcome, scope and one-time project fee before work begins. You do not need to book an AI Workshop or ongoing care. AI is included only when it is useful for the task.

Do we have to take out a subscription after the website?

No. You receive the agreed website and handover. Monthly website care is a separate offer with a defined scope, fee and term. Domain, hosting and any licences can still incur recurring costs without a care plan; we list them separately. The AI Partnership and its minimum term apply only if you explicitly commission it.

Do we already need to know what we want to build?

No. Your idea, an open question or an everyday example is enough. If you already have a plan, brief or prototype, we build on it directly. You do not need a workshop or the Workflow Check before an intro call.

We already have an idea. Can we start from there?

Yes. We discuss your project and review the foundations you already have. If the objective, technical feasibility, value, responsibilities and acceptance criteria are clear, implementation may be the right starting point. You do not have to go through all five services.

How do we keep cost and scope under control?

Before each engagement, a binding proposal sets out the scope, acceptance criteria, timeline and total investment. You decide whether to continue after seeing the outcome. You do not have to commit to the entire project at the start.

Do we have to replace our systems?

No. We first examine how the solution can fit into your existing systems and workflows. A platform change is not automatically part of the work; the key question is where impact needs to happen in daily operations.

How long until something is running?

For websites and focused projects, we agree a timeline based on the scope and available content. For AI projects, the Audit takes 2 weeks, the Blueprint 3–4 weeks. Implementation happens module by module: each module goes live individually and is measured — you see impact per module, not only at the end of the project. We deliberately do not quote a blanket total duration: it depends on your processes, and invented numbers are not our style.

Who owns the code and the data?

You do. Always. All code created specifically for your project and all of your data belong to you — with no technological dependency on Arthova, no vendor lock-in. It is one of our five principles and it is written into the terms and conditions.

What happens after go-live?

For a website, you receive the agreed handover. You can maintain it yourself, appoint another specialist or arrange monthly care with us. For live AI systems, we offer the AI Partnership: operations, monitoring, quality checks and model updates, with a minimum term of 6 months. It is a separate service, not a requirement for a website project.

Can we stop after a stage?

Yes. You commission only the service you need and decide again afterwards. Implementing an AI system requires a clear and approved business case, architecture, scope, responsibilities and acceptance criteria. Your existing work can provide these foundations; a separate Blueprint engagement is not automatically required.

What does the delivery promise mean in practice?

Before work starts, scope and acceptance criteria are recorded in the written proposal. If those criteria remain unmet for reasons attributable to Arthova after the agreed remediation, we refund the fee for the affected stage under the agreed guarantee terms. The promise covers our delivery — not unknown future P&L effects, missing client-side cooperation or external disruption.

What if no potential shows up in our company?

Then we say so. If we see no added value, we do not recommend AI — that is the rule we work by. In that case the Audit ends with an honest executive summary instead of a sales pitch.

Who is Arthova not right for?

Before an integration project, the workflow, measurable objective and accountability need to be clear. Where these foundations are missing, we prepare them first or recommend waiting. The Workflow Check helps you find a practical next step for one specific workflow.

Didn’t see your question?

Ask it directly — via an intro call or the contact form.