What do you already hold?
Cyber Essentials, Cyber Essentials Plus, ISO/IEC 27001, sector requirements or an internal security framework.
Adoption / governed from day one
Startwell AI gives your IT team a controlled route from “should we?” to “this is how we run it”—with permissions, evidence and human ownership at every gate.
See the adoption pathStartwell has no access to company data.
Deployment ownerNamed and accountable
Security baselineWaiting for IT
Data boundaryNot yet defined
Connector approvalLocked
DEFAULT: DENYAccess is granted connector by connector, purpose by purpose.
We begin with your environment, risk appetite and obligations—not with an integration checklist. If a control is missing, we stop and fix the foundation before asking for access.
Cyber Essentials, Cyber Essentials Plus, ISO/IEC 27001, sector requirements or an internal security framework.
We classify information, map residency and retention, and identify personal or commercially sensitive data before ingestion.
Named service owner, security owner, connector owners and human approvers—with escalation and shutdown routes agreed.
We align the deployment to your existing controls. We state certifications only when they are independently verified.
The first workshop does not connect a thing. It establishes whether the organisation, the use case and the environment are ready.
Architecture, accreditations, policies, network boundaries, identity provider, data locations and accountable owners.
Agree the first use case, permitted data classes, prohibited data, retention, model boundary and measurable success criteria.
Read access before write access. Minimum scopes, service accounts, owner approval and a documented purpose for every system touched.
Begin with synthetic, historical or low-risk data where practical. Test answer quality, failure modes, permissions and human approval.
Role-based onboarding, clear listening indicators, safe-use rules, feedback routes and named champions. Adoption is measured, not assumed.
Only after the first scope is safe and useful do we add a new team, connector, action or model. Every expansion returns through the gates.
Every connector has an owner, a purpose, a minimum permission set and a revocation route. Nothing inherits trust merely because it is available.
Models, memory and permissions stay inside the approved boundary.
The safe route should also be the easiest route. Controls are built into how people ask, approve and act.
No system, dataset or action is available until an owner approves it.
Access is limited to the smallest scope needed for the agreed job.
New connectors begin read-only. Actions are a separate approval.
Material actions wait for the right person—not merely any person—to approve.
Users can see the source, time and permission context behind important outputs.
IT can suspend a connector, user, action or the service without dismantling the system.
Your IT team receives the evidence needed to operate, review and challenge the deployment after Startwell leaves.
Controlled copy / example structure
01—08System architectureComponents, boundaries and deployment topology
Data flow and retention mapWhat moves, where it is processed and for how long
Connector registerOwner, purpose, scopes, credentials and revocation
Role and access matrixUsers, teams, memory boundaries and approvers
Risk and exception logKnown limitations, decisions and accountable owners
Test and evaluation resultsPermission, failure mode and answer-quality evidence
Operations runbookMonitoring, update, incident and shutdown procedures
Adoption measuresUsage, value, confidence and support signals
Cyber Essentials gives UK organisations a practical baseline around five technical controls. ISO/IEC 27001 defines requirements for managing information-security risk through an ISMS. Startwell uses your applicable framework to shape the deployment gates and evidence—not as a logo exercise.
The first conversation is about the boundary, not the demo.