Stuart Logan

Jevons paradox:

Wild simonwillison.net/2026/jan/30/mo…

@brettdash_ PE company with branding

ok ill bite, what the fuck is bending spoons and should I be scared?

Call me pedantic but this is 2.3x better

@zobeir Nice intro video 👏

I’m Zobeir Hamid I built the new Anything app I've got 500M credits sitting in my dev wallet for you to try it out reply if you want some

Chat is no more sacred than my eyeballs or ears which get shoved full of ads daily Google, written content and socials (particularly TikTok/IG) made ads very opaque. As part of the tech world, we're all far more attuned to what an ad is. Most people don't care. If the ad is semi-useful by being interesting/entertaining, it will thrive. Medium doesn't matter at all.

@collin_ruth89 “there's no such thing as bad publicity” come to mind. Unless you’re that couple from that Coldplay concert

"It's clearly generating more than I'm paying." A strong personal brand might be the answer to your problems. founderbrands.io

Should you build or borrow? The default founder mentality is to build everything custom. Feels safer + better. We did it at Twine. Admin panels, upload media processing, even HR systems. The dumbest thing we built was a kind of CRM system Essential Q, so you don't waste team time: Build your edge. Borrow the rest.

12. Corporate espionage

Safe to say the recruitment industry is changing

@SpecialistPH Exactly

@stuartlogan Yeah, people just take whatever AI gives them and move on, like being spoon fed without stopping to think or question it. Feels like that’s the real risk, not the tech itself. –Paula

We need The Socrates Test not whether AI can think like us, but whether we can still think like Socrates. Probe and reason. Don’t just accept AI

@joshua_xu_ Congrats @joshua_xu_! Massive milestone

HeyGen just hit $100M ARR this month, 29 months after we first reached $1M in April 2023. None of this happens without our incredible team, customers, partners, and community. Thank you 💜 When we shared our first $1M milestone, it was to give back to the build-in-public community. The AI landscape has changed completely since then, but one thing hasn’t: how we build. Internally, we’ve called it our “bible,” the system that’s guided us from $1M to $100M. It’s built from countless team discussions, experiments, and lessons learned along the way. After much reflection, I wanted to document what’s worked for us — for our team and for everyone building in AI. We’re sharing it not because it’s perfect, but because it’s working. It’s how we deliver customer value, learn faster than the world changes, and keep riding the wave. This is The HeyGen Way.

@joelgascoigne Did it lower refunds and chargeback rates?

This is one of my favorite charts at Buffer right now. It's the chart of our number of paying customers. And it might look like we've just experienced some awful churn, but that's not what it is. Those drops in number of paying customers are when we proactively cancelled subscriptions for some of our inactive customers. We sent them an email and let them know that unless they responded asking to keep their subscription or started using the product again, we would cancel their subscription at the next renewal. We made a decision recently as a company that it doesn't feel right to keep charging customers who are not actively using the product. While keeping these customers might pad our revenue a bit, I believe it will make us a more responsive business to proactively cancel those inactive subscriptions and rely on revenue from customers who are actually getting value from the product.

@Scobleizer @bhalligan Are you maybe interested in AI? Just a little bit?

@bhalligan Hmm, I have lists of 7,200 AI startups at x.com/scobleizer/lis… I did not come to that conclusion.

I've looked at a lot of AI startups recently at the app/agent layer. My take: Everyone's building the same stuff.

Backlogs make or break startups. Ours was breaking. Knowing what to work on next in a startup is a massive challenge. We started with Jira as the backlog. It was effectively siloed to engineering and too expensive for the whole team to live in it. We added a spreadsheet so sales, marketing, and CS could add ideas. We used effort/impact to prioritise since the “RICE” methodology skewed toward the freelancer side of a two-sided marketplace (reach biased the scoring). This worked for a bit, but customer feedback and bugs still weren’t getting the priority they deserved. And it felt kinda weird having our backlog on a spreadsheet. We pushed more of that into Jira, but things continued to get lost. So we moved the source of truth to Notion. What changed and how: 1. A single “Backlog” database in Notion. Each ticket tracks an owner, discussion, the What, the Why (user story), the How (including “Appetite” from Basecamp’s Shape Up), assumptions around effort and impact, rabbit holes to avoid, and links to the relevant Objective and KR. 2. A dedicated “User Feedback” Notion database. Every feedback item links to a Backlog ticket, and a roll-up/SUM field shows which tickets have the most customer signals so patterns surface quickly. 3. Helpdesk integration. When a tag is added in support, a record is created in User Feedback with type (bug, product feedback, feature request), a GPT summary of the thread, and useful context like browser, device, and location for debugging. We use Crisp Chat and n8n for this automation. 4. An “Experiments” Notion database. We migrated an experiment spreadsheet to track product and marketing tests with hypothesis, expected result, actual result, and links back to the related Backlog tickets. 5. One priority view everyone can see. Product, marketing, sales, CS, and engineering all look at the same ordered list. 6. Delivery stays where it belongs. Engineering still runs sprints in Jira/GitHub, while Notion is the front door for ideas, evidence, and decisions. (An integration here is next on our list) Why this helped us: - A true single source of truth for “what’s next.” - Customer weighted prioritisation that’s hard to ignore. - Clear ownership and OKR alignment across teams. - Fewer status meetings and faster commits. - A simple structure that doesn’t need some crazy expensive tool. I hope this helps anyone else going through the pain of what to work on next, and doesn’t want to fork out £s on bloated software. And of course, if you need help with n8n, Notion, or automation in general, we’ve plenty of consultants who can help you.

Go and create 🧑‍🎨🎨🧑‍🎤🏴‍☠️

A positive trend

Accountancy firms worldwide shitting themselves that they just lost half their work

He’s now acknowledge he was off