|
|
|
|
|
|
by carlossouza
1107 days ago
|
|
|
I think a reasonable approach to sell would be try to convince the buyers that your QA-as-a-Service would replace QA employees for a fraction of their cost.
Thus, pricing would be a fraction of the cost of these employees. I think it's a good idea. Btw, you can pretty much validate it entirely before getting started: just approach companies with mid-large QA teams and try to convince them of the value prop (high-quality QA at a fraction of the cost). |
|
|
Yeah I think I can undercut the cost of a dedicated team because the number of tests that are similar between companies are quite high - I've contracted across multiple startups as a test engineer and seen this time and time again. If I can template these smart enough I can quickly boilerplate the tests & then add the more specific domain logic they might have.
Plus there are teams out there still using no-code automation tools which are flakey, so writing these in a non-flakey way (and validating it is a true bug before reporting so clients only get valid bugs) should help prove it's a better service too.