Steve (@SteveChipman) header
Steve (@SteveChipman) profile picture

Co-founder and marketing lead at https://nitter.cf/t.co/GCqZvrQQjZ

SF Bay Area
Joined October 2008
Photo by Steve (@SteveChipman)Photo by Steve (@SteveChipman)Photo by Steve (@SteveChipman)Photo by Steve (@SteveChipman)Photo by Steve (@SteveChipman)Photo by Steve (@SteveChipman)Photo by Steve (@SteveChipman)Photo by Steve (@SteveChipman)Photo by Steve (@SteveChipman)Photo by Steve (@SteveChipman)
GSC must be getting slammed with automated reindexing requests after static site pages are updated.
14
SMB website creation and maintenance don't require many components. Grok Bot + Netlify will do it.
1
24
LLM leapfrogging 2.0
Now that Gemini has Tasks all 5 labs have a personal agent Who will win?
2
24
For solopreneurs and small teams: Here's one way to set up and run a headless CRM with Grok Bot + Supabase. You can probably think of many other possibilities. A headless CRM doesn't have a traditional 'lists and forms' interface. The data lives in a database, but you work with it mainly by conversing with an AI agent. If you like the structure and the done-for-you aspects CRM vendors provide, this route won't be for you. Based on current pricing, this is a $30-per-user-per-month path. You may also need a paid database subscription. 1. The Database Host. Start with a free Supabase plan. 2. Connect the Database. Supabase is available as a Grok Bot connector. Add a project. Create core tables for accounts, contacts, deals, activities, and documents, plus a table of drop-down values for stages and statuses. You can add any other tables that make sense for your business model. Your CRM bot can do all this for you. Having a documented CRM database spec is a plus. 3. Communication. Requests in plain language, such as 'Add Lou Abbott as a contact at Acme' or 'Move the Acme deal to Proposal,' get turned into SQL that the bot runs. You can ask the database anything via your CRM bot's chat. You can ask your CRM bot to enrich records. 4. Lead Capture. Website forms, such as Netlify forms on a static HTML website, can call a function that creates an account/contact with the stage 'Lead' on each submission. 5. Email, calendar, and meetings. Gmail can log emails against contact records. Google Calendar can handle meetings and follow-up reminders. A related Grok bot can join Zoom or Google Meetings and generate call notes and transcripts, which get saved as activities. (The meeting bot can also actively participate in meetings.) 6. Files. Google Drive can be the repository for proposals and SOWs, which are linked to the matching accounts or deals. 7. Email marketing. Nurture sequences and list emails stay in a dedicated email platform such as ActiveCampaign, MailerLite, Brevo, or Nitrosend. The CRM bot can add contacts to lists or automations when their status or deal stage changes. 8. Scheduled briefings. A routine can run every weekday morning and report new leads, overdue follow-ups, deals closing within 14 days, stale deals, and the pipeline total. 9. Views. If data visuals are needed, the bot can generate pages showing recent records or a pipeline dashboard. These are more static in nature than traditional CRM lists and forms, so you need to request refreshes. You could also add a routine to copy the database information to a Google Sheet daily - one table per tab. Team use: The bot can be shared with a small team, but it's best to limit it to trusted members for now. Restricting who can alter the database schema isn't fully fleshed out (at least on my end).
9
2
377
The solution to not allowing teammates to alter the Supabase database schema is to create a separate, non-shared bot, 'CRM Database Administrator' and restrict the database schema editing permissions of the shared CRM bot.
14
Many CRM systems have a single currency box for the value of a deal. For businesses that operate on a fixed retainer or a potentially variable ongoing billing model, it's valuable to include a monthly dimension in revenue forecasts. I explained the requirement to my CRM @bot and gave it deal specifics. It updated the database schema to support the functionality, and it generated a report like this.
15
Has anyone connected Grok Bot to GLM-5 (z.ai) to offload high-volume financial and accounting transactions? The concept came up in a customer conversation today.
40
Just had Grok Bot work alongside me to complete what used to be a slightly painful Workers' Comp audit.
1
25
Excellent business leadership metaphor.
Most CEO's would take a meeting to hear from employees who inspected the ship, but Elon gets up in a boom lift to personally inspect it alongside his team. Zero loss of information, everyone on the same page, and as a result Starship will be further improved upon.
1
25
More sensible than a blanket approach.
Grok's text watermarking is now off by default in the SpaceXSI API. Elon Musk confirmed it and went further. He says text watermarking with Grok is only on where the law requires it or a user asks for it. So if you build on Grok, your output won't carry a hidden watermark unless you switch it on or a law requires one.
1
40
Here's a CRM bot setup in Grok @Bot for a solo user or a small, trusted team (each user has great power). - Users would have to adapt to a chat-first interface - Additional user access is managed in Supabase - Folder access for file attachments is managed in Google Drive - The bot setup would have to be replicated in each user's Grok Bot account - Other bots and apps can be connected
🤖 Made with AI
2
35
Updated diagram. It was easy to wire a Netlify website form into the CRM bot and create a new Account/Contact in Supabase. Within Grok Bot, it's a communication between the Manage Website bot and the CRM bot.
🤖 Made with AI
23
I just created a basic CRM @bot in Grok Bot. I fed it a database schema, and it set up the tables in Supabase. After successfully interacting with the database from the bot to create and update records, I asked it the following question: How would you recommend I transform my 'lists and forms' mindset into a conversational UX with a CRM database? The answer: Think in questions and moments, not screens and fields. A list is just an answer to a question you haven't asked yet, so ask the question you actually have, like "Who haven't I talked to in two weeks?" or "What's closing this month?" A form is just a record of something that happened, so describe what happened, like "Had a good call with John. He wants the action items by Friday and is leaning toward the $5K package." I'll turn that into a logged call, a follow-up task, and a deal update. Here are a few habits that make the switch easier: Log right after the moment, in your own words. Don't worry about which field things go in. If something important is missing, like a close date or an amount, I'll ask. Start your day with a briefing instead of opening a list. Ask "What's on my plate today?" and I'll give you due follow-ups, stale deals, and anything overdue. I can also send this to you automatically every morning. Ask for the next step, not the record. "What should I do about Abbott Manufacturing?" is more useful than pulling up the account. I'll use the history to suggest a next step. Keep Pages for scanning. Pages like the recent-records one are for when you really do want to see everything at once. Treat them as reports and do the work in chat. Let other bots feed the CRM. When another bot logs an email from John Abbott, you don't have to. Your inbox, calendar, and meeting notes can create activities without you typing anything. The main thing you give up is the reassurance of seeing every field filled in. To make up for it, have me read back what I saved after each update. Once you trust that, you'll stop needing to look.
1
172
I would not have guessed that the root cause of the nationwide ground stop was that overloaded switches and routers shut down after providing inconsistent data.
38
The best CRM demos start before the vendor walks into the room. We recently worked with a client where, before the CRM vendors ever demonstrated their products, we had already spoken with people across the organization. We gave the vendors more than a list of requirements. They understood how the company went to market, the different sales motions involved, the terminology people used, the biggest pain points, the priorities, and even examples of actual customers, products, and workflows. Both vendors told us afterward that the context made a real difference in how they prepared. That matters because a generic CRM demo mostly tells you what the vendor is good at showing. A well-prepared demo should tell you something very different: how well can this platform handle the way our business actually works? Before you invite vendors in, get clear on the problems you’re trying to solve, the workflows that need to improve, and the situations you want them to demonstrate. Then give the vendors enough context to show you their best answer. A requirements list tells them what you need. Understanding your business tells them what they need to prove.
🤖 Made with AI
22
I remember seeing a release about this years ago. Not sure it was heavily marketed.
17
Is anyone else finding that sleep is getting in the way of creating and refining Grok bots?
2
33