We represent client who is a 60 year old father have troubles after working with Lovable. Here is what we found
We work for ScoutQA and we made this auto vibe testing agent using Amazon Bedrock with our friends and colleagues. I was wondering if anyone had the same pain points as some of our clients have reached out to us on. We're devs and QA people at heart and it's surprisingly hard for us to know what the community would want from a tool like ours. So we would like to share more about the trouble of old people making wordpress business and Lovable website. I'll post below one of the POV and quote from our client:
"I’m a 60 year old vibe coder, building SaaS only on Lovable and ScoutQA - it's never to late to learn new stuff"
I’m 60. I’ve been working as Project Manager in software testing for 40 years.
I still don’t write code though.
And I’m making my SaaS with basically two things:
Lovable to build + ScoutQA to test
No IDE. No CI pipeline. No walls of Git diffs. I think old age make it hard for me to learn new tool, but it a progress made for finally finish building something that shippable with quality
1. What I actually ship:
I use Lovable to build full products, not just MVPs:
- A contract management SaaS with paying customers
- An infra management platform (GG Workspace)
All of this, built without touching the generated code. The code lives in GitHub purely as a backup. If I open it, it mean nothing to me.
2. Before ScoutQA, my weak spot was back and forth stuck:
- Change one thing in Lovable -> Random flows break somewhere else
- Spend hours clicking through everything, still miss issues
Now my workflow with ScoutQA help me caught a real XSS vulnerability I didn’t know about. It organizes everything as projects/web apps, not repos. Kinda lets me think like a product person, not a developer
Manual testing is like hoping your web app would not broken after launch, but for automation test, I’m just clicking a button.
I build for about an hour most evenings. That’s it. No 12‑hour debug marathons.
That is the story of our client in their 60s base in UK, I hope you guys enjoy it and if possible, feel free to give out feedback and try our product. It basically a vibe testing website with no set up, just paste your URL and let Scout handle all the bug like SEO, Functional, Performance, Navigation, etc...ScoutQA is perfectly fit for vibe coder, web builder, solo dev and tester with little resource. The product is in beta free mode so you can run as many test as you like.
TL;DR: Our 60 years old client, who can’t read code, using Lovable + ScoutQA to ship stable, revenue SaaS products (his product is small scale with few customers so I hope pro dev would empathize with him about scaling). Automated vibe‑testing agent like ScoutQA can help you save less effort with manual grind and improve your credibility to customer with bug fix report
We work for ScoutQA and we made this auto vibe testing agent using Amazon Bedrock with our friends and colleagues. I was wondering if anyone had the same pain points as some of our clients have reached out to us on. We're devs and QA people at heart and it's surprisingly hard for us to know what the community would want from a tool like ours. So we would like to share more about the trouble of old people making wordpress business and Lovable website. I'll post below one of the POV and quote from our client:
"I’m a 60 year old vibe coder, building SaaS only on Lovable and ScoutQA - it's never to late to learn new stuff"
I’m 60. I’ve been working as Project Manager in software testing for 40 years.
I still don’t write code though.
And I’m making my SaaS with basically two things: Lovable to build + ScoutQA to test
No IDE. No CI pipeline. No walls of Git diffs. I think old age make it hard for me to learn new tool, but it a progress made for finally finish building something that shippable with quality
1. What I actually ship: I use Lovable to build full products, not just MVPs: - A contract management SaaS with paying customers - An infra management platform (GG Workspace)
All of this, built without touching the generated code. The code lives in GitHub purely as a backup. If I open it, it mean nothing to me.
2. Before ScoutQA, my weak spot was back and forth stuck: - Change one thing in Lovable -> Random flows break somewhere else - Spend hours clicking through everything, still miss issues
Now my workflow with ScoutQA help me caught a real XSS vulnerability I didn’t know about. It organizes everything as projects/web apps, not repos. Kinda lets me think like a product person, not a developer
Manual testing is like hoping your web app would not broken after launch, but for automation test, I’m just clicking a button.
I build for about an hour most evenings. That’s it. No 12‑hour debug marathons.
That is the story of our client in their 60s base in UK, I hope you guys enjoy it and if possible, feel free to give out feedback and try our product. It basically a vibe testing website with no set up, just paste your URL and let Scout handle all the bug like SEO, Functional, Performance, Navigation, etc...ScoutQA is perfectly fit for vibe coder, web builder, solo dev and tester with little resource. The product is in beta free mode so you can run as many test as you like.
TL;DR: Our 60 years old client, who can’t read code, using Lovable + ScoutQA to ship stable, revenue SaaS products (his product is small scale with few customers so I hope pro dev would empathize with him about scaling). Automated vibe‑testing agent like ScoutQA can help you save less effort with manual grind and improve your credibility to customer with bug fix report