The second club is when a project becomes a product

The most important thing we did in July fits in one boring sentence.

We cloned PagoCRM's development platform for a second club.

That's it. No launch. No party. A copy.

But the first time you build something for a client, it's a project. Everything is custom. Every decision is made for them. The second time is the exam. Can you take what you built and set it up again, for someone else, without starting from scratch?

On July 25th we found out. We cloned the platform into a new hosting space for the club.

And of course it failed.

The error said the destination hosting already existed, even though we couldn't see it in our panel. A ghost room in a house you thought you knew. We asked our hosting provider, they found it, we deleted it and cloned again. That same morning, everything was copied correctly.

I'm glad it failed. That hiccup showed us a step that still depended on someone checking something by hand. Not bad luck. A check that wasn't on the list yet.

Meanwhile, in the other tab

That same morning I was also dealing with a project that had just come to us from someone else. A subscriptions site where customers had signed up correctly, but the system wasn't charging their fees automatically.

A subscriptions system that doesn't charge on its own is, in practice, a list of people who owe you money.

I wrote to the developer of the payment plugin to ask for help, and we started gathering what they needed from the client.

The contrast was hard to miss. One system we could clone in a morning. The other, inherited and built as a one-off, wasn't doing its most basic job. If fees only get charged when someone notices they weren't, you don't have automation. You have a chore.

A project works once. A product works the second time without you having to remember how.

A project wearing a product's clothes

It's easy to think something is a product because it has a name and a price.

I don't think that's enough. Until you set it up a second time, you don't know how much of it is still a project wearing a product's clothes. Steps that only work because you know them. Settings that only make sense because you chose them for one client.

The second setup is where all that comes out. It's humbling. Like cooking your signature dish in someone else's kitchen and realising half the recipe was "you know, the usual pan".

It's also exactly what you need. Write down every step of that second time, because the first was full of decisions and the second shows you the real process. And whatever changes per club, name, colours, payment details, should be configuration, not code.

This matters more for us than it would for a funded company. Our services pay for our products. That only makes sense if the products, at some point, stop needing the same hours as the services.

A project grows with our time. A product grows with clubs. Setting it up for another club is one of the first real tests of which one we're building.

Building it once proved PagoCRM could work.

Cloning it proved it could work again.

P.S. The third one, I hope, will be so boring I won't even write about it.