01Do you evolve systems built by another company?
Yes, after the assessment. We need the code, the database and access to where the system runs. Packaged software, which the company only uses, stays with its vendor.
02What's the difference between evolution and support?
Support keeps the system doing what it already does: it fixes, updates and adjusts when a law or a vendor changes. Evolution changes what it does: a screen, a report or a new feature, quoted and approved upfront. Both can run side by side on the same system.
03What's the cost?
It depends on the size of the improvements and the pace of the cycles. After the assessment, our sales team sends a written proposal with the price, what's included and what's not.
04Who decides what goes first?
You do. The list shows each improvement's value to the business, effort and goal, and is reviewed every cycle. We recommend the order; the company approves it.
05Does the system go down while you work on it?
No. The new version is released gradually, first to one group, with rollback ready. When a change requires downtime, it goes in during a window you approve, outside business hours.
06Isn't it cheaper to rebuild from scratch?
Almost never: rebuilding takes months with nothing new for users. We evolve piece by piece and replace on its own the part that has no way forward. When the assessment shows the whole system can't be fixed, we say so in writing, and the path is a new custom system, with the current one live until the new one is ready.
07What if an improvement doesn't deliver?
Every improvement has a goal, measured with real usage. If it falls short, the fix goes into the next cycle, or the improvement is dropped if it isn't worth it.
08What data do you use to measure?
System usage, like the time spent on a screen or how often a feature is used, without looking at the content of personal data. We access only what the improvement needs, and every access is logged. The contract states how we handle this data, in line with the LGPD.