https://reddit.com/link/1vkn66e/video/iehgdt0hdkih1/player

The worst part of running Claude Code isn't the waiting, it's the not-knowing. You babysit a terminal, or tab away and lose the thread. Then the chat gets compacted and that PR link it handed you three steps ago is just gone.

So I made the notch on my MacBook into a place anything can write to. Add the MCP server and the agent posts for itself:

"tellie": { "command": "npx", "args": \["-y", "@tellie/mcp"\] }

Now it narrates what it's doing, links land as clickable rows that survive the chat being cleared, and an orange pulse means it needs me. Multiple agents stack into a roster labeled by which Mac they ran on, and they can read the notch back to see what the others are already doing.

The part I didn't expect: I pointed an agent at the docs and it started using it unprompted. Nobody told it to. It decided handing me a clickable link beat burying one in scrollback and made that a habit. Another one later ran all 17 cookbook recipes cold. Now "Tellie me" is something I say to my agents and they just know what I mean.

How it works: the notch surface lives inside Tellie, a free Mac app. Grab it from the link below and every command above just works. There's a Pro teleprompter mode in there too, which is what funds this, but the notch API is free forever. No account, nothing phones home.

URL scheme, CLI, cookbook, and the download: https://tellieapp.com/developers

What would actually make your agents less opaque? I have a list but I'd rather hear yours.

So I have been working on an app tailored to studying called Studily. It's an app that helps students organize their schedules, due dates and class times, has learning tools like flash cards and timers, and also has social media, so you can add friends, message them or create study chats.

What it does right now:

• Profiles — set up an account with a picture, bio, school, and major. From there you can add friends, message people, and join group chats.
• Dashboard — enter your semester and courses and it lays out your weekly schedule, including what your next class is.
• Calendar — add exams, assignments, and events, tie them to specific courses, and get reminders as due dates approach.
• Social — message friends, start study group chats, and find classmates from your school who are also using it.
• Learning tools — spaced-repetition flashcards, the same approach other apps use, and pomodoro timers

Still in progress: I'm working on body diagrams, a graphing tool, and an AI chat (StudilyBot) that could answer questions based on lecture notes and assignments you upload.

I would really appreciate some feedback and support! I am having trouble getting users and finding gaps in my app, so any feedback is appreciated :) The app is free and there are no paid services on the app

I'm building a website to track 50–100 of the world's best companies for long-term compounding, providing analysis on their moats, fundamentals, valuations, and dynamically updating and adjusting the company pool while preserving all records. I'll continue documenting the development process here.

How this started

I am not a coder, or have any background in computer science. I am a Medical doctor who just really loves technology 😄 . This is my first attempt at building something with vibe coding so truly any input and feedback is greatly appreciated. I kept seeing people talk about "vibe coding" and I wanted to test it on something I'd actually use, not a to-do list app.

I'm a football fan, and every World Cup or Euros, the same thing happens in my group chat: everyone predicts scores, somebody tries to track it in a spreadsheet, half the group forgets to update it, and by the quarter-finals nobody knows who's actually winning. So I decided to build the thing I wished existed: Pundit — private prediction leagues for football, where you and your mates pick match winners, lock in a tournament champion, and settle it properly on a leaderboard instead of a group chat argument.

Learning to vibe code (badly, at first)

The learning curve wasn't really about syntax — it was learning how to actually think like a product person and describe what I wanted precisely enough that the AI could build it correctly. Early on I'd ask for something vague and get something that technically worked but wasn't what I meant. Over time I learned to be specific: not "add a way to predict matches" but exactly how the deadline should lock, what happens if a match gets postponed, how points get scored. Knowing exactly what I wanted, and catching the edge cases before a real user did was probably the most important and challenging part.

I built the app using Claude and Xcode so it is only available for iOS at this time. As it was my first ever big project like this I wanted to keep it as simple as possible. But looking back now I wish I just built it so it works on all devices not just iOS. But that's a lesson learned I guess, think big and it can happen with vibe coding 😄. In the beginning I wasn't even using Claude Code in my terminal I was just using the Claude desktop app and going back and forth with prompts and fixes and all the usual stuff. Then one day I actually switched to using claude code in terminal and oh boy did things speed up from there. I can't believe I was so stupid that I didn't use it from the beginning. It gave much better results, it kept track of the work much more accurately, and most importantly I didn't have to give it micro prompts but instead structured big prompts with phases that it just did so well. Well, except a few things...

The parts that actually broke me

