Our job in the first call: after 30 minutes you can place the technical proposal on your desk – with a clear assessment of scope and price.
Web frontend, Android app, backend and database – designed by a senior architect, delivered as a running system in your environment. Scope fixed in writing, hand-over documented.
An independent review of your architecture, a plan for replacing legacy systems, or an honest assessment of the proposal sitting on your desk right now.
You describe the bottleneck. We tell you what of it fits into the sprint – and what follows as a build-out afterwards.
What gets built is on paper before you pay anything. Everything beyond it is quoted separately – also in writing.
Architecture and data model in weeks 1 and 2, development in weeks 3 to 6, delivery and validation in weeks 7 and 8. Running increments in every phase.
Trial with real users, then milestone-based build-out, monthly development – or hand-over to your own team.
Whatever goes beyond the sprint we offer separately – in writing, before we start.
The MVP Sprint costs a fixed 9,500 € for web frontend, Android app, backend, database and deployment in eight weeks. The price is agreed in writing before work starts and covers the entire agreed scope. Architecture advisory is offered project-based or at a day rate. For reference (market ranges, as of 2026): agencies in the DACH region charge 25,000 to 75,000 € for comparable scope over three to six months; a senior freelancer charges 800 to 1,200 € per day, i.e. 32,000 to 48,000 € for eight weeks.
Yes, for an MVP scope bounded in writing. Authentication, synchronisation, catalogue management and ERP hand-off exist as proven modules from our own products. We build what is different about your case. Whatever goes beyond the sprint we plan as a build-out in the first call – in writing, before the invoice.
Usage and ownership rights to the source code are agreed in the contract, matched to your project – we discuss this in the architecture call. Regardless of that, the code is always fully documented and built on a conventional stack (Angular, Kotlin, Spring Boot, SQL, Android) that any competent development team can continue.
First a trial phase with real users in your operation. Then either milestone-based build-out, monthly development on a retainer – or hand-over to your own team. You decide how to continue after the trial, not before.
Through documented architecture, a widely used stack and code any competent team can take over. We build for hand-over from day one. In addition, the person in the first call is the person who designs and builds – decisions and knowledge sit in one place and are written down.
Yes. Cloudwerks is based in Gelsenkirchen and works across Germany; enquiries from Austria, Switzerland and the Netherlands are equally welcome, in German or English. Architecture calls take place via video; on-site meetings in the Ruhr area and North Rhine-Westphalia are possible at short notice.
