Starter workflows

A Workflow is a playbook. It tells Runner how you want a job done. Try one in a session first. Save it as a Workflow when you want the same method again. Have a Runner invoke it when you want that job to run on a schedule.

​

Find the right Workflow

​

Protect revenue

​

Proposal follow-up

Job: Find proposals that have waited more than three business days for a reply. Value: Protects work you’ve already paid to win. Needs: Gmail, plus the CRM or proposal tracker you use. Output: A ranked list with proposal value, last contact, days waiting, and a draft follow-up. Human decision: You choose the timing, message, pricing, and whether to send. Use as: A weekday Runner for an active sales pipeline, or a Workflow you invoke before pipeline review.

“Find proposals sent more than three business days ago with no reply. Rank them by value. Read the thread, draft the next follow-up, and don’t send anything.”

​

Pipeline inspection

Job: Find open deals with no next step, overdue follow-up, or no recent activity. Value: Protects revenue from quiet process gaps. Needs: Your CRM and, when useful, Gmail. Output: A short exception list with owner, stage, value, last activity, and missing next step. Human decision: The seller owns discovery, forecast judgment, pricing, negotiation, and the relationship. Use as: A weekday or Monday-morning Runner.

“Check open deals for missing next steps, overdue follow-up, or no activity in seven days. Show only exceptions. Don’t change records or contact anyone.”

​

Renewal watch

Job: Surface upcoming renewals and unresolved customer risks before the deadline. Value: Protects recurring revenue and customer trust. Needs: Your CRM, agreement folder, support source, or renewal tracker. Output: Renewals ranked by date and value, with visible risks and missing owners. Human decision: You own the customer conversation, commercial terms, and the renewal call. Use as: A weekly Runner.

“Find renewals due in the next 60 days. Show contract value, owner, open customer risks, last contact, and the next decision needed. Don’t infer health when the source is unclear.”

​

Cut costs

​

Invoice check

Job: Compare incoming invoices with signed terms and flag mismatches. Value: Stops duplicate charges, wrong rates, and avoidable spend before payment. Needs: Gmail or the invoice folder, the signed-agreement folder, and your tracking sheet. Output: Exceptions with vendor, invoice, contract term, difference, and source links. Human decision: A person verifies the evidence, handles the vendor, and approves or pays. Use as: A daily or weekly Runner, depending on volume.

“Check new invoices against the signed agreement and our tracker. Show only duplicates, rate mismatches, missing terms, or totals that don’t reconcile. Never approve or pay anything.”

​

Spend review

Job: Find recurring charges, renewals, and spend that changed unexpectedly. Value: Removes waste you don’t notice one receipt at a time. Needs: Gmail receipts, statements or a spend sheet, and any agreement folder you use. Output: A table with vendor, amount, frequency, last charge, change, and evidence. Human decision: You decide what the business still needs and whether to cancel or renegotiate. Use as: A monthly Runner or an on-demand Workflow.

“Build a recurring-spend review from the sources I give you. Flag duplicates, price changes, and renewals due in the next 45 days. Don’t cancel or contact a vendor.”

​

Save time

​

Morning attention brief

Job: Turn Gmail and Google Calendar into a short plan for the day. Value: Saves the first part of your morning and makes missed commitments less likely. Needs: Gmail and Google Calendar. Output: Three candidate priorities with source evidence, meetings that need prep, open commitments, conflicts, and important messages. Human decision: You choose the priorities, make the calls, and reply to people. Use as: A 9am Personal Assistant Runner. The Quickstart builds this one.

“Give me a short plan for today from Gmail and Google Calendar. Cite the source for each item. If the evidence is unclear, say so instead of guessing.”

​

Meeting prep

Job: Assemble the context you need before the next important meeting. Value: Saves research time while protecting the quality of the conversation. Needs: Google Calendar, Gmail, and any Project sources you name. Output: Attendees, recent history, open commitments, useful context, and questions to consider. Human decision: You choose the goals, read the room, build the relationship, and lead the meeting. Use as: A Workflow you invoke for selected meetings, or a scheduled Runner for a narrow calendar rule.

“Prepare me for my next meeting. Use the calendar event, relevant email threads, and the Project context. Separate sourced facts from suggestions.”

​

Inbox triage

Job: Sort recent email into what needs you, what can wait, and what looks like noise. Value: Saves time while keeping sensitive replies under review. Needs: Gmail. Output: A short priority list, waiting-on list, and drafts for messages that need a reply. Human decision: You decide which relationships matter, how a reply should land, and what gets sent. Use as: An on-demand Workflow first. Schedule it only after the rules are stable.

“Triage email from the last seven days. Show what needs me, what I’m waiting on, and what can wait. Draft important replies, but don’t send or archive anything.”

​

Protect customer delivery

​

Delivery risk check

Job: Find commitments with no owner, overdue work, blocked work, and client dependencies. Value: Protects delivery dates and the trust behind them. Needs: Your project tracker, Gmail, and the Project brief. Output: Exceptions ranked by customer impact, with owner, due date, blocker, and source. Human decision: The team owns priority, tradeoffs, promises, and the customer conversation. Use as: A weekday Runner for one delivery team or client Project.

“Find delivery risks from the tracker and relevant email. Show only missing owners, overdue items, blockers, and commitments likely to slip. Cite the source. Don’t change dates or contact the client.”

​

Weekly client update

Job: Draft a factual update from work that actually happened. Value: Saves reporting time and keeps client updates on schedule. Needs: Your project tracker, calendar, relevant email, and the client Project. Output: Progress, decisions, risks, next steps, owners, and dates, with gaps called out. Human decision: You choose the framing, handle sensitive news, and send the update. Use as: A Friday Runner with sending on Ask, or a Workflow you invoke after review.

“Draft this week’s client update from the sources in this Project. Separate completed work, decisions, risks, and next steps. Don’t hide missing information and don’t send it.”

​

Put a useful Workflow on a schedule

Run the procedure once in a session. Check the sources, edge cases, output, and which actions or decisions still need a person. Then choose:

• Keep it in the session when the work happens once.
• Save it as a Workflow when you want the same procedure on demand.
• Have a Runner invoke it when the job should run on a schedule.

A Workflow says how. The Runner owns the job. The schedule says when. The Project supplies background. Don’t add another Runner until this one produces useful work you can inspect and measure.

---

​

What’s next?