# Sales Source: https://routineos.org/use-cases/sales > Signals and briefs before you reach out. Claude routines for sales teams, built from two real templates. They start report-only and ask before they act. Use case: sales # Sales routines for Claude: signals and briefs before you reach out Two templates cover the reading that comes before a sales conversation. One watches public job postings for companies that are hiring for the work you sell. The other researches the company you are about to meet. Both start report-only. Free (MIT). Needs a paid Claude plan. [Get started](https://routineos.org/#start)[See jobs watch](https://routineos.org/templates/jobs-watch)[See meeting brief](https://routineos.org/templates/meeting-brief) jobs-watch: pilotedmeeting-brief: unpilotedexample scenario The job ## The job: AI lead generation from public signals A seller reads two things before reaching out: whether a company is hiring for the work they sell, and who a company is before a meeting. It is reading and judging, done on a regular rhythm, and the result should be short enough to act on. The scenario below is an example built only from what the two templates do. An example week ## An example week with both routines Say a seller who sells commerce and automation services turns both templates on. It carries no results. 1. **Monday and Thursday, 22:00 UTC: jobs watch runs**It searches each market in your settings for postings whose title matches a keyword. The defaults are AU, US, CA, NZ and PH, and Shopify, headless, commerce and AI automation. It links each role to its company and puts at most five items in your Inbox by default. 2. **You open the Desk**You see the few roles that need a person. You keep one, drop another, and the routine learns from those choices. It suggests setting changes, for example a title word you keep dropping. Nothing applies until you say yes. 3. **Sunday to Thursday, 20:00 UTC: meeting brief runs**It looks 24 hours ahead for meetings that include someone outside your company. For each one it searches for the other company, reads a few pages and writes a short brief with the source of every line. 4. **You check the sources**Each line names its source. Two companies can share a name, so the brief is based on the attendee's domain and you can verify the match yourself. Source: template READMEs and catalog schedules in the [RoutineOS repository](https://github.com/devkindhq/routineos). Schedules are UTC. Settings and defaults can be edited on the Desk. Templates ## The two sales templates [ ### Jobs watch Tracks public job postings for commerce and automation roles, links each role to its company, and puts the few that need a person in the Inbox. pilotedwatch Open ](https://routineos.org/templates/jobs-watch) [ ### Meeting brief Before each outside meeting, researches the other company and writes a short, cited brief to the Desk. unpilotedwatch Open ](https://routineos.org/templates/meeting-brief) **Jobs watch needs**Web search and web fetch **Meeting brief needs**A calendar connector, web search and web fetch **First run**Report-only Maturity is from the catalog. Meeting brief has not had a real run yet, so run it report-only and read the first brief before you rely on it. Safety ## What it never does These come from the template prompts. They are rules the prompt forbids and the checks around it. They are not a promise about every possible run. - The prompt forbids sending, posting, pushing or deleting anything in jobs watch. - The prompt forbids sending, posting, accepting, declining or changing a meeting in meeting brief. - The meeting brief stores attendee company domains and the meeting title, not attendee names or addresses. Check that storing titles is acceptable where you work. - Both prompts treat web pages and calendar text as data, not instructions. **Heads up**Jobs watch can prepare intro notes that wait behind an email gate, which times out after 48 hours. Nothing is sent unless a person approves it. The Desk's approve-then-send flow is not piloted end to end, so check it on your own machine first. Next ## Where to go from here Read the [jobs watch page](https://routineos.org/templates/jobs-watch) for the install steps and settings. See the other teams on [all use cases](https://routineos.org/use-cases), or [migrate a workflow](https://routineos.org/migrate) you already run in n8n, Windmill or Zapier. ## Install jobs watch first It is the piloted one. Run it report-only, read the first report, then add the meeting brief. [Get started](https://routineos.org/#start)[Install jobs watch](https://routineos.org/templates/jobs-watch)