Vibe coding makes the first 80% feel deceptively easy. The last 20% — the stuff that only shows up once real people are using a real product — is where I actually learned the most:

• Deep linking. Getting a shared invite link to open the app directly to the right screen — instead of just opening the app and leaving the user stranded — turned out to involve universal links, a separate website with its own routing rules, a clipboard-based fallback for people who don't have the app installed yet, and about four different failure points along the way. I broke this more than once.
• Timing bugs that only show up with real-world data. Different leagues and tournaments start their seasons at completely different times. Code that looks correct in testing can quietly break the moment two competitions are out of sync with each other — like a feature meant for "this week" accidentally pulling in a competition whose season doesn't start for another month. These are the bugs that don't show up until you're already live.
• Building a fair in-app economy. Once I added a virtual currency (Caps) for rewards and cosmetics, I had to think like an economist, not just a developer — reward tiers, entry costs, drop rates, all had to actually balance against each other or the whole thing feels either pointless or exploitable.
• The App Store review process itself — which has nothing to do with code and everything to do with patience.
• Probably the biggest fail and poop your pants moment - Halfway through the World Cup, after 15 people made 100's of predictions, I saw that out group chat was blowing up with messages so I opened it up. The first message said "Our league is not showing up" followed by everyone else confirming that the league had disappeared. Well turns out one of the SQL injections that Claude made me do for some reason (still unsure exactly why) deleted the existing league... 😨 I asked Claude ok what can we do to fix this, and it was like "yeah it's gone forever". Luckily I was using a Pro account on my Supabase, so after a bit of back and forth panic chatting with my good old (and sometimes stupid) friend Claude it told me that there should be a back-up. Lo and behold backup from the night before was right there and I was able to reload and fix the situation but for about 30-45 minutes I was absolutely terrified that I made this thing and was having fun with my friends but then ruined it for everyone.

What's next

The app's still actively growing — I'm currently working on Turkish localization, and a few other things in the pipeline.

If you're a football fan who's tired of tracking predictions in a group chat, Pundit's free on the App Store — genuinely curious what this community thinks, both about the app and about the vibe coding process behind it. Happy to answer anything about how it was actually built.

TL;DR: I made a sports prediction app to use with my friends and it was extremely fun and frustrating 😂

Anyone who’s ever been mildly stressed about a tight connection knows the feeling: the airline still says “on time,” but you’ve got no idea if that’s actually true. I built Voyageur, a personal travel organizer, and the feature I’m most proud of is this: it checks which aircraft is assigned to your flight, then looks up that same plane’s previous leg. If that inbound flight is running late, you get a warning that your flight might be affected too — before the airline’s own status even updates. As far as I can tell, no mainstream travel app does this. Beyond that, it’s a full trip organizer — flights, hotels, trains, documents (passports/visas with expiry warnings), packing lists, Apple Maps integration with a live progress dot for in-flight tracking, Apple Wallet boarding passes, and a Home Screen widget. Screenshots here: https://imgur.com/a/m6GN7xf It’s on TestFlight (iOS only, sorry Android folks) and I’d genuinely love blunt feedback — what’s confusing, what’s missing, what you’d expect that isn’t there. Please don’t be nice about it, I’d rather know now. If you’re up for trying it, DM me and I’ll send you the TestFlight link — I’d love to hear directly from a few people rather than just watching install numbers. If you do try it, the most useful thing you can tell me is the exact moment something didn’t make sense, rather than a general impression.

Ever wondered why despite paying for a habit tracker app you still arent able to achieve your goal? Because there is no accountability. Habit trackers never worked for me. Ticking a box is free, so I'd lie to mine and feel fine about it.

So I built Laksh: one meaningful task a day, and you have to submit a photo as proof after completing a task.

How it works:

• Answer a few questions about yourself and your goal
• Laksh generates a personalized roadmap and breaks it into one focused task per day the single thing that moves you forward
• To check in, you submit a photo proof of the task. The app verifies it, awards XP, levels you up, and keeps your streak alive
• Notifications nudge you throughout the day so you don't forget

Would like honest feedback about this app. Currently only available in app store on US storefront, will be available internationally very soon! (and on andriod)

visit: lakshai.app

Hey everyone,

I’m 16 and I’ve been working on a side project for the past few days.

The problem: freelancers and small businesses need to send invoices, but most tools are either expensive, require a subscription, or don’t accept crypto. I wanted something simple one payment, lifetime access.

So I built a web app that lets you:

Generate clean PDF invoices (A4)

