Expertise
Three services, not a catalogue. They follow on from one another naturally: we build, we operate, we equip your teams. Each can be bought on its own.
The most common arrangement: a scoping increment, then delivery increments of two to four weeks.
When the spreadsheet has hit its limit and no off-the-shelf software fits the business. Public front end, customer area, back office: a single coherent product.
Legacy application, supplier gone, debt piled up. We always start with a written assessment: what holds, what breaks, what it costs to keep.
Payment, invoicing, signature, transactional email, connections between existing tools. Webhooks are the source of truth, never what the browser displays.
Clickable screens, architecture, costing. Delivered in two to three weeks, and yours. You take them with you, even if you have the build done elsewhere.
Monthly fee, written scope, cancellable quarterly. No minimum term: if we are useful, you stay.
A delivered application is not a finished application. Certificates expire, dependencies age, volumes grow, laws change. Operations is the work you only notice when it isn't being done.
| Service | What it covers | Frequency |
|---|---|---|
| Managed hosting | Servers, certificates, domain names, firewall, containers, system updates. | continuous |
| Backups | Database and files, encrypted, off the production server — and actually restored once a quarter. | daily |
| Monitoring | Availability, application errors, disk saturation, stuck queues. Alerted before the client calls. | continuous |
| Fixes | Blocking defects handled first, security patches applied without waiting for the next increment. | as they arise |
| Operations report | What happened, what was fixed, what is ageing and will need attention. Two pages, readable. | monthly |
With our expertise, on your code, with your teams. By the day or as monthly support, on site or remotely.
Every team has tried. Few have gained anything lasting — because the difficulty isn't the tool, it is what you entrust to it, what you deny it, and the discipline that has to exist before it. That is exactly what we put in place.
What is entrusted to the tools, what never is, which data leaves under no circumstances, where human review sits. A written policy that is workable and enforceable — the document almost every team starting out is missing.
Tools installed and configured on your repository, conventions written down, systematic review, continuous integration that blocks, decisions recorded. Without that foundation, what AI mainly accelerates is the production of debt.
On your code, on your real tickets, not on an exercise. We work alongside the developers until they no longer need us — the only measure of success that counts.
Half a day a week or a fortnight: decisions, review, unblocking, and the architecture review that keeps things on course. The most effective arrangement when the team already exists and what it lacks is technical direction.
Straight talk
Saying no early costs a conversation. Saying no late costs a project.
Invoicing
Two to three weeks. Deliverables: clickable screens, written architecture, breakdown into increments, a cost for each increment. They are yours to keep, whatever happens next.
Fixed amount, stated before we start.
Each increment is costed and approved separately, on the basis of the scoping. You can stop between two increments: what has been delivered already works.
Invoiced on delivery of the increment.
Written scope, hosting costs passed on to the last franc, with no hidden margin. Cancellable quarterly.
No minimum term.
Rates in CHF, excluding VAT. A written quote every time; no work starts without a signed order.
Describe the need in three lines; we reply within two working days, candidly.
Get in touch