Sponsored LinkedIn post
A dedicated post to introduce your brand to my audience.
I help SaaS founders find the bugs that cost signups and payments, before launch | QA who also writes code | Web, Android & iOS | Manual, API (Postman), Playwright
Jawad is a creator on Naano, where companies pay creators to write posts about their product.
Below: Jawad's audience and recent posts.
€63per post, fixed price
You approve the post before it goes live
Looking for Jawad? View LinkedIn profileView X profileA creator yourself? Create your own page
The bugs that cost a startup money usually don't crash anything. They just make people leave. A signup email lands in spam. A Submit button saves a draft instead of publishing. The main button disappears on a smaller Android screen. Nobody sends you a bug report. They close the tab. I test web, Android and iOS apps for SaaS founders and small teams before a launch or a release, so I find these problems before your first customers do. What I usually do: - Test the flows that bring in money: signup, login, onboarding, checkout and payments - Re-test old features before each release - Check the API with Postman (wrong inputs, missing auth, error handling) - Write bug reports your developers can fix from: steps, expected vs actual, device, video - Automate the 3 to 5 flows that must never break, with Playwright I do QA full-time at a software company. Before that I spent over a year building web apps, so I know what developers check before they ship, and what they skip. I've also tested 3 SaaS products I built myself. The easiest way to start is a pre-launch check. I test your signup, login and checkout on web, one Android and one iOS phone, and send you a bug report sorted by severity within 48 hours. I'm based in Pakistan and online in the evenings, which is US mornings and UK afternoons. Send me your signup link. I'll tell you the first things I'd check.
LinkedIn export · Nov 4, 2026 – Nov 17, 2026 · Provided by the creator, not independently verified by Naano
X
Public X data · Captured Nov 17, 2026
Two-thirds of the visitors were on iPhone. All 9 emails came from Android. A founder shared that in a Product Hunt thread last week. It was day one of their ad campaign. Not one signup from iPhone. They were honest about it. The number doesn't tell you what broke, it only tells you where to look. And you only see it if you count signups by platform. Most dashboards just say "9 signups". The thread itself started with another founder's point. The preview inside the builder almost always looks fine. The live page, opened by a stranger on a phone, often doesn't. Here's the kind of bug that hides inside a split like that. A tester on LinkedIn shared one in October: on a small iPhone in Safari, the keyboard covered the only Continue button on signup. Their note: "I thought signup was broken." So when I test a signup flow, I open the real link on a real iPhone and a real Android phone, inside the apps people actually tap ads from, like Instagram and LinkedIn, and I keep going until an account or an email really exists. Then I check it again. This week I'll do that for free for 3 recently launched products. Signup only, iPhone and Android, with screen recordings of anything that breaks. Comment PHONE and I'll DM you. #SaaS #Startups #ProductHunt
"Someone paid for our product and got nothing." A founder wrote that on DEV on November 11. The card was charged. The account stayed on the free plan. Here's what happened. The customer paid before they'd created an account. When the payment event hit the app, there was no account with that email, so the code skipped it and still answered "200 OK". The payment provider read that as "done" and never retried. No error. No alert. Nobody noticed. On November 12, a second founder posted almost the same thing. This one used Lemon Squeezy. Same ending: card charged, plan never unlocked. Both checkouts worked. Both demos worked. What broke was the order of events. Real buyers don't follow your test script. They pay with a work email and sign up with Gmail. They pay on their iPhone tonight and create the account on a laptop tomorrow. And that customer won't file a bug report. They'll email "I paid, where's my access?" Or they'll just ask their bank for the money back. So when I test a payment flow, "payment successful" isn't the finish line. I check what the account shows 5 minutes later, for both of those paths. Founders on Stripe or Lemon Squeezy: do you match a payment to an account by email, or by customer ID? #SaaS #Startups #Stripe
The dashboard was green for 25 hours. Login was broken the whole time. Mari Luukkainen runs about 70 small apps. On 1 November a user emailed to say they couldn't log in. A routine update had moved the login library from 1.6 to 1.7. The new version rejected the app's own login link. Pages loaded. The health check passed. The error tracker stayed quiet, because nothing on the server was failing. Two days earlier, in the same log, a Stripe webhook started getting "not found" after a server move. The monitoring missed that one too. Mari's takeaway: for most apps, the real monitoring is still a customer sending an email. Most release checks have this gap. Teams check that the app is up. Far fewer check, after every update, that a new user can still sign up, log in and pay. Founders: how did you find out about the last bug that reached a real user? A dashboard, or an email? #SaaS #Startups
Choose a format for your next LinkedIn collaboration.
A dedicated post to introduce your brand to my audience.
Reposts your LinkedIn post to my network.
Reposts your LinkedIn post with my own comment.
Not taking bookings on LinkedIn right now.
Choose a format for your next X collaboration.
A dedicated post to introduce your brand to my audience.
Not taking bookings on X right now.
Your collaboration, managed on Naano
How does this price compare? B2B creator rates 2026
People who saw my posts, from my LinkedIn export.
People who saw my posts, from my LinkedIn export.
People who saw my posts, from my LinkedIn export.
People who saw my posts, from my LinkedIn export.
People who saw my posts, from my LinkedIn export.
X
Your Submit button "works". Now check the 3 seconds after the click: 1. Did the thing actually happen? 2. Does the user know it happened? 3. Can they find it again tomorrow? One "no" is a bug. Even if the code did exactly what it was told.
A founder on Indie Hackers found out his Submit button was saving every listing as a draft. No error. No confirmation. Creators thought they were live, never heard back, and left. It cost him signups for weeks. Nothing crashed, which is exactly why nobody caught it.
I'm Jawad. I built web apps for over a year. Now I test them full-time. Before a launch, I check the flows that make you money: signup, login, checkout. Web, Android, iPhone. I share what I find here. Launching soon? Stick around.
Storefront by Naano · Create yours
Jawad Mughal QA is a B2B LinkedIn creator based in Pakistan with 400 followers, posting about Software, SaaS, and Fintech. On Naano, one sponsored LinkedIn post by Jawad Mughal QA costs €63, a fixed price per post. A sponsored X post costs €63. Jawad Mughal QA is not taking new bookings right now.
The Naano team casts the creators, writes the briefs, reviews every draft with you and reports results per creator. You approve the shortlist and every draft.