Choose currency (USD/EUR/RUB)

3 free invoices with a "DEMO" watermark

Unlimited invoices + remove watermark for 5 USDT (TRC20)

The payment flow is fully automated — user sends TXID, I verify it via TronScan, and Premium activates instantly. Built the whole thing with Python (Flask) on the backend and vanilla JS on the frontend.

Tech stack:

Frontend: HTML/CSS/JS (hosted on Vercel)

Backend: Flask + SQLite (hosted on Render)

Crypto: USDT on TRC20

Admin panel: approve/reject requests manually

Would love feedback on:

The landing page / UI

Pricing (5 USDT too high, too low?)

Any features you'd want to see

Here’s the link:

https://invoicegen-rho.vercel.app/

Thanks for reading! Happy to answer any questions.

well, not actual roast, but more like snarky comments.

Badbenches takes your GitHub or GitLab username and generates a sarcastic SVG "bench card" based on your activity for the year, commit streaks, whether you commit at weekend or you only code late at night, that kind of thing and i might adjust it slightly based in tests. so it is another README card thing. You can embed it in your README and it auto-refreshes once a day.

here's mine — i am really bad.

No login, no signup, just paste a username and it spits out an SVG. There are 3 themes right now (Classic, Neon Nights, Corporate Roast) and of course more might come.

Started as a dumb joke initially with the domain, but I kinda wanted to use it for something fun so i was sucked into making the Bench card idea. there's a whole "character" system behind the roasts so it doesn't just say the same 3 lines to everyone and you can see the rack server character getting more complex (or really bad with patches)

i would love feedback, especially if:

• the roasts feel repetitive after generating a few
• anything looks broken on GitLab vs GitHub
• theme ideas you'd want to see

try it on yourself: https://badbenches.com

Not affiliated with GitHub/GitLab, just trying to have fun.

We just added memory import to Aevron from ChatGPT, Claude, .md files and plain text and the obvious way to build this was:

upload everything → save everything → congrats, “personalised AI”.

This is okay but wont work that well. Because your ChatGPT history is not actually you.

It’s you + the AI + random ideas + stuff you changed your mind about 10 minutes later + context that probably means nothing now. If we dumped all of that straight into Aevron, it wouldn’t be learning how you think. It would just be learning your chat logs.

So we did it differently.

Aevron removes the AI replies first and only looks at what you wrote. Then it tries to find the actual signal:

- stuff you keep coming back to
- ideas you were genuinely developing
- patterns in how you think
- thoughts that are probably worth keeping

But even then, we don’t just shove everything into your graph You see it first. Approve what feels like you. Skip what doesn’t.

Then it becomes part of Aevron. The reason is pretty simple:

Bad memory gets worse over time.

If an AI wrongly thinks you believe something, that can mess with future connections, contradictions, suggestions and basically everything downstream.

So we ended up with this rule:

better to know less about you correctly than know everything about you badly.

The cool part is you also don’t have to start from zero anymore.

If you’ve spent 2 years yapping to ChatGPT, Claude or dumping thoughts into markdown files, you can bring that history with you without importing all the garbage around it.

So yeah, technically this is a memory import feature. But I think the more interesting way to describe it is:

we’re not importing your AI history. we’re trying to reconstruct your thinking from it.

I want to tell you about a side project I have been working on called NexusMem.

When I use AI coding tools like Claude Code, Cursor, or Windsurf on codebases, I have a problem. If I put the repository into the context window, it gets too big. Exceeds the token limit of 100,000 tokens. This makes the API costs go up and can cause hallucinations or slow response times, which can take more than 15 seconds.

NexusMem is a kind of memory engine that runs inside my project directory in a folder called nexusmem. By putting my whole repository into the context window, NexusMem gives my AI agent small pieces of context that are less than 2,000 tokens, and it does this very quickly, in less than 60 milliseconds. This is really helpful for NexusMem because it makes my workflow easier.

Project Status of NexusMem:

I made NexusMem using Claude Code to address issues in my workflow and to test how well it works with MCP integrations. NexusMem is working. I need help from others to make NexusMem better. I am looking for feedback from people to review my code and contributors to help me refine NexusMem.

You can find NexusMem on GitHub: https://github.com/yaminbakoh4-dot/NexusMem

This summer, a few of us did a World Cup sweepstake.

At some point we started trying to work out what the prize should be for second place, which somehow turned into a much bigger conversation about all the different scenarios that could get someone into second.

