From prototype to production - Your proof of concept works in the demo. We get it ready for production.

Many organizations already have an AI prototype: a proof of concept from an innovation project, from an agency, or from their own IT. It convinced people in the demo. But nobody signs off on it for daily use, because the questions that decide a go-live were never part of the project.

We take the prototype as it is and check it against four questions. Is it secure? Does it respect data protection? Are the answers good enough, and how do you know? Does it fit into your systems? Then we fix what is missing and operate the result for a fixed monthly fee, which we quote after the review.

What we deliver - Practical outputs, not generic AI strategy

  • Security check. Access rights, authentication, the handling of passwords and keys, software dependencies, and what the AI model is allowed to do in your systems.
  • Data protection check. Which data goes where, where it is stored and processed, and what that means under nFADP and the rules of your sector.
  • Evaluation of answer quality. A test set built from your real cases, so you can see how often the system is right, where it fails, and whether a change makes it better or worse.
  • Integration check. How the prototype connects to your systems, logins, and data, and what is missing for it to run without manual workarounds.
  • What we fix. You get a written list of what we found, ordered by risk. We close the points that stand in the way of a go-live and tell you which ones can wait.
  • Operation for a fixed monthly fee. Hosting in Switzerland, monitoring, updates, and support. We quote the monthly fee after the review, when both sides know what the system needs.

Best fit - Who this service is for

  • Organizations with an AI pilot or proof of concept that worked in the demo but never went live.
  • Teams whose prototype was built by another supplier, by a project team, or by their own IT, and who now need someone to take responsibility for running it.
  • IT and security leads who have to approve the go-live and need the open points documented and closed.
  • Organizations that must keep their data in Switzerland and need to know where the prototype actually sends it.

Typical architecture - Designed for reliability, grounding, and operational handover

The exact stack depends on the problem, but these are the design principles we usually optimize for.

  • Keep what works. We build on the existing prototype wherever its foundation is sound, and say clearly where a rebuild costs less than a repair.
  • Measured, not assumed. Answer quality is tested against real cases before go-live and again after every change, so quality is a figure and not an impression.
  • Human approval where it matters. Sensitive steps need a person’s approval, every action is logged, and access is limited to what the task needs.
  • One team from review to operation. The engineers who check and fix the system are the ones who run it afterward, so nothing gets lost in a handover.
  • An honest result. If the prototype is not worth taking to production, or an existing tool does the job, we tell you after the review.
  • Swiss-aware hosting choices. We select hosting regions, providers, and logging setups with Swiss data protection, nFADP, and sector-specific requirements in mind.

FAQs - Questions we hear early in the conversation

These are the kinds of questions that usually matter before a team commits to scope, architecture, and rollout.

We did not build the prototype with you. Is that a problem?

No. This service exists for exactly that case. We start with a review of the code, the infrastructure, and the operational risk, and tell you what we found before any further work begins.

What does it cost?

That depends on the size and state of the prototype, so we do not publish an amount. You get a fixed price for the review before we start, and the monthly fee for operation is quoted after the review.

Do you rebuild everything?

Only where it is necessary. We keep what is sound and replace what would be unsafe or unmaintainable in production. If a rebuild costs less than a repair, we say so and explain why.

Can our own team run the system afterward?

Yes. If you prefer to operate it yourself, we hand over the corrected system with documentation, runbooks, and training.

Where is the system hosted?

In Switzerland by default. We choose the provider and region with you, based on data residency, nFADP, and the rules of your sector.

Related proof - Case studies, articles, and next steps

If this is close to what your team needs, these pages are the best next places to look.

Hosting and maintenance

What operation covers once your system is live: hosting, monitoring, patching, backups, and support.

AI agents for your workflows

No prototype yet? Start with a workshop, a pre-study, or a six-week pilot at a fixed price.

Request a review

Start with a short conversation about your prototype, who built it, and what is holding up the go-live.

Which workflow should we start with?

Our office

  • HQ
    Hohlstrasse 206
    8004 Zürich, Switzerland