Custom Software and Process Automation — Frequently Asked Questions
Last updated: September 27, 2026
Frequently Asked Questions
How long does custom software development take?
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 custom software 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).
Why build custom software when off-the-shelf options exist?
Off-the-shelf software usually handles the standard part of your business well and costs less; if it's enough, we won't propose custom development. Custom software makes sense when the cost of forcing your business into someone else's mould exceeds the cost of the software itself: when your process is genuinely different, when data is moved by hand between several tools, or when no package covers what you need.
Will it integrate with our existing systems?
System integration is one of the main things we do: connecting accounting software, e-commerce platforms, shipping, email and messaging services to each other. The deciding factor is whether the other side offers an API or a data export. We check this case by case during discovery, and if a system turns out to be closed, we say so upfront.
Our process isn't clearly defined yet — can we still start?
Turning an unclear process into software only makes the confusion run faster. So we clarify the process together first: who does what, where each piece of information comes from, and where decisions are made. That discovery work is often the most valuable part — it's where it becomes clear that some steps need simplifying rather than automating.
Will our staff be able to adapt to the new system?
The goal isn't to impose a new habit but to reduce manual work, so we design the screens around how the work actually happens. Usage is walked through at delivery and support is provided throughout the first month — questions usually come up in the first few weeks.