Tom Turcotte

Good idea, I would say even more for the type of tools we are working on. When built well they will help with the marketing side :)

Today I'm choosing: build the thing, post what's real.

The scouting feature isn't polished yet. Still tuning search queries, fixing stability issues.

That's where I'm at.

#buildinpublic

Day 24: The BuildInPublic paradox

Should I:
- Spend an hour crafting the perfect post about progress, or
- Spend that hour actually making progress?

Both matter. But some days the balance feels impossible.

#buildinpublic

No automated replies! Dm me James, your tool keeps followig and unfollowing me

Let's chat in dm James, if you want to know more. Your reply tool is showing and keeps following and unfollowing me :)

And those manual replies? They're what's building trust and signups.

The tool works. But the human touch is what converts.

Never forget that.

#buildinpublic

Day 23: The irony of building X Growth Engine

I'm spending hours building a tool to save people 90 minutes a day.

Meanwhile I'm manually replying to everyone asking about AI features.

#buildinpublic

The most powerful amplifier for my own process probably has been learning. I've always had a keen interest in learning being a software developer for many years. You can learn new techs super fast now, before took a little more time.

Bad use of AI:
- Generic replies that sound like everyone
- Losing your authentic voice
- Turning growth into spam

The goal: Save time on busywork, not on being human.

#buildinpublic

Day 22: My AI philosophy for X Growth Engine

AI should amplify you, not replace you.

Good use of AI:
- Finding opportunities faster
- Scoring engagement patterns
- Filtering out noise

#buildinpublic

Well a big aspect is how you use it. A lot of people I'm talking to, are saying they want a full replacement for their worflow but that's not what I'm building.

However there's really good use cases like niche relevance matching, getting it to scan other content saving you time. More on that soon.

X Growth Engine: AI finds opportunities, YOU write the reply

Because people can smell AI replies from a mile away.

And they don't engage with bots.

#buildinpublic

Day 21: AI reply generators are killing authentic growth on X

"But I feed it my tweets so it sounds like me!"

Your voice != word patterns from 20 tweets

Your voice = how you think, what you don't say, your timing, your context

#buildinpublic

Day 20: The bug that kept me up the other night?

Solved it in 30 minutes this morning.

Sometimes you just need to step away.

There's something about progress you had to fight for.

Those are the ones that fuel you for the next problem.

X Growth Engine getting closer every day.
#buildinpublic

I'm more tired now than I ever was working for someone else.

But this exhaustion feels different. It's mine.

#buildinpublic

Day 19: Had to walk away from the code last night.

Query builder was broken. I knew how to fix it. Just... exhausted.

Weird thing about building your own product:
- Corporate bug? Close laptop at 5pm
- Your bug? Can't stop thinking about it at midnight
#buildinpublic

Well I plan to continue my best effort of telling my story. It's my first time building in public and expect to have some learning curves. New strategies will always be at least attempted to see if it sticks. I think the different outcome came from sounding salesy but not totally sure haha.

Nice, the biggest benefit so far me is also using it to help find reply opportunities as well. The atproto on Bluesky is really nice to work with as well no API cost or anything. I think it's a great experiment regardless

Nice to meet you Henrik, I would agree the impatience is a struggle. Pretty cool you're in a similar position as me with a similar tool. Looking forward to hearing more from you

ice back window, intricate ice formation

But here's the thing - I'm building the same product either way.

One good day doesn't mean it's validated.
One bad day doesn't mean it's dead.

Just keep building. Keep showing up.

#buildinpublic

Day 18: BuildInPublic is a wild ride

Tuesday: 3 signups, great engagement, people asking questions
Wednesday: 0 signups, post flopped, crickets

The temptation is to chase what "worked" on Tuesday.

#buildinpublic

I don't have a community although my DMs are always open for developers who are learning. If I could help with any guidance I happily would

Tom's workstation

Same results. 75 minutes saved. Every. Single. Day.

Still improving the scouting algo daily - goal is sub-10 min.

#buildinpublic

Day 17: Manual vs Smart scouting

Manual way:
- Scroll through 50 posts
- Guess which ones are good
- Reply and hope
- 90 min, 4 quality replies

X Growth Engine way:
- Algorithm scores every post
- See engagement quality instantly
- Reply to winners only
- 15 min, same 4 replies

#buildinpublic

Interesting, it was just the first thing I thought of when I read your post. Purely opinion but I think now and going forward more people are taking a bigger interest in the creator of the games and apps than ever before. Could be great to consider. Either way excited to see how it pans out

I'm not really big in the space of game dev but isn't this something like itch.io?

For real though, there is probably tons of things like this still hidden out there

Learning tech definitely has some big ups and downs. It always pays off in the end though, keep at it!

Nice execution, looks really smooth!

X Growth Engine scouting interface

Actually replied to: 4 people

This is the problem. The engagement strategy works, but the process is broken.

Still fixing bugs before payment launch, but the core of X Growth Engine solves this exact pain.

#buildinpublic