In partnership with

GM. This is Needs to Exist (aka NTE), delivering you a startup idea that makes building feel collaborative again.

NTE Pro: 6,500+ ideas you can actually build, go steal one.

WhoFiled: See what’s becoming important before it’s obvious.

Check out all the past newsletters here

Here’s what we’ve got for you today.

• Daily Idea - Collaborative localhost sharing

• The Async Crowd vs The Multiplayer Builders

Multiplayer localhost collaboration tool

The One Liner

Turn localhost into a multiplayer workspace

The 140 character tweet (or X) version

Share any localhost app as a live, collaborative workspace with comments, presence, and secure access. No staging, no screenshots ever again

The Longer Story Version

The Problem

Sharing work-in-progress is still broken.

You build something locally. It works. You want feedback.

So you send screenshots.
Or record a Loom.
Or spin up staging (and pray it works the same).

Then the dance starts:

“Can you see this?”
“No.”
“Wait… refresh.”

We’ve normalized friction.

Meanwhile, tools like Figma made real-time collaboration feel obvious.

You see people.
You see cursors.
You comment exactly where it matters.

Then you go back to building actual apps…
and all of that disappears.

The problem isn’t building.
It’s sharing what you’ve built.

The Solution

What if every localhost link was collaborative by default?

You run your app locally.
Click a button.

It generates a secure link (like ngrok).

But layered with:

• live presence (who’s here)
• cursor tracking (what they’re doing)
• inline comments (feedback exactly where it matters)

Now someone opens your app…

And they’re not “viewing it.”
They’re inside it with you.

Design reviews.
Client walkthroughs.
Debugging sessions.

All real-time.
All shared.

It’s Figma… for anything.

How We’d Build It

Phase 1: Prove it (fast + scrappy)
• CLI or Chrome extension to expose localhost (Cloudflare tunnels / ngrok)
• Inject simple comment layer into DOM
• Basic auth (password / invite link)
• Presence indicator

Tools: Supabase (realtime), Liveblocks, Lovable

Goal: devs say “this is magic”

Phase 2: Make it sticky
• Cursor tracking + click heatmaps
• Threaded comments tied to UI
• Session replay
• Slack + Notion integrations

Tools: Replay.io, PostHog

Goal: replace Loom + screenshots

Phase 3: Own the workflow
• Team workspaces + permissions
• Persistent preview environments
• GitHub PR + VS Code integrations
• API for embedding into dev workflows

Goal: become default sharing layer for apps

Why It Needs to Exist

We sped up building.

AI. Indie hackers. Faster iteration.

But feedback loops? Still slow.

And that’s the real bottleneck now.

The teams that win won’t just build faster.
They’ll learn faster.

This turns:

“check this out” → into a shared moment

And once you feel that…

Screenshots feel prehistoric.

700+ teams have Viktor reading their Google Ads every morning.

Your media team opens Slack at 8am. There's a cross-platform brief in #growth: Google Ads spend vs. ROAS, Meta CPA by campaign, Stripe revenue by channel. Viktor posted it at 6am. Nobody asked for it.

Last week, one team's Viktor caught a spend spike at 2am on a broad match campaign and flagged it in Slack: "CPA up 340%. Recommend pausing and shifting budget to the top two performers." That would have burned $3K by morning. The media buyer woke up to a problem already handled.

Your strategist reviews spend trends. Your account manager checks revenue attribution. Same Slack channel, same colleague, before anyone's first coffee.

Google Ads, Meta, Stripe. One message. No Looker, no Data Studio. Anomaly detection runs around the clock. Cross-platform reporting runs on autopilot.

5,700+ teams. SOC 2 certified. Your data never trains models.

"Viktor is now an integral team member, and after weeks of use we still feel we haven't uncovered the full potential." — Patrick O'Doherty, Director, Yarra Web

Start free. $100 in credits →

The Async Crowd vs The Multiplayer Builders

There’s a version of this where the idea sounds amazing… and completely unnecessary.

An engineer hears it and thinks:
“Cool demo. But I already use ngrok. I can send a link if I need to.”

And they’re not wrong.

Because technically… this already exists.
You can share localhost.

So why build a company around it?

—

But then you watch what actually happens.

People don’t just need access.
They need alignment.

And ngrok gives you a tunnel… not a shared experience.

No presence.
No cursor.
No way to say “this exact thing right here.”

So what happens?

People still default back to Loom.
Or screenshots.
Or long Slack threads explaining what someone else should be seeing.

—

Now the skeptic pushes harder.

“Okay, but how often does this really happen? Is this a daily problem… or just a dev edge case?”

Fair.

Because if this is only used occasionally, it’s a feature.
If it’s constant, it’s a workflow.

And that’s the entire bet.

—

Then comes the real concern.

“Is this even safe?”

You’re literally exposing localhost.
Internal tools. Half-finished features. Possibly sensitive data.

One mistake, and you’re sharing more than you should.

So now the product isn’t just about collaboration.
It’s about trust.

Permissions. Access control. Expiring links.

Without that… it never gets adopted.

—

And then the final pushback.

“Even if it works… do teams switch?”

Because people don’t change workflows easily.

They tolerate bad ones.

So the bar isn’t “this is cool.”
The bar is “this is so much better that I stop using Loom.”

—

But if it clears that bar…

It’s not a sharing tool anymore.

It’s the default way work gets reviewed.

And suddenly the question flips from:

“Do we need this?”

to

“Why were we doing it the old way at all?”

You don’t need more ideas. You need better ones.

NTE Pro is 6,500+ startup ideas that actually make you stop and think, “wait… why doesn’t this exist?”

Not recycled trends. Not AI wrappers.
Real ideas with clear wedges, real demand, and actual paths to build.

When you’re stuck, you don’t need inspiration.
You need direction.

Scroll once, and you’ll find something you could start today.
Something no one’s executed on yet.
Something that could be yours.

NTE Pro isn’t content.
It’s a starting line.

Go sign up

Something important just happened. And you are early.

WhoFiled surfaces companies the moment they become relevant. Not trending. Not viral. Relevant.

A Form D gets filed.
A product quietly launches.
A team starts shipping.

Most people find out months later.

You see it now.

Start with one thing you care about. A company, a market, a random idea.

WhoFiled connects the dots across filings, products, and communities, then explains why it matters in plain English.

No noise. No dashboards you won’t use.
Just signal.

If timing matters to you, this matters.

Start discovering.

One More Meme