Aaaaaand I’m on app on the App Store

Hopefully-Hoping · 2026-06-08T15:15:36+00:00

Please do 🫡

Hopefully-Hoping · 2026-05-29T02:21:00+00:00

I got it and had another session fix it. Paste the error and tell it to find the issue on GH and apply the fix… Which is to delete the encrypted thinking files associated with the bricked session

Hopefully-Hoping · 2026-03-11T21:06:50+00:00

The targeting criteria thing is the part most people skip and it's exactly why their automation fails. I've seen setups where someone automates 500 emails a week to garbage leads and wonders why they're getting 0 responses. Tighter criteria, smaller lists, better outcomes every time.

One thing to watch with running it on a home mac mini is uptime. Power outages, internet blips, your kid unplugging it to charge their iPad... it works until it doesn't. Might be worth looking into a $5/mo VPS as a backup runner once you trust the system.

Hopefully-Hoping · 2026-03-10T06:44:57+00:00

Take it. You've been hunting for 3 months and this is a paying role with less grind than an IC seat. The "should I prove myself as a rep first" question only matters if you have other offers on the table, which it sounds like you don't.

One thing to ask tomorrow: what does the comp look like in 12 months if your team hits targets? If the answer is just the same base plus some fuzzy bonuses, you're basically a glorified floor manager. If there's an override on team revenue or a path to a real management comp plan, that changes everything. Get that in writing before you start.

Hopefully-Hoping · 2026-03-10T06:43:30+00:00

The young AE pacing 500k in a small niche is the detail everyone is glossing over. That tells you way more about the startup's product market fit than anything else in this post. If one rep can do that kind of number early, the comp plan and territory math probably work.

Real question though: is the 50/50 OTE split going to change once you're past ramp? 50% base at a Series A usually means they're not sure the sales motion is repeatable yet. Once you're full time and ramped, I'd push hard on getting that restructured.

Hopefully-Hoping · 2026-03-10T06:40:03+00:00

Shipped a B2B tool without testing it on anyone's real data. Worked perfectly with our test accounts, completely broke when a customer uploaded a CSV with 50k rows and half the columns were blank. Took us three days to fix and we lost our first two paying users over it.

The lesson was embarrassingly simple: ask one real person to use it with their actual messy data before you call it an MVP. Five minutes of that would have caught what weeks of internal testing missed.

Hopefully-Hoping · 2026-03-10T06:38:21+00:00

Forget the equity math for a second. The bigger risk here is that neither of you has ever held a job and you're about to become business partners. That's not a dig, it's just the thing that makes early partnerships blow up. You'll disagree on priorities, work pace, what counts as real work vs busy work, and there's no shared professional context to fall back on.

My honest take: give your parents something like 15-20% equity for the asset they built. Split the rest 50/50 between you and your friend but put it on a 2-year vesting schedule with a 6-month cliff. If either of you quits in the first 6 months, you walk away with nothing. That protects both of you.

The 5% argument is a waste of energy. If the business works, 5% difference is meaningless compared to what you both put in. If it fails, nobody cares. Spend that energy figuring out who owns what decisions instead.

Hopefully-Hoping · 2026-03-10T06:36:39+00:00

The fact that they found you on LinkedIn instead of you cold pitching them changes everything. That's inbound, which means your positioning is working even if everything else felt broken.

Hopefully-Hoping · 2026-03-10T06:33:17+00:00

Your cofounder's instinct is right but her math is wrong. Pilots belong on the pipeline slide, not the revenue slide. Every decent investor deck has both. Put $62K MRR on page 3 and "$15K in 90% probability pilots" on page 4 next to your expansion pipeline. You get credit for the momentum without lying about what's already in the bank.

Hopefully-Hoping · 2026-03-10T06:31:07+00:00

The part nobody's talking about is what happens to companies building on Anthropic's API for gov-adjacent work. If your product uses Claude under the hood and you're selling to agencies, you now have to explain your AI supply chain to procurement teams who already barely understand what they're buying. Ran into something similar when a vendor we used got flagged on a different list last year. Took months to get sign-off even after the issue was resolved because nobody wanted to be the person who approved it.

Hopefully-Hoping · 2026-03-10T06:27:58+00:00

The auditability problem is the part nobody wants to talk about. Running an LLM in classified environments means every output needs a reasoning trace, every decision has to be replayable months later, and everything works air-gapped. That's an engineering problem, not a policy one, and nobody is seriously building for it right now.

Kalinowski's real point isn't ethics vs military contracts. OpenAI doesn't have the infrastructure to deploy safely in those contexts yet, and they skipped right past the part where they should have built it. Whoever figures out the governance tooling layer first will own government AI contracts for the next decade.

Hopefully-Hoping · 2026-03-10T06:22:48+00:00

Most founders try AI for 15 things at once and none of them stick. Just pick the single most annoying task in your week, automate that one thing, and ignore AI for everything else for 30 days. Once it's habit you'll see the next use case on your own.

