Amir Ghowsi

Ask first

• Where do form submissions arrive today? (default an email to you from your website builder)
• What subject or sender identifies them? (default the website builder's no-reply address)
• Which channel should leads post to? (default a #sales-leads channel)
• Which fields should each post keep? (default name, email, company, title, team size, message)

Needs

• The inbox that receives form submissions.
• A team chat channel the assistant can post to and read back.
• Connecting email: "It only opens emails from your form sender; it never replies or moves mail."
• If your assistant can only chat: forward or paste each submission and ask it to format the post; you paste it into the channel.

Build

1. Read: every hour, search the inbox for form emails received since yesterday's date. Use a calendar date in the search, not a timestamp.
2. Read: collect every email address already posted in the channel in the last 2 days.
3. Decide: for each form email, keep only the lead block (drop footers, tracking and signatures). Lowercase the email; if it is already posted, skip it. A lead without a block is counted and skipped, never stops the run.
4. Deliver: one post per new lead, fields in a fixed order, bare email address, no commentary.
5. Report: found, skipped as already posted, skipped as unreadable, posted. Found must equal the other three added up.

Check

• Run with posting off against yesterday's inbox. Every lead already in the channel must show as skipped; the count of new leads must match what you see by hand.
• Run twice in a row: the second run must post nothing.

In my version

• Cora with Gmail and Slack connected; leads come from a Webflow form.
• Hourly.

Ask first

• Who gets reminders? (default everyone on the team with an assigned task)
• Which tasks count? (default not started, overdue, or waiting for review; ignore done and snoozed)
• What time and which days? (default 8am weekdays, local time)
• Where do reminders go? (default a direct message in your team chat; email if none)

Needs

• A shared task list where each task has an owner, a status and a due date.
• A team chat tool that can send direct messages, or email.
• Connecting the task list: "It reads who owns which open tasks; it never changes a task."
• If your assistant can only chat: paste your task list each morning and ask "who owes what, and what is overdue?"; send the nudges yourself.

Build

1. Read: at the set time, pull every task with an owner, status and due date.
2. Decide: keep tasks that are not started, waiting for review, or past due. Group by owner. Skip owners with zero.
3. Decide: count per owner: overdue, waiting for review, due today, other open. Name the oldest overdue task.
4. Deliver: one direct message per owner with the counts, the oldest overdue task and a link to their list. Fallback: one email per owner.
5. Memory: none needed; each run reads the live list, so a finished task stops appearing the next morning.

Check

• Run it with delivery off and print the message for each owner. Pick one owner and compare the counts against their list by hand.
• A teammate with nothing open must get no message.

In my version

• Cora, the agent product my company makes, with a built-in task list and Slack.
• Weekdays at 8am Pacific.

Ask first

• Which meetings count? (default meetings on your calendar with someone outside your company)
• Where should each update go? (default the account's internal channel; a DM to you if there is none)
• Should you approve before anything posts? (default yes)
• What time should it run? (default 6pm on weekdays)

Needs

• Notes or transcripts from your meetings, from a note-taker or pasted in.
• Your calendar, to know which meetings were with customers.
• A team chat tool.
• Connecting notes: "It reads notes from today's customer meetings only."
• If your assistant can only chat: paste the day's notes and ask for one update per account.

Build

1. Read: today's calendar events with an outside attendee, and the notes for each.
2. Decide: for each meeting, list commitments with an owner and a date. Keep: "I'll send the pricing by Friday". Drop: "we should catch up soon". Split into what we owe and what they owe; add one risk line if something changed.
3. Decide: group by account; skip meetings with no notes and say so.
4. Deliver: draft updates to you for approval; post each one after you approve.

Check

• Run on yesterday's meetings with posting off. Every commitment must quote a line from the notes.
• A day with no customer meetings sends nothing.

In my version

• Cora reading Granola notes and Google Calendar, posting to Slack.
• Weekdays at 6pm Pacific.

Ask first

• Which accounts have a launch checklist? (default every account in onboarding)
• How sure must it be to suggest a task is done? (default only with a direct quote)
• Who approves? (default you, or the account owner)

Needs

• Meeting notes or transcripts per customer.
• A checklist or task list per customer, with task names and status.
• If your assistant can only chat: paste the notes and the checklist; ask which tasks the notes show as done.

Build

1. Read: after each customer meeting, its notes and that customer's open checklist tasks.
2. Decide: a task counts as done only if a line in the notes says it happened. Keep: "we connected the CRM Tuesday". Drop: "we plan to connect the CRM".
3. Deliver: a numbered list of suggested tasks, each with its quote, and the checklist link. Wait for approval.
4. Act: mark only the approved tasks done; leave the rest untouched.

Check

• Run on last week's notes with updates off. Each suggestion must quote the notes, and no task without a quote may appear.

In my version

• Cora's task lists and meeting notes from Granola; I approve in chat.

Ask first

• What counts as critical? (default two or more of: usage down 30% over 4 weeks, no contact in 45 days, champion left, renewal within 90 days)
• Where do alerts go? (default a team chat channel, plus the account owner)
• How often may one account alert? (default once per change in status)

Needs

• Product usage per account, a list of accounts with owners and renewal dates, and recent email, meeting and support activity.
• Missing usage data: fall back to activity and support volume, and say so in the alert.
• If your assistant can only chat: paste a weekly account export and ask which accounts meet the rule.

Build

1. Read: daily, each account's usage, activity, support and renewal date.
2. Decide: apply the rule; an account alerts only when it newly becomes critical.
3. Decide: write the signals that tripped and one next step.
4. Deliver: an alert in the channel naming the owner. Remember each account's last status so it does not repeat.

Check

• Run on last month's data with alerts off; the accounts it flags should match the ones your team was already worried about.

In my version

• Cora's risk signals across our customer accounts, alerting in Slack.

Ask first

• Where do customers ask for things? (default shared chat channels, email and calls)
• Where are requests logged? (default your issue tracker)
• Who owns each kind of ask? (default the account owner)

Needs

• The places customers write or speak to you, and your issue tracker.
• If your assistant can only chat: paste the day's customer messages and ask for a list of asks.

Build

1. Read: the last 24 hours from each source.
2. Decide: an ask is a customer requesting a change, fix or feature. Keep: "can we export this to CSV?". Drop: "thanks, looks great".
3. Decide: match each ask to an existing ticket; mark it logged or not, and name the owner.
4. Deliver: one daily message grouped by account; nothing on a quiet day.

Check

• Run on yesterday with delivery off; compare against the asks you remember.

In my version

• Cora reading our customer Slack channels and call notes, checked against Linear.

Ask first

• Which meetings count? (default every meeting with notes in the last 7 days)
• Who are you, by name and email, so it can tell your items from the team's? (default your account's name)
• When and where? (default Monday 8am, a direct message to you)

Needs

• Notes or transcripts from your meetings, from a note-taker or pasted in.
• If your assistant can only chat: paste last week's notes on Monday and ask for the two lists.

Build

1. Read: notes from meetings in the last 7 days.
2. Decide: pull action items. Yours if assigned to you or said by you in the first person ("I'll send it"). The team's if assigned to "we", the team or nobody. Unclear goes to the team.
3. Decide: merge duplicates; add the meeting title to each item.
4. Deliver: one message with two headed lists, "For me" and "For the team"; "None" under an empty one. If there were no meetings, say so in one line.

Check

• Run on last week with delivery off; every item must trace to a line in a meeting's notes.

In my version

• Cora reading my Granola notes, sending a Slack DM on Monday mornings.

Ask first

• Which company is the mockup for? (default the prospect you meet next)
• Who is the reader? (default a customer success manager at that company)
• What layout do you reuse? (default one saved email template, always the same)

Needs

• Web search, to find the company's real customers and product names.
• One saved template file, so every mockup looks identical.
• If your assistant can only chat: ask for the digest as plain text with the company's public customers and products.

Build

1. Read: 4 to 8 searches for public customer stories, case studies, award announcements and product names.
2. Decide: keep only customers named on a public page; keep the page address for each.
3. Decide: invent health numbers and suggested next steps; never invent customer or product names.
4. Deliver: fill the saved template and save it as a file; list the sources used.

Check

• Open the file; every customer name must trace to a public page in the source list, and every number must be marked as invented in your notes.

In my version

• A Claude skill with one saved HTML template and our product's avatar.
• I send the file to the prospect after a first call.

Ask first

• When does chasing start? (default the day after the due date)
• How often per invoice? (default once a week, at most 3 times, then flag to you)
• Who sends? (default you, from your own email, after you approve)

Needs

• A list of open invoices with customer, amount, due date and billing contact.
• Payments received, to close invoices that were paid.
• If your assistant can only chat: paste your open invoices weekly and ask for drafts.

Build

1. Read: weekly, open invoices and recent payments.
2. Decide: close any invoice matched by a payment. List overdue and due within 7 days.
3. Decide: draft a short, polite reminder for overdue ones; the tone gets firmer on the third.
4. Deliver: the list and drafts to you; nothing sends without your approval.

Check

• Run with sending off; every invoice you know was paid must be absent.

In my version

• An assistant reading our invoicing and bank tools; I send from Gmail.

Ask first

• Who is the call with, and when? (default your next external meeting)
• What sources may it read? (default notes, email and recordings involving those people)

Needs

• Your notes, email and recordings with the attendees.
• If your assistant can only chat: paste prior notes and emails and ask for the prep doc.

Build

1. Read: every source mentioning the attendees or their company; check all of them, not just one.
2. Decide: separate what they confirmed from what you are guessing; mark guesses.
3. Deliver: goal, agenda, talk track, objections with answers, and "don't say" items.

Check

• Every claim about the customer must cite a note, email or recording.

In my version

• Claude with Granola, Gmail and a call recorder connected.

Ask first

• Which side are you on? (default the vendor)
• What matters most? (default IP, liability, term, renewal and data)

Needs

• The contract as a file or pasted text.
• If your assistant can only chat: paste it and ask for issues ranked by risk.

Build

1. Read: the full contract, and any agreement it references.
2. Decide: rank issues by real-world risk, not count; suggest wording for each.
3. Deliver: the list; a draft amendment only when asked. Remind the person it is not legal advice.

Check

• Each issue must quote the clause it refers to.

In my version

• Claude reading Word files; amendments drafted as docs.

Ask first

• Who will see it? (default the customer, who may forward it)

Needs

• The deck file; rendering it to images helps catch layout problems.
• If your assistant can only chat: paste the slide text and attach screenshots.

Build

1. Read: every slide's text, speaker notes and images.
2. Decide: flag contradictions first, then copy fixes, then layout.
3. Deliver: a list by slide number with the fix for each.

Check

• Plant one typo and one contradicting number in a test deck; both must be caught.

In my version

• Claude reading PowerPoint files and rendering slides to images.

Ask first

• Who is it for, and will it be forwarded? (default yes; keep internal details out)

Needs

• Notes on the person and past emails.
• If your assistant can only chat: paste them in.

Build

1. Read: notes and threads.
2. Decide: remove anything confidential to either side before drafting.
3. Deliver: one draft; shorten on request.

Check

• Reread for anything you would not want the reader's boss to see.

In my version

• Claude with Gmail and Granola connected.

Ask first

• Where is the list from? (default a conference badge scan)
• Should it create missing contacts? (default no, list them only)

Needs

• Your CRM, connected; the list as text or a file.
• If your assistant can only chat: paste the list and a CRM export.

Build

1. Read: search by last name, then first name, then company or email domain.
2. Decide: found, missing, or duplicate (two records for one person).
3. Deliver: three lists with record links; suggest merges, change nothing.

Check

• Include one person you know is in the CRM twice; it must be flagged.

In my version

• Claude with HubSpot connected.

Ask first

• What is the source? (default a working doc you used with a real customer)
• What invented company name and domain? (default Acme Co and .example addresses)

Needs

• The source file or setup.
• If your assistant can only chat: paste the text and ask for the rewrite.

Build

1. Read: the full source, including comments.
2. Decide: list every real name, address, field and link; replace each consistently.
3. Deliver: a clean copy and the list of replacements.

Check

• Search the copy for each real name on the list; none may remain.

In my version

• Claude editing Word files and a demo workspace in Cora.