When workneeds a custom solution.

It depends on scope. A simple dashboard, an automation or a first version of a webapp does not have the same cost as an application with login, database, permissions, integrations and AI. The usual approach is to define a small first version, with the essentials needed to check whether it really solves the problem.

A first version can take a few weeks when the problem is well defined. Projects with several user roles, external integrations, data handling or specific rules need more time. Before estimating, the process and what already exists need to be understood.

No. Sometimes it is enough to reorganise a spreadsheet, connect two tools, create a dashboard or automate a specific task. Custom software only makes sense when it reduces complexity, avoids repeated work or gives the team a clearer way to decide.

Internal webapps, custom dashboards, simple databases, tools with login, private areas, automations, report generators, integrations between systems and applications with AI. The shape depends on the problem, the available data and who will use it.

Yes, when those tools have an API or another safe way to integrate. It can make sense to connect a CRM, spreadsheets, forms, email platforms, internal systems, databases or external services. Not every tool allows the same quality of connection, so that should be checked early.

It depends on the case. Data can come from forms, files, spreadsheets, databases, APIs or manual entry. The important part is defining which data is actually needed, who can see it and what history should be stored.

AI should not receive sensitive data by default. When it makes sense, data can be filtered, anonymised or transformed before being sent to the model. For example: removing names, emails, phone numbers, addresses, confidential values or any detail that is not needed for the task.

It does not have to. In many cases, AI is used to prepare, summarise, classify or suggest. The final decision can stay with the team. For sensitive work, this should be defined from the start: what AI can do, what it should only suggest and what always needs human review.

It depends on the solution. The most common pieces are a web interface, database, authentication, per-user permissions, APIs and AI integrations when they make sense. The technical choice should serve the product, not the other way around.

After a first version, there are usually adjustments based on real use: fixing friction, simplifying screens, adding fields, improving reports, tuning prompts or connecting new data sources. A custom solution is rarely finished just because it has launched; it improves when it starts being used.

The solution can integrate with what already exists or work as a separate tool. Sometimes it is better not to touch the main system and instead create a simpler layer on top: a dashboard, an internal area, a support tool or a specific flow for the team.

With a conversation about the problem, not the technology. The first step is to understand the current process, where time is lost, which data comes in, which decisions come out and which parts should not be automated. From there, it is possible to decide whether a custom solution is worth designing.