How to vet a $120-a-seat digital coworker before it signs into your tools

The seat is a hire, not a feature

You are about to give a persistent agent seat a login. Before it signs into your calendar, ticket queue, or document folder, run a six-point stack-evaluation note: plan coverage, shared compute, credential scope, approval gates, cost per seat, and rollback.

A small team can survive a bad document. It cannot survive a bot that has the right to send customer emails, edit billing records, or approve its own work. The model can be clever. The seat can still be too broad, too cheap to notice, and too easy to leave running.

Grok Bot launched in beta on August 11, 2026.

Cursor, the software company, was officially acquired by SpaceX on August 14, 2026, in a deal valued at $60 billion.

The product is a coworker. It runs on a dedicated cloud computer and signs into users' existing apps and websites through their interfaces rather than only through APIs or MCP integrations, the usual ways to link software.

For a small founding team, the agent can sit inside the same tools your humans already use. That is useful. It is also where the operational risk lives.

Run six checks before the first sign-in

Keep the note in the same place you keep vendor contracts and access reviews. The list below is the minimum. Each answer should be written down before the seat gets a login.

• Plan coverage: On August 21, 2026, xAI expanded Grok Bot access to SuperGrok Plus, Cursor Pro+, and all Cursor Teams plans; confirm which plan includes the seat and note the plan line.
• Shared compute: Record the compute model; the machine setup changes how you monitor load, data location, and off-hours activity.
• Credential scope: List every app or website the agent can sign into, and remove any login it does not need for the initial scope.
• Approval gates: Grok Bot is designed with human approval gates, with Bots returning for approval and users retaining final decisions; set the rules for when the agent must stop and ask.
• Cost per seat: Grok Bot access was priced at $120 per seat for Cursor Premium Teams, $200 for Cursor Ultra, and $300 per month for SuperGrok Heavy; decide who owns the renewal and what usage triggers a plan change.
• Rollback: Name the person who can disconnect the seat, revoke its logins, and restore the last known good state without waiting for vendor support.

Plan coverage and cost per seat belong together. A seat that is available on more plans can quietly change the invoice, so the owner should know which plan line to watch. Shared compute and credential scope belong together: the setup with broad logins is the part that can keep working after a human stops watching.

Approval gates and rollback are the off-ramp. If the agent can act without a human stop point, the team needs a faster way to stop it. Write the stop point in the note, not in a chat thread.

Keep the stop point in the file

The note should be short enough to reread in a meeting. Name the owner, the plan line, the apps in scope, the approval rule, and the person who can turn the seat off. If the vendor changes access or pricing, update the note before the next renewal.

When the answer is only in a vendor dashboard, the team does not have an operating record. Treat the note as a current record. Add a new app, then update the scope. A person leaves, so check whether the agent still has a login that should be removed. A workflow changes, so decide whether the approval gate still matches the risk.

The seat is always-on, so the note should name who watches it. Make it readable by the person who inherits the tool after the founder is too busy to explain it. Show it to a new hire, a contractor, or an auditor who asks why the seat has access. Put the evaluation in the file, and put the stop point next to the access review.