CERNOVANCE / EXPERTISE
Working with us: frequently asked questions
Practical answers from discovery through system handover. Scope, fees, timing and support are governed by the agreed engagement.
Can we start without well-organised data?
We can start by assessing the problem and available information, then decide on preparation or a smaller pilot. Data preparation cost and delivery scope follow that assessment.
Do you provide on-site discovery?
On-site interviews and workflow observation can be discussed, with location, staffing, timing and travel agreed separately, potentially alongside remote work.
Will you replace our existing systems?
We assess systems, interfaces and usage first, including configuration and integration options. Replacement depends on cost, risk and the enterprise’s decision.
How do you work with internal IT and vendors?
Agree owners, interface permissions, development roles and test environments, then review dependencies at milestones. Vendor involvement and fees are scoped separately.
Who owns the deliverables and code?
Agree rights to outputs, bespoke code, pre-existing components and third-party licences before engagement. Ownership and transfer are not assumed to be identical across projects.
How is acceptance determined?
Agree deliverables, test cases, data conditions, metrics and reviewers first. Evaluate against that scope and evidence, including any required human review of AI outputs.
What if requirements change?
Assess the effect on timing, effort and fees, then agree changes. Additional interfaces, use cases or research subjects are not automatically included.
Who maintains the solution after launch?
Agree responsibilities among the enterprise, vendors and us before handover. Defect fixes, business changes, model or cloud costs and support duration are defined separately.
Are fees and payment percentages fixed?
No. The website illustrates negotiable structures. Fees, milestones, payment periods and third-party costs follow the agreed quotation and contract.
Should we send confidential material initially?
No. Start with a problem description and public or aggregate information. Before sensitive material is exchanged, establish necessity, confidentiality, permissions and handling arrangements.