Building with an AI assistant be like --
AI: Click this option, and set it to this.
Me: I don't see that option.
AI: That's because it doesn't exist. Good job pointing that out.
My blessing is that I am an overly ambitious individual. I'll keep my nose to the grindstone until I meet my goals.
My curse is that I'm overly ambitious individual π I WILL attempt to turn every idea I have into a business, regardless of whether the last ones profitable yet π
After a few days of constant distractions and, honestly, a much-needed break, I'm feeling good about our progress again. If we can get the appointments in a list with CRUD today, I'll feel good about the Calendar implementation waiting until tomorrow.
Well, the weekend ended up being for other things, so here's to getting back on track!
Day 3 of building our CRM in public--Today we have a running start on the UI for the appointment page.
I'm taking a step back to evaluate the functionality of this page, because I know how MY company would like to use it, but even though I'm our FIRST customer, I hopefully won't be the only one.
So, we're at the drawing board, and I think we have a concept nailed down. Just need to figure out the cleanest way to build it out.
I'm giving myself 2 days as the target to get this feature shipped. Once it's done, my company can adopt it as our primary software and we can move onto the less essential core features.
@FynCas This is sick man. I know the topic in itself is controversial, but the people complaining about AI instead of using it are missing opportunities left and right. Gotta ride this wave as long as its profitable. π―
Where do you see most of your converting traffic coming from? I'm looking forward to releasing mine, but I know my audience for the most part and I'm not yet sure how easy its goig to be to get steady traffic. I've definitely found a gap -- theres a need for the product -- but getting in front of them is going to be a challenge.
Day 2 of building in public
Not gonna lie. Having some trouble focusing today, but determined to make some progress.
Yesterday, my internet went out, so I lost some time. The services page is built, and just needs add/edit/delete functions wired up. Once that's done, we'll try to tackle appointments.
Already have some mockups made of the list/calendar views for the Appointments page, so we can start that buildout today as well. The goal is to at least get the list view functional.
Goal for tomorrow is to get into the calendar view with drag/drop.
Getting closer to our MVP!
I'm conquering my fear of this build-in-public thing.
***Day One***
So far we have:
-Our aesthetic nailed down
-We know what the MVP is going to include and what it won't
-We have authentication set up and user invites
-A contact list page with add, edit and delete
-Individual contact pages (incomplete until service functionality is built)
-Flexible UI settings are functional
What's being built now:
-Today, we nail down services. DB is in place and now we can start on the front-end. We need a Service Catalog to house and control services and individual service pages for granular control.
What's next:
-Tomorrow, we tie up loose ends and implement our Appointment feature, which will give the user the ability to bundle services into a single visit on the calendar.
I don't often like tooting my own horn -- but most of my career in tech has been web development and SEO. Not necessarily SaaS.
I'm really proud of how well this software is coming together.
And I'm really proud of the discipline I've conjured in implementing and cutting features for the MVP.
I'm officially doing it.
This year, I'm taking my shot at filling a market gap.
And I'm documenting EVERYTHING in public.
My goal? Accountability. To challenge myself. To face the public and deliver a game changing software to the trades.
Tell me I can do it. π€£