While working on ScrapeForge, I figured out a reliable approach to reverse engineer backend APIs used by many applications. This allows data to be accessed directly at the API level before it is rendered on the frontend.
I started working on the SERP scraper using Playwright. After some initial success, I ran into captchas, IP blacklisting, device fingerprinting, and other anti-bot mechanisms.
I researched the legal considerations around this product and concluded that a properly defined Terms of Service will be required once backend features are finalized.
After that, I initialized the repository and completed the initial project setup.
Building fast matters, but building responsibly matters more. More updates soon.
I shared the build in public announcement, worked on improving my problem-solving skills, and created a detailed project brief to clearly define the scope of ScrapeForge.
The goal was to reduce future rework and set a clean path from build to launch to marketing.
I am also sharing the project brief template for anyone who wants to plan their product more clearly. https://1drv.ms/w/c/7d1d62d19aca...
I ve been building a small CRM called Azuori. Mostly because I just wanted something calm to help me track deals and not make my brain catch fire. And apparently other people also enjoy not suffering, so here we are.
I m getting ready for a proper launch soon, but before I unleash this thing into the wild, I d love to get feedback from the PH crowd.
What I m trying to learn:
Does the UI feel clean or too clean?
Are the pipelines and reminders actually useful or am I hallucinating simplicity?
What would make this more I want to use this daily instead of cute demo bro ?
Anything that feels cursed? Unclear? Suspiciously over-engineered?
