Day 30 of building apps to $1k MRR in public The waitlist/landing page took way longer than expected to make. I ended up having to re-write this at least 3 times. For some reason, claude just was not producing good code today. Like it was just fucking bad today. - constantly spinning a dev server on 3001 despite clear instructions never to do that - completely breaking everything and forcing me to roll back changes - producing sloppy code Anyways landing page is done... - ✅ Fixed critical font system preventing proper typography display on landing page - ✅ Resolved CSS variable circular references that broke Instrument Serif and DM Sans loading - ✅ Implemented comprehensive font weight specifications matching LeadNudge brand guidelines - ✅ Applied Instrument Serif 400 to all display text (headings, logo, stat values) - ✅ Applied DM Sans with correct weights (300/400/500/600) throughout UI elements - ✅ Replaced external CSS with inline styles architecture for better performance - ✅ Maintained all existing form submission logic and API integrations - ✅ Added proper font fallbacks and responsive padding consistency - ✅ Successfully built and tested with no TypeScript or build errors

Day 43 of building apps to $1k MRR in public: Holy shit what a day but we managed the following: - submitted web app for google branding verification (passed on the second try) - currently in the process of submitting everything for oauth verification. Spent hours cleaning shit up for the video. Don't know if it's worth it, but I've read that it's a pain in the ass for the scopes our app uses. Worked overtime at work today and my brain is fried.

Day 42 of building apps to $1k MRR in public: Holy shit what a day... 😅😅 classic example of "It works on localhost but not in production". I was demoing a touring hours feature to my partner and it kept caching our old questions. No idea wtf was going on until I head through vercel/nextjs docs and realized I forgot to add the correct headers lmao. Despite that, I was able to fix the issue and complete my demo. I am mentally drained right now. When's the last time something like this happened to you? (Works in dev but not in production)

I used to think "over-engineering" was just something lazy devs said to avoid hard problems. I was wrong. They were right. Most of the complexity I built early on was just ego. How much of your stack are you maintaining out of pride vs. necessity?

Day 41 of building apps to $1k MRR in public: Need to figure out how to get more of my time back! I spent the majority of my working time onboarding the team to help with the project. Took longer than expected, but all good.

Not sure wtf is wrong with my For you but I am really struggling to find posts I genuinely like.

Day 40 of building apps to $1k MRR in public: - AM 21 Mile Run - Managed to finish the touring hours feature so prospects can't use the agent to request tours at odd hours of the day. A small but critical improvement.

Can you build an express train that allows me to go from brooklyn to queens without going through manhattan?

Day 39 of building apps to $1k MRR in public: - AM 8 Mile Run - Yet another overtime day at work, actually finishing shit now, couldn't get much done. Will have to double down tomorrow

Day 38 of building apps to $1k MRR in public: - AM 15 Mile Run, PM Lift. Legs are toast. - Tested with the team and everything's working - Need to switch domains, rotate a couple of keys, finish this touring hours feature, and we can onboard our first client. Guy's really eager. For further context, we can't have the agent setting tours/open houses at ridiculous times like 2AM so what I'm shipping right now is essentially the guard rails for that - if you can only tour between 1pm-3pm it will push prospects to tour between those hours.

Day 37 of building apps to $1K MRR in public: - confirmed that I caught food poisoning - still ran 12 miles - still migrated from sync architecture to JIT API endpoints for my ai agent. We fucking ball boys. Now excuse me while I find a bathroom

Biggest issue with building an app with a job is overtime. Sometimes you're just way too busy at work and can't spend as much time as you'd like on your project. It leads to me forgetting some of the things I did and why. Documentation is so important

Day 36 of building apps to $1K MRR in public: - 7 Mile run. - Felt EXTREMELY under the weather at work today, nonetheless we pushed through. In other news, I'm almost done migrating to Just in time API endpoints for our AI agent. I ran some tests and had to spend longer than I wanted debugging some parsing issues, but we pushed through and got things functioning. Once this is out the way, I need to remove the disgusting supabase URL when users sign in lmaoo (should've done it sooner, but I didn't expect to even get this far tbh) I have a couple of prospects with large portfolios that are ready to get their hands on this tool, and I don't feel like burning leads. Therefore, it's important that this MVP works the way it's intended.

Day 35 of building apps to $1k MRR in public: So before, users would "publish" their qualification process (questions, etc.) for our ai agent. However, this was just too clunky tbh. I'm way better at state management and I'm changing our APIs so our bot pulls information on leads, properties, and qualifying/disqualifying information as necessary. This is way smoother than before because our users don't need to 'publish' and rely syncing between the crm and their bot. The bot just grabs it.

Days 34 of building apps to $1k MRR in public: Been extremely busy and working alot of overtime due to my job, but managed to find time to do the following: - Ran 20 Miles - Changing the product name and acquired a new domain - Sounds crazy but finally figured out state management on a third party tool we're using. The documentation on it was terrible - Rewriting our AI agent customization feature because the UX sucked after testing it with some beta users Game plan for tomorrow is to grind all day

Holy shit I am absolutely swamped today dude

Career switchers have an unfair advantage in tech. You're not building solutions to imagined problems. You're fixing the pain you lived through. What industry did you leave behind to build your product?

You took the unconventional path. skipped college, changed careers, went solo. The doubt hits hardest right before the breakthrough. When did your "risky" choice finally click?

Founders who admit "I suck at marketing" build more trust than those pretending to be experts at everything. What skill gap have you been hiding that you should probably just own?

I learned this the hard way in my last business: Stop being the person who does everything. Start being the person who builds systems that work without you. When your app crashes at 2 AM because YOU'RE the only one who can fix it, you don't have a business-you have a job. Are you building something that scales or something that needs you to function?

The hardest lessons in business aren't from courses or mentors. They're from watching your savings drain while that "perfect" employee ghosts clients. From realizing your partner's vision died the moment someone shot a gun into your investment property. From that anchor account walking away and suddenly you're scrambling. Survival mode teaches what success never could.