QA Rating

ILoveMyQA vs Software Secured

QA Rating is published independently, and its publisher owns no company listed in this catalog.

ILoveMyQA and Software Secured meet the same applicability conditions (Nearshore for the USA), so the tags do not separate them. The catalog has Frameworks, Published rates only for ILoveMyQA, and Engagement models, Client stages only for Software Secured. Neither publishes Certificates, Signs a BAA / GDPR DPA, Onboarding, Crowd tester pool, Device lab, so the table cannot answer those.

Field by field

ILoveMyQA and Software Secured compared on the fields published for every company in this catalog
FieldILoveMyQASoftware Secured
HeadquartersVancouver, CanadaOttawa, Canada
Delivery locationsCanada, the USACanada
Team size11-50 people11-50 people
Founded20182010
OwnershipIndependentIndependent
ServicesUsability testing, Manual testing, Test automation, Performance testing, Compatibility testing, API testing, Mobile app testingPenetration testing, Secure code review, Red teaming
IndustriesEcommerce, Education, BankingHealthcare, Banking, SaaS
Frameworkspublished by one of the twoCypress, Selenium, WebdriverIO, Cucumber, Playwright, Postman, AppiumNot published
Engagement modelspublished by one of the twoNot publishedManaged testing service
Client stagespublished by one of the twoNot publishedScaleups
CertificatesNo certificate confirmed by a register entryNo certificate confirmed by a register entry
Signs a BAA / GDPR DPANot confirmed / Not confirmedNot confirmed / Not confirmed
Published ratespublished by one of the twoNot published
Minimum project$1,000clutch.co$5,000clutch.co
OnboardingNot publishedNot published
Crowd tester poolNot publishedNot published
Device labNot publishedNot published

Who each one fits

A buyer weighing this pair chooses a discipline before choosing a vendor: a security practice that hunts for exploitable defects sits next to a functional-QA practice that checks everyday features behave as intended, and that discipline choice comes first, before either vendor's client roster does. Inside that choice, ILoveMyQA's profile does not say what stage of company its practice usually serves, so a very early team and a funded round read the same page and get no signal about whether ILoveMyQA has served a company at their point before. That silence costs more in a cross-discipline match than in a same-discipline one: security work and functional QA carry different assumptions about what a young product still lacks, and paying for the wrong depth is easy to do without a stated reference point. On the first call, ask ILoveMyQA directly what stage its recent engagements sit at, founder-funded, seed, or later. Check the answer later against the named clients its profile already lists: a roster weighted toward small, founder-led companies reads differently from a roster weighted toward funded platforms.

A tag is attached when the company's published fields meet its condition, never by judgement. Both lists come from the same closed vocabulary, so a tag missing from one side means the condition was not met, not that nobody looked.

ILoveMyQA

ILoveMyQA meets no applicability condition in this catalog. That is a statement about what its published fields show, not about the company.

Software Secured

Software Secured meets no applicability condition in this catalog. That is a statement about what its published fields show, not about the company.

Both meet the conditions for Nearshore for the USA, so those conditions do not separate them.

Where the data runs out

Completeness against the 14 fields of the comparison checklist is 64% for ILoveMyQA and 71% for Software Secured. A field is counted as filled when a source confirms it, so a gap means nobody published it.

Neither company has a value recorded for these fields: Certificates, Signs a BAA / GDPR DPA, Onboarding, Crowd tester pool, Device lab. The table shows those rows empty rather than estimating them.

Field definitions and the completeness checklist are on the methodology page. The sources behind each field are listed on the ILoveMyQA profile and the Software Secured profile.

Questions

Does either ILoveMyQA's or Software Secured's published profile list a security or quality certification the company holds?
ILoveMyQA's published profile lists zero held certifications, checked 3 September 2026. Software Secured's published profile also lists zero held certifications, checked 3 September 2026. Software Secured's own source list names a third-party directory of firms that support other companies' SOC 2 audits; that page documents individual staff credentials such as OSCP and OSWE rather than a certificate Software Secured itself holds. A buyer who needs a specific accreditation before signing has to get it confirmed directly from either vendor, since neither published page states one.
What team size band does each company's published profile report?
ILoveMyQA's published profile reports a team size band of 11 to 50 people, checked 3 September 2026. Software Secured's published profile reports the same band, 11 to 50 people, checked 3 September 2026. A buyer trying to judge available bench strength from headcount alone gets no separation between the two from this field. A follow-up question worth asking either vendor is how many of that staff work on active engagements at once, since the published band does not say.

Published by QA RatingUpdated on September 6, 2026

Every fact about a company comes from a listed source. A field without a source stays empty. A certificate counts as confirmed only when a registry, certificate or auditor report backs it; a certificate the company only claims about itself is published separately, under that label. Vendors can request a correction at hello@qa-rating.com. A correction is applied when it comes with a public source.