Sorry SEO gurus, dev agencies, VCs asking to invest, recruiters trying to place ppl.... but I'm not even triaging your messages anymore. Cold emailing me is effectively useless. Potentially the best feature we ever shipped on Fernand, powered by Jev (for now, but likely going to replace with a local open weigh solution soon..) Oh, and it works with everything. You can just say: A conversation is about... "A bug, but it's not really clear and doesn't include reproduction steps" → AI draft reply "Clarify and ask more details" + send Webhook to create a Linear issue

Just released scoped API keys on Fernand. You can now limit what each key can do (all, read-only, or pick from a list of permissions) so you can give AI agents like Claude Code or Codex access without giving them full control.

Currently exploring a new direction for Fernand's landing page, doubling down on the calm aspect and increased focus of our tool. I want users to feel like they've landed on an oasis of positivity in an ocean of slop

Pricing handled via a micro-interaction on the permission list for active vs passive users. Need the user to reply to customers? $29/mo. Or just collaborate inside the tool? free. No need to pre-purchase seats and assign them to team members, then realizing you never have the right amount. Also, it automatically re-adjusts every month based on your team composition. → product craft series #015

> Start writing a reply > Get distracted > Close the tab or refresh by accident > Come back... and it’s still there 😍 → product craft series #013

Snooze with natural language —product craft series #011

I’ve spent the last four days secluded on a tiny island in North Germany shooting and editing the new @getfernand product demo video. This place has literally three times more sheep than people. This photo sums up the setup pretty well: my camera is propped up on a baby chair we've found lying around, and held in place by a jar of Nutella. Hey, whatever works! The biggest learning is that this stuff is harder than it looks. As a bootstrapped founder you just end up picking up new skills because it’s faster than coordinating with someone else. Sure, we could have hired someone to do this for us, but the time and energy it would’ve taken to find the right person and brief them isn’t really aligned with how we’re building this company. So... I wrote a script, sat in front of the camera (..yikes!), learned video-editing basics, and spent 30+ hours to get to something that felt “good enough”. I'm still not really satisfied, but it does the job. Huge respect for the founders like @dceddia who manage to ship a video every day. I genuinely don’t know how you do it. Now that Fernand’s product has reached a certain maturity, it feels like the right moment to invest more in product marketing. Explaining the feature set better, showing real workflows, and helping teams get more out of what they already have. Our pricing is super simple: one active seat, everything included. Unfortunately, some customers still only use a third of what’s available. I think sometimes it's because the feature doesn't totally fit their use case, but sometimes it's just because they don't even know it exists... and that's on me to fix. My setup: - Google Pixel 9 camera shooting in 4K - Makeshift lights we gather from around the house - @screenstudio for UI footage - Shure MV7 microphone recorded separately with Quicktime - Adobe Podcast Enhance to erase my cofounder keyboard tipping noise 😬 - Descript for editing (Really impressive tool!) - A jar of Nutella for stability

When Alex first reached out to invite me on his podcast, I hesitated. If there’s one thing I’ve never really seen myself as, it’s a “true operator”. I’ve always felt more like a starter, someone who likes to build, simplify, and move on once things get humming. But maybe that’s part of operating, too. Maybe there isn’t just one way to run things. Some people operate by scaling, others by shaping. Both matter. One keeps things alive, the other gives them direction. We ended up having a great conversation about what it means to build a calm customer support operation: why most setups break, where AI helps (and especially where it doesn’t), and why I believe in embracing slowness. Taking the time to keep improving a small, focused product instead of chasing endless features and complexity. Calm doesn’t mean static; it means intentional.