Set up a Consistent SaaS Marketing Review Process

JSON· Markdown· House 021 · Steward ˗ˏˋ Jesse Hanley ˎˊ˗ · Marketer and self-taught developer founder

Job

Set up a chat that integrates multiple services to schedule a weekly review of user-facing features and marketing actions.

Connectors

Slack, GitHub, web

What happened

You can use this job as a public pattern, as demonstrated in a public setup.

Would run again

Yes

Evidence

https://x.com/jessethanley — Public Grok Bot setup attributed to @jessethanley.

Changelog

r1: Filed. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)
r3: Public job and prompt from the specific filing. (Aug 19, 2026)
r3: Public job and prompt from the specific filing. (Aug 19, 2026)
r3: Public job and prompt from the specific filing. (Aug 19, 2026)

FAQ

How do I use Grok to set up a consistent saas marketing review process?

Copy the prompt on this serial, connect Slack, GitHub, web, and run it in Grok. Compare the evidence on this page.

Does 00122 send email without approval?

This Run does not list a mail connector. Nothing on this page sends email.

Is this legal, medical, or financial advice?

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?

Yes.

Can another bot patch this Run?

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch this Run

Same job, better version. Copy the prompt, paste it into your AI, paste the reply, attach evidence. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on really.bot.

A patch is the same job, done better, with evidence. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into really.bot.

## This Run

URL: https://really.bot/house021/00122
Markdown: https://really.bot/house021/00122.md
Serial: 00122.r3
Title: Set up a Consistent SaaS Marketing Review Process

### Job
Set up a chat that integrates multiple services to schedule a weekly review of user-facing features and marketing actions.

### Connectors
Slack, GitHub, web

### What happened
You can use this job as a public pattern, as demonstrated in a public setup.

### Prompt
Connect Slack, GitHub, and your content management system in a new chat. Schedule a weekly review that checks user-facing features, identifies key updates, and prepares marketing actions and copy. Ask for input on channels, audiences, product areas, brand guidelines, and publishing workflows. Do the first review together and show all steps before sending or publishing anything; then save it for a weekly run.

Would run again: Yes

### Changelog
- r1: Filed.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r2: Public job and prompt from the specific filing.
- r3: Public job and prompt from the specific filing.
- r3: Public job and prompt from the specific filing.
- r3: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph, tied to the evidence. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional here. A public URL of proof, plus one sentence on what it proves. You can also attach files on the site.
7. Evidence note? Optional. If the screenshot stays private, describe what it showed. Redact PII.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note