Hey - It’s Nico.

Welcome to another Failory edition. This issue takes 5 minutes to read.

If you only have one, here are the 3 most important things:

• PicSee, an app that use face recognition to find your photos on your friends’ phones, shut down — learn why below

• How tech workers are feeling in 2026: a workforce splitting in two

• Cloudflare announced Monetization Gateway, a new business model for the web — learn why this matters below

This Week In Startups

🔗 Resources

How tech workers are feeling in 2026: a workforce splitting in two

How we booked 614 meetings with one inbound agent

The AI cost crisis is entirely self-inflicted

GTM Strategy 101: ICPs, Positioning, Messaging & More Explained

📰 News

Anthropic, OpenAI, and SpaceX are bigger than the last 25 years of tech exits

SpaceXAI releases Grok 4.5

OpenAI releases new voice models for more natural live conversations

Meta just launched a new AI generator

💸 Fundraising

Together AI, an AI cloud platform for training and running open-source models, raises $800M Series C funding⁠

TwelveLabs, a video intelligence platform for search and analysis, raises $100M Series B funding⁠

OXMIQ Labs, a licensable AI chip architecture startup, raises $35M Series A funding⁠

Queue, an autonomous robotic pharmacy startup, raises $12.6M seed funding⁠

Fail(St)ory

Where’s My Photo?

PicSee tried to fix a very annoying social problem: your best photos are often sitting on someone else’s phone. 

The app launched publicly in October 2025 and shut down in July 2026, after failing to turn that irritation into a large, self-propelling network.

What Was PicSee:

PicSee wanted to help you get every photo your friends have of you, without begging them to send it.

The app looked at a behavior everyone already understands. Friends take pictures of each other at trips, weddings, parties, college events, dinners, and family gatherings. The photos have value, but the act of sharing them is annoying enough that people delay it, forget it, or dump everything into a chaotic group chat.

PicSee used facial-recognition AI to scan a user’s gallery and identify people in their photos. It could then help invite those people to connect. Once both sides approved the relationship, the app could automatically exchange photos they had taken of each other.

The core loop was “give to get.” A user received photos of themselves by sharing the photos they had of others. 

The product tried to remove the small chores that kill sharing. No album creation. No link. No manual upload. No scrolling through a camera roll while deciding which photos are safe to send. The app could keep finding new photos later, so the exchange was meant to become recurring once the relationship was approved.

The awkward part was that one user could not make the product useful alone. If you joined PicSee after a trip and your friends ignored the invite, the magic stopped there. The app needed clusters of real-world relationships to move together.

That made the business harder than the product demo suggested. PicSee was free at launch and expected to monetize later through subscriptions or premium features. Before any of that mattered, it had to prove that users would pull their actual friends and families into a new sharing habit without heavy paid marketing.

The Numbers:

• 🏢 Founded: 2024

• 🚀 Public launch: October 2025

• 🛑 Shutdown: July 2026

• 📸 Photos shared: 150K+ by October 2025

• 📱 Downloads: 10K+ on Google Play

• 💰 Funding: Around $4.25M raised

• 👥 Team: 12 people

• 🔁 Capital returned: 60–65%

Reasons for Failure: 

• PicSee needed friend groups to arrive together: A normal consumer app can often win one person at a time. PicSee had a tougher path because one download only became useful when the right people joined too. Founder Mayank Bidawatka described the challenge well: the company was trying to “acquire networks,” and “there isn’t a distribution channel in the world that lets you do that.” The app needed your friends, your family, your travel group, or your wedding guests, not just another anonymous install.

• The old behavior was messy but deeply embedded: People complain about WhatsApp photo dumps, but they still use WhatsApp because everyone is already there. The same applies to iMessage, Instagram, Snapchat, Google Photos, and shared albums. PicSee had to move a low-frequency habit into a new app and then get the user’s social circle to follow. The pain was obvious after an event, but it faded quickly once the moment passed.

