QA tester for a SaaS

I run a SaaS product that lets insurance brokers and HR teams build employee benefits portals. Upload a company's carrier plan documents, the system extracts the plan details, and it produces a website employees use to understand their coverage. The product works. It has never been used by anyone outside my own team. I want a focused eight hours from someone who will break it and tell me exactly what happened. This is a tightly scoped job, not an open-ended one. I've written a 73-point test plan broken into seven timed sessions and a Google Sheet with all the logging tabs already built. You work down it in order and fill it in as you go. I am not asking you to test everything, and I don't want you exploring off-plan. I've already decided what matters in eight hours. About 70% of the work is hunting for things that are broken. The other 30% is telling me where you got confused. That second part is not filler. If a screen made you stop and reread it, I need to know, because thousands of brokers will hit the same wall. What you'll be testing Signing up as a broker, with both email and Google sign-in Building one complete benefits portal end to end Uploading plan PDFs and checking the extracted numbers against the source documents line by line The Stripe checkout on all three paid tiers, including a declined card Whether the cheaper plans correctly lock people out of the expensive features Inviting an HR manager and confirming they can't reach billing or other clients' portals The employee-facing portal that all of this produces An AI assistant built into the portal What you need One computer and one smartphone. That's it. No tablet, no second machine, no BrowserStack. A computer with Chrome, plus any one of Safari, Firefox or Edge A smartphone, iPhone or Android, either is fine Tell me in your proposal which computer and which phone you have. What you'll deliver Everything goes in the Google Sheet I provide. Four things come back to me: A bug log with severity, exact reproduction steps, the device it happened on, and evidence. A confusion log: places where the product worked correctly but you had to stop and think. Write these in the moment, on first encounter, before you learn how the feature is meant to work. Every account and portal you created, with passwords, so I can log into all of it afterwards. A closing summary: the five things you'd fix first, and why. Budget about twenty minutes for this. Evidence is your judgment per issue. Screenshot for anything visual. A short Loom for anything involving timing or multi-step flows. Nothing at all for a typo, as long as you quote the text and say where it is. Requirements Manual QA experience on web applications, ideally SaaS with a signup and billing flow Clear written English. Vague bug reports are worse than no bug reports. Able to start within a few days and finish inside two days once you start Willing to hand over every credential you create at the end Not required, but useful: any exposure to US employee benefits or health insurance. If you don't know what a deductible is, that's arguably better, since most people using the finished product won't either. To apply Skip the template cover letter. Answer these three: What web app did you test most recently, and what was the worst bug you found? Describe it the way you'd write it in a ticket. What computer and phone will you test on? You're testing a signup flow. Give me two edge cases you'd try that most testers skip. Start the first line of your proposal with the word BLUEBIRD so I know you read this far.