Kansoft AI Sprint

AI that runs after six weeks — instead of being presented.

A fixed-scope, fixed-price pilot on one defined process. What you have at the end is a working application running on your own data, not a slide deck.

CHF 12'500 4–6 weeks Fixed scope and price

* Price is part of our launch campaign.

30 minutes, no obligation · Swiss point of contact · you own the code and hosting

Why pilots stall

Most AI pilots end as a presentation.

01

The use case is too big

Something meant to cover everything cannot be finished in any sensible timeframe.

02

There is no path to production

A prototype on synthetic data says nothing about whether the system holds up in operation.

03

The vendor ends up owning it

If you do not own the code and the environment, you negotiate the next step from the weaker position.

The sprint in detail

What is fixed before we start.

The five points below are the offer, not the small print.

Scope
4–6 weeks · fixed scope, fixed price
Outcome
A working application on your own data — not slides
Acceptance
Success criteria and acceptance points are fixed during scoping
Ownership
Code and hosting stay with you — no lock-in
Who you work with
A Swiss point of contact; your teams choose the process
For comparison

What separates a sprint from a typical pilot.

The right-hand column is what the offer says. You can have every line of it written into the scoping document.

Criterion Typical pilot Kansoft AI Sprint
Scope Negotiated as the project runs Written down before the start
Price Time and materials, open-ended Fixed, known up front
Duration Open-ended 4–6 weeks
Data Synthetic or sample data Your own data
Outcome A presentation and a recommendation A running application
Code Stays with the vendor Yours from acceptance
Hosting Open Your environment, Switzerland or EU
How it runs

Three steps to a running application.

01 30 minutes

Scoping call

Together we find a process narrow enough to solve in six weeks.

→ One chosen process

02 Before kickoff

Fixing the terms

Scope, success criteria and start date are written down before anyone builds.

→ Fixed scope and price

03 4–6 weeks

Sprint

Built on your data, in a shared environment that you and we have the same real-time access to.

→ A running application, code yours

Where it applies

What a sprint is good for.

Six areas we have shipped to production in. Which one holds up in your case is what the scoping call is for.

AI strategy and consulting

Readiness, use-case selection and a sequence ordered by return.

AI agents

Agents with deterministic guardrails — for approvals, procurement and documents.

Generative AI

LLM integration, retrieval architectures and evaluation of what comes back.

AI-assisted delivery

AI at every stage of development — from requirements through to release.

MLOps and infrastructure

Deployment, monitoring, drift detection and scaling in operation.

AI integration

Connecting to CRM, ERP and the core systems your data already sits in.

Proof

AI in production, not in a lab.

13
AI systems shipped to production in the past twelve months
25–30
Kansoft engineers at Palisis AG, for five years
18
years of engineering experience in the Kansoft group
Palisis AG

«An invaluable software partner over many years.»

Josef Birchler, CEO, Palisis AG

Six workstreams across a multi-year partnership — from a full front-end rebuild during live operation to a GenAI chatbot in production. See the case studies

ISO 27001 · Certified ISO 9001 · Certified SOC 2 Type II · Report revDSG · Aligned GDPR · Aligned PCI-DSS · Aligned
About the price

Why the price is what it is.

Kansoft is building its presence in Switzerland and, as part of the launch campaign, subsidises selected entry projects to do it. The figure is a contribution to costs, not a market rate. What you are testing over six weeks is not the price — it is whether we deliver.

CHF 12'500

* Price is part of our launch campaign.

Included in the price

Duration
4–6 weeks
Scope
One defined process
Outcome
A running application
Ownership
Code and hosting yours
Common questions

What clients ask first.

What happens after the sprint?

Nothing automatically. You have a running application, the code and the environment. Whether it becomes a project is your decision afterwards.

Who owns the code?

You do, from acceptance onward. It is hosted in your environment. There is no licence and no dependency tying you to us.

Where does our data sit?

In Switzerland or the EU, as you specify. Access is granted by role and logged; who can see which data is written down before the start.

Who do we work with?

Your point of contact is in Switzerland and stays the same beyond the sprint. The build happens in the engineering hubs in Pune and Udaipur, with overlap into CET hours for same-day coordination, reviews and demos.

Thirty minutes is usually enough to find the first process.

No proposal up front, no obligation. We look at which process fits — and whether a sprint is worth doing at all.