/qdeployment // from audit to production
Three deployment variants. Measurable performance guarantee with KPIs auditable 90 days post-Go-Live: process time reduction ≥63%, TDC ≥84%. Post-deployment care 2–4 weeks. From distributed data to a data-driven company.
/qdeployment/archetype // who this is for
QDeployment starts from the Audyt AiP recommendations. The client profile — organisation size, source system stack, regulatory regime — determines the variant.
Production lines with a heterogeneous controller stack, MES with no ERP integration, anomalies detected by the operator — not the system. The deployment covers an anomaly detection layer on shop-floor data and automatic escalation to maintenance teams.
Law firms, design offices, audit companies, advisory firms. Case- and contract-based workflows — senior partner time burned on operations that should be handled by the system. The deployment covers a case triage layer and automatic document distribution.
Chain operations — from single delis to networks of hundreds of outlets. Replenishment done manually, demand forecast in a spreadsheet, SKU rotation losses. The deployment covers a forecasting and replenishment layer integrated with POS terminals and the warehouse.
/qdeployment/variants // pricing and scope
The QDeployment methodology is singular — gate-driven, with a performance guarantee and measurable KPIs. The variant determines only the breadth of scope, the length of the schedule, and the depth of the redundancy layer. The same foundation throughout: from distributed data to a data-driven company.
150 000–1 500 000 zł
4–8 mo.
250 000–50 000 000 zł
8–16 mo.
from 50 000 000 zł
open-ended
/qdeployment/workflow // four phases, three gates
It is not a deadline that determines progression — it is criteria. A gate you haven't passed blocks the invoice for the next stage and sends the work back to the previous one.
/qdeployment/sla // number guarantees
Every variant shares the same SLA foundation. They differ in response time, optional auditor cross-check, and depth of standards (from ADR + runbook in Core to custom governance in Enterprise).
| Criterion | Core | Performance | Enterprise |
|---|---|---|---|
| Production system (not a pilot) | yes | yes | yes |
| Process time reduction ≥63% | yes | yes | yes |
| TDC (Throughput-to-Defect Coefficient) ≥84% | yes | yes | yes |
| ADR documentation + runbook | yes | yes | + custom governance |
| P1 response time | 4 h | 2 h | 1 h |
KPIs measured over 90 days post-Go-Live, on the client's production data — under working conditions, not synthetic ones. Full architecture and decision documentation stays with the client, regardless of variant.
/qdeployment/transfer // what remains after us
After post-deployment care, your team can maintain, debug, and extend the system without us. ADR documentation and runbooks remain with you — not in our repository.
/qdeployment/post-deployment-care // 2–4 weeks post-Go-Live
Response time measured in hours, not days. Dedicated Slack channel, weekly standup, rollback playbook per production stage.
Incident classification on first contact. P1 = production down. P2 = KPI degradation. P3 = cosmetic, no operational impact.
Direct access to the QA10 team without tickets. Weekly standup with three roles — client product owner, QA10 lead engineer, optionally risk officer.
Every production stage has a documented safe-state checkpoint. Rollback to the last stable state — a playbook executable by the operator without engineering support.
/qdeployment/compliance // regulatory stacks
Deployments in regulated sectors require more than a checklist. Every architectural decision maps to a specific regulatory article — an external auditor receives ready-made compliance documentation.
Chemicals
Substances, mixtures, hazard classification. SDS card mapping to the REACH register, CLP audit in the labelling layer, IUCLID integration.
Cybersecurity
Operator of essential services. Incident policy, CSIRT reporting within 24 h, supplier risk management, basic audit every 24 months.
Metrology
Polish Office of Measures — measuring instruments, legalisation, standards. Annual legalisation cycle workflow, 90/30/7 day alerts, authority-side audit.
E-invoicing
National e-Invoice System. Integration with the MF gateway, FA(2) schema, invoice stream audit, 10-year retention compliant with tax law.
/qdeployment/discount // from audit to deployment
−9%
For clients of the Platinum variant of Audyt AiP. Active for 12 months from report sign-off — this is the 12-month exclusivity period for deployment with QA10 only. Discount applied to the contract price, with no lower thresholds.
Cross-stage logic — the audit pays for answers, the deployment pays for results. The 9% discount reflects the value a Platinum client has already delivered in the discovery phase (organisational context, stack access, AS-IS process maps) plus a commitment to deployment exclusivity. Full variant structure at /en/audyt-aip/#warianty.
/qdeployment/faq // questions that come up repeatedly
Three differences. First, a production system — not a pilot — the deployment ends in target conditions, not demo-ready. Second, foundations — we start from distributed data and finish with a data-driven company with measurable KPIs (process time reduction ≥63%, TDC ≥84% measured over 90 days post-Go-Live). Third, ADR documentation (Architecture Decision Records) — every architectural decision has documented rationale, rejected alternatives, and cost of change. A typical IT deployment leaves you with a system; QDeployment leaves you with a system, a foundation, and the knowledge of why it looks the way it does.
8–16 months depending on the number of processes (3–8), integrated systems (5–15), and regulatory requirements. The deployment is gate-driven, not deadline-driven — each of the three gates (Architecture → Build, Build → UAT, UAT → Post-deployment Care) must pass acceptance criteria. Forcing a deadline at the expense of quality is a path to technical debt, so we don't do that.
2–4 weeks of post-deployment care included in the price — P1 response time under 1 h, dedicated Slack channel, weekly standup with the client's team, rollback playbook per production stage. After care, three paths — QCare subscription (a separate product — monitoring, minor changes, quarterly review), transition to in-house mode with our ADR documentation and runbooks, or scope expansion in a subsequent QDeployment contract.
Yes — the Core variant is exactly for that. Up to 3 processes, up to 5 integrated systems, 4–8 months. We most commonly start with the most critical process from the Audyt AiP recommendations — the one with the highest ROI and lowest integration risk. Additional processes are added under the Performance variant after the first Go-Live, once the client's team has seen what our production workflow looks like.
/qdeployment/ // next step
30 min discovery session. Preliminary scope + contract outline + variant estimate within 48 h of the session.