Artem Burachenok, CEO @alloy.cx

Takes a minute to get used to sharing folders with agents. Weirdly normal after that

Another one: how did we end up calling guides/SOPs - ‘skills’?

Reading this feels like that moment when the roller-coaster car hangs for a second at the top before plunging off a cliff. And this isn’t even the full picture. Sellers aren’t immune either. The more is bought by Agents, the less need there is for meetings.

This is the opposite of what everyone on X says and yet it it’s true. Not literally ofc, but directionally

@gauri__gupta if you use GSuite + telegram - try Alloy cx - it handles this setup well + built in knowledge base

what is the best personal ai assistant setup that someone has done, that actually works? like takes all context across, slack, different email accounts, calendar etc and gets work done e2e. please comment your setup, would love to try!

@saranormous We’re building exactly that at Alloy. Our internal agents, as well as any vendor agent (Claude, Codex, etc) share this repo. Happy to walk you through it.

all I want is for my notes/content repo to be: 1. simple, reliable, fast 2. take recordings and do transcription/ASR 3. legible to code agents 4. enable more content creation (.md guidance) w/repo 5. not trap me in weird proprietary agent-building gui 6. sharing/permissions

@zeeg Yeah, this is the idea we bullit Alloy around. Your agents are yours, not vendors’. And then have all your agents (grom Codex, Claude, etc) - share the same context, build knowledge together, and access each other memories - feels magical.

vendor-specific chatbots are broken by design that means the Sentry agent, the Linear agent, and any others you might have in Slack they are fine for some point situations, they're nice to get started with, but agents with generalized access outperform them in every single scenario some weeks ago we built an internal Slackbot, gave it access to a bunch of systems (Sentry, GitHub, Linear, Notion, etc), and its capabilities overnight far exceed these other bots "Oh cool Linear can now search your code bases" - our bot did that on day one, and then could push that information wherever it needed to go. Its useful to the point where I now discourage use of things like the Linear bot because it _creates worse outcomes_. this also goes beyond the simple generalization of access: we can customize it. we throw in skills-as-runbooks, templates, etc and the outcomes once again incrementally improve if your org hasnt already built a general purpose bot internally you should. if you need inspiration ours is open source on GitHub (albeit fairly unstable still) github.com/getsentry/juni…

@michael_chomsky We've been working on LLM-agnostic managed agents as service. But if a better shape is OSS - I'd love to chat and understand the reasons. Is this about governance/data isolation?

can someone PLEASE launch OS claude managed agents?? I’ll pay anything. Was building this myself at some point but would prefer someone do it with 100% focus. generational opportunity right here. i can list 30-50 companies that would use it instantly

@yijiefeng Can't agree more - the army of teachers converted a lot of people into vibe-coders

I'm noticing a trend there's a growing number of "AI consulting" firms charging $20K+ to "deploy Claude" to legacy businesses (mid-sized law, accounting, PE firms) as "Anthropic enterprise partners" what this means: - they install claude code, cowork - run a few commands to connect to tools - give generic or misleading advice on a tech stack meanwhile, there's more interest than ever for firms with 0 technical staff to build SaaS in-house and there's an entire industry of advice givers seeking to profit off of this trend last week I was on a call with a PE firm (working with one of these agencies) and someone who had never written code was asking whether to run a RAG vector DB on a Mac mini to chunk internal docs can't make this up

@WorkflowWhisper Awesome ideas, 4-5-6 are the ones we're seeing the most interest in.

The AI Automation Agency Starter Kit: 7 Offers You Can Sell For $5k Each Without Sounding Like AI Slop Most automation offers fail because they sound too vague. "We build AI agents." "We automate your operations." "We help you save time." Nobody wakes up wanting to buy that. They wake up annoyed that leads are going missing, invoices are unpaid, the CRM is wrong, and nobody knows which workflow broke. That is where the money is. Here are 7 automation offers you can sell for around $5k each if you package them around a painful business outcome. 1. Missed-call recovery system For local businesses losing leads when nobody answers. Build: - missed call capture - instant SMS or email reply - AI summary of voicemail or context - CRM update - team alert - retry if nobody responds Outcome: more leads recovered before they call a competitor. 2. Quote follow-up system For service businesses that send quotes and forget to chase them. Build: - quote sent trigger - timed follow-ups - reply detection - sales alert - status update - no-response reporting Outcome: more open quotes converted into jobs. 3. Booking reminder and no-show reduction system For clinics, salons, med spas, consultants, repair companies, and appointment-led businesses. Build: - booking confirmation - reminder sequence - reschedule flow - calendar update - no-response alert - daily appointment summary Outcome: fewer dead slots and fewer wasted staff hours. 4. Invoice chasing workflow For businesses where cash gets stuck because nobody wants to follow up. Build: - invoice sent trigger - due date tracking - polite reminder sequence - overdue escalation - payment status check - weekly unpaid report Outcome: faster cash collection without awkward manual chasing. 5. CRM auto-update system For teams where the CRM is always behind reality. Build: - lead capture from forms, calls, and inboxes - duplicate checks - contact update - owner assignment - task creation - daily summary Outcome: a CRM the team can actually trust. 6. Client onboarding handoff system For agencies, consultants, and service businesses that lose momentum after the sale. Build: - kickoff form capture - document checklist - task creation - client reminder sequence - internal owner alert - handoff summary Outcome: faster onboarding and fewer "who owns this?" moments. 7. Workflow failure monitoring system For companies already using n8n or Zapier but scared of silent failures. Build: - failure detection - retry logic - error summaries - owner alerts - incident log - weekly reliability report Outcome: less time finding broken automations after the customer notices. The pattern is simple: Do not sell "AI." Sell a specific business leak getting fixed. Do not sell a giant transformation. Sell one workflow with a before and after. Do not sell technical complexity. Sell recovered leads, cleaner handoffs, fewer no-shows, faster cash, or fewer broken workflows. Synta fits in the build layer for these offers. You can take messy client process notes, turn them into n8n workflows, verify the logic, catch broken branches, and debug failures without spending hours inside the node canvas. That matters because agency profit is not just what you charge. It is how fast you can build the workflow and how little time it eats after launch. I put these into a starter kit with: - the 7 offer breakdowns - who to sell each one to - what to build - what outcome to promise - pricing notes - simple pitch angles Comment STARTER and I will send it over. No AI slop. Just 7 boring, painful, sellable workflow offers.

