Tao

@nikunj Scraping trust center for subprocessors is a great idea. And your visualization is just beautiful.

SOC II is in the news right now for being security theater.. You know what SOC II is *actually* good for? Subprocessor lists. I scraped 417 companies subprocessors to investigate what AI native companies are using for their infrastructure. Introducing DeployGraph dot com 🥞

@ivanburazin I was looking for an execution sandbox for our agent and found daytona appearing to be the best and most startup-friendly. Will onboard as soon as our product is ready. Looking forward to your great future.

We're targeting $10M run rate by next month. Going from 0 to 1M in 60 days, hitting 1-3M in the next 45, and finally closing in on 10M in less than a year feels amazing. But it also puts enormous responsibility on us since customers depend on this infrastructure and their agents run production workloads. The validation constantly pushes us to be at the top of our game.

As a founder in this space, my reaction is pretty simple: compliance can’t be theater. Startups need a real path to SOC 2: clear policies, real evidence, audit-ready structure. That’s what we’re building at Screenata. screenata.com We also made our SOC 2 Type I audit prep program $299 one-time for early teams.

> Startup accused of fraud > Check bios of both founders > Forbes 30 under 30

Thank you @garrytan for the great /office-hour skill (the suggestion did confirm the direction I'm pursuing) and I'm truly honored for this opportunity.

In what circumstances would you find subagents useful?

@ivanburazin SaaS for Agents

New category emerging: Headless SaaS Not infrastructure as a service / platform as a service Traditional software (Photoshop, Slack, Jira) rebuilt with agent-first APIs. - No UI - Programmatic access - Essentially the same product with different interface Entirely new business model.

Multimodal SOP Generators (Glyde) Glyde is a Chrome extension that records your screen while you work and generates a polished SOP automatically. Unlike basic screenshot tools, it captures DOM state, structured step data, screenshots, and optional voice narration. This means it produces step-by-step documentation with contextual descriptions. It understands the difference between navigating to a new page and filling out a form, grouping those actions logically. You don't have to manually format images or write out every step like you do in a word processor. You just do the work, and the documentation is generated. Glyde then exports directly to PDF, Notion, or Confluence, allowing you to separate the creation of the SOP from the storage of it.

What Are the Best Alternatives to Google Docs for SOPs? The best alternatives to Google Docs for SOPs include auto-documentation extensions like Glyde, structured knowledge bases like Notion and Confluence, and dedicated process management platforms. Choosing the right alternative depends on whether your primary problem is creating the documentation, organizing it, or tracking compliance. Tool CategoryExamplesBest ForMain DrawbackKnowledge BasesNotion, ConfluenceOrganizing text and building interconnected wikisStill requires manual screenshotting and formattingBasic GeneratorsScribe, TangoQuickly capturing simple, linear workflowsOutputs generic "click here" text that requires heavy editingMultimodal GeneratorsGlydeCreating polished, contextual step-by-step guides automaticallyHyper-focused on digital workflows, not physical processesProcess ManagementProcess StreetEnforcing checklists and tracking completionHigh setup time and steep learning curve

Google Docs for SOPs: Templates, Limits, and Better Alternatives When it is time to document a process, opening a blank word processor is the path of least resistance. If you need to write an SOP, Google Docs is usually the first tool teams turn to because everyone already has an account and knows how to use it. You write the steps, paste in a few screenshots, and share the link. But as your process documentation grows from five files to fifty, this manual approach breaks down. Formatting images takes longer than doing the actual work, and finding the right file in a crowded shared folder becomes frustrating for new hires. This guide explains how to structure a reliable Google Docs SOP template, exactly where the platform falls short for growing teams, and which tools offer a better way to capture workflows.

How Do You Create a Google Docs SOP Template? To create a Google Docs SOP template, open a new document and establish a standardized header, purpose statement, scope, step-by-step instructions section, and revision history table. Save this file with "[TEMPLATE]" in the title and set permissions to "View Only" so team members are forced to make a copy. Without a template, your documentation will be inconsistent. If you are going to use a word processor, you need to enforce a rigid structure. A highly functional Google Docs SOP template should include these specific sections: Document Control Header: A table at the very top containing the document owner, last update date, department, and target audience. This immediately tells the reader if the document is current. Purpose and Scope: Two sentences explaining why this process exists and exactly when it should be used. Prerequisites: A bulleted list of software access, permissions, or physical items required before starting step one. Step-by-Step Instructions: The core of the document. This must be a numbered list. Force authors to put the action verb at the beginning of the sentence ("Click the blue 'Submit' button" rather than "You will then need to go ahead and click submit"). Exception Handling: A brief section at the bottom explaining what to do if the process fails or an edge case occurs. Practically, you should also change the document setup to "Pageless" (File > Page setup > Pageless). Standard operating procedures are read on screens, not printed on A4 paper. The pageless format prevents wide software screenshots from being awkwardly shrunken or split across artificial page breaks.

Predicted this was going to happen. Code review is a natural extension of the Coding agents. It's no surprise that foundation models will eat this space.

Introducing Code Review, a new feature for Claude Code. When a PR opens, Claude dispatches a team of agents to hunt for bugs.

Every SaaS builders, how do you write your product guides?

@NickVanWig @prisma @DrizzleORM I'm working on being your customer

@Tao_DeepGuide @prisma @DrizzleORM every customer of ours that’s switched has had nothing but good things to say

Anyone has experience with switching from @prisma to @DrizzleORM ? Is it worth in long run? We have pretty good experience with prisma so far, but deploying prisma migrations on supabase hasn't been smooth. Also drizzle seems have much better performance from the description of their website.

Glyde turns any workflow into a living SOP. Record any workflow. Glyde captures every step and generates polished SOPs your team can actually follow. Private Beta Now. Launching Soon. glydehq.com

Does anyone know how I can reuse a workspace after submitting PR in @conductor_build It is marked as Done now and it seems the only way I can start new work is creating a new workspace, which I have to re-run setup. Our repo is pretty large and set-up takes quite some time.

@AntonioEscudero This is amazing. Which source did you find the most distribution?

My little SaaS made $1,407 in the last 30 days!! And it also got to 2,128 users! 🥹 It grew 128 users today!! My goal is to get to $2K before the end of this month!! Wish me luck! 🤞