1. Company
| Legal name | Smartintent AI Solutions Private Limited |
|---|
| Trading name | Zenius QA |
|---|
| Registered office | T-18, Plot No. 9B & 9C, Cross River Mall, Shahdara, Delhi 110032, India |
|---|
| US office | 221 Camille St, Leander, TX 78641, USA |
|---|
| CIN | U58200DL2025PTC441662 |
|---|
| GSTIN | 07ABPCS1163B1ZH |
|---|
| D-U-N-S | 766421844 |
|---|
| Regions served | United States, Europe, India, United Arab Emirates |
|---|
| Working hours | US Central and Eastern mornings from India; UK and Gulf business hours; scheduled standby during peaks |
|---|
| Experience | 15+ years of engineering experience; QA for a live ticketing platform for 7 years, including World Cup on-sales; 316-case proven library; 7 industries served |
|---|
3. Services
| Find a Zenius (platform) | Self-serve QA platform: repository connection, AI agent that maps critical flows and generates tests from acceptance criteria and the 316-case library, runs on every merge, scheduled runs, pass-rate trends, failure drill-down, AI triage (flaky / environment / defect), flaky and release reports. First run free; enterprise tier for the full suite. |
|---|
| Hire a Zenius (managed QA) | Everything in the platform, run and maintained by a named senior engineer: automated coverage on every release, exploratory testing by senior engineers, load and performance rehearsal before peaks with standby during the window, verified bug reports (video, traces, logs), 24-hour failure triage, documented go/no-go signed before every release. |
|---|
| Sectors | Ticketing & events, travel & booking, flash sales & reservations, e-commerce checkout, fintech & payments, marketplaces, SaaS platforms |
|---|
| Platforms | Web (Chromium, Firefox, WebKit), mobile web; Playwright-based automation; CI-agnostic |
|---|
4. Capability checklist
| Typical RFP question | Zenius answer |
|---|
| Functional, regression, integration and mobile-web automation | Yes — on every merge, in the customer's pipeline |
| AI-generated test cases reviewed by humans | Yes — every generated test reviewed by a senior engineer before joining the suite |
| Manual / exploratory testing | Yes — senior engineers with sector experience; verified findings with evidence |
| Load and performance testing | Yes — event-scale rehearsal 2–3 weeks before peaks; breaking point documented; engineer on standby during the peak |
| Accessibility testing | WCAG 2.2 AA checks available within scope on request |
| Test data management | Synthetic and pseudonymised data; no production PII copied into test systems |
| CI/CD integration | GitHub Actions, GitLab CI, Jenkins, CircleCI or any runner that executes Playwright; results as PR checks |
| Reporting | Trend dashboard, release and flaky reports, signed go/no-go verdict per release, post-peak note within 24 hours |
| Defect management | Findings logged in the customer's tracker with evidence; classification flaky / environment / defect; audit trail to fix and re-run |
| Test asset ownership | Customer owns all tests, configuration and evidence; open standards; exportable at any time |
| Named single point of accountability | Yes — a named senior engineer who signs each release |
| Onboarding time | Coverage scope agreed in week 1; suite live in weeks 2–3 |
| Business continuity for peaks | Standby plan, pre-agreed rollback path, backup engineer for the window |
| Languages | English; engineers across India, US, UK and Gulf time zones |
5. Service levels
| Item | Commitment |
|---|
| Coverage promise | An agreed percentage of critical user flows automated by an agreed date; if the date is missed, that month is credited |
| Failure triage | Every red run investigated and classified within 24 hours |
| False positives | Investigated and fixed within 24 hours |
| Bug reports | Human-verified, with video, traces and logs |
| Release verdict | Written go/no-go before every release in scope, signed by the named engineer |
| Load rehearsal | Scheduled 2–3 weeks before each agreed peak; report within 2 business days; engineer on standby during the peak window |
| Response to customer queries | One business day |
| Security incident notification | Within 48 hours of confirmation |
| Questionnaires & contract redlines | Five business days |
6. Security summary
Least-privilege, named access through the customer's identity provider where possible; MFA everywhere; staging by default and production only with written authorisation; TLS 1.2+ in transit and encryption at rest for hosted evidence; test evidence retained 90 days by default and deleted on request; secrets kept in the customer's vault; peer review, dependency and secrets scanning; patching targets of 7 days (critical) and 30 days (high); documented incident response; confidentiality obligations and annual security training for all engineers. Controls are mapped to ISO/IEC 27001:2022 and the SOC 2 Trust Services Criteria; the platform targets OWASP ASVS Level 2; hosts follow CIS Benchmarks. Certification roadmap: ISO 27001 and SOC 2 Type II. Full detail on the Security & trust page.
7. Data protection
Zenius acts as a processor for customer data handled during an engagement and as a controller for its own business contacts. We sign a Data Processing Addendum incorporating the EU Standard Contractual Clauses (Module 2) and the UK International Data Transfer Addendum for transfers to India and the United States; sub-processors are listed in the DPA with 30 days' notice of changes; customer data is returned or deleted within 30 days of engagement end. Our Data Protection Officer and Grievance Officer under India's Digital Personal Data Protection Act is Rahul (rahul@zenius.ai). Website processing is described in the Privacy Policy.
8. Commercial terms
| Pricing model | Per test under management — creation, infrastructure, maintenance, triage and reporting included; performance validation as a separate line item |
|---|
| Typical range | Managed engagements $60K–$250K per year depending on scope; platform first run free |
|---|
| Pilot | Paid 3-week pilot on one product area; deliverables: critical-flow map, coverage number, performance report, signed verdict on one release |
|---|
| Term & billing | Annual after pilot; monthly or quarterly invoicing; USD by default, INR from the Indian entity, other currencies on request |
|---|
| Payment terms | Net 30 from invoice |
|---|
| Credits | Coverage-date credit (one month) if the agreed coverage date is missed |
|---|
| Termination | Termination for convenience after the pilot with 30 days' notice; 30-day handover; all assets returned in open formats |
|---|
| Liability & insurance | Standard MSA limitation of liability negotiable to contract value; insurance certificates on request |
|---|
9. Documents we provide
- Mutual NDA (ours, or yours)
- Master Services Agreement and Statement of Work template
- Data Processing Addendum with SCCs and UK Addendum; sub-processor list
- Service-level schedule (section 5)
- Security control mapping (ISO 27001 / SOC 2); completed questionnaire in your format
- Sample signed verdict (see the format)
- Named client references during evaluation
- Certificate of incorporation, tax registrations and insurance certificates on request
10. Onboarding & exit
Week 1 — map critical flows with your team, agree coverage scope and peak dates in writing, complete access provisioning through your identity provider. Weeks 2–3 — map the 316-case library to your flows, agent fills gaps from acceptance criteria, senior engineer reviews every test, suite live on every merge, first coverage number reported. Ongoing — suite maintenance, 24-hour triage, exploratory sessions each release, load rehearsals before each peak, signed verdicts. Exit — 30-day handover with knowledge transfer, all tests and evidence in your repositories and storage, access revoked, deletion certificate on request.
This pack summarises standard terms; the executed MSA, SOW and DPA govern. Version 8 September 2026.