GameSignal

I’ve been thinking about the usual advice for starting a software business:

Don’t build too much.

Validate first.

Put up a landing page. Find some beta users. Talk to them. Manually onboard them. Make sure people want the thing before investing in infrastructure, payments, onboarding, etc.

That advice makes a lot of sense when building software is expensive.

I’m starting to wonder if the economics have changed.

Over the past year, AI has dramatically reduced the amount of time it takes me to build software. Setting up authentication, infrastructure, a dashboard, Stripe, deployment pipelines—these aren’t month-long investments anymore.

Sometimes they’re afternoon investments.

I ran into this while building GameSignal.

I initially built an early-access process where someone requests access, I talk to them, manually register their repository, and then they can try the product.

I did that because I didn’t want to spend time building a complete self-service SaaS around something that hadn’t been validated yet.

But then I realized something:

I’m spending more time not building the infrastructure than it would take me to just build it.

So I’m changing the approach.

I’m building the self-service onboarding. GitHub authentication. Repository setup. Trial. Payments.

Then I’m going to put it in front of people.

If nobody wants it, that’s okay.

I’ll change it.

And that’s the other part I think AI has changed: the cost of being wrong has dropped.

If I spend three months building the wrong product, that’s expensive.

If I spend two days building the wrong experiment and discover nobody wants it, that’s information.

I can change direction on day three.

For a long time, one of the rules of startups has been:

Don’t build until you’ve validated.

I’m starting to wonder whether the new rule is closer to:

Build the smallest real version you can, put it in people’s hands, and let reality validate it.

Coding is increasingly becoming the cheapest part.

Waiting is becoming the expensive part.

One thing I've realized building side projects is that writing the software isn't actually the hard part - it's consistently telling people what you're building.

Every time I stop coding to write a devlog, weekly update, or X post, I feel like I'm taking time away from the thing I actually enjoy.

So I started building something for myself, which I called GameSignal.

Instead of asking me what I worked on, it watches my pull requests and generates:

• social post drafts

• weekly development summaries

• dev logs

right inside GitHub where I can see it.

The goal isn't to replace writing, it's to eliminate the blank page.

I've been dogfooding it on my own projects, and this week it generated my first automated weekly summary from a bunch of merged PRs, which was cool to see.

Now I'm trying to answer a simple question:

Is this a problem other developers actually have?

I'm looking for a handful of developers willing to try it on one of their repositories.

Website:
gamesignalai.com