9
3 Comments

6SaaSinSix - Week one of my 1st SaaS

I launched RepoHealth.io about a week ago.

Quick intro for everyone since no one will know, I created RepoHealth.io for two reasons. One is I'm doing a 6 SaaS in 6 months project to try and find something that gets some traction. The second reason is while developing getparthenon.com my SaaS boilerplate GitHub actions have been missing features I want/need. So this is a solve 2 problems with one SaaS sort of thing.

Product-wise

I launched with just the ability to have slack notifications sent on: Every Success, Every Failure, First Failure, and build fixed.

Over the last week, I've added the following:

  • Custom messages for each of the notification types
  • Build triggers - Trigger other repositories' workflows to run upon the successful run of a workflow.

Build Configure

  • A dashboard to show the current status of the builds that are enabled

Dashboard

  • A weekly git stats announcement that says who had the most additions, commits, deletions, and what repository is the busiest.

Weekly announcement

Here is how it has gone stats-wise

Traffic has been 169 visitors.
There have been 0 signups. (Technically, there has been 1 signup. But that signup was someone signing up with my email so clearly not a real sign up.)

Here is the number everyone cares about.

Currently, the MRR is €0. (Well technically, €1 if you could my own subscription.)

This week's Plan

  • Create documentation that is SEO-able.
  • Add daily announcements of the current broken builds. The idea is, every morning if there are any broken builds it gets sent to a channel.
  • Add a state untouched PR announcement. The idea is, every PR that hasn't been touched in X days get listed and sent to a channel.
  • Add auto-comment on new PRs. The idea is, remind people (me) of a checklist to ensure everything is done before merging.
on June 5, 2022
  1. 2

    Love how you're building out your boilerplate project at the same time. Making the work create twice as much value is brilliant.

  2. 1

    I have to be honest: what's a PR?

    1. 1

      Pull Request, when you code review code before merging it to the main branch.