How I managed to get Google Business API approval on my first try (in 35 days, between burger shifts)
Hey IH,
Fabrice here. By day, I run a local burger shop in Spain (La Casa de Burger). By night, I code.
If you’ve ever tried to build a tool around the Google Business Profile (GBP) API, you know the absolute nightmare that is the compliance audit. It's notorious for multi-month delays, endless email loops, and unexpected rejections over technical details.
35 days ago, I submitted my side project LocalPatron for production access, fully expecting a long battle.
I recently got the approval email. First try, 35 days total (submitted July 16, approved August 20).
I wanted to share how a solo dev managed to clear it cleanly without a legal or compliance team:
The Scrappy Verification Hack: Google’s auditor required strict proof of real-world SMB usage and domain ownership under specific policy guidelines. Instead of writing long documentation, I live-edited the footer of my own restaurant’s live website on the spot, injecting the exact technical disclosures requested. The auditor saw a real brick-and-mortar business running the software in real-time, which cleared all doubts instantly.
Building on a $0 Edge Stack: Keeping infrastructure simple helped immensely. I built using Next.js, Cloudflare Workers and Supabase. When the auditor tested performance, the light stack naturally delivered a blazing sub-2s LCP and 0ms TBT on PageSpeed Insights, showing the app was stable and production-ready.
Building from Real Need: I didn't build this from a theoretical spec—I built it to solve my own daily headaches managing my restaurant's local presence. That ground-level focus made passing the practical compliance checks much easier.
I'm currently preparing our official launches, but I wanted to drop this experience here first in case it helps anyone else navigating API audits.
If you’re currently stuck in Google's compliance loop, tweaking Cloudflare Workers/Supabase, or balancing a physical business with coding, drop a comment below—happy to share any details that might help!
Thanks Manu! Spot on—showing auditors a live, functioning integration on a real business site changes the entire conversation compared to throwing static documentation at them.
Balancing the burger shop shifts with late-night refactoring was intense, but it meant zero tolerance for useless code. Are you building products backed by your own domain experience as well, or currently scaling UluP Studio clients?
Visual project management makes total sense—traditional linear task lists break down the second you're context-switching between different products.
Allowing early user behavior to override initial roadmaps is the ultimate cheat code. Are you finding that early users are using Spaces more for personal scratchpads or team async collaboration?
Wishing you massive traction with UluP Spaces—will definitely keep an eye on how it evolves!
The fact that your own restaurant became the real-world validation is probably the strongest part of this story.
Curious whether building for your own operational needs is also shaping who LocalPatron is ultimately for, or if you're still seeing a broader SMB market.
100%! Building it for my own daily shifts forces me to focus only on what actually moves the needle during a rushed service—no bloated features. While the core Google Business engine applies to any local business, starting hyper-focused on restaurants gives us a huge edge on product-market fit before expanding to general SMBs.
That makes sense. Starting from a workflow you know firsthand should give you a clearer signal as you test it with other businesses.
Realizing today how easy it is to fall into the 'feature tool' trap.
Spent a chunk of the afternoon discussing positioning with other founders here, and it hit me: nobody buys 'Google Business API management' or 'Local SEO dashboards'. Restaurant owners just want a full house on a slow Tuesday night.
Iterating on our messaging right now to lead strictly with outcomes rather than technical specs. Curious how other local SaaS founders here handled that shift from 'what it does' to 'what it delivers'?
Bonus update for anyone going through the Google Business API audit:
The biggest bottleneck wasn't the code itself, but proving to the auditor how we store and scope scopes/tokens securely without over-privileging app data.
If anyone is currently stuck in the Google audit workflow, drop your questions below—happy to share our exact documentation framework!