The $8,000 Surprise and the Slack "Cringe" Factor: Building a New Era of Micro-SaaS

For a long time, software development followed a predictable, slow-moving arc: idea, weeks of architecture, months of boilerplate, and finally—if the motivation held—a launch.

Recently, I’ve been breaking that cycle. I’ve moved into a high-velocity "AI-Native" workflow where I partner with Claude (specifically the Opus 4.6 model) to act as my lead engineer. But this isn't "vibe coding" that stays in the terminal. These are production-hardened, revenue-generating tools built with a simple philosophy: Identify a high-stakes pain point, build the leanest solution, and ensure it’s bulletproof through rigorous human review.

Here is a look at the first three pieces of this ecosystem.

1. LandlordKeep: Stopping the "Forgot It" Emergency

The Problem: Most landlords are reactive. They don't think about the HVAC until it stops working in July, leading to an $8,000 emergency replacement that could have been a $150 service call.The Solution: LandlordKeep.comLandlordKeep is your rental property’s memory. It’s not a bloated rent-collection suite; it’s a focused maintenance shield.

2. DevProps: Recognition Without the Cringe

The Problem: Modern "Employee Recognition" platforms are often exhausting. They involve arbitrary points, gift card marketplaces, and a layer of corporate "cringe" that makes engineers want to opt out.The Solution: GiveDevProps.comDevProps brings recognition back to the metal. It’s built for teams that want to celebrate the work that actually keeps the lights on—code reviews, successful deploys, and heroic on-call saves.

3. The "Meta" Experiment: ProjectHub & MCP

Before these became commercial offerings, I needed a way to manage the chaos of building multiple products simultaneously. I built ProjectHub (projecthub.tomcompagno.com) as my internal test kitchen.

While not a public SaaS, it has become the "brain" of my development process. It serves as a central collaboration point where team members can drop links, notes, and tasks. More importantly, it features a Public MCP (Model Context Protocol) Server. This allows Claude to "step out" of the chat window and actually interact with my project data—helping me manage tasks and context across my entire portfolio in real-time.

The Mission: Smaller, Smarter, Faster

I am on a mission to prove that a single developer, empowered by a sophisticated AI partner and a "review-first" mindset, can build a portfolio of high-value, niche tools that solve real problems.

The goal isn't just to write code; it's to create Sovereign Software—tools that are lightweight, private, and focused on one job. These are just the first three.

What should I build next?