Code of Conduct
The principles that guide every Apicci engagement — from first discovery through to handover and beyond.
Last updated: August 2026
Purpose
This Code of Conduct sets out how Apicci works with clients, partners, and specialist contributors. It applies to every engagement, regardless of size or sector.
Professional standards
We deliver to a consistent, architect-led standard. Work is scoped before build begins, documented throughout, and handed over with enablement so client teams can operate independently.
We do not deliver undocumented systems, shadow IT, or solutions designed to create unnecessary dependence on Apicci after go-live.
Confidentiality and NDAs
Client information, tenant details, and project materials are treated as confidential unless otherwise agreed in writing.
Mutual non-disclosure agreements are available and are standard practice for regulated-sector and sensitive engagements. We expect the same confidentiality from specialist contributors engaged on a project.
Governance and security
We work within the client's environment strategy, security model, and DLP policies. Least-privilege access is used at all times.
Managed solutions, ALM, and audit-friendly design are part of normal delivery, not optional extras. We advise openly when a requested approach would weaken governance or long-term maintainability.
Knowledge transfer and ownership
Client-specific solutions built in the client's tenant belong to the client. We deliver managed packages, documentation, and admin training as part of handover.
Governance and knowledge transfer are deliverables, not billable afterthoughts.
Communication and responsiveness
New enquiries receive a response within 24 hours on business days. During active engagements, response times and escalation paths are agreed in the project communication plan.
We communicate clearly about scope, risks, and changes. Surprises at go-live are avoided through structured discovery, architecture sign-off, and UAT.
Integrity
We represent our capabilities honestly. We do not overstate team size, certifications, or delivery capacity.
We decline work that we cannot deliver to our standard, or we bring in vetted specialists with client agreement when additional expertise is required.
Reporting concerns
If you have a concern about how we handle data, security, or professional conduct on an engagement, contact support@apicci.dev. We will acknowledge and address legitimate concerns promptly.
Questions about this document? Contact us at support@apicci.dev.