We develop your custom software usable within a month,

The budget is built with you, from your numbers and your objectives: together we set the amount and the problem your application has to solve. Your application is usable within a month of development. From then on, the budget covers its maintenance and evolution for as long as you want, so that it keeps adapting to your business. Invoicing is monthly and fixed, with no surcharge for licences or number of users. You know your exact spend before you start.

A fixed-price project on a written specification freezes the scope on signing day; when the business need evolves, every adjustment goes through an addendum. Hiring in-house takes six to twelve months to recruit and onboard, and concentrates the knowledge of a role on a single person. This model replaces the estimate with a fixed monthly budget, a scope steered by delivered value, and a continuous delivery discipline written into the contract from day one.

In the first month, the first 15 working days are a trial period. Delivered features are accepted as they come in, by you or by us if you delegate acceptance to us. If you do not want the deliverables and do not wish to continue, no invoice is issued and you owe nothing. If you want your application in production before the trial period ends, you can ask us in writing: we issue the invoice for the days worked, and we release to production once it is paid.

It covers the behaviour of accepted and approved features, for the duration of the contract. If one of them starts behaving differently after a later modification to the application, we fix it at no extra cost and we lock the behaviour with an automated test. It does not cover change requests on existing features (that is an evolution), nor defects found during acceptance testing of a new feature (the feature is not yet delivered).

No minimum commitment duration. You can terminate the contract in writing at any time, without justification.

Software developers with the technical skills to cover the development process end to end: understanding your business, your information system and commercial objectives, aligning technical decisions with your strategy, specifying, developing, testing, deploying. When your project calls for it, we assemble a focused development team. Your developers understand your business, develop your software, and make the technical decisions on your project.

Each day, you decide your priorities: the next feature to specify, to develop, to deploy. We build it, then it goes through acceptance, by you or by us if you delegate acceptance to us. The scope adjusts day to day with what you learn from real usage.

Scrum, SAFe, ceremonies, sprints, estimates, release planning: these methods have become an industry in their own right. They often add bureaucracy where less is needed. They replace steering by outcomes with steering by velocity, and end up slowing down the teams they were supposed to accelerate.

We follow the Manifesto for Agile Software Development (do not be put off by its dated appearance). Sébastien Nobour, founder of DEVEDANOS, is co-signatory and certified by Dave Farley, the inventor of the deployment pipeline, on the Continuous Delivery discipline. Our DevOps culture means the same people who develop are also the ones who deploy and monitor in production.

Concretely, every modification goes through a deployment pipeline in three stages: fast verification (unit tests, type checking, static analysis), business validation (acceptance tests), and quality control (performance, security, accessibility). Code is managed in a shared version history (Git). Rather than parallel versions isolated for weeks, we integrate our changes into the main version daily, because the more frequent the integrations, the simpler and safer they are. The result: the application moves forward in production, one feature after another.

You can terminate the contract in writing at any time, without justification. The source code, infrastructure, deployment pipeline and documentation are your intellectual property once the first monthly invoice is paid. During the reversibility month, we support your team until they can build, test and deploy without us. The pipeline continues to protect every future change, regardless of which developer works on it.

Corrective maintenance (bug fixes), adaptive maintenance (dependency updates, security patches, browser compatibility), preventive maintenance (refactoring, performance optimisation), and evolutive maintenance (new features) are all included.

In the traditional model, one provider builds and delivers, then another handles application maintenance under a different contract. The problem: a maintenance contract funds bug fixes rather than product evolution. Your software stops evolving while your market moves. The model creates a perverse incentive: fixes are billed per incident, so every bug not resolved at its root generates recurring revenue. When the same organisation delivers the project and wins the maintenance contract, the model rewards incident volume rather than their disappearance.

Software in production keeps evolving for as long as your business evolves. At DEVEDANOS, the same team develops, tests, deploys, and maintains your software continuously, in the same pipeline.