We develop new software and modernise existing systems so they operate reliably, fit their environment and can be evolved by your team.
Software engineering turns a real workflow, decision or service into software people can rely on. Good software not only does the job today; it remains understandable, operable and safe to change as the organisation moves on.
Nuitio develops new software and adapts existing systems to the way your organisation actually works. We take responsibility from clarifying the outcome through implementation and hand over a system your team can run and continue to improve.
Once the work and desired result are clear, software can take shape around the way your organisation actually operates. The examples below make that possibility tangible and provide concrete reference points for identifying where a focused software outcome could improve day-to-day work.
Important steps run through spreadsheets, email and manual checks when standard software does not reflect how the operation actually works. We model the workflow with your team and develop the application around clear interfaces to existing systems, so ownership of operation and further development can remain with the team.
Outdated components are replaced while data remains consistent and essential functions continue to work reliably. We map dependencies, capture the behaviour that must be preserved in characterisation tests, and implement the modernisation path in reviewable stages.
Tasks, photos and sign-offs still have to be recorded when connectivity drops at the point of work. We design local storage, synchronisation and conflict handling around the workflow, then test connection changes and failure cases before rollout.
Below is a selection of work by Nuitio and earlier projects by our founders.
Nuitio developed the in-house platform to cover the complete lifecycle of quantitative trading strategies in one system. Built from the ground up with its software delivery pipeline, it connects research and validation with execution and operations.
For a bank, the project extended an existing online-banking portal across web, iOS and Android without redeveloping its core functions for each channel. Reusable components kept customer access, communications and analytics consistent across all three.
A bank’s digital-banking division wanted to divide an existing online-banking platform into smaller, independently changeable applications without replacing everything at once. The hub gave new applications one shared integration point, reusable functions and documentation for development teams.
For a bank, the project brought banking functions and services from several systems into one online portal. It also established the internal tools and processes needed to keep developing and releasing the portal.
For a large Swiss bank, the project moved an established desktop CRM to the web. It replaced the interface, migrated the existing data model and implemented, tested and documented the CRM processes.
Send Fabian a short note about what you have in mind. In an initial conversation, we discuss the project and possible next steps.
MSc Computer Science, ETH Zürich · MAS MTEC, ETH Zürich
