First month
First signs of data staleness — models lose precision on new data, BI reports drift by 2–3%. The team hasn't noticed yet, but TDC (Throughput-to-Defect Coefficient) is dropping.
/qcare // production operator, not a helpdesk
Production operator, not a helpdesk. SLA with contractual penalty.
Five subscription tiers 1 800–18 500 zł/mo. Penalty of 5% of the monthly fee per SLA violation, max 50%. Quarterly ROI report — hours freed + defects eliminated.
QA10 technology stack
/qcare/degradation // cost of no operator
What happens without QCare.
First quarter
Data staleness is measurable in production defects. Integrations need patching — webhooks fail, data duplicates. The client team starts writing workarounds instead of using the system.
First year
Integrations diverge systematically. Regulatory changes (KSeF, REACH, NIS-2) are not absorbed. The system becomes technical debt — costing more than it delivered.
Degradation is deterministic, not probabilistic. Data staleness, integration evolution, regulatory changes — three vectors acting independently and cumulatively. Without an operational layer, every deployment loses value at a rate of 8–12% per quarter. QCare stops the curve.
/qcare/pricing // five subscription tiers
Tier matched to scale. Price matched to scope.
1 800 zł/mo
monitoring + monthly report
- Uptime monitoring + alerts
- Monthly PDF report
- Email support — 24h response
- No dev pool
3 200 zł/mo
+ P1/P2 response + dev pool
- Everything in Lite
- P1/P2 response with SLA
- Dev pool 8h/mo
- Slack channel + on-call
5 800 zł/mo
+ 24h dev pool + BI dashboards
- Everything in Core
- Dev pool 24h/mo
- BI dashboards maintenance
- Quarterly ROI report
9 800 zł/mo
+ dedicated engineer + compliance audit
- Everything in Standard
- Dedicated engineer 40h/mo
- Quarterly compliance audit
- REACH/CLP, KSeF, NIS-2 modules
18 500 zł/mo
+ dedicated SRE pod + custom SLA + 24/7
- Everything in Performance
- Dedicated SRE pod
- Custom SLA + 24/7 on-call
- Architecture review every quarter
/qcare/incidents // P1–P4 classification
Response time per tier, per priority.
| Priority | Lite | Core | Standard | Performance | Enterprise |
|---|---|---|---|---|---|
| P1 Production down | — | 4h | 2h | 1h | 30 min |
| P2 Feature degraded | — | 8h | 4h | 2h | 1h |
| P3 Cosmetic / minor | 72h | 48h | 24h | 12h | 8h |
| P4 Request / change | — | 5 days | 3 days | 2 days | 1 day |
Response time measured from the moment the incident is registered in the runbook (Slack, email, monitoring webhook). P1–P4 classification determined by QA10 according to the severity matrix — the client can escalate the decision within 2h.
/qcare/sla // contractual penalty mechanism
SLA violation — automatic contractual penalty.
Per violation
Each SLA violation = −5% of the monthly fee, automatically booked in the next month's invoice. No negotiations, no disputes over root cause.
Monthly maximum
Penalty accumulation limit in a single month — 50% of the fee. Client protection: even in a catastrophic month, half the subscription is returned as a credit memo.
Monthly reset
Every month starts from zero. Violations do not accumulate between billing periods — new cycle, clean slate, fresh exposure.
We don't sell trust — we sell a mechanism. A violation registered in the runbook generates an automatic credit memo in the next billing cycle. The client sees penalties on the invoice, not in an apology email. That's the difference between a support contract and a production operator.
/qcare/compliance // audit modules
Four regulatory domains. Full change absorption.
REACH / CLP
Chemical substance classification, SDS cards, registration dossiers — absorbing ECHA updates.
KSeF
National e-Invoice System — integration, schema mapping, monitoring regulatory changes.
NIS-2
Critical sector cybersecurity — audit, policies, incident reporting to CSIRT.
GUM
Legal metrology, measurement instrument calibration, certification paths from the Central Office of Measures.
/qcare/modules // add-on packages
Not included in the tier — order separately.
Extra dev engineers
1 200 zł/day
Additional engineer day beyond the tier dev pool limit. Bookable with 48h notice, no amendment required.
BI dashboards build
4 800 zł setup + 800 zł/mo
Building the BI layer (Metabase / Superset / Looker Studio) with full dashboard maintenance.
Quarterly security audit
3 600 zł/quarter
Full security audit — application pentest, permissions review, library supply chain audit.
/qcare/renegotiation // 12-month cycle
Every 12 months — scope, price, and module review.
What we renegotiate
- SLA scope — response times per priority, incident classification, dev pool scope.
- Pricing structure — cost inflation review, tier adjustment based on actual consumption.
- Adding / removing modules — KSeF, NIS-2, REACH/CLP, GUM, BI, security audit.
Why not 24 / 36 months
Your product evolves. Our stack evolves. Regulations evolve. Fix-price-for-life doesn't work in SaaS production — it's a mechanism for legacy outsourcing, not for a production operator. Annual renegotiation gives both parties real control over scope and price, without a multi-year contractual mortgage.
Clients who want a 24 / 36-month lock-in with a discount get it optionally (8–12% discount). Scope renegotiation still occurs every 12 months — just based on the previous price.
/qcare/faq // frequently asked questions
What to know before choosing a tier.
How does QCare differ from a typical SLA support contract?
Three things set QCare apart from a generic support contract. First — full production readiness, not a reactive helpdesk. Our engineers know your stack because we deployed it during the QDeployment phase. Second — automatic contractual penalty: 5% of the monthly fee per SLA violation, booked in the next billing cycle without disputes. Third — quarterly ROI report with concrete numbers (hours freed, defects reduced, subscription cost vs return). We sell the mechanism, not trust.
What if I exceed the 8h dev pool in the Core tier?
Two paths. Extra engineer day — 1 200 zł net, one-time, no contract amendment required. Or upgrade to Standard effective from the next billing month (24h dev pool, difference of 2 600 zł/mo). Most clients switch to Standard after 3–4 months of exceeding the Core limit.
Can I change tiers during the contract?
Yes. Every QCare contract has a 30-day notice window for tier changes. Upgrade — effective from the next month, downgrade — from the month after (due to dedicated resource rotation). A full tier change requires a simple amendment, not a new contract.
What exactly do you report quarterly?
The quarterly ROI report is a 4-page PDF with four sections. Page 1 — hours freed (total client team hours removed from administrative work thanks to QA10 automations). Page 2 — defects pre/post (number of registered production defects before and after deployment, q/q delta). Page 3 — costs (subscription, extra hours, cumulative). Page 4 — cumulative ROI with trend from the first quarter of service.
Do you offer 1-year or 3-year contracts?
Standard is 12 months with renegotiation. Every year we review SLA scope, pricing structure, and module additions/removals. Long-term 24/36-month contracts are optional — with a 8–12% discount depending on the tier, but scope renegotiation still occurs every 12 months.
What if a P1 occurs and you don't respond?
Automatic penalty of 5% of the monthly fee per SLA violation — booked in the next month's invoice. An incident report (root cause, timeline, corrective actions) is issued within 24h of resolution. Violations accumulate up to a limit of 50% of the monthly fee, then reset from the next month. The client does not negotiate the penalty — the mechanism is embedded in the runbook.
/FAQ // QCARE
Frequently asked questions about QCare
What exactly does the contractual penalty cover?
For every SLA violation we charge a penalty of 5% of the monthly subscription fee per commenced hour of breach, up to a maximum of 50% of the monthly fee. The penalty is automatic — we calculate it ourselves and deduct it from the next invoice.
How does the 4h SLA work?
The 4h SLA means that from the moment a critical incident is reported, we have 4 hours to restore the service. For non-critical incidents — 24h. We measure time from your report, not from when we detect the problem ourselves.
Can I cancel at any time?
Yes, subject to the notice period: Lite and Basic — 1 month, Standard and Pro — 2 months, Enterprise — 3 months. There is no early termination fee beyond the notice period. Data is exported and delivered to you within 14 days.
What happens to my system after QCare ends?
The system remains yours — full ownership of the code and configuration from day 1. After termination: data export in standard formats, handover of technical documentation, optional training for your technical team.
How do I report an incident?
Through three channels: dedicated email support@qa10.io (ticket created automatically), direct phone to the on-call engineer (number in the contract), client portal. In Pro and Enterprise tiers — dedicated Slack/Teams chat.
Does QCare include new features?
No — QCare maintains what has been deployed. New features are a separate scope. Exception: minor UX and configuration fixes (up to 2h/month) are included in the Standard tier and above.
/qcare/ // next step
Deployment complete. Time to watch the numbers.
Audit-of-current-state session 90 min — assessment of your current state, incident mapping from the last 90 days, tier recommendation with 24-month TCO.
Audit with no obligations. Tier recommendation with full TCO delivered 5 business days after the session.