Frequently asked questions

We work in four phases. Discovery: we understand your business and define measurable goals. Design: prototypes and the shape of the experience. Development: two-week sprints, each ending with something that works. Launch: final testing, deployment and training for your team.

It depends on complexity. A minimum viable product usually takes 6 to 10 weeks. A full enterprise platform can run 3 to 6 months. The proposal gives you a schedule with concrete milestones, not a vague range.

Requirements evolve, and that is normal. We work in sprints, so we fold feedback in every two weeks. If a change materially affects scope or budget, we discuss it before touching it, with the impact estimated in writing.

We work with a fixed price per phase for defined scope, or a dedicated monthly team when the product is evolving continuously. Either way you know what you get and when before anything is signed.

A description of the problem, who it affects and what happens today without the software is enough for a first conversation. If you have documents, screenshots or an existing system, even better — it speeds up the diagnosis.

We choose based on scalability, maturity and who will maintain the system afterwards. Typically: TypeScript across the stack, NestJS and PostgreSQL on the backend, Angular or Next.js on the frontend, Kotlin Multiplatform or Ionic on mobile, Docker and Cloudflare for infrastructure.

Yes. The intellectual property in code developed for you is yours, and it lives in your repository from the first commit. We do not use proprietary licences that tie you to us.

Yes. We offer plans covering security updates, monitoring, bug fixes and priority support. We do not disappear after deployment.

Support plans define response times by severity. A critical incident is picked up immediately and you receive a root-cause report, not just the patch.