First month
First signs of data aging — models lose precision on new data, BI reports drift by 2–3%. The team has not 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 PLN/mo. Penalty of 5% of monthly fee for each SLA violation, max 50%. Quarterly ROI report — hours freed + defects eliminated.
QA10 technology stack
/qcare/degradation // the cost of no operator
What happens without QCare.
First quarter
Data aging is measurable in production defects. Integrations require patching — webhooks fail, data duplicates. The client team starts writing workarounds instead of using the system.
First year
Integrations drift systemically. Regulatory changes (KSeF, REACH, NIS-2) are not absorbed. The system becomes technical debt — it costs more than it delivered.
Degradation is deterministic, not probabilistic. Data aging, integration evolution, regulatory changes — three vectors act 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 to match your scale. Price to match your scope.
1 800 PLN/mo
monitoring + monthly report
- Uptime monitoring + alerts
- Monthly PDF report
- Email support — 24h response
- No dev pool
3 200 PLN/mo
+ P1/P2 response + dev pool
- Everything from Lite
- P1/P2 response with SLA
- Dev pool 8h/mo
- Slack channel + on-call
5 800 PLN/mo
+ 24h dev pool + BI dashboards
- Everything from Core
- Dev pool 24h/mo
- BI dashboards maintenance
- Quarterly ROI report
9 800 PLN/mo
+ dedicated engineer + compliance audit
- Everything from Standard
- Dedicated engineer 40h/mo
- Quarterly compliance audit
- REACH/CLP, KSeF, NIS-2 modules
18 500 PLN/mo
+ dedicated SRE pod + custom SLA + 24/7
- Everything from 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 is measured from the moment the incident is registered in the runbook (Slack, email, monitoring webhook). P1–P4 classification is 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 monthly fee, automatically booked on the invoice for the following month. No negotiations, no arguments about 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 comes back as a credit memo.
Monthly reset
Every month starts from zero. Violations do not accumulate between billing periods — new cycle, fresh start, new exposure.
We do not 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 is the difference between a support contract and a production operator.
/qcare/compliance // audit modules
Four regulatory domains. Full absorption of changes.
REACH / CLP
Chemical substance classification, SDS cards, registration dossiers — absorbing ECHA updates.
KSeF
National e-Invoice System — integration, schema mapping, monitoring of regulatory changes.
NIS-2
Cybersecurity for critical sectors — audit, policies, incident reporting to CSIRT.
GUM
Legal metrology, measuring instrument legalization, Central Office of Measures certification paths.
/qcare/modules // add-on packages
What is not in your tier — order separately.
Extra dev engineers
1 200 PLN/day
Additional engineer day beyond the tier dev pool limit. Bookable with 48h notice, no contract amendment required.
BI dashboards build
4 800 PLN setup + 800 PLN/mo
Building the BI layer (Metabase / Superset / Looker Studio) with full dashboard maintenance.
Quarterly security audit
3 600 PLN/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 to 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 makes no sense in SaaS production — it is 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% off). Scope renegotiation still happens 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 distinguish QCare 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 for each SLA violation, booked in the next billing cycle without argument. Third — quarterly ROI report with concrete numbers (hours freed, defects reduced, subscription cost vs return). We sell a mechanism, not trust.
What if I exceed the 8h dev pool in the Core tier?
Two paths. Extra engineer day — 1 200 PLN net, one-time, no contract amendment needed. Or upgrade to Standard effective from the next billing month (24h dev pool, difference of 2 600 PLN/mo). Most clients after 3–4 months of exceeding in Core move to Standard.
Can I change tier during the contract?
Yes. Every QCare contract has a 30-day window for termination / tier change. Upgrade — effective from the next month, downgrade — from the month after next (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 hours of client team extracted from administrative work thanks to QA10 automations). Page 2 — defects pre/post (number of production defects recorded 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 an 8–12% discount depending on tier, but scope renegotiation still happens every 12 months.
What if a P1 occurs and you do not respond?
Automatic penalty of 5% of monthly fee for SLA violation — booked on the invoice for the following month. Incident report (root cause, timeline, corrective actions) is issued within 24h of resolution. Violations accumulate up to the 50% monthly fee limit, then reset from the next month. The client does not negotiate the penalty — the mechanism is written into the runbook.
/FAQ // QCARE
Most common questions about QCare
What exactly does the contractual penalty cover?
For each SLA violation, we charge a penalty of 5% of the monthly subscription per commenced hour of breach, up to a maximum of 50% of the monthly subscription. 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 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, with a notice period: Lite and Basic — 1 month, Standard and Pro — 2 months, Enterprise — 3 months. There is no penalty for early termination beyond the notice period. Data is exported and handed over to you within 14 days.
What happens to my system after QCare ends?
The system remains yours — full ownership of code and configuration from day 1. After termination: data export in standard formats, handover of technical documentation, optionally technical team training.
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 contract), client panel. In Pro and Enterprise tiers — dedicated Slack/Teams chat.
Does QCare include new features?
No — QCare maintains what was deployed. New features are a separate scope. Exception: minor UX and configuration fixes (up to 2h/month) are included in Standard tier and above.
/qcare/ // next step
Deployment complete. Time to watch the numbers.
Audit-of-current-state session 90 min — assessment of current state, mapping incidents from the last 90 days, tier proposal with 24-month TCO.
No-obligation audit. Tier proposal with full TCO delivered 5 business days after the session.