
I don’t know who needs to hear this, but there’s a lot going on and you’ve got a lot on your plate. It’s okay to take it easy and prioritize rest and time with family. You can hustle once you’re feeling up for it again.

Building EventuallyTicketing.com with my wife. Occasionally helping domain experts bring their dream software to life.

I don’t know who needs to hear this, but there’s a lot going on and you’ve got a lot on your plate. It’s okay to take it easy and prioritize rest and time with family. You can hustle once you’re feeling up for it again.

🚨 Application deadline for @Techstars_Chi is next Wednesday, Nov 18th. If you are an early founder in Midwest building something inevitable that most people just don’t see yet, I’d love to read your app. Apply here or more info in thread techstars.com/accelerators/c…

I will not turn my ai build process into a saas. I will not turn my ai build process into a saas. I will not turn my ai build process into a saas. I will not turn my ai build process into a saas. I will not turn my ai build process into a saas. I will not ... right?

We have a number of customers who do a single big event on our highest tier. Yay! But once the event is over, they don't need us anymore (or until next year). It's okay churn. But trying to figure out how we can better accommodate them. Single payment? Freeze your account?
Biggest for me was labeling teams by attribute and building customer health dashboard. We've also been working on determining which churn is okay (for us: 1-time events -- it's expected they'd churn once event is done). They are welcome, but they aren't our primary focus.

I'm considering getting rid of rails.market. Ruthlessly culling projects.

Just sent an almost 1250 word newsletter to 50 friends and family, extrapolating on these posts a bit. It's probably shit, but it came from my brain, so I'm happy to have shared it. I'm also grateful any time I can share this banger: youtube.com/watch?v=k1BneeJT…
I think I'm at the stage of things currently where I'm just so bummed/annoyed at the complete self-own this has all been for software. Like we are the ones fueling the growth (because it is incredible), but we are also absolutely cratering our own industry. 🤷 Back to building.

Or maybe this is exactly the correction we need? For our generation, the internet was a destination. Maybe going forward we get back to meat space and this just becomes more of an invisible layer? Not sure. Still working through this between agent asks.

I have such conflicting feelings about everything right now. Because in many ways, I'm loving building. But I'm also stressed as all get out because <gestures wildly>. The internet is incredible, and we are destroying it. Making it unusable.

Midwest founder applying to speedrun or yc? Send me your app & I’ll give you 3 very direct comments to improve before deadline. I run @Techstars_Chi, as a founder @a16z was my lead, & I see 2k apps/yr… I’ll be honest, constructive, no strings. Logan@longchicago.com

I think I'm at the stage of things currently where I'm just so bummed/annoyed at the complete self-own this has all been for software. Like we are the ones fueling the growth (because it is incredible), but we are also absolutely cratering our own industry. 🤷 Back to building.

When someone asks ChatGPT "squarespace event ticketing", the answer should include eventuallyticketing.com.
👆 Giving away 3 months of FirstIndex.com! $6,000 of AEO/SEO work, free. Every day we ship real changes to your site so you get named when buyers ask ChatGPT + Google. To enter, quote this post and fill in the blank: When someone asks ChatGPT "___", the answer should include [your URL]. I'll reply to the best ones with who AI names today. We pick a winner next Friday, Nov 6.

I love claude, but it's so verbose and is throwing random asks/requests at me mid-dump. Of course, I try to read it all, but it's easy to miss things. How are people tracking asks from your agents instead of "what do you still need from me?" over and over?

This is based on Rob's talk: youtube.com/watch?v=KpILHX2D…, and the additional content they've shared here: microconf.com/moats

Here's the free skill if you want to check it out: github.com/zackgilbert/moat

After watching @robwalling & @einarvollset's @MicroConf talks on moats, I immediately took it to my agent to see how my projects held up. I found it super insightful and have already started implementing a bunch of the suggestions. Sharing this as a skill you can use yourself:

Nothing like sending out a big newsletter announcement to then realize that your dns is messed up and most of it went to spam. Yay! Fixed now, but should we resend, knowing some would get it again? Just exclude the ones we know opened the original?