Start with the constraints. We'll bring the plan.
The more precise the brief, the more useful the answer. Budget band and timeline are not a filter — they are what turn a conversation into a scoped plan instead of a guess.
Tell us about the project.
The things worth asking before the first call.
With a paid discovery, almost always. Two to four weeks in which we audit what exists, interview the people who depend on it, and come back with a scope, an architecture and a number. You own the findings whether or not you continue with us — which is the point: nobody should commit to a build on the strength of a pitch deck.
A focused platform build is typically three to six months to first release; industrial and embedded work runs longer because validation does. We would rather quote a range we can hold than a date that requires everything to go right. You get a sequenced roadmap after discovery, not before it.
Engagements generally start in the mid five figures and scale from there with scope, integrations and compliance load. We quote fixed price per phase wherever the scope is genuinely knowable, and time and materials where it honestly isn't. If your budget and the problem don't match, we will say so in the first conversation rather than the fifth.
You do — outright, on delivery, including the repositories, the infrastructure definitions and the design source files. No licensing of your own product back to you, no proprietary runtime you cannot leave. We build on standard, well-supported technology precisely so that replacing us stays possible.
The team that built it keeps running it, under a support agreement sized to the platform: monitoring, performance budgets, security patching and a agreed iteration cadence. If you would rather bring it in-house, we plan the handover into the build and train your team during it, instead of treating it as an exit event.
Routinely. The studio is based in Milan and works across Europe, the UK and the US, in English and Italian. Discovery is usually on-site if the work touches physical operations, and remote if it doesn't — we will tell you which, rather than billing travel you did not need.