The typical client
An SME from Germany, Austria or Switzerland that needs its own application: a customer portal, an ordering or service application, an internal tool that lives in Excel today, or a business application replacing old industry software. There is no in-house development team, or it needs relief.
What you have after six weeks
A reviewed requirements specification with user stories, acceptance criteria and measurable quality requirements. A clickable prototype of the key flows, tested with your users, and an architecture with documented decisions. A first increment with up to five user stories, each with automated tests against its acceptance criteria, and a pipeline that builds, tests and delivers on every change. The application in production with monitoring and backup, an operations manual and a fixed price for the next increment.
Secure operation from day one
For us, operation means more than the application being up. Every dependency is checked for known vulnerabilities before it is used, and we adopt new package versions only after seven days, so compromised releases do not slip through unnoticed. We produce a software bill of materials (SBOM) for the software we deliver. Updates arrive automatically as pull requests and go through the same tests and reviews as any other change. Every pull request is scanned for accidentally committed credentials; passwords and keys live in a secrets manager, never in the code. The runtime environment is checked continuously against security baselines, and security-relevant events flow into a SIEM. We back up databases continuously and rehearse the restore regularly, because a backup only counts once the restore has worked.
How we work
AI agents write a large share of our code. People decide, review and approve: every change has a ticket with acceptance criteria, every user story brings its tests, and no pull request is merged without a green build and a review by a person who did not write the change. A ticket is done only when the change runs in production. Tickets, pull requests, tests and deliveries are visible to you at any time.
How our own products are built
Our own products are built exactly this way, among them ClearSky (Spring Boot and Angular), our CRM (Rust and Angular) and our operations console (Rust and Angular). Design happens in Penpot; colours, type and spacing flow into the code as design tokens, and an automatic check reports when design and code drift apart.
Yours from day one
Source code, design, documentation and configuration belong to you and live in your repository. The software runs on your infrastructure, with a provider of your choice in Switzerland or the EU, or on our platform. You can take over yourself or switch providers at any time.
Four phases, six weeks
Week 1: requirements analysis
Interviews, system context, user stories with acceptance criteria, quality requirements. On Friday you decide: continue, or stop with the finished specification.
Week 2: design
Clickable prototype, test with your users, architecture and architecture decisions. You approve the design.
Weeks 3 to 5: implementation
The first increment is built story by story, with tests and reviewed pull requests. Weekly demo on the running system.
Week 6: secure operation
Delivery to production with monitoring, vulnerability scanning, automatic updates and backup with a tested restore. Acceptance against the acceptance criteria, handover.
Frequently asked questions
What does the Software Sprint cost?
We quote the price on request, as a fixed price after a first conversation about your project. It is fully credited if you continue development with us.
What if we do not want to continue after the requirements analysis?
Then you stop after week 1 at a partial price agreed in advance and keep the reviewed specification. You can continue with it yourself or put it out to tender.
What if the project is bigger than five user stories?
We capture the requirements for the whole project. The most important increment is built first; for each further one we quote a fixed price.
Who runs the software afterwards?
You decide. Your team takes over with the operations manual and documentation, or we run it with on-call support, price on request.