The work people hand to Mitra.
42 jobs somebody used to do by hand, every week, forever. Each takes one sentence to set up. Search for yours, or filter by what you do.
Follow-upsContract renewal remindersRead my renewals Google Sheet every weekday at 8am, draft a renewal email in Gmail for any contract inside 60 days and leave it for my approval, then post this week's renewals to #ops in Slack.
Weekdays at 8amStatus updatesDaily standup summaryEvery weekday at 8:45am, check what moved in Linear and what merged in GitHub since yesterday morning, then post a short standup summary to #standup in Slack, grouped by person, with anything blocked called out at the top.
Weekdays at 8:45amReportingExpense anomaly watchEvery Monday at 8am, compare last week's Brex charges against the last three months, write anything unusual to the 'Flags' tab of my Google Sheet, and post to #ops only the charges that need a decision from me.
Mondays at 8amFollow-upsInvoice chasingEach weekday at 9am, list the QuickBooks invoices past their due date, draft a polite chase per customer in Gmail for me to approve, and post the total outstanding to #finance in Slack with the worst offenders first.
Weekdays at 9amReportingAutomated weekly business reportEvery Friday at 4pm, pull this week's revenue from Stripe and new deals from HubSpot into the 'Weekly' tab of my Google Sheet, then post the three biggest changes to #leadership in Slack.
Fridays at 4pmTriageEscalation watchCheck Intercom every hour for open conversations that are going badly — three or more customer replies, an angry tone, or anyone from our top accounts. Post each one to #support-escalations in Slack with a short summary and the link, and open a Linear issue when there is a bug behind it.
Every hourResearchHelp doc gapsEvery Friday at 2pm, read this week's Zendesk tickets and find the questions we answered by hand that have no article in our Notion help center. Draft the missing article for each one from the replies we actually sent, and open a Linear issue asking someone to review it.
Every Friday at 2pmTriageRefund request triageEvery morning at 10am, take the open refund requests in Zendesk and find each customer's payment in Stripe. Summarize what they paid, when, what they have been refunded before and what the ticket is asking for, then post each case to #refunds in Slack for one of us to decide.Every day at 10amFollow-upsSLA breach watchEvery thirty minutes, check Zendesk for tickets within an hour of missing their first-response target and send the assignee a Slack message with the ticket, the customer and how long is left. If a ticket has already breached, post it to #support-leads instead.Every 30 minutesFollow-upsSupport ticket follow-upsEvery morning at 10am, check Zendesk for tickets that have been waiting on a customer reply for more than two days and send each one a polite nudge. Then post the tickets waiting on us for more than a day to #support in Slack.Every day at 10amReportingSupport volume reportEvery Monday at 9am, count last week's Zendesk tickets, work out the average first-response time, and find the five most common reasons people wrote in. Append the numbers to my Support Metrics sheet in Google Sheets, then post a summary to #support showing how each one moved against the previous week.Every Monday at 9amResearchChurn signal digestEvery Monday at 8am, compare each account's PostHog activity last week against the previous four weeks, find the ones whose usage dropped sharply, look up the owner and the last note in HubSpot, and post the list to #customer-success in Slack, biggest drop first.
Mondays at 8amResearchCustomer feedback themesEvery Friday, read this week's Intercom conversations and Typeform responses. Group what customers asked for into themes, and give each theme a count and one quote. Write the summary to Notion, and open a Linear issue for any theme mentioned more than five times.
Every FridayReportingMonthly roadmap digest for execsOn the first Monday of every month, read the roadmap in Linear and write a five-slide Google Slides deck covering what shipped, what slipped and what is next in plain language, then email the deck to the leadership list from Gmail.
First Monday of the monthStatus updatesSprint status update automationEvery Monday at 9am, summarize last week's Jira movement by epic — what shipped, what slipped and what is still open. Write the full summary to the 'Sprint updates' page in Notion, then post a three-line version to #product in Slack.
Mondays at 9amTriageUsage anomaly alertsEvery six hours, check the signup funnel in Mixpanel and compare each step's conversion with the same hours over the past two weeks. If a step has dropped well below its usual rate, post the before and after numbers to #product in Slack and open a Linear issue.
Every 6 hoursResearchAutomated competitor monitoringEvery Monday at 8am, check my three competitors' ranking changes in Ahrefs and look for new mentions of them on Reddit. Post anything genuinely new to #marketing in Slack, each with a one-line note on why it matters.
Mondays at 8amFollow-upsContent calendar nudgesEvery weekday at 9am, check my Notion content calendar for pieces due this week whose status has not changed in three days, and send each owner a short Slack message with the piece, the due date and how long it has been stuck.Weekdays at 9amReportingNewsletter performance reportEvery Wednesday at 10am, take the newsletter Mailchimp sent last week, add its opens, clicks and unsubscribes to my 'Newsletter log' sheet, then post to #marketing in Slack how the send compares to my running average and which subject line performed best.
Wednesdays at 10amReportingWeekly SEO ranking reportEvery Monday at 7am, read my tracked keyword positions from Ahrefs, compare them with last week, log the new positions in my 'SEO tracking' sheet, and post only the keywords that moved up or down to #seo in Slack with the page ranking for each.Mondays at 7amReportingAutomated weekly marketing reportEvery Monday at 9am, pull last week's traffic from Google Analytics, signups from PostHog and email performance from Mailchimp into my 'Marketing weekly' sheet, then post what went up and what went down to #marketing in Slack.
Mondays at 9amResearchLost deal debriefEvery Friday at 5pm, find the HubSpot deals that closed lost this week, read the loss reason and the notes on each, then add them to my 'Why we lose' page in Notion under the theme they belong to and post the week's tally to #gtm in Slack.Fridays at 5pmResearchMeeting prep briefsEvery weekday at 7am, look at today's external meetings in my Google Calendar and, for each one, look up who is attending and their company, read the deal notes in HubSpot, and send me a one-page brief in Slack with what happened last time and three questions to ask.
Weekdays at 7amReportingPipeline hygiene reportEvery Friday at 4pm, check my open HubSpot deals for missing close dates, stages that have not changed in 21 days and deals with no next step logged, then post the list to #sales in Slack grouped by deal owner.Fridays at 4pmFollow-upsQuote to signature chaseEvery weekday at 8am, list the PandaDoc quotes sent but not signed, match each to its HubSpot deal for the value and owner, and post them to #sales in Slack with a nudge drafted for me to approve, flagging anything unsigned for more than seven days as at risk.
Weekdays at 8amFollow-upsSales follow-upsEvery weekday at 8am, find the HubSpot deals with no contact in the last seven days. Draft a follow-up email for each one in Gmail and leave it for me to approve. Then post the list to #sales in Slack with deal values, so I know what to chase first.Weekdays at 8amTriageBug intake triageEvery morning at 9am, go through yesterday's Zendesk tickets and, for the ones describing a bug rather than a question, open a Linear issue with the reproduction steps and a link to the ticket. Post each issue link back to the Slack channel the report came from.Every day at 9amFollow-upsCode review nudgesAt 11am on weekdays, find every open pull request that has been waiting on a review for more than 24 hours and send its reviewer a direct Slack message with the link and how long it has waited, oldest first.Weekdays at 11amTriageDependency alertsEvery Monday at 7am, check our repositories for new dependency security advisories, open one Linear issue per repository listing the affected packages and their severity, and post only the critical ones to #eng.Mondays at 7amStatus updatesDeploy digestAt 6pm every day, look at what was deployed to production in GitHub since the last digest and post one message to #shipped naming each change, the person who shipped it, and any revert that happened today.Every day at 6pmStatus updatesOn-call handoffEvery Monday at 9am, go through the PagerDuty incidents from the past week, pair each one with the pull request that fixed it, and write a handoff note in Notion listing what paged, the cause and what is still open. Post a short version to #on-call.
Mondays at 9amReportingRelease notesEach Thursday at 5pm, read every pull request merged in our repos since last Thursday, write release notes that separate features from fixes and chores, publish them as a new page in Notion, and share the three biggest items in #product.Thursdays at 5pmReportingUptime incident logEvery Friday at 4pm, pull the alerts and downtime Datadog recorded this week, add them as a new dated section in our Notion incident log with one line comparing this week to last, and drop that line in #ops.
Fridays at 4pmTriageaccessibility audit logEvery Friday at 2pm, check the screens added to Figma this week against our accessibility checklist — contrast ratios, tap target size, and how text behaves when scaled. Open a Linear issue for each miss with the screen named, and post a summary to #design.
Fridays at 2pmResearchContent to social visualsOn Tuesdays at 10am, pull next week's approved items from our content calendar in Notion, draft a social visual in Canva for each one using our brand template, and post the drafts to #design for someone to finish.
Tuesdays at 10amResearchdesign feedback from supportEvery Monday at 10am, go through last week's Zendesk tickets and find the ones where somebody could not work out how to do something, rather than hitting a bug. Group them by the screen involved and post the list to #design with links, then open a Linear issue for any screen mentioned more than five times.Mondays at 10amFollow-upsDesign handoff trackerEach Monday at 10am, cross-check the Figma files marked ready for build against Linear, then tell #design which of those designs have no issue yet and which shipped issues still have designs sitting in progress.Mondays at 10amStatus updatesDesign review agendaAt 9am on Wednesdays, look at which Figma files changed since last week's design review in Google Calendar, then post an agenda to #design ordered by how much moved, with one line on each file.Wednesdays at 9amResearchdesign system driftEvery Thursday at 4pm, go through our Figma libraries for components that have been detached or restyled with values that are not in our tokens. Open a Linear issue for anything used on more than three screens, and post the full list to #design-system in Slack grouped by file.Thursdays at 4pmFollow-upsFigma comment roundupEvery Friday at 3pm, go through the unresolved comments in our Figma files and post a checklist to #design in Slack, grouped by file and by whoever owns the fix, with anything older than a week flagged. Open a Linear issue for the ones that need real work.Fridays at 3pmReportingsales deck refreshOn the first Monday of each month, check the figures on our sales deck against HubSpot and tell me which slides are out of date. Draft the corrected numbers slide by slide and post them to #sales-enablement for approval. Do not edit the deck.First Monday of the monthStatus updatesweekly design digestEvery Friday at 5pm, look at what moved in our Figma files this week and write a short design digest: what shipped, what is in review, and what is blocked and on whom. Save it to the Design digest page in Notion and post the headline version to #design.Fridays at 5pm
Nothing matches “”.
These are examples, not a menu. Describe the job you actually repeat and Mitra will build an agent for it, whether or not it is listed here.
See how it worksHand over the work you keep repeating.
Your first agent is one sentence away.
Get started free200 credits to start · no credit card · nothing to install