Refer TestGrid and Earn
You know whoclears releases.
They sign off releases they could not fully test: too few devices, too little time, automation that breaks every time the UI moves. TestGrid fixes that, and you earn a commission when they buy.
Of licence value, once the licence is purchased and the first invoice clears.
What TestGrid actually does
Worth being precise, because most teams already own something they call a testing tool and will assume you mean that.
A cloud of actual Android and iOS devices and real browsers, rather than emulators approximating them.
This is usually the gap, not the framework.Codeless and low-code building for the team, alongside scripted automation for the engineers who prefer it.
Nobody has to throw away what they have.Works with the usual frameworks, plugs into existing CI, and runs in the cloud, on-premise or hybrid.
Not a platform migration.Who to introduce
If you know one of these people, you can make a referral
Anyone accountable for shipping working software. Best fit is a team releasing mobile or web products frequently, where a bad release is visible to customers within minutes.
The opening ask is always the same. A free live demo, about thirty minutes, no obligation. Engineering buyers usually want it hands-on.
QA managers and heads of quality engineering
●Engineering managers and VPs of engineering
●Release managers and anyone who owns a ship date
●CTOs at product companies shipping on a regular cadence
●Testing services firms and QA consultancies
●Does this remind you of someone?Every name you can think of is a commission you cannot collect yet. Partners can.
Join the programListen for
If you've heard one of these comments, there's a commission waiting
Engineering teams describe this problem in almost identical words, which makes it unusually easy to spot.
QA is our bottleneck.
Said in exactly these words, and often.
We still test most of it by hand.
Automation is the entire proposition.
Regression takes us a week.
Every cycle, forever, until something changes.
We cannot test on enough devices.
A real device cloud is precisely the answer.
There is a new device version every other month.
Coverage that was complete last quarter no longer is.
Integration testing takes us another week.
Two weeks of the release cycle, gone.
We shipped a bug that should have been caught.
The expensive version of the same problem.
We only find out it is broken in production.
No coverage before release, so customers do the testing.
After you refer
Five stages, then you are paid
Visible in the PROearn app as they happen, so once you are a partner you never have to wonder whether a referral counted.
- Stage 1Referred
- Stage 2Demo scheduled
- Stage 3Demo done
- Stage 4Trial or proof of concept
- Stage 5Licence purchasedYour commission clears
Expect a long stage four
Technical buyers run proofs of concept and they take time. A TestGrid deal can sit at stage four for weeks while a team runs it against their own suite. That is normal, not a sign your referral has gone cold, and you will see every stage change as it happens.
If you would rather run it yourself
Once you are a partner you can request represent access for TestGrid in the app, and an admin reviews it. It suits partners with a genuine engineering or QA background, because buyers ask detailed technical questions early and a shaky answer costs the deal. Approval is per product.
You watch your money move stage by stage.Join, and the app opens up once your application is approved.
Join the programObjections
Questions you will get asked
Not by us. By the people you introduce, once you start. How to handle each without overreaching.
“We already have an automation framework.”
Most teams do, and the real gap is usually device and browser coverage rather than the framework itself. Do not argue the point. Say the demo will show how it sits alongside what they have built.
“What does it cost?”
Licensing depends on team size, test volume and device access. Do not quote a figure. A wrong number is worse than no number.
“Which frameworks and languages does it support?”
A reasonable first question from any engineer, and one where support changes over time. Tell them the stack when you refer and the team can confirm before the call.
“Can it reach our internal staging environment?”
Network access and security decide these deals. Firmly demo territory, so flag it when you refer and the right person will be on the call.
With engineering buyers, admitting the limit of your knowledge is a credibility gain rather than a loss. Being the introduction rather than the expert is an entirely respectable position.
None of these are yours to answer alone.Partners get the materials, the training and a team who closes the deal you get paid on.
Join the programReferrals happen in the app
Which means joining comes first. Apply, and once you are approved we send you the PROearn app. From there you submit a company in about two minutes and watch it move stage by stage.
Free to join, no targets, and nothing to pay at any point.
