testRigor ICP

testRigor Ideal Customer Profile

Complete the fields below to develop your Ideal Customer Profile. Keep in mind, for this exercise think of companies, not a person.
Industry Ecomm, Retail, EHR, EdTech, HealthTech, Insurance, FinTech, ERP, Software Dev*
Geography USA, CAN, UK, The Netherlands, Belgium, Lux, Eastern Europe, Australia, Singapore, LATAM, Western Europe EU (Inbound only), India (Karnataka, Telangana, Maharashtra, Delhi-NCR, Tamil Nadu, inbound only)
Size
Could be revenue, employees, or locations
Mid Market (100-999 EEs, $50M - $1B)
Enterprise (1000+ EEs, $1B+ rev)
SMB (40+ EEs Inbound Only, IF 2+ FTE Manual Tester)
Budget Confirm if SMB, Government, or ENT
Using Which Product(s) None, Integrated Test Case Mgmt (TestRail, XRay, Zephyr, Azure DevOps), Using Multiple Tools to solve QA, Legacy Open Source Tools (Selenium, Playright, Appium, Cypress, etc)
Pain Points Test Automation Coverage <70% (Ideally <40%), High Maintenance, Slow releases, Manual testers can't build/fix tests, Product owner/managers doing testing, Not enough time, Devs taking too much time to fix bugs, Can't do cross-platform testing, Too much time to build tests, Maintaining infrastructure, Too many bugs, Costs too high. Customer flow not smooth
Types of Roles on the Team QA/testing leaders when empowered by CTO, CTOs/CIOs/CEOs, QA Managers/Directors, VP/Dir of Eng/Software dev, Eng Mgr, Product Managers/VPs
Notable Attributes Looking for more AI, Need UI, frequent UI changes, recent re-organizations, need to test multiple environments, need resources to run testing, need testing knowledge
Multiple correct answers
E-commerce
Heavy construction manufacturing
Retail
FinTech
ERP
HealthTech
Multiple correct answers
Mid-Market (100-999 employees, $50M-$1B revenue)
Enterprise (1000+ employees, $1B+ revenue)
SMB (40+ employees inbound only, if 2+ FTE manual testers)
Solo founders with no QA team
Multiple correct answers
Test automation coverage below 70% (ideally below 40%)
High maintenance and slow releases
No unit test coverage at all
Manual testers are unable to build or fix tests
Too much time spent building tests and maintaining infrastructure
Application breaks under pressure