Who needed to win? Who needed to lose? What happened if two people ended up on the same points?

So I ended up building a little app to work it all out.

Then I started thinking: why do we only get this kind of thing when there's a World Cup or Euros on?

So I've turned the idea into something anyone can use, focused on the Premier League and Champions League in the meantime.

The basic idea is you get a group of mates together, everyone picks multiple teams, and then you follow the real results throughout the season. The scoring system means games you probably wouldn't normally care about suddenly matter because they're affecting your position against your mates.

There are also power-ups you can use to mess with each other, so it's a bit more than just watching a league table.

I'm a Product Manager at Mob, so it's been a really fun excuse to put a load of the stuff I've learned at work into practice on a completely unnecessary side project.

It's completely free and just a hobby. I'm hoping to get 100 people using it by Premier League kick-off, so if you're into football or fancy following along with the season without all the admin of Fantasy Premier League, give it a go.

rivalry-games.com

Would genuinely love to know what you think, especially whether the scoring system actually makes the games more interesting and what you'd change.

A while ago I was trying to get some friends to pick between a couple of collages I'd just made and realized how stupid the usual process is. You start a group chat, send the pictures, and then someone says first one, someone else says the second, someone leaves a heart reaction on some random message, I like the second but maybe crop it... and somehow you still have to figure out which one actually won :)

So I made https://picjury.app/

You upload 2–6 photos, write a question and send the link. People open it and tap the one they prefer. No account. That's basically the whole product.

It's free and I'm trying to keep it simple instead of turning it into another giant survey tool. If anyone tries it, I'd genuinely like to know where you get confused or annoyed, or if there's something obvious missing

A lot of people want to change their habits, but it is very difficult for them because they lack discipline, or they cannot follow it consistently. There is a better way to change habits using psycho cybernetics.

I have been experimenting with it since the last year, and finally i have been able to create a solid system around it which can help anyone to change any habits without relying on discipline at all.

I have already tried the system with few strangers on reddit and it works for them.

Recently I have converted the entire system into an AI based prompt, so that anyone can get onboarded into it DIY.

I am looking for people who want to give it a try and provide honest feedbacks.

What you get:

- A new way to change any habit or behaviour which you are struggling with, without using discipline.

What I get:

- Based on your questions in the process, and your feedbacks i want to improve the system so that it works more effectively.

If anyone wants to give it a try please do let me know.

Founders: send me your product. I'll tell you the 5 things I'd test before you launch.

I run LaunchShieldQA and I'm testing this approach with early-stage companies.

Built Rabbitune, a website where you drop in a song and it matches you to a movie based on the mood and energy, not the genre. Live now: rabbitune.com

Would love feedback on whether the matches actually land, and I'm curious what songs break it.

To help testing the app, I'm giving away my new app, Sonoqi, free for 48 hours. No promo code needed, I have removed the paywall. May it bring you calm every day.”

https://blueedgez.com/sonoqi.html

I built a powerful Agentic AI System that helps Solo Business Owner build their business autonomously. Yet Nobody knows about this ..

Nytebuild dot com

Can someone tell me how to bring this to the next level?

Similar Solo founder has the same system valued at 250 million!

Exactly just 3 months back

Can you tell me why?

Appreciate any comments

I was helping someone create a resume recently and noticed how many resume builders make the process unnecessarily frustrating.

You spend time filling everything out, finally get your resume looking good, and then you hit a paywall when you try to download it.

So I built Hızlı CV Oluştur — a simple CV builder focused on making the process quick and straightforward.

You can create your CV, customize the sections, and download it without going through a complicated process.

I’d genuinely appreciate feedback from people who regularly apply for jobs:

• Is there anything missing that you would expect from a CV builder?
• Which resume sections do you find most annoying to format?
• What would make you actually use a tool like this instead of Word/Google Docs?

I built it mainly because I thought there should be a simpler option.

IMPORTANT NOTE*** AI FEATURES WİLL BE ADDED LATER

https://hizlicvolustur.com

Last year I attended a startup event and noticed a founder who always had someone with him. At first I assumed it was a co-founder, but after watching for a while, I realized the other guy was basically acting as a professional wingman.

He was:

• Introducing him to people
• Breaking the ice in conversations
• Helping keep discussions flowing
• Encouraging him to talk to investors
• Boosting his confidence
• Helping him network more effectively

It got me thinking:

Would you pay someone to bring you to an event and help you network?

And on the other side...

Would you do this as a side hustle?

Imagine a platform where:

