From Scissors to Syntax. 20-year Hairdresser building AI SaaS agents.
AI Engineer based in Nara, pivoting from a 20-year career as a hairdresser. Currently building Stylus (AI captioning for salons) and Harmony (Instagram automation). Obsessed with workflow automation using n8n, Python, and LLMs. My mission is to solve inefficiencies in the beauty industry through code. Writing about SaaS development, automation, and my journey from the salon floor to software architecture.
Markdown supported · ⌘↵ to post
OnlineProxy
First up, you're ballparking Apify costs, but where's the actual receipts from running this in production? Then, you never actually show us what percentage of shops make it through your filters alive - and that number matters big time because if you're only keeping like 5% of scraped data, you're basically hemorrhaging API budget, but if you're sitting at 50%+, your scoring is probably way too generous. And your businessScore is looking at how recent posts are, but it's sleeping on engagement velocity - like how many likes and comments shops are actually racking up - which is usually a way better signal for finding shops that actually give a shit and will reply. If you threw together a quick A/B test showing that a businessScore ≥ 50 actually predicts higher reply rates in the real world, and now you've got a defensible case study instead of just a solid tutorial