Topics ▾
Workflows ·

Compare tools from their official pricing pages, into a shareable sheet

Beginner, 10 minutes

Ask a Bot to compare a few products for your team size using only the official pricing pages, with no signing in, and return a table plus a spreadsheet in your library.

How this helps you

You get a buying decision with sources in minutes, in a file you can pass on.

✦ Try it
Compare [products] for a team of [number]. Use only each company's official pricing page and don't sign in anywhere. Tell me the cheapest paid option that fits, then give a table with plan name, price per user per month, total per month, billing terms and the key limits, with a link to each pricing page and the date you checked. Save it as a spreadsheet in my library.

Fill in: [products] is the list you're comparing. [number] is the number of seats.

What they did

Zain Kahn's third starter job for work: a Bot called Price check compared Zoom, Google Meet and Microsoft Teams for a team of 10, using only the official pricing pages and without signing in. It read each pricing page, answered which paid option was cheapest for 10 people, then sent the full table and a spreadsheet saved in the library. His rules for beginners: one Bot per job, your rules in the first message, a routine for work that repeats, and ask for a file you can share. He suggests starting with public web jobs like this before connecting apps such as Gmail.

Who it's for: Office managers, founders and anyone asked to pick a tool for a team.

Before you start

How to try it

  1. Create a Bot for the job (Zain names his Price check).
  2. Put the rules in the first message: official pricing pages only, no signing in, your team size.
  3. Ask for the answer first, then the full table, then a spreadsheet saved in the library.
  4. Open the spreadsheet and check one price against its pricing page.
  5. Share the file with whoever signs off on the purchase.

What to expect

A one-line answer naming the cheapest fitting plan, a table with a row per plan and a link per row, and a spreadsheet in the library you can open or share.

Common mistakes

Related tips

Worth knowingCarved from a segment of this video starting at 1:23. Paraphrased by us; watch the original for the full walkthrough.
Next in Workflows →From support form to fix: a webhook, a Bot and a Cursor cloud agent

Learn more: Grok Bot Use Cases: Real Workflows From Real Users · All Grok Bot workflows tips

Related Grok Bot tips

More Workflows →
Workflows

Two habits that make usage last: batch requests, send words not screenshots

Every message makes a Bot reread the chat, so send related requests together, skip 'thanks' replies, and paste text or cropped images instead of full screenshots and PDFs.

How this helps you The same work uses fewer messages and less image reading, so your weekly usage goes further without dropping any jobs.
Spotted by Sharbel A. (YouTube) · 3 Nov 2026
Workflows

Let your Bot cancel free trials and unused subscriptions

Three built-in templates from 0.78: start a trial and cancel it before it bills, cancel plans you don't use, and watch renewal prices.

How this helps you You stop paying for trials and plans you forgot about, and nothing is cancelled without your OK.
Spotted by @spectnfa · 31 Oct 2026
Workflows

From support form to fix: a webhook, a Bot and a Cursor cloud agent

A support form posts to a webhook, a Bot picks up the ticket, and for bugs it starts a Cursor cloud agent that reproduces the issue, adds a failing test and opens a pull request for an engineer to review.

How this helps you By the time an engineer looks at a bug, it has repro steps, a test and a proposed fix waiting.
Spotted by Grok, Santi Garza (YouTube) · 29 Oct 2026