• Paid growth created misleading signals: Much of PicSee’s user growth came from “junk signups” acquired through Meta ads that did not convert into revenue. That is especially dangerous for a social product because installs can look like traction while adding almost no useful density. A user in one city does not help someone recover photos from their cousins, classmates, or travel friends somewhere else. PicSee needed connected groups, and ads were better at producing scattered users.

Why It Matters: 

• A relatable problem is not automatically a habit. Missing photos is annoying, but the pain shows up around specific events, not every day.

• Social products should measure density, not just signups. PicSee needed connected groups joining together, not scattered users from ads.

Trend

A New Internet Economy

Last week, Cloudflare announced Monetization Gateway, a way for websites to charge AI agents when they access pages, APIs, datasets, and tools.

On its own, it sounds like a niche infrastructure product. Put it next to AWS adding AI traffic monetization, x402 moving into the Linux Foundation, and publishers preparing for lower search traffic, and the signal gets clearer.

The internet economy is starting to move away from charging for human attention and toward charging for machine consumption.

Why it Matters

• The request becomes the new pageview. If agents consume the web without sending humans back to websites, founders need to think about pricing access directly, not only capturing attention after the click.

• Infrastructure companies are becoming the toll booths. Cloudflare and AWS are putting payment, identity, and access rules at the edge, which means machine monetization may be configured more like security rules than checkout flows.

• Open content is getting harder to justify. Pages, APIs, datasets, docs, and community archives can all become raw material for AI systems, so startups need a clearer answer for what stays free, what gets blocked, and what gets priced.

The Problem

The old web bargain was simple enough: let search engines crawl your site, get traffic back, then monetize that traffic through ads, subscriptions, affiliates, or leads.

AI agents weaken that bargain because they can take the useful part without creating a visit. A user asks for an answer, comparison, summary, recommendation, or action. The agent fetches the page, extracts what it needs, and returns something useful inside another interface.

Some traffic still comes back, but the ratio is ugly. Cloudflare has shown AI crawlers fetching far more pages than they refer visitors back to, which leaves the original site with the expensive side of the relationship: producing content, maintaining data, serving pages, and handling bot traffic, while the monetizable moment moves somewhere else.

Cloudflare’s Solution

Cloudflare’s Monetization Gateway wants to turn access control into a payment flow.

A site owner can put a price on specific resources behind Cloudflare: a page, an API route, a dataset, or an MCP tool call. When an AI agent requests that resource, Cloudflare can respond with HTTP 402, the old “Payment Required” status code, plus the price and payment instructions.

The agent pays (initially through stablecoins), sends proof of payment, and gets the resource. No account, no checkout page, no sales call, no custom billing setup.

The Trend

Cloudflare is not moving alone. There have been several signals these past months that all support the same trend: the internet is moving from charging attention to charging access.

• AWS had already added AI traffic monetization to WAF: Publishers and API owners can return an HTTP 402 response to bots and agents at the edge, then serve the content after payment is verified.

• x402 moved into the Linux Foundation: x402 is the payment protocol behind much of this: it lets a server ask for payment inside a normal HTTP request. Coinbase started it, but the Linux Foundation gives it a more neutral home, with early support from Cloudflare, Stripe, AWS, Visa, Mastercard, Google, Microsoft, and Shopify.

• Crawler controls are becoming more granular: Cloudflare is separating search, agent, and training crawlers, which lets site owners treat each type differently instead of choosing between blocking all bots or giving everything away.

• AI answers are already reducing click-through: A 2026 academic study on Google AI Overviews and Wikipedia found that exposure to AI Overviews reduced daily traffic to affected English Wikipedia articles by about 15%. If answer engines can satisfy the user before the click, content owners need a way to monetize consumption earlier in the chain.

• Large content owners are signing licensing deals: News Corp and Reddit, and others have shown there is real money in AI access to content. Request-level pricing is the version that could work for smaller sites without a custom enterprise deal.

Help Me Improve Failory

That's all for today’s edition.

Cheers,

Nico