← Back to homepage
FAQ

Questions about working together

What clients typically clarify before starting a project.

What kinds of projects fit Cognitrace?
Cognitrace fits when a proprietary AI capability, ML system or platform needs to be built or improved — and model quality, software architecture, data, integrations and cloud operations belong together. Typically not: standalone tool rollouts, no-code automation, training programmes or staff augmentation.
Do you only advise, or do you also implement?
Both, with a clear bias towards implementation. Architecture and technical leadership are also available as a standalone assignment when an existing team owns delivery.
Can you take over an existing system or prototype?
Yes. We start with a technical review of architecture, quality, operability and the path forward. We then take on the implementation or work with the existing team in the areas that need support.
How do you work with existing product and engineering teams?
We integrate directly with existing teams rather than building a parallel stack. Responsibility is divided clearly across architecture, technical decisions and the areas where we implement. Code, documentation and knowledge transfer to the internal team.
How do you measure quality, latency and cost?
Through evals, production telemetry and cost attribution built into the system: test sets, metrics and monitoring for output quality, failure behaviour, latency, cost and tool use. The exact measures depend on the product and its risk profile.
Who owns the code, infrastructure and documentation?
The client does. Code, infrastructure, models and documentation transfer to the internal team and can be operated without Cognitrace.
How do you handle security, data protection and regulatory requirements?
As part of the architecture: through data flows, roles and permissions, deletion concepts, audit trails and suitable operating models. GDPR and the EU AI Act are assessed per use case, with the necessary evidence produced throughout delivery.