When QA is bought
Testing is usually procured after a failure reached customers, which means the buyer is urgent, embarrassed and looking for competence rather than price. They need to know which testing types you provide, what device and browser coverage you have, whether you can automate regression, and what a report actually looks like. Companies presenting a service list cannot be assessed, and testing is easy to fake.
What we build for a QA company
First, services by testing type — functional, regression, load, security, usability — since buyers arrive needing a specific one. Second, automation capability and device coverage published, which is the practical constraint on what can be tested. Third, example reports, because the deliverable is a document and the buyer needs to know it will be usable by developers. Fourth, engagement models from a one-off audit to embedded testers, plus a free initial assessment that demonstrates competence.