The story in three sentences

What changes for Simon.

The problem
The supplier promises “next quarter”, the budget shrinks and demands grow. Simon forwards e-mails.
The turn
Requests from across the company go to Omnisnap as tickets. Simon talks them through with the business teams, and engineers build.
The result
Old Excel sheets become web apps, quotes that took months become afternoons. IT becomes the place where things get made.

Simon · head of IT

The story, chapter by chapter.

For reading rather than watching: each chapter of the film as a short text.

Chapter 01The problem

A year earlierSimon did not go into IT to pass tickets along.

214 open tickets, a budget sheet in the red, an e-mail from the supplier: “Q3 2027”. When everything runs, nobody notices. When it doesn’t, Simon’s name is on it. And because everything takes too long, staff copy customer lists into outside AI tools. In the end, IT cleans up.

Corridor · 10:15

Tom I quickly pasted the customer list into an AI tool. Way faster!

Simon Which tool? And where is the data now?

Tom No idea … somewhere in the US? 😬

Simon Okay. We'll clean that up — and build it for you safely, in-house.

Faster isn't always safer.

Chapter 02The turn

Hans’s spreadsheetAn Excel file from 2009 becomes a web app.

Hans has done the month-end close in the same spreadsheet since 2009. In March he retires. Simon submits the spreadsheet as a ticket. The next day it runs as a web app with roles, history and export. Hans gets a leaving party instead of a panicked handover.

“The spreadsheet becomes a proper web app. And Hans gets a party instead of a panic.”

Simon, head of IT

Chapter 03The turn

A voice noteThe paper slips in the warehouse disappear.

In the warehouse Simon has an idea and records it as a voice note: scan the label, booked, done. The AI turns it into a requirement and an engineer builds the scanning flow. The first trial runs.

Solving it together

Sandra explainswhat her team needs

Talk

Simon thinks alongat the same table

precise

Omnisnap AIrequirement & build

deploy

Livethis very week

You deliver before others have finished writing their ticket.

Chapter 04The turn

The quoteCHF 80,000 and nine months for one change to the CRM.

That was the previous supplier’s offer. Through Omnisnap the same change is live that same afternoon, reviewed by an engineer under the four-eyes principle and reversible at any time. Simon turns the quote down.

“Live this afternoon. And the quote: declined.”

Simon, head of IT

Chapter 05The result

In love againSimon builds the onboarding himself.

Accounts, laptop and access on the first working day: Simon puts the process together himself in Flows. #it-support now fills with hearts instead of complaints. IT that managed costs becomes IT that creates value.

Team chat · Thursday

Sandra The new approval is already live? I only mentioned it on Tuesday.

Simon We looked at it together and built it right away.

Sandra You're honestly the fastest department in the building. ★★★★★

Simon And now we get to the big ideas.

The dependency loop is broken.

The platform behind it

What keeps Simon in control

Simon hands over the building, not the responsibility for his systems. Every change takes the same reviewed path into a private cloud in Zurich.

Modules instead of legacy systems

Spreadsheets, isolated solutions and supplier software become modules on one platform, with your source code.

Flows for your own processes

Onboarding, approvals, requests: processes your team puts together itself, with AI that works alongside.

Reviewed and reversible

A named engineer reviews every change, and you sign it off on staging. A rollback takes minutes.

Operations without maintenance windows

Private cloud in Zurich, 3 zones, immutable images. No maintenance windows. Larger migrations are announced weeks in advance.

Simon no longer passes tickets along. He solves problems.