SaaS and Admin Panel — Frequently Asked Questions
Last updated: September 27, 2026
Frequently Asked Questions
How long does it take to build an admin panel?
We don't quote a fixed timeline, because the workload and scope differ for every project. We determine the timeline in the first conversation, once we understand the work, and present it to you as a concrete schedule. An estimate given before the scope is clear tends to become a promise nobody can keep.
How is the price of a SaaS or panel project determined?
We don't have a price list. Pricing is set per project once the scope is clear, because two projects under the same heading can be very different. We start by understanding the need, define the scope together, and the price follows from that.
Will we own the software's 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; usage questions and any issues you run into are covered during that period. 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. We don't hand over work that doesn't function. Everything else is treated as separate work: new feature requests, scope extensions, and adaptations required by changes third parties make to their own systems (operating systems, payment providers, APIs).
How are roles and permissions structured?
We build the permission layer from the start, not as a control bolted on later. Who can see which screen, change which record and perform which action is tied to roles. Critical actions are recorded in an audit trail: which user did what, and when. Adding permissions later means reviewing every screen one by one, which is why it comes first.
Do you also set up subscriptions and payments?
Yes — plan and limit management and wiring up the payment flow are in scope: what each plan grants access to, how limits are enforced, and the subscription lifecycle. The choice of payment provider depends on the project and the country; we decide that together.
Can you turn our existing tool into a multi-user product?
Yes, and it's one of the most common requests: adding accounts, roles and data separation to a tool used by one person. The real work here is on the data side rather than the interface — separating which existing records belong to which account. A handover starts with a code review.
What happens as the number of users grows?
We build the system to handle growth, but only real usage reveals the real load. That's why measurability matters: slow queries and bottlenecks need to be visible, so that when growth arrives nobody has to guess where to intervene. Infrastructure and hosting choices are made together per project, and because the code is yours, it stays portable.