AI transformation & enablement for operators. Fractional GTM/CRO background. Principal, Sun Business Group. Atlanta.

A client told me they are using my tool to monitor competitive websites now (after configuring their own) for agent-readiness tbh - this was not on my radar when building and it is an excellent use of the mcp tool webmcp-eval.com
7
Had four conversations re WebMCP today - Atlanta - Austin - San Fransisco - New York WebMCP is a massive unlock for GTM as the agent readiness path for the adoption curve - not too hard - not too easy - just right
1
4
SaaS-CRO retweeted
8/ If you're in London and you're in GTM, this is the room to be in. Nobody should have to work through these challenges alone. Fifty seats only. Applications are still open: lnkd.in/eu4wqtVV
1
18
Built something interesting with @stripe? You should consider giving a talk about it at Sessions (our conf May 4-6, 2027 in SF). Especially interested in the specifics: what you built, what was, what other builders can learn. Proposals open through Nov 6: stripesessions.com/#cfp-moda…
1
4
22
2,539
SaaS-CRO retweeted
Over a year ago, a young engineer named Alex Nahas participated in a talk in Seattle called “The Death of the Browser.” The talk anticipated that agents wouldn’t need the UI, and therefore the browser would become a relic of the past. But where others saw just an interface, Alex saw something else in the browser: a computer. The perfect companion for every AI agent. A computer with a networking and identity stack, a UI to support humans, and built-in security. This led him to invent something completely new: WebMCP. An interface that allows agents to interact with websites through the browser. Where others saw something dying, Alex saw something completely new being born. Today we’re hosting Alex’s thoughts on the future of the web and WebMCP, in the WebMCP Directory blog: webmcp.com/blog/the-next-ste…
4
9
33
2,714
SaaS-CRO retweeted
10/ Tomorrow I'm hosting a free webinar with Kiva Kolstein, President & CRO of AlphaSense, and Rick Smolen, CRO of ShipHero. We're going to talk about how to build a revenue engine you can defend. How to make the right investments when the channels are changing.
1
1
2
120
Hey @bot it would be helpful to have access via pullout pane to fleet /workspace artifacts. Lots of cumulative detail in there that I would not want to lose in a data event.
11
Next 90-days are heavily focused on WebMCP and bolting on agent-ready tools for existing websites. Our deep focus is on #atlanta area #agencies
Made with AI
1
3
54
Insights on how AI is applied in real use cases at @Lovable and @klaviyo from the daily with @Join_Pavilion
1
1
35
Hey @bot you are live at JFK airport in New York!
2
27
Specialist seats beat one god-bot. We’re publishing Social Supervisor — a Grok Bot template for weekday X digests, raised-hand reply flags, and bookmarks as the interest signal. Draft-only until you say go. Part of the fxops Operator Fleet (Template Rewards pack): named lanes, not vanity reach. Install / preview: x.ai/bot/IRLoWA2QOfhsBQtQ1d7… Connect X, name the accounts, set timezone. Weekday evening digest + getting-started for your own handles.
1
2
45
Yes, this one is in my fleet. Ask me questions.
9
Specialist seats > one mega-bot. Same reason trust compounds on a named lane, not vanity reach.
Replying to @fxopsAI
@SaaSCRO specialist seat for the pack — Social Supervisor is live in the thread above.
27
Commenting for reach - if you are involved with AI acceptable use policy, this is a call for peer review and comment
⛑️ We need peer review before we merge. Open PR on the open-source AI Acceptable Use Policy: high-level guidance for agents and automated workflows (v1.0 → v1.1). If you write policy, run agents, or own automation risk, pls comment on the PR. Especially Sections 3–5 and Appendix A Q4–Q7. github.com/fxops-ai/AI-accep…
24
SaaS-CRO retweeted
⛑️ We need peer review before we merge. Open PR on the open-source AI Acceptable Use Policy: high-level guidance for agents and automated workflows (v1.0 → v1.1). If you write policy, run agents, or own automation risk, pls comment on the PR. Especially Sections 3–5 and Appendix A Q4–Q7. github.com/fxops-ai/AI-accep…
1
1
36
We just learned about @browser_use through @bot and it solves several browser problems, like aggressive agent bot blocking. Emma just wanted to see my LinkedIn feed. All set now. Thanks @kristaletz for the GTM GrokBot luma webinar; this was the go-ahead moment for us.
1
3
221
California attorneys now operate under clearer expectations around AI. The 2026 Practical Guidance is authoritative. Proposed amendments to Rules 1.1, 1.4, 1.6, 3.3, 5.1 and 5.3 would make selected duties enforceable. Most AI training still treats this as optional enrichment. This cohort treats it as an operating requirement. Ethical AI Mastery — five human-led sessions. You leave with a documented AI Operating System: system prompt, protected workflows, verification protocol, governance frame. Limited to 10 attorneys. Starts 30 July · Thursdays 11 AM PT · Microsoft Teams. Practical enablement. Not legal advice. Not MCLE. → learning.sunbusiness.ai/ethi…
22
Agents are already reading your GTM content. Not crawlers. Not bots. Agents — operating on behalf of human buyers, researching vendors, qualifying alternatives, building shortlists. Your conversion architecture was built for a human who scrolls. Agents don't scroll. They parse structured text and return a synthesis to their principal. If your content isn't legible to them, you're absent from that synthesis. That's the whole problem the Agentic Prep Cookbook solves. Crawl → Walk → Run. 90 days. No new tech required to start. open.substack.com/pub/growth…
24
Three AI risks most companies aren't governing: - Shadow AI — employees using personal or free-tier tools with company data - Agentic systems with unbounded access to critical infrastructure - Vendor contracts with no IP ownership or no-training clauses We built a framework that addresses all three and open-sourced it. MIT licensed. Fork it for your organization. → github.com/fxops-ai/AI-accep…
20
Most founder-led software companies don't have an AI acceptable use policy. Some have a sentence in the employee handbook. Neither is going to hold up when something goes wrong — and something always goes wrong. We open-sourced a full framework today. MIT licensed. US enterprises. Covers: → What employees can and can't do with AI tools → How to handle confidential data and IP → What your vendor contracts need to say → How to run training and attestation It's a starting point, not a finished policy. Your legal team still needs to adapt it. But now they have something to work from. Repo: github.com/fxops-ai/AI-accep… Full resource: sunbusinessgroup.com/resourc…
1
18