Services — Frequently Asked Questions
Last updated: September 28, 2026
Frequently Asked Questions
What services do you offer?
We offer five: mobile app development, websites and web platforms, SaaS and admin panels, custom software and process automation, and AI integration. Each page sets out the scope and also who the service is not suited to — we're explicit about the work we don't take on.
I don't know which service I need — what should I do?
You don't need to know. Describing the need is enough; we'll work out the right fit together. Most projects don't map neatly onto a single heading anyway. The point of the first conversation isn't to sell a service, it's to clarify what the work actually is.
Can several services be combined?
Yes, and most projects work that way. An admin panel can sit on top of a web platform, and an AI feature on top of that panel. The services aren't alternatives to each other; they layer.
How long does a project take?
We don't quote a fixed timeline, because the workload and scope differ for every project. We determine it in the first conversation, once we understand the work, and present it as a concrete schedule.
How is the price determined?
We don't have a price list. Pricing is set per project once the scope is clear. We start by understanding the need, define the scope together, and the price follows from that.
Will we own the source code?
Yes. In every service and product we build, the source code belongs to you — down to the last line. Our aim is for each client to own a product that is genuinely theirs, not to hold the code and keep you dependent on us.
Do you provide support after delivery?
Every digital product or service we deliver comes with 1 month of free support. After that, we set up a separate support agreement if you need one. Beyond that, our defect warranty has no time limit: if a fault originating from us appears in what we delivered, we fix it no matter how much time has passed.
Do you take over unfinished or ongoing projects?
Yes. Maintaining running software, rewriting parts of it, or finishing work that stalled are all things we do. A handover always starts with a code review: we don't discuss timeline and scope before seeing what is worth keeping and what needs rewriting.