Lovely time speaking with hopeful YC prospects at the office yesterday.
Flowglad
Software Development
Agent payment infra. Program spend + approvals. BYO or use our agents.
About us
Set up your product’s billing in seconds. Adapt it to any pricing model you can imagine.
- Website
-
https://www.flowglad.com
External link for Flowglad
- Industry
- Software Development
- Company size
- 2-10 employees
- Type
- Privately Held
- Founded
- 2025
Employees at Flowglad
Updates
-
We just shipped a massive update to Flowglad Resource-Based Billing is live - track seats, projects, storage, or any resource with capacity limits and real-time claims. Better Auth plugin reworked with automatic organization customer resolution and improved routing. Pricing Model scoping - customers and payment methods now fully scoped to pricing models, discounts can use same code across models. Subscription lifecycle emails redesigned with trial-specific handling and professional templates. Notification preferences - per-organization controls for test mode, subscription, and payment notifications. Plus comprehensive documentation, migration testing scripts, performance improvements, and expanded test coverage. Open-source payments in under 3 minutes. What are you building?
-
-
A better YC application won’t save a bad startup. A confusing one can hurt a good one. Flowglad is hosting a small workshop tomorrow for founders applying to YC on how applications are actually read, where people overthink, and how to clearly explain your idea, traction, and team.
-
-
How we're fixing "AI Slop" with...AI? (our founding designer is cracked) Our Merchants said our emails sucked... and they we're right. 🤷♂️ - No visibility in how emails get generated 👎 - Unclear messaging sent to our merchant's customers 👎 - No branding customization 👎 Most of our email infrastructure Flowglad was built with AI spaghetti code from McDonalds 🤢 Fast and cheap calories that you'd probably regret later. So here's how Andres Gonzalez turned McDonalds spaghetti 🤢 → Cacio e Pepe from Cinque Terre. 🤤 1. 🔍 Research: He prompted Claude to generate a "make_emails_not_suck.md" (markdown file) that: - Scanned our codebase to identify issues - Suggest "best-practice fixes" that made emails scalable, highly composable, and easily maintainable. 2. ⚔️ Refine Then he used another session of Claude to review that markdown file and: - Verify issues - Scrutinize the proposed fixes - Suggest even better fixes - Identify open questions 3. ✍️ Plan Then he used another session of Claude to review "make_emails_not_suck.md" and generate a gameplan that: - Focuses on providing implementation context - Includes test coverage 4. 🚣♂️ Ship Then, he SHIPPED BABY! 🚣♂️ 🚣♂️ 🚣♂️ (literally just ask Claude to execute on the gameplan) Are you coding with AI? Let me know what your workflow is like? Super curious.