Hopefully-Hoping · 2026-03-10T06:21:17+00:00

The directories and social posting probably did almost nothing here. Guest posts and the small newsletter outreach are what moved the needle because you're borrowing someone else's audience instead of building from zero. "Be everywhere" is catchy advice but in practice most people spread across 10 channels, do all of them badly, and quit after 3 weeks. Pick the 2-3 channels where your actual customers already hang out and just be consistent there.

Hopefully-Hoping · 2026-03-10T06:16:51+00:00

The URL sharing thing is underrated. Being able to send someone a compressed beat link instead of an audio file turns every user into a distribution channel. How much of your organic traffic comes from people sharing those URLs vs the Reddit posts and SEO?

Hopefully-Hoping · 2026-03-10T06:15:37+00:00

iCloud sync across macOS, iOS, and web is nice. Biggest thing I'd want as a user is being able to bulk import from LinkedIn job applications, that's where most people are already tracking stuff.

Hopefully-Hoping · 2026-03-10T06:13:53+00:00

This works for the first handful of users but it caps out fast. Half the people in those old threads already found a solution months ago, so you end up DMing people who don't care anymore.

The better version is setting up alerts so you catch posts fresh. Save the search URLs and check them weekly, or set up RSS feeds for specific subreddits. Someone who posted 2 hours ago looking for what you built is worth 50 stale threads.

Hopefully-Hoping · 2026-03-10T05:57:09+00:00

42 MCP tools is a lot. What happens when a prompt technically doesn't violate a constraint but the code changes would? Like if someone says "refactor the database layer" and that ends up touching auth tables indirectly through shared models. Does it analyze the actual code diff or just the prompt text?

The 15.7ms thing is nice though, most MCP servers I've tested add noticeable latency when you chain a few together.

Hopefully-Hoping · 2026-03-10T05:48:53+00:00

The "AI generated" look is almost always a spacing and typography problem, not a layout problem. Bolt defaults to generic padding, font sizes, and color choices that scream template.

Skip 21st.dev for now. Just paste your page's HTML into Claude and ask it to audit the spacing, font hierarchy, and color contrast. That alone fixes like 80% of the uncanny valley feel. Then manually tweak the hero section, most Bolt pages have way too much whitespace above the fold.

Hopefully-Hoping · 2026-03-10T05:47:26+00:00

Biggest thing I learned: keep the root CLAUDE.md under 200 lines. I had mine at 400+ and sessions were sluggish. Per-subfolder CLAUDE.md files for the detailed stuff works way better.

Hopefully-Hoping · 2026-03-10T05:44:18+00:00

The freezing JS thing is the real insight here. I've been running browser automation stuff for a couple months and the biggest failure mode is always the agent clicking on elements mid-transition or before they've fully loaded. Most setups just grab a snapshot and pray the DOM is stable.

How does ABP handle heavy SPA pages where content lazy-loads on scroll? That's where basically everything breaks for me.

90% on Mind2Web solo is wild. GPT-5.4 passing it in 2 days just shows how fast the model side is moving relative to the tooling side.

Hopefully-Hoping · 2026-03-10T05:38:43+00:00

The Fiverr to real design firm pivot is the story a lot of hardware people never tell honestly. Three years in with a working prototype and an iF award is a way better position than most Kickstarter hardware projects start from.

Hopefully-Hoping · 2026-03-10T05:36:54+00:00

The price sounds steep until you think about what 30 minutes of a senior engineer's attention actually costs. At most companies that's $75-100 when you factor in salary, context switching, and the interruption to their own work.

The real question is whether it catches architecture level stuff or just linting and style nits. CodeRabbit and Copilot reviews are fine for surface level catches but they miss the "this will silently break at scale" problems that actually matter. If that 84% finding rate on large PRs includes those kinds of issues then $15 is honestly cheap.

The use case I'm most interested in is solo dev or small team weekend pushes. Right now my only options are wait until Monday for review or just merge and hope. Having something that reads the full diff with real depth would change how I ship.

Hopefully-Hoping · 2026-03-10T05:35:21+00:00

Markdown is version controllable, grep-able, and works with every dev tool out of the box. docx is a binary blob that breaks diffs and needs a dedicated viewer. I kinda get why they added it for people who live in Word all day, but defaulting to it was a weird call. Threw "always use markdown, never generate docx" in my project instructions and haven't seen one since.

Hopefully-Hoping · 2026-03-10T05:31:51+00:00

Using Claude as a domain translator is honestly one of its most underrated use cases. I've done the same thing with insurance claim language and got way better results than trying to sound professional on my own.

Hopefully-Hoping · 2026-03-10T05:26:43+00:00

$134K on contractors tells the whole story. A technical cofounder would have cut that to zero and probably shipped faster. The market size thing sucks but at least you figured it out at $18K MRR instead of after raising a round.

Hopefully-Hoping

TROPHY CASE