Last week I launched Gumcrm, and I wanted to share some issues I had with long-running functions on Vercel and Supabase.

Watch the preview here.

What is CRUDAPVLMEIGK and why your SaaS needs it sooner or later?

The first release of SaasRock came with only 2 pricing models: Flat-rate and Per-seat. Soon enough I would realize 2 things: I need to support more pricing models, and that pricing is VERY complicated.

This is the biggest SaasRock update since v0.3.

Let your users know the cookies used on your site, and track their page views and events with the built-in analytics Enterprise feature.

Check out v0.5.0 → enterprise.saasrock.com.

July's goal was to build in public an actual SaaS for 2 reasons:

• Validate SaasRock as a production-ready SaaS starter
• Launch my own SaaS

Use the Events to log essential data and use Webhooks to customize your business logic within internal or external webhooks.

Check out v0.4.0 → saasrock.com.

I'm planning to start my own SaaS this month. June was packed wit a lot of features, such as Roles and Permissions, Row Visibility, Tags/Tasks/Comments, Workflows, Filters, Kanban and API usage.

The entity builder just got stronger with a lot of new features for every created Row. Plus a Kanban board component and API limits based on the account's subscription.

Check out v0.3.2 → saasrock.com.

I’ll write about the steps I take as I’m creating my own CRM for SaasRock’s core.

I’m going to use its Entity Builder, and add everything I need on the fly.

Added admin and application Roles & Permissions for page views and actions. Added application Groups and Row-level visibility - only you, public, or share with account members, groups, or specific users.

Custom Entities with autogenerated Views and Forms, API + API Keys and Webhooks. Added PER_SEAT pricing model, and documentation pages.

Download a front-end or a full-stack boilerplate to start your SaaS at github.com/AlexandroMtzG.

In my previous post, I talked about how UI/UX is a challenge you face right after you start your SaaS. TLDR: Use an existing UI library like Tailwind UI, have your components documented (like this), and get inspiration from other SaaS websites, but always add your own UI/UX style.

It's daunting thinking of building a SaaS app because deep down, we all know how much stuff we'll need to go through, and you know that every day will be a decision challenge. Especially if you're alone.

I’ve been using @remix_run for 1 month now, it’s like nothing I’ve used before, here are some of the best features I've encountered:

• Full-stack Routes 💽
• Loaders ⌛
• Actions ⚡️
• Error Boundaries ⚠️
• No more Loading Spinners 💀
• UI/UX 💅🏻
• Integrations 🎁

Thank you for trying out my Remix SaaS kit! I did not expect so many downloads, so I thought I this Quickstart Tutorial.

If you like what you got, consider giving it a 5-star on Gumroad :).

Introducing Remix SaaS kit v0.0.1.

In 2020, I released my first boilerplate for building SaaS applications, netcoresaas.com. It included a Vue2 frontend with a .NET backend.

Not until 1 year later, I was able to migrate from Vue2 to Vue3, Vue3 to React and React to Svelte.

Introducing SaasFrontends v1.0.

I've been a developer for almost 9 years, but I always found designing to be tedious work. These are my application designs since 2016.

From text applications and Winforms to functional Vue + TailwindCSS components.