Frequently asked questions

Custom software is worth considering when an important process depends on manual data entry, spreadsheets or several disconnected tools. You do not need to know whether the answer is a new application, an integration or automation. We first identify where technology can genuinely simplify the work.

No, you do not need a finished specification for the first conversation. It is more useful to understand the process, its users, the necessary data, current delays and existing tools. We use that context to organise requirements for a sensible first version.

The first stage is understanding how the company works, which tools it uses and which problem needs to be solved. We then organise the main needs, dependencies and risks. Only then can we define the solution, schedule and budget responsibly.

Yes, Catable also builds smaller integrations and automations when they solve a specific problem and can be maintained safely. Not every company needs a large application. Sometimes connecting two existing systems or removing one repetitive task creates the most value.

The cost of custom software depends on its scope, process complexity, integrations and data requirements. A reliable estimate therefore requires an initial understanding of the project. After that review, we propose a scope and discuss its realistic cost before work begins.

The delivery time depends on scope, integrations, data availability and the number of scenarios the system must support. A simple automation and a multi-module system require different schedules. We define the timeline after organising the first project scope.

The first version should contain the functions required to solve the company’s main problem. Other ideas can move to a later stage. This makes the release useful in real work without overloading it with features whose value has not yet been confirmed.

We first assess every scope change for its effect on timing and cost. This keeps the decision explicit and prevents a new idea from quietly replacing something already agreed. A larger change can also become a separate project stage.

Yes, when the existing tools provide a suitable API or another secure way to exchange data. Before confirming an integration, we assess its limitations, documentation and error handling. That review determines the realistic scope of the connection.

After launch, support may include fixing defects, monitoring integrations, making small improvements and developing further areas. We agree the specific maintenance model before release so that responsibilities and the way requests are handled remain clear.

Your company data remains your data. We define code rights, licences, access and documentation handover in the agreement before work begins. This makes it clear what will be transferred and under which conditions.

We choose safeguards based on the type of data, user roles and how the system will be used. Before development begins, we define requirements for access, permissions, backups and external services. Projects involving sensitive data require additional obligations to be included in the scope.