Sponsored by ferociter.co
← Back to the directory

PRACTITIONER REPORT · GROK BOT

Seven ways Peter Lohmann uses Grok Bot

A property-management operator’s account of using bots across business and personal administration.

Source: Peter Lohmann (@pslohmann), October 12, 2026 ↗

What Peter reported

  1. Inbox cleanup

    Peter reports clearing spam and unwanted email four times a day.

  2. Executive-assistant recruiting

    He describes using Dripify and LinkedIn to recruit a new EA. The post does not explain his search criteria or recruiting process.

  3. Personal medical administration

    He reports tracking HSA receipts, appointments, insurance, and other medical admin. This is a personal example, not a property-management workflow or clinical advice.

  4. Proptech and property-company filing monitoring

    He says the bot monitors more than 100 proptech vendors and property-management companies for legal filings. Source coverage and accuracy are not specified.

  5. Crane support

    He says the bot helps him manage Crane. The post gives no specific tasks or implementation details for this example.

  6. Processing inboxes with GTDBot

    He describes GTDBot processing multiple inboxes, connected to personal and work email and a task list. The post does not detail its rules for turning messages into actions.

  7. Group-trip RSVPs

    He reports confirming and managing RSVPs for Horizons, a planned Brazil trip with 30 property managers the following year.

Where this fits in property operations

Vendor monitoring is directly relevant to property-company research. Inbox processing, recruiting, and RSVP tracking are broader administrative examples that a property team could adapt. This post does not report underwriting, leasing, or investment-performance results.

What the post does not establish

These are Peter’s reported uses. We have not reproduced the setup or verified its accuracy, time savings, or account permissions. The post supplies no implementation recipe for Crane support.

In the reply supplied with this post, Peter agrees that the setup involves broad access to personal data and accounts. That does not establish the exact permissions or mean every workflow needs unlimited access. Each implementation needs its own access decisions and review points.

Start with one defined task and an approved sample. Review proposed messages and account changes before execution. For filing research, verify the company match and distinguish allegations from court findings.

Reviewed October 13, 2026. Summary of the original author’s post; replies from other people are not attributed to him. Sources & editorial policy