Custom software
AI that takes the work off your hands.
The review that reads itself, the file that files itself. Built around the work your team actually does, and handed over with the keys.
What we build
Software the size of the problem.
Most companies do not need a platform. They need one careful piece of software that removes a task nobody should still be doing by hand.
The review that reads itself
A second reader for contracts, reports and filings. It marks what deserves attention, and it stays quiet about the rest.
The file that files itself
What arrives is read, sorted and put where your team already works. The register is kept without anyone keeping it.
A pipeline that reads what arrives
Email, portal and post are read and passed on in the right shape. The parts that need a person are handed to a person.
A worked example
Three days at a stand.
A stand is paid for long before the doors open, and it is staffed for the whole of the fair. It usually goes home with a bowl of business cards and a set of impressions nobody can reconstruct by the following week. The same three leaks appear at almost every stand, and each of them is a piece of software.
- The visitor who walks pastBoth people on the stand are already in conversation, so the next visitor slows down, sees nobody free and keeps walking. An agent on the stand greets that visitor, answers the plain questions and holds the thread until a person is free.
- The conversation nobody wrote downWhat was said stays in one person's head until the drive home, and by the following week it is gone. Every conversation is captured while it happens, in the words that were used, with the next step attached to it.
- The follow-up that leaves too lateThe generic mail that arrives a fortnight later is read as exactly what it is. Each follow-up goes out while the stand is still standing, written from what that visitor actually said.
What the research shows
- Leads lost without systematic follow-up80%
- Booth conversations never followed up44%
- Companies that follow up systematically20%
- The window before a conversation cools24 to 48 h
Published research on trade fair follow-up.
A stand is only where this is easiest to see. The same three leaks turn up wherever a day produces more contacts than an evening can answer, and the same three pieces of software close them.
How an engagement runs
Scope, build, hand over.
Three steps, in order. Nothing is built before the first one is agreed in writing, and nothing is held back at the end.
- 01ScopeWe sit with the people who do the work and write down what the software has to do. You receive one page with the boundary of the work and a fixed price before anything is built.
- 02BuildWe build in short stages, and each stage runs on your own work. You see the software as it grows, and you can move the boundary while it is still cheap to move.
- 03Hand overThe code, the documentation and the accounts are registered in your name. We stay available for maintenance, and you are free to end that at any time.
The standard
Three things that do not change.
Engineered
Nothing here is vibe-coded. We build with AI at its speed, and we understand every line that ships: reviewed, tested, and built to scale.
Independent of any model
Your software runs on the best model available, with fallbacks in place and zero data retention where it matters.
Yours.
Built on site in Zürich. The data stays in your accounts, in your name. What is said in your rooms stays there, and no client is named here without their word.
Memorandum 01
Before a first conversation.
Before a first conversation, most people ask the same question about data. This answers it in one page: what happens to your data when a company uses AI tools, and what to ask a vendor before anything is signed.
Next step
Arrange a conversation.
You will hear back within one working day, from the person who would lead the conversation.
Custom software for your team · Fixed scope · Handed over · Arranged directly