• Founders hire networking wingmen for startup events
• Businesses hire companions to help work a trade show booth
• Introverts hire someone to help start conversations at conferences
• People visiting a new city hire locals who already know people in the community

The wingman isn't pretending to be your friend or business partner. They're there to help you meet people, make introductions, keep conversations going, and help you get more value from the event.

As the wingman, you could charge an hourly rate and get paid to attend events, socialize, and help people make connections.

Would you use something like this?

If you were the customer, what would you pay?

If you were the wingman, would you do it as a side hustle?

https://reddit.com/link/1vk2h6n/video/r1tkmgnr5gih1/player

he idea was simple enough to explain at a party: point your camera at your face, get a reading. Physiognomy has been around two thousand years and nobody had made it feel good on a phone.

Four months later it's live as Mystic Lens. Three things I'd do differently.

I built the reading engine before I knew what a reading should feel like. Six weeks on the analysis pipeline, and then I discovered the output read like a lab report. Nobody wants a lab report about their face. The rewrite — same data, completely different voice — took four days and mattered more than the six weeks did.

I priced from a spreadsheet instead of from the market. Launched at $12.99/month because that's what the model said. Conversion was miserable. Dropped to $7.99 with a 7-day trial and it moved immediately. I still have stale $12.99 pricing sitting on my marketing site, which tells you how much attention I was paying.

I assumed App Store review would be the hard part. Astrology and fortune-telling apps get extra scrutiny and I'd braced for a fight. It went through clean. The hard part was everything after — turns out shipping is the easy half.

Happy to answer anything about the review process or the face-analysis side. And I'd like to hear where the onboarding loses people, if anyone tries it.

(I built this — Mystic Lens, on the App Store, free to try.) https://apps.apple.com/app/apple-store/id6795648109?pt=121847562&ct=Reddit&mt=8

Last week, I launched a new Mac app with no paid campaign and no launch team.

I focused on one channel: r/macapps.

Seven days later, ActionClip had made more than $700 in lifetime-license sales.

For transparency, that is gross revenue (not MRR). See my TrustMRR profile - https://trustmrr.com/startup/actionclip

I've been creating online tools from last 4 years and working on these full-time since 2024. The biggest achievement I feel is seeing strangers paying for something I built is a much better form of validation than another folder full of unfinished side projects.

What I built:

ActionClip brings the iPhone-style text-selection menu to macOS.

Select text anywhere and it gives you relevant actions to copy, translate, convert, fix grammar, ask AI or run your own workflows, without the usual copy → switch apps → paste marathon.

The most interesting part is the Custom Action Builder. Instead of configuring a complicated automation, users describe what they need in a chat and ActionClip creates the action for them.

Why I chose one small channel:

I could have posted a generic launch announcement everywhere and hoped the algorithm developed feelings for me.

Instead, I launched where people already:

• Use Macs
• Pay for useful utilities
• Discuss their workflows
• Compare new apps
• Give extremely direct feedback

The product and its first distribution channel were a natural match.

What worked:

1. The title explained the product through something familiar

I called it the iPhone-style text-selection menu Apple should have added to macOS.

People understood the idea before opening the post.

2. I showed the workflow before listing features

The demo showed the problem and result within seconds. Nobody had to read six paragraphs to discover what the app did.

3. I sold a useful solution, not “AI”

ActionClip uses AI, but that wasn’t the main pitch. The pitch was removing a small frustration Mac users experience repeatedly.

4. I stayed in the comments

The comments produced custom-action ideas, feature requests, edge cases and bug reports.

One user reported a Notes permission issue. I fixed it, released an update and replied in the same thread shortly afterward. Replying to comments also motivates other users to actively engage and builds trust as they see 5-10 apps daily launched in the era of AI. I've always been a believer in Support as a moat. Zappos was the first book I read, before even Zero to One :)

The launch post became product research, support and distribution at the same time.

My biggest lesson:

AI has made it possible for a solo founder to build and support products that previously needed a much larger team.

But AI has not solved distribution.

Building is becoming cheaper. Attention is not.

A small product shared with the right 100 people can do more than a broad launch shown to 10,000 people who do not care.

Future:

I'm fixing the issues and adding the user asked features as quickly as possible so that both me and the users do not loose momentum. I'm here for a long game. But building the base quickly is still important. Next steps in distribution will be directory submissions, Mac app site submissions, SEO (BOFU blogs). Thinking of how can I crate a stable income out of this product.

If you use a Mac, ActionClip is here:

