Struggle SaaS

My journey building Melitix Events and the struggle leading up to it.

Changes to Struggle Saas

Hey folks, this past Sunday (April 21st) was the first Sunday I haven’t published since this blog started. I’m not happy about it. Keeping a weekly pace took a lot of work. In that light, there will be some changes to this blog to make it more sustainable for me. Publishing Cadence—My journaling of building Melitix Events will continue, now bi-weekly. The intention is to give me more material to write about on particularly slow weeks of Melitix Events. continue →

Week 6: Building the SEO Content Engine

I’m going to be straight with you. This week’s post is short and sweet. My motorcycle trip could have gone better. After 22,000+ miles, my Harley had its first breakdown; the front cylinder had a hole in it! Anyway, you can understand why I was physically and mentally unable to move forward with the company last week. I wanted to quickly dive into my focus this next week, getting content marketing started. continue →

Week 5: Reminiscing About My First Public Software

Hey folks. I’m on a motorcycle trip from Florida to Texas to see the 2024 solar eclipse. On top of that, I’m still in the middle of the code rewrite I discussed last week. As you can imagine, I haven’t gotten much done this past week, so there is little to discuss. While I was roaring west on Interstate 10, my mind was on the EventHunt launch later this month and how it would feel to have the software public. continue →

Week 4: Launching Melitix Next Month Yet Starting a Rewrite

In my first weekly blog post, I mentioned that I was “sort of” starting from scratch. While I was creating a new company, I was starting off with the code from the Get Together project. This decision allowed me to start with a working app and lay improvements on top rather than building an entire app from scratch. Using an existing codebase was supposed to be a competitive advantage, so near the end of last week’s post, I stated that I would be launching in April. continue →

Week 3: Two Steps Forward, One Step Back

Over the past two weeks, I’ve primarily been working on branding for Melitix Events and EventHunt. I’ve done this kind of work for many projects before, so it’s not unfamiliar. Around the start of these two weeks, my co-founder quit the “business”, making the whole process a bit awkward and demotivating for me. I pushed through and wanted to share what I have and the experience of losing a co-founder so early. continue →

Week 2: Open-Source Branding

Branding—I’m no expert, but I acknowledge its importance and power when done right. Starting on this journey of building an event management platform meant starting with branding. Every business benefits from good branding, but in the open-source world, it’s especially needed. Branding gives direction In episode 58 of the To Be Continuous podcast, Paul Biggar (CircleCI co-founder) rants about how open-source projects need a roadmap and direction and how significant a problem it is. continue →

Week 1: Starting From Scratch... Sort Of

A week into my startup-building journey, we’ve arrived at the first update. My co-founder and I started the month by putting together a 31-day plan. Starting from scratch isn’t necessarily difficult, but it is tedious. There are several social media accounts to create, analytics and a mailing list to set up, logos to design, and more. However, some tasks involve putting in time and using our brains. These tasks are where I was able to take a shortcut. continue →

Struggle SaaS: Documenting the Blood, Sweat, and Tactics Behind My Startup Dream

👋 Welcome to Struggle SaaS, my new blog documenting the journey of building Melitix Events and the struggle leading up to it. Why I’m building a “nights & weekends” startup with a friend I’ve known since middle school. Right in that previous sentence, there are a few points of potential hardship ahead: nights & weekends—Building something just on your nights and weekends is hard. I know. I’ve tried many times before and have failed again and again. continue →