- Makers Make by SaaSykit
- Posts
- The New Startup Bottleneck, How to Avoid AI Code Slop, Idempotency: What, Why and How & more
The New Startup Bottleneck, How to Avoid AI Code Slop, Idempotency: What, Why and How & more
Ahmad
May 24, 2026
Hey Makers 👋
If you’re building a SaaS right now, keep going.
Seriously. Most people never make it past the “idea” phase. They never ship, never launch, never give themselves the chance to build something real.
And while building the product itself is already hard enough, rebuilding the same SaaS infrastructure over and over makes the journey even slower.
Authentication. Billing. Teams. Permissions. Subscriptions. Admin panels. Onboarding. Multi-tenancy.
These things are necessary, but they’re usually not the reason your users will love your product.
That’s exactly why I built SaaSykit.
Instead of starting every SaaS from a blank Laravel project, SaaSykit gives you a production-ready foundation with the essential building blocks already connected together, so you can focus your energy on what actually makes your idea unique.
The goal is simple: spend less time rebuilding boilerplate, and more time shipping.
👉 Use code “SAASYKIT2YEARS” to get 20% off the Complete package while it’s still active.
Now, let’s jump into what’s happening in the Laravel & SaaS world this week 👇
From the Community
Laravel v13.10.0 introduces a storage cache driver backed by Laravel's filesystem abstraction, making it possible to use an S3 disk (or any configured disk) as a key/value cache store without additional packages. It also adds a --stop-when-empty-for queue worker option, a WorkerIdle event, schedule group lifecycle callbacks, Schema::hasForeignKey(), and several queue testing improvements.
Retries are one of those things that look harmless until they are not.
A user clicks the checkout button twice. A mobile client loses the response after sending the request. A load balancer retries a connection. A queue worker calls an internal API again because the first attempt timed out. The client is not trying to break your application. It is just trying to recover from an uncertain state.
Laravel has introduced native passkey authentication support through new first-party packages:
Authorization usually starts simple.
Maybe you begin with an is_admin column, then add a couple of if statements, and everything looks fine for a while. But as the application grows, that simplicity starts working against you.
We just released v7.3.0 of laravel-query-builder, which adds a new way to group multiple filters under a single URL parameter. Before getting into the new feature, let me show you how the basics work, so the new bit makes sense in context.
One of the most useful yet widely misunderstood functions in PHP is empty(). At first glance, empty() seems like a handy shortcut for checking if a variable is, well, empty. However, its behavior goes beyond the obvious. According to the PHP documentation, empty() considers the following values as "empty".
One of the most useful yet widely misunderstood functions in PHP is empty(). At first glance, empty() seems like a handy shortcut for checking if a variable is, well, empty. However, its behavior goes beyond the obvious. According to the PHP documentation, empty() considers the following values as "empty".
All about SaaS
Founders are shipping so much right now that a lot of them have lost the thread. A demo works. Launch goes out. Teams feel momentum. Then the uncomfortable part shows up. Nobody knows what the company learned.
That is the part of this AI moment I cannot stop thinking about.
It came up in my conversation with Luba because she asked what has changed for founders. My answer keeps getting simpler the more I think about it.
Game theory was one of my favorite classes in college, and the study of finite and infinite games impacted me profoundly. Years later, I found two books that speak to these different game frameworks: Finite and Infinite Games by James P. Carse (1986) and The Infinite Game by Simon Sinek (2019).
A founder I advise asked me last week: “Should we go wide or should we go deep?”
She runs an AI startup. Two big incumbents had just announced they were entering her space. The team was anxious about this. Hence their question: do we expand the surface area of the product, or sharpen what we already have?
It’s a perfectly rational question. It’s also the wrong question.
Here is what I told the founder: reframe that question. Completely. Get rid of it.
Google has broadened experiment support in the Google Ads API, and that matters for both advertisers and developers who rely on controlled testing rather than assumption. The May 2026 update extends experimentation into more of Google’s newer campaign environments, giving teams a clearer path to test changes in AI-led campaign formats without abandoning measurement discipline.
This has led to office fights, drama, accusations, finger pointing, and more since the dawn of B2B software.
Growth decelerates. The board asks tough questions. And then the blame game starts.
The VP of Sales says the product isn’t competitive enough
The VP of Product / CTO says sell what we’ve built, it’s what you asked for
The CEO fires the VP of Sales, hires a new one, and waits 6 months to see if it works.
Rinse, repeat.
Engineers spend only 30-40% of their time actually coding. The rest goes to deployments, sprint planning, admin overhead, support questions, design reviews, incident response, and everything in between.
Until now, we’ve had no way to map and measure where that invisible work actually goes. Larridin changes that. Mapping how engineering work flows across your org, surfacing the blockers and friction that drag on productivity, and showing you exactly what to fix.
Videos
Keep building, keep rocking! 🤘