Common Questions
Direct answers to the questions we hear most. Implementation, integrations, security, AI governance, ROI, and support — all addressed plainly.
Implementation
How long does implementation take?
Single-domain deployments (SDLC, Operations, or Management) are typically live and producing measurable results within 30 days. Full enterprise deployments across all three domains are typically complete within 60–90 days, depending on integration complexity and organizational size. The Friction Audit (free, 45 minutes) gives you an accurate scoping estimate before any commitment.
What does the onboarding process look like?
Phase 1 (Days 1–5): Workflow mapping session, friction baseline measurement, integration inventory. Phase 2 (Days 6–20): Protocol configuration, integration setup, team training. Phase 3 (Days 21–90): Live deployment, measurement, optimization. You have a dedicated implementation lead throughout.
Do we need to replace our existing tools?
No. 10ˣ integrates with your existing stack — it doesn't replace it. We connect to your current systems (Jira, Slack, GitHub, ERP, HRIS, etc.) and provide the execution layer on top. Your team keeps using the tools they already know.
How much does our team need to change their workflow?
Less than you might expect. 10ˣ is designed to eliminate friction, not add it. The first phase is passive — we observe and measure without changing anything. Protocol changes are introduced incrementally and are always opt-in at the team level during the first 90 days.
Integrations
What systems does 10ˣ integrate with?
10ˣ integrates with the most common enterprise systems: GitHub, GitLab, Jira, Linear, Slack, Teams, Salesforce, SAP, NetSuite, Workday, and custom APIs. Growth tier includes up to 3 integrations; Enterprise includes unlimited. If you have a specific system, contact us — we build integrations as part of deployment.
What read/write access do you need?
The Friction Audit requires read-only access or no access at all — you can walk us through your workflow manually. For live deployments, we require read access to relevant systems plus write access only to the specific workflows being automated. We never request administrative access. Every permission is documented and auditable.
Security & Data
Where is our data stored?
Data is processed and stored in your region. We support US, EU, and APAC deployments. For enterprise customers, we support on-premises or private cloud deployment on request. We never use your organizational data to train models. Your data is yours — we are purely a processing and execution layer.
What security certifications do you have?
10ˣ is SOC 2 Type II compliant and supports GDPR, CCPA, and HIPAA-aligned deployments. All data in transit is encrypted with TLS 1.3. Data at rest uses AES-256 encryption. Full details are available in our Security documentation.
Can we see exactly what data the AI has access to?
Yes. Every data access is logged in an immutable audit trail. You can query exactly what data was accessed, by which process, at what time, and what decision it influenced. There are no black-box operations. Transparency is not optional — it's part of the product.
AI Governance
10ˣ is in active deployment. Protocol behaviour described here reflects current system design.
What is the Corporate Cortex?
The Corporate Cortex is 10ˣ's organizational memory layer. It retains context, decisions, and patterns from every workflow cycle — so the system compounds instead of restarting. Every handoff, decision rationale, and outcome is preserved. The organization learns permanently, not just for the duration of a session.
How is AI autonomy controlled?
Every AI action in 10ˣ follows one of three protocols: Suggest → Verify → Execute (human in the loop), Autonomous with Audit (AI executes within defined boundaries, every action logged), or Human Escalation (high-stakes decisions always route to humans). Autonomy levels are configured per workflow and can be adjusted at any time. You define the boundaries. The system enforces them.
What happens if the AI makes a mistake?
Every AI action is reversible within defined rollback windows and logged in the audit trail. For actions above a configurable risk threshold, the system routes to a human for verification before execution. We build for the assumption that AI will occasionally be wrong — the protocol design accounts for this, not just the marketing materials.
Do you use our data to train AI models?
No. Your organizational data is never used to train any model — ours or third-party. We use your data only to execute the workflows you've configured. This is a contractual commitment, not just a policy statement.
ROI & Business Value
When will we see ROI?
Most customers see measurable operational improvement within 30 days of going live. Quantified ROI (reduced overhead, faster cycles, recovered capacity) is typically measurable within 60–90 days. The ROAI Calculator on our resources page lets you model your specific scenario before committing.
How do you measure the impact?
We baseline your Friction Score, Cycle Time, and Flow Rate before deployment. We track these continuously during and after deployment. At 30, 60, and 90 days, you receive a progress report comparing baseline to current state. You always know exactly what changed and by how much.
Can we customize 10ˣ for our specific workflows?
Yes. Every deployment is configured to your specific workflows. We don't sell a generic software product — we deploy a configured execution layer. Protocol rules, integration mappings, escalation paths, and autonomy boundaries are all specific to your organization. Customization is included in every deployment tier.
Support
What does ongoing support look like?
Growth tier: Dedicated implementation lead + weekly check-ins for 90 days, then async support. Enterprise tier: Dedicated strategic account lead, SLA-backed support, quarterly business reviews, and strategic roadmap alignment. All tiers have access to our documentation, playbooks, and resource library.
What if we want to expand to additional domains after initial deployment?
Domain expansion is straightforward. Once your first domain deployment is complete, adding a second or third domain is a scoped engagement. Most customers expand within 6 months of initial deployment — the first domain generates evidence that makes the case internally for expansion.
Still have questions?
The fastest way to get answers is a direct conversation. Book a 45-minute Friction Audit — you leave with a report and we answer everything specific to your organization.