Currently building Orange County Scoop

Southern California, USA

←All notes
BuildingSEP 18, 2026 · 6 min read

Something I learned building with Laravel.

A short write-up on what clicked, what didn't, and what I'd do differently next time I start a new SaaS project.

When I started building Nextup, I wanted a stack that would let me move fast without painting myself into a corner. I'd used Laravel before for small things, but this was the first time I leaned on it for something I planned to run for years.

This is a sample note body. Replace it with the real story: what you set out to build, what surprised you, and what you'd tell someone starting the same project tomorrow.

1. Conventions are a feature

The biggest win wasn't any one package. It was not having to make a hundred small decisions about where things go. That freed up time for the decisions that actually mattered to customers.

app/Actions/AssignNextUp.php
public function handle(Opportunity $opp): Rep

“The best code I wrote this year was the code I didn't have to think about twice.”

2. What I'd do differently

A few things I'd change on day one next time:

  1. Write the boring admin tools first. You'll use them every day.
  2. Put real users on it before it feels ready.
  3. Log everything you'll wish you had in six months.
Caption for the image goes here.

3. The takeaway

Pick tools that get out of your way, then spend the saved time with the people you're building for. That's it. Build useful things.

Filed under
  • Building
  • SaaS
  • Laravel

Written by Timm Cuzzo

Entrepreneur and product builder in Southern California. Currently building Orange County Scoop. Get new notes by email, no spam.