Whalesync

Draft in Notion, publish in Webflow...in 5 minutes. Connect Notion → Webflow CMS with Whalesync to eliminate copy/paste and keep content synced. The result: fewer manual steps, fewer errors, and faster content updates. Read the guide: whalesync.com/blog/how-to-co… #Notion #Webflow

Just released @screamingfrog SEO Spider v.24: screamingfrog.co.uk/blog/seo-spide… Includes - 🤖Screaming Frog MCP 🧑‍🤝‍🧑Auto Compare Crawls 📊View Crawl Changes in Email Notifications 📧Send Crawl Export Attachments by Email 🚫Find Uncrawlable Links & lots more! Enjoy.

Scratch is here! Time to get the news out. We've been pretty quiet recently regarding what we've been working on, mostly because we were still figuring it out ourselves. We knew that AI was shifting the whole data game and for a while we were experimenting with concepts internally to see what felt right. Now we're pretty confident that we're onto something really cool and we want to share it. Here's what we're building: scratch.md/blog/what-is-s…

Distribution is the hard part now. Just like before.

@real_kaspr @cynthiamcgillis One pull does everything. So yes, they have to pull to get the latest files, but also no, because they're doing that to get the latest files from the CMS, CRM, Intercom, etc. anyway.

@WhalesyncData @cynthiamcgillis Does this rely on the developer running your tool each time they sit down to work, to ensure they're always pulling the most recent skills?

How are y'all handling company-wide skills? Putting them in a repo? Does that work for Cowork and less technical teams? I feel like there has to be a better way to organize these.

We’ve agreed to a partnership with @SpaceX that will substantially increase our compute capacity. This, along with our other recent compute deals, means that we’ve been able to increase our usage limits for Claude Code and the Claude API.

We've formed some strong opinions over the years at Whalesync. I think there's going to be a pretty big shift in how SMBs need to think about their SaaS tools and company data to work with AI efficiently and safely. Decided to write up my thoughts: whalesync.com/blog/9-lessons…

Whether it’s existing consulting firms, new ones that emerge, FDEs from agent vendors, or new internal agent engineering roles, the amount of work that is going to be created to implement agents in enterprises will exceed anything we imagine today. The complexity of implementing agents in any existing organizations is very real. When I talk to large enterprises, as you move from a chat paradigm to agents that participate in meaningful workflows, there are a number of things they need to do. First, you have to get agents to be able to talk to your data securely across your systems. In many cases, enterprises have decades of legacy infrastructure that contain the valuable context for AI agents. That’s going to take a ton of work to go modernize and move to systems that work well with agents. Then, you need to ensure that you’ve implemented agents with the right access controls and entitlements, the right scopes to be safely used, and have ways of monitoring, logging, and securing the work that they do. Next, you need to actually document the processes in the organization in a way that agents can utilize for doing the work. You also need to figure out what the new workflow looks like when agents and people are working together on a process, and who steps in where. Just replicating the old workflow will mute the gains. Oh and you likely need to create evals for your top new end-state processes. Finally, you have to keep up with a rapidly changing set of best practices and architectural shifts happening in the agent space. While it’s fun for people to change their personal productivity tools on a dime, it’s 100X harder to do this in a business process. The speed of change is a blessing and a curse right now for anyone trying to keep a stable system design. All of this means that individuals and companies that develop expertise on the above set of components (and more) are going to be needed to help organizations actually implement agents at scale. This is also the rationale for vertical AI agents right now that can go in deep on a business domain and help bring automation to it. This is a huge opportunity right now whether you’re doing this internally or as an external business provider.

most growth marketers use AI to rewrite headlines and call it a day. here's how I actually use Claude on the growth marketing team at @AnthropicAI across chat, Claude Cowork, and Claude Code 👇

@jerryjliu0 We built @scratchdotmd to give AI agents saas content as git backed local files but with HITL review and publishing. Because file systems are what make Claude Code/Codex effective.

This is really well thought out. Filesystems are the new default abstraction for agents to interact with documents (the new RAG stack in 2026). The issue is actually figuring out how to productize this; you can't "productize" Claude Code over a local file system. Seems like this tool has all the semantics of filesystems with the versioning of git

HITL is a feature, not a bug.

You can now ask Gemini to create Docs, Sheets, Slides, PDFs, and more directly in your chat. No more copying, pasting, or reformatting, just prompt and download. Available globally for all @GeminiApp users.

@joncphillips I call it "JS component beige"

We have unlimited design possibilities, infinite color palettes, amazing coding agents, and AI that can generate literally anything. Yet every website still looks like it came from the same fucking Figma file.

@everestchris6 How many sales did you get?

this OpenClaw bot finds restaurants with ugly menus, rebuilds them as live web menus, and mails the owner a postcard...on autopilot. here's how agencies can land recurring contracts with this system: - scrapes every restaurant in a city in real time - filters by review count + rating + last menu update + photo quality - pulls the real menu items from the official site, PDF, or Google reviews - samples the brand palette from the restaurant's own visual identity - renders a 9:16 brand-matched menu, hosted live at a QR-accessible URL - writes a personalized postcard referencing a real reviewer and a real dish - mails it to the registered office addressed to the owner by first name every step from discovery to brand-matching to outreach is automated. reply "MENU" + RT and i'll send you a free guide so you can build this too

@hemeon Pengineer

What do we call this new hybrid builder? • Design (taste, interaction) • Engineering (ship fast) • AI-native (LLMs, agents) • Product sense (MVP, prioritization) I hear “Product Engineer” or “AI Builder” What are you calling this role?

Introducing our /parse endpoint 🔥 Convert any document into clean data for AI agents via API. - Turn PDF, DOCX, and XLSX files into Markdown or JSON - Preserves reading order and tables - Zero Data Retention support All powered by our 5x faster Rust-based parser.

I don't need Pomodoro anymore, my workday has natural breaks now

@MatthewBerman @garrytan @atmoio @ThePrimeagen Coding is less fun now. Building is more fun now.

Wild how split opinions are on AI coding. I love building now more than ever. I know @garrytan feels the same way. But some like @atmoio and @ThePrimeagen are hating this moment. What gives?

here's the exact process we built to automate content creation using Claude Code, 23 custom skill files, and the .@ahrefs MCP: ahrefs.com/blog/how-i-do-… (the article also includes a YouTube video where i demo the whole system to our ever-discerning CMO, @timsoulo) hope this is helpful, and spurs a few ideas for automating the drudgery out of your work :)