FAQ
Frequently asked questions
Common questions about how Cinza Tech develops, prices, delivers, and maintains systems and automations.
Development and scope
Scope starts with a technical diagnosis: we understand the current process, identify the core problem, and propose a solution with clear stages and deliverables before any development begins.
Yes. Many projects start with a specific module or process and evolve in phases, based on the company's priorities and budget.
We work with companies across different industries. What matters isn't the sector, but how clearly the process that needs solving is defined — which is why the initial diagnosis always comes first.
Timelines and investment
Investment depends on scope, complexity, and the integrations required. We don't work with generic flat rates — every quote is prepared after diagnosing the specific project.
Point automations and integrations can be ready in a few weeks. Full systems usually take a few months, depending on complexity. A realistic timeline is set right after the diagnosis.
The first conversation and initial assessment are free of charge. The goal is to understand whether there's a fit between the company's needs and what Cinza Tech can build.
Maintenance and support
The system enters a cycle of ongoing support and evolution. We fix bugs, apply security updates, and develop new features as the operation changes.
In many cases, yes, after a technical assessment of the existing system. When the technical foundation doesn't allow for safe maintenance, we recommend restructuring it before taking on ongoing support.
Automation flows depend on the systems they connect to. When one of those systems changes, the flow may need adjusting — which is why ongoing maintenance keeps an automation from silently breaking.
Security, ownership, and scalability
The client company. Source code and intellectual property for custom development belong to the client, as defined in the contract.
We apply security practices across the entire infrastructure — access control, encryption of sensitive data, and regular backups. No credentials or sensitive data are ever stored in exposed form.
The architecture is designed from the start with the operation's expected growth in mind. When needed, the system is adjusted to support a larger volume of data and users.
Yes. Custom systems are built specifically to allow for continuous adjustments, unlike off-the-shelf tools with fixed features.