1
1 Comment

I launched an app. B2B companies hijacked it within 24 hours.

The first sign-ups came in fast.
Too fast.

They weren’t users.
They were very generic B2B companies.
The kind selling “automate your leads”, “AI for growth”, “optimize your funnel”.

They signed up.
They built a first awkward experience.
Then a second one.

Nothing illegal.
Nothing broken.
Just out of bounds.

I noticed it very concretely on my public page.
You know, when a close-up photo of a scalp, clinical vibe,
ends up right in the middle of turquoise Caribbean waters.

In this case, that image wasn’t there by accident.
It was deliberately out of context.

That’s when you realize it’s not an aesthetic problem.
It’s an authority problem.

And you also understand why Squarespace only showcases
the very best sites built on its platform.

While I was dealing with RLS policies, webhooks,
random TypeScript errors coming out of nowhere,
that page was open without guardrails.

A place where some people came to test the limits
(and my nerves) at 2 a.m.,
while I was still figuring out where those limits were.

They weren’t using my product.
They were very clearly showing me
what I hadn’t locked down yet.

Later, I understood why.

That image wasn’t a mistake.
It was a message.

A very concrete way to show me
why I would “need” their service,
by creating chaos exactly where
I hadn’t planned guardrails yet.

I fixed it immediately.

Users can create, test, and iterate.
The public showcase, however, is protected.
New accounts don’t appear there by default.
Public visibility is switched ON
only when the framework is respected.

Since then, the public showcase does its job.

It shows the product.
Not experiments.
Not abuse.
Not disguised sales demos.

The framework is set.
The use cases are clear.
And now, finally,
the product speaks for itself.

posted toAvatar for product ¡HolaOlas!
¡HolaOlas!
  1. 1

    I’m waiting for the next hijack.
    It tells me where control still leaks.