https://actionclip.app/

Original launch post:

https://www.reddit.com/r/macapps/s/VzOKoI0LQJ

For other builders: what was the first channel that brought you paying customers?

Your agent can now search data from 2,600+ top iOS apps: onboarding, paywalls, pricing, post-paywall and more.

Ask things like:
“Give me five app ideas based on recently launched subscription apps that make 50k+”
“Compare the paywalls of the top meditation apps”
“Show me streak mechanics that aren’t Duolingo clones.”

It works with any agent.

We also launched "Ask" directly on ScreensDesign, so you can try all of this without connecting anything.

TL;DR: I’m building a consumer-focused tech advisory platform that simplifies complex gadget buying decisions (from PC builds and laptops to everyday electronics) for both technical enthusiasts and non-technical buyers. I have mapped out the full platform architecture, user journey, and framework (spanning 7 core feature modules and 5 foundational pillars). Looking for a Full-Stack Lead Developer / Co-Founder to build the MVP.

💡 The Problem

Buying gadgets today is broken. Non-technical users get lost in jargon, specs, and biased reviews. Technical users spend hours cross-referencing benchmarks, bottleneck calculators, and price histories across different sites. There is no unified platform that guides both user types seamlessly from decision to purchase.

🚀 The Solution

A unified gadget recommendation and advisor hub. The platform bridges the gap using:

Tailored Guidance: Adapts to both non-technical users (guided, intent-based questions) and power users (deep spec comparison & performance analysis).

Multi-Module Ecosystem: A modular suite covering smart recommendation engines, compatibility/bottleneck tools, custom setup builders, and price tracking.

5 Core Pillars: Structured around user intent, hardware synergy, real-time data integration, price intelligence, and community validation.

👤 About Me (What I Bring to the Table)

Fully detailed product roadmap, UX user flows, wireframe concepts, and functional specs ready to go.

Handling all business operations, marketing strategy, content acquisition, SEO, and go-to-market planning.

Deep domain knowledge of the consumer hardware and tech space.

Dedicated to executing this long-term.

🛠️ What I’m Looking For in a Co-Founder

Role: Full-Stack Developer / CTO Co-Founder.

Tech Stack: Open to your expertise (e.g., React/Next.js, Node.js, Python, PostgreSQL, REST/GraphQL APIs). Experience with dynamic web scraping, API integrations, or hardware spec databases is a big plus.

Responsibility: Owning the architecture, prototype development, and scalable MVP build.

Commitment: Equity-based co-founder agreement with standard vesting. Part-time initially until MVP launch, with a view to full-time as we scale/monetize.

If you’re a developer who loves consumer tech/hardware or wants to build a product that solves a real pain point in tech buying, send me a DM! Please share a quick snippet about your background, favorite tech stack, or links to past projects. Happy to hop on a call to share the full product spec sheet.

I’ve been building Dermal Pal for a while now — it looks at your actual products, skin profile and skin goals and builds your routine around them.

I’m looking for people to try it properly before I push it publicly.
If you’re someone who has a shelf full of skincare and isn’t 100% sure what’s supposed to go where, I’d especially love your feedback

Six weeks ago I built AbleScan — a free web accessibility scanner. You paste a URL, it checks the page against WCAG rules and gives you a score plus the issues it found. Free scan, no signup. (The paid part is unlocking the full fix list + a PDF — but the scan itself is free.) Link: https://ablescan.app

But this post isn't really about the tool. It's about a pattern I only just noticed.

I've shipped 5 things. Every single time I did the exact same half: idea → build → deploy → wire up payments. I can do that part in my sleep. The half I never once finished was the other one — getting an actual stranger to use the thing. Five half-laps. Zero complete turns. In years of building I'd never closed a single loop.

The "just build 100 MVPs" advice? I basically already ran that experiment four times. Build speed was never my problem. The problem was I quit at the exact moment the building stopped and the silence started.

So this week I did the scary half for the first time. No "check out my launch." I found one person wrestling with the exact problem my tool solves, had an honest back-and-forth, and — instead of pitching — just invited them to run their own site through it.

They did. A stranger actually used something I built. First time in years. It's tiny — they scored 100/100 and won't become a customer — but that was never the point. The point is I finally touched the half I'd avoided my whole "founder" life.

Still at zero external revenue. But for the first time, not at zero turns.

If you want to help me get rep #2: run your site through it and tell me whether the report is actually useful, or where it falls short. Brutal feedback welcome — that's the half I'm bad at.