@lukepierceops Yep, very similar to what we see

Yesterday I said stop selling AI for $2-5k. Here's what you should actually be selling instead: Phase 1: Audit ($3K-$5K, 2-4 weeks) Phase 2: Build ($25K-$60K, 6-12 weeks) Phase 3A: Dev Retainer ($3K-$8K/mo, ongoing) Phase 3B: Maintenance ($500-$2k/mo) For mid-market ($10M-$50M ARR), shift up: Audit: $4K-$6K Build: $35K-$75K Retainer: $5K-$10K/mo For enterprise ($50M+): Audit: $7.5K-$15K Build: $75K-$250K+ Retainer: $10K+/mo The audit is the wedge. The audit is what separates you from every 22-year-old with Claude Code who'll build whatever they're told. You're selling the map. The build becomes inevitable once they've seen the map.

@stanine Is the persons-related part for humans only rn or we can expand it to agents?

If you're building a company and want the easy button for SOC 2, we built this for you: rippling.com/soc2

Today, we launched @Rippling Automated Compliance, starting with SOC 2. We have a unique advantage here: we aren't telling you how to fix your stack, because we ARE your stack. device management, identity and access management, HR, performance management...

It somehow feels that the surest way to kill a write up is to ask an AI to draft an outline. Result kills the mood. Or maybe it's because I didn't want to write that thing in the first place.

@bhalligan Picked a source of info lots of people need but hate dealing with because its UI sucks (Graylog in one particular case). Set an AI agent that can dig through it. Immediately everyone is excited. There are a few more - will write them up

What's the smartest, fastest way you've seen a company force-multiply their people with AI? Just saw the most clever way a founder is AI-pilling their entire 300-person team. Writing it up to share, but I wonder if it can be topped...

@aymanalabdul We are quite good

Getting requests from clients for real AI implementation partners. All I'm finding are Vibe Code Bros or Zapier shops. I want firms that: • Diagnose the actual business problem • Bring PMs + Product + AI talent • Build + integrate into real workflows • Care about security and stability • Ship and iterate Who’s best in the world at this?

Soon we’ll look at agents.md files and wonder: what was that?

Yesterday talked to an entrepreneur whose team is himself + 3 AI agents. He said it felt a bit crazy at first. Not how he used to work. Not how people around him worked. He lives outside a major tech hub. Until he came to SF and met others.

Secret to high self-esteem: oversized basketball hoop

@emollick What do you mean it can make Office documents? How exactly? I’ve been looking for a good model for this for a while

The continuing gap between the capabilities of Gemini Pro 3.1 (very good model) and the capabilities of the Gemini app/website is odd. The model can do what Claude/GPT can do, but there is a minimal harness for tools (file creation, research etc), no auditable CoT/actions, manual canvas, etc. The reason this is odd is that Google is trusted by enterprises & has the compute to burn, so a good harness would solve so many of Gemini’s gaps and make it an easier sell to companies. The model can make Office documents, for example, but the harness doesn’t allow it. It could also decide when to use other Google tools (and Google has a lot of very good AI tools) and apply them, taking advantage of the ecosystem, but it doesn’t consistently. I assume something will be coming out here eventually, but the gap with Claude and ChatGPT has only been growing.

Every business should be thinking about AI/AX and ABJ/ABX AI/AX - agentic interface/experience ABJ/ABX - agentic buying journey/experience (almost) everything will soon be bought / operated by agents

@dharmesh Exactly. A naive MCP doesn’t solve AI access. it just gives agents a pipe into systems built for humans. The real problem is permissions: human access is role-shaped, while agents need task-shaped access. x.com/Burachenok/sta…

Every B2B software company is (or should be) building a "headless" version of their product. One that can be used by agents. But "headless" doesn't mean "brainless". You don't just wrap your existing APIs into an MCP server and call it a day. The companies that succeed in the agentic era are those that take a thoughtful approach to *designing* an agentic user experience (AUX). Yes, that will likely involve APIs, MCPs and CLIs. But the difference will be in the *ergonomics* of the interface. We need to figure out *how* agents actually want to use our products/platforms. Because if all they wanted to do was use them like humans do, we have "computer use" for that. I'm personally very excited about this new agentic world when it comes to B2B software. HubSpot is all-in on building the #1 agentic customer platform. Just posted this in a private Slack thread with the HubSpot exec team: Being agentic is not just about agents running *on* our platform, it's about agents *running* our platform (being able to operate it). That's how you take AI from being a simple tool to a savvy teammate.