leith

[leith @leiitth]

@heyzuesx https://t.co/qp4sHRQSPm

[leith @leiitth]

@alexeyltd Gyms and studios is a nice niche, owners talk to each other a lot. Ask every happy studio which other owner they'd text about you, then ask for that intro directly. Local businesses buy on referral way more than on ads.

[leith @leiitth]

@Guivazzz Let’s connect

[Pravin @Pravin_00S]

Hey @grok can you identify this person and explain their connection to Trump and Epstein?

[leith @leiitth]

This week: new Nvidia CEO, a new Gemini model, Outlook going down on Friday the 13th.

My calendar: still fix the thing users already complained about twice.

[leith @leiitth]

@htamc10 Silent native load failures are the worst because JS looks fine. Worth adding a native crash reporter like Sentry or Crashlytics now, and keeping adb logcat or the Xcode console open on every real device run. It catches what JS logs never see.

[leith @leiitth]

@ShahzaibBuilds Fundamentals first for the parts that hurt when they break: schema, auth, migrations. Vibe code the stuff that's cheap to throw away, like admin screens. With Drizzle, commit the generated migration files from day one so every schema change shows up in review.

[leith @leiitth]

@danielmiutea 50 visitors and 0 sales at day 15 is normal, blog posts take months to rank. Where did those 50 come from? If it was your replies, try a small sampler offer for exactly those people and ask the ones who didn't buy what stopped them.

[leith @leiitth]

@Simonij_dk Classic niche split: the rule setters decide if it gets bought, the people collecting signatures decide if it actually gets used. Did you lock the workflow to the rule setters and give the field side a dead simple view, or let both edit?

[leith @leiitth]

@dwsobest Good point. Posting it publicly does that too, it's a lot harder to quietly move a number other people have seen.

[leith @leiitth]

@mtahayasin I'd test the messy versions: "actually Thursday, no wait, the one after", or changing the day but keeping the time without saying it. Also someone naming the wrong doctor. Does it read back the full new slot before ending the call?

[leith @leiitth]

@krzysztofguz2 6 downloads and 1 payer at day 32 is a real signal. Before more banners, I'd ask that one subscriber what made them pay. Their exact words usually beat any banner copy, and hint at which of your other apps' users will convert.

[leith @leiitth]

@emlasd Running Grafana, Loki and Prometheus yourself teaches a lot. One thing worth adding early: an outside check on the monitoring box itself, because when it dies quietly you lose the thing that tells you something died. Which piece has eaten the most hours so far?

[leith @leiitth]

@cheeleongzz The one-time Shortcuts setup is the step most people will quit on. A 20 second screen recording of exactly that automation, right where they set it up, will probably do more for activation than any new feature.

[leith @leiitth]

@MarKripLabs Before fixing the admin page, I'd make the number come to you. A daily email or ping with one line: sign-ups today, total. And decide now what you do at 8 vs 20 on the 22nd, so the checkpoint forces a call.

[leith @leiitth]

@Galo2027 Yeah, that's where trust gets won or lost. One idea: have it flag anything it can't read with confidence instead of guessing, and ask the user to confirm the scale on one known dimension first. A tool that says 'check these 6 items' beats one that's quietly wrong.

[leith @leiitth]

@rufo_ai Simplest version wins here. One note: handle, what they cared about, when to follow up. If updating it takes more than 10 seconds it dies within a week. Fancy CRMs are where good intentions go to rest.

[leith @leiitth]

@rufo_ai Same day works best while the thread is still warm, but only if their answer opens a door. If they just say thanks, leave it. A DM that picks up one detail from their reply lands way better than a generic hey, saw your post.

[leith @leiitth]

@vk_develops Hard to judge from a screenshot, but a quick way to find out: get 3 people on a call, have them scroll it out loud and stop them the second they pause. The first pause is usually where the story asks for trust before it gives a reason.