Frequently asked questions.

CarrotStudio is an independent software engineering studio specialised in developing custom AI software, operational automations and high-performance websites. We start from the client’s real processes and needs to build reliable, integrated solutions designed to evolve over time.

Yes. We manage projects entirely remotely through an organised process, regular updates, and defined check-in points. Communication stays direct and the client keeps visibility over the progress of the work.

We work with companies, organisations, professionals, and startups that need to improve a process, connect existing tools, or develop a custom digital solution. We assess every project based on the problem to solve, its complexity, and the operational goals.

It’s a system designed around a specific operational process. It can gather information, analyse documents, check requirements, organise tasks, and prepare decisions, documents, or actions, integrating with the tools the team already uses.

A chatbot mainly generates answers. Operational AI software manages a broader process: it receives data, applies rules, interacts with other systems, records the state of the work, and requests human approval when needed.

An automation connects tools and handles narrow steps, such as notifications, updates, or data transfers. Custom software is the right choice when the process requires dedicated interfaces, roles, complex rules, document management, traceability, or more structured functionality.

Yes. We use Make, n8n, and APIs when they’re the best fit for the process. When a project needs more control, complexity, or room to evolve, we develop custom software components.

Yes. We can connect CRMs, calendars, email, databases, payment systems, management software, document platforms, and other services through APIs and custom integrations.

The goal is to reduce repetitive tasks, re-entering data, and manual checks. Important decisions, ambiguous cases, and exceptions can stay under the team’s control.

Yes. We can develop a first working version when you need to validate a process, a workflow, or a new feature. Before development, we define goals, essential requirements, and verification criteria.

Yes. We design and develop custom sites for companies, professionals, and organisations, with attention to visual identity, content clarity, performance, accessibility, and security.

Yes, when the project calls for a customised experience or specific integrations. We can work on catalogues, payments, purchase flows, and automations connected to orders.

The process starts with an initial conversation about the problem, the goals, and the operational context. We then define requirements, priorities, integrations, responsibilities, and the project’s boundaries.

The scope is formalised before development, specifying features, deliverables, milestones, and any exclusions. Requests that come up later are assessed separately to avoid ambiguity over timelines and costs.

We organise the project in phases and share progressive updates, intermediate versions, and review points. The client keeps visibility over decisions and the state of the work.

It depends on the complexity. A narrow automation can take a few weeks, while a complete AI software or a structured system can take several months. After the initial phase, we provide a realistic estimate.

The cost depends on features, process complexity, integrations, the data involved, security requirements, and the level of customisation. Every project is assessed individually.

For more structured projects, payment can be split into an upfront amount and milestones tied to the main development phases.

Yes. We can handle monitoring, technical maintenance, fixes, updates, new features, and post-launch optimisations.

We design every solution taking into account access, roles, input validation, credential management, logging, and environment separation. The measures are defined according to the type of system and the data handled.

The use of data depends on the services and providers chosen for the project. Before development, we define how data is processed, stored, and accessed, favouring configurations compatible with the client’s needs.

Yes. When the process requires it, we build in checks, confidence thresholds, and human approval steps before the system produces final actions.