@ghz86 Yes it connects via the appstore connect api using the key you create in asc. No password used. It includes sales, downloads, purchases and ad spend for analytics. What metric are you specifically looking for?
Every few months I talk to a founder who has most of the pieces right. The product is sharp, the team is strong, they’ve been at it for a year or two, and yet something isn’t quite working. They can feel it, but they can’t quite name it.
Almost every time, the answer is the same. They’re excellent at two of the three things that actually determine whether a startup makes it, and they’ve been quietly hoping the third would sort itself out.
It almost never does.
Underneath the specifics, most startup stories come down to three underlying challenges. Getting any one of them wrong is enough to sink you, and the painful part is that they’re rarely the ones you think you’re bad at.
1. Knowing what problem to solve
This is the one founders most reliably underestimate, because it feels like the easy part. You have an idea. You’re excited. You start building. By the time you realize the problem wasn’t quite what you thought it was, you’ve spent a year of your life on it.
The core difficulty isn’t generating ideas, the world has no shortage of those. It’s telling the real ones from the ones that only look real, which is much harder than it sounds when you’re the one who came up with them. Founder bias is a quiet killer here. If you faced the problem yourself, or you’re sure your customers must be facing it, you can hold that belief indefinitely without a single piece of external evidence. Conviction is useful fuel, but without validation, it’s indistinguishable from wishful thinking, and it feels exactly the same from the inside.
The sharpest framing I’ve heard for this came from the YC crowd: vitamin versus painkiller. You can validate that a problem exists and still be completely wrong about whether it’s worth going after. The real question isn’t “is this problem real?”, plenty of real problems aren’t worth a company. The real question is “is this problem painful enough that someone will actually pay to make it go away?” Most problems aren’t. Most problems have a workaround that’s just good enough, and customers are perfectly content to live with it forever. Vitamins are nice. Painkillers are necessary. Startups that sell vitamins spend years explaining to people why they should care, and most of them run out of money before the explanation lands.
Timing lives inside this question too, even though it often gets treated as a separate thing. A painkiller is only a painkiller right now. Show up three years too early and you’re educating a market that isn’t ready to buy, which, from the customer’s point of view, is indistinguishable from being sold a vitamin. Show up two years too late and the workarounds have hardened into incumbents with every structural advantage you don’t have. Timing isn’t really something you solve; it’s something you notice. When you realize you’re fighting the calendar, pushing harder is almost never the answer.
Get this layer wrong and nothing downstream can save you. You can’t out-execute a problem the market isn’t ready for.
2. The skill to build something genuinely great
This is the most obvious of the three, which is why I almost skipped it. But there’s something non-obvious buried underneath it that’s worth naming.
Most teams don’t fail at quality because they lack the skill. They fail because, somewhere around version two, they stopped caring about the details that made version one feel alive. “Good enough” is a seductive trap, because it always looks like pragmatism. You have a roadmap. You have limited time. Shipping feels like progress. And it is, until you notice that every shortcut you took is now a small tax your customers pay every day they use your product.
The teams that win are the ones who refuse to normalize mediocrity in their own work. Not because they’re perfectionists, perfectionists don’t ship, but because they understand that quality is the compound interest of every small decision, and customers can feel the accumulated weight of those decisions even when they can’t articulate why. In a world where every category has five credible competitors, customers don’t owe you their loyalty. They want ROI. They’ll give it to whoever obsesses hardest over earning it.
If you’re willing to settle for a good-enough product, you’d better hope your competitors are too. They almost never are.
3. Figuring out distribution
This is the one that kills more startups than the other two combined, and it’s the one most founders quietly hope won’t apply to them.
You can solve a real painkiller problem. You can build something beautiful. And you can still die, cleanly and completely, because no one ever hears about it. A great product with no users is not a company. It’s a hobby with a higher burn rate.
The trap is that distribution looks like a solved problem from the outside. There’s a whole playbook: run ads, plan a Product Hunt launch, grind on SEO, publish on the blog, post on LinkedIn and X, build in public, line up influencers, sponsor a newsletter. Every one of these tactics has worked for someone. None of them, on its own, is a strategy. When founders work through the whole list and nothing moves, the usual response is to try again, harder and louder and with more budget. That’s almost never the answer.
The uncomfortable truth is that distribution can’t really be copied, it has to be discovered. Every company that broke out did it on the back of some motion that was unique to their product and their moment, and looked obvious only in retrospect. Dropbox turned storage into a referral loop. Airbnb piggybacked on Craigslist’s existing supply. Figma made the shared link itself the growth mechanism. None of those were on anyone’s playbook before they worked. Each of them came out of founders staring long and hard at the specific shape of their own product until they saw a path no one else had seen.
That kind of insight takes time. It’s uncomfortable, because it means you can’t just do what the last successful company did. You have to find your own thing, and you have to keep looking, often past the point where it feels like you should have found it already. Most founders give up on that search too early and fall back on the playbook, which is why most startups die with a great product and no one using it.
The part no one tells you
Here’s the thing that took me a while to internalize: almost every founder I’ve ever met can recite the challenges above. That’s not what separates the companies that make it.
What separates them is honesty, the ability to stay honest with yourself about which of these you’re currently failing at. And there’s always at least one. The product that felt great last quarter feels dated this quarter. The problem you validated a year ago has shifted under you. The distribution channel that was printing money is now saturated. Or, the one that takes the longest to show up, the unit economics you waved your hand at in year one turn out not to work in year three, no matter how well everything else is running. Product-market fit gets all the attention, but model-market fit is a quieter killer, because the symptoms tend to look fine right up until they don’t.
None of this gets solved once. It gets re-solved, constantly, as the ground moves underneath you.
The founders who survive aren’t the ones who are strongest across the board. They’re the ones who can look at their own company on a Tuesday morning and correctly name which piece is broken right now, even when it’s the one they most want to believe is fine.
That’s the whole game.
Computer use is now in Claude Code.
Claude can open your apps, click through your UI, and test what it built, right from the CLI.
Now in research preview on Pro and Max plans.
Every outreach message I get these days are super targeted as they are all now written by agents. Its unbelievable how obvious these messages are. I will hereafter only respond if your message has at least one typo or grammatical mistake 😀
#outreach#marketing
We are in Austin, TX for #SXSW2026 🤘
The official schedule has 4,000+ events! Finding the sessions that actually matter to you means endless scrolling, dozens of tabs, and a lot of guesswork.
So we quickly built a tool with Claude to make it easier to find tech events this year.. Filter by date, time, category, search across sessions, bookmark your picks, and view venues on a map. And, yes, it’s mobile friendly so you can check on-the-go.
It’s at https://t.co/LiSBiLreRv
No login. Just a better way to plan your SXSW.
Ideas collide with ambition at SXSW - and this year, Sw3ll AI is in the mix.
#sxsw #ai #sw3ll #claude #futureofwork #buildinpublic #startups #SXSW26
Software developers are nervous right now. And honestly? They should be paying attention.
The question spreading through every coding bootcamp and engineering team is the same: If AI can build software, do we still need the people who build it?
To answer that, travel back to 1970. Meet David an accountant filling ledgers by hand, one column at a time. Every number entered carefully. Every mistake a disaster. One wrong figure on page 12 and it cascades through forty calculations two hours of correcting work he'd already done, fingers smudged gray from erasing. Tomorrow, he'd do it all again.
Then, in 1979, everything changed.
A programmer had an idea that seemed almost absurd at the time: what if a machine could hold the entire ledger, and when you changed one number, it recalculated everything automatically?
VisiCalc was born. The first killer app.
What required a trained specialist now required... a desktop machine and someone who knew how to use it.
The spreadsheet revolution had begun. Lotus 123 followed. Then Excel. Then Google Sheets. Decades of software, each more powerful than the last all designed to do what David used to do by hand.
So here’s the question: Where is David now?
He still has a job.
Not despite the spreadsheet, because of it.
His company no longer needed him to adjust cells manually. They needed him to think. What happens to margins if costs spike 20%? What does this revenue dip actually mean? David stopped being a calculator. He became a strategist.
The tool didn’t replace him, it freed him to do the work only he could do.
But history leaves something out: not everyone made that leap. The clerks who clung to manual work who waited for the machine to go away were displaced. Not because technology was cruel, but because the value had moved somewhere else, and they didn't move with it.
This is exactly where software development stands today.
AI coding tools are the spreadsheet moment. They don't get tired, don't make typos, and can scaffold an entire application while you're still writing your first function.
The developers who thrive won't be the ones pretending this isn't happening.
They'll be the ones who put down the ledger.
**Be less like the bookkeeper. Be more like David.**
#claude #ai #generativeai #futureofwork #gemini #codex #buildinpublic #indiehacker #cursor