> ## Documentation Index > Fetch the complete documentation index at: https://docs.spinnable.ai/llms.txt > Use this file to discover all available pages before exploring further. # Hiring Your First Worker > Learn how to hire your first AI worker by focusing on the job you need done, not job titles ## The "Job Description Not Job Title" Approach When hiring your first AI worker, think about **what you need done** rather than what role title to assign. This practical approach helps you get started quickly and see real value. ### Start With Your Actual Needs Instead of thinking "I need a marketing manager" or "I need a data analyst," ask yourself: **"What specific work am I doing repeatedly that I wish someone else could handle?"** Common examples: * "I need someone to monitor our support inbox and draft responses" * "I need someone to review sales calls and pull out action items" * "I need someone to track competitor pricing and alert me to changes" * "I need someone to summarize long documents before meetings" ## Example: Gil's Multi-Worker Setup Gil, one of our early users, started with a simple need: better visibility into what his team was working on. Here's how he approached it: ### The Problem "I wanted to know what everyone was working on without having to ask them constantly or wait for weekly updates." ### His Solution: Two Specialized Workers **Worker 1: The Slack Monitor** * **Job Description**: "Watch our team Slack channels and identify what people are actively working on" * **Skills Needed**: * Read Slack messages * Identify work-related discussions * Distinguish between casual chat and actual work updates * **Knowledge Base**: * Team member names and roles * Current project names * Common abbreviations the team uses **Worker 2: The Notion Updater** * **Job Description**: "Take the work updates and maintain a clean summary in our Notion workspace" * **Skills Needed**: * Write to Notion * Organize information by person and project * Keep summaries concise and scannable * **Knowledge Base**: * Notion workspace structure * Preferred summary format * Which projects are priorities ### Why Two Workers Instead of One? Gil chose to split this into two workers because: 1. **Separation of concerns**: One worker focuses on listening, one on organizing 2. **Easier to debug**: If something goes wrong, it's clear where the issue is 3. **Reusability**: The Slack monitor could feed other workers in the future 4. **Better context management**: Each worker stays focused on its specific domain ### The Results After setting this up: * Gil gets a daily summary of team activity without asking anyone * Team members don't need to remember to update status docs * The Notion page becomes a natural place to check "what's happening" * No additional burden on the team - they just keep using Slack normally ## Your Turn: Starting Simple ### Step 1: Identify One Repetitive Task Pick something you do at least weekly that: * Takes 15-60 minutes each time * Follows a somewhat predictable pattern * Doesn't require deep creative judgment ### Step 2: Describe the Job Clearly Write out: * **Input**: What information does this task start with? * **Process**: What steps do you follow? * **Output**: What's the end result? * **Context**: What background knowledge is needed? ### Step 3: Consider If It Should Be Multiple Workers Ask yourself: * Are there distinct phases to this work? * Would different parts benefit from different skills or knowledge? * Do I want to reuse any part of this for other tasks? If yes to any of these, consider splitting it up like Gil did. ### Step 4: Set Up and Test 1. Create your worker(s) in Spinnable 2. Provide the job description as the worker's instructions 3. Add any necessary knowledge (docs, examples, context) 4. Run a test with real data 5. Refine based on what you see ## Common First Worker Ideas Here are proven first workers that deliver quick value: ### Information Aggregation * Monitor multiple data sources and create daily digests * Track mentions of your company/product across platforms * Compile weekly metrics from various tools ### Document Processing * Summarize meeting notes and extract action items * Review contracts or proposals for standard clauses * Generate reports from structured data ### Communication Support * Draft responses to common customer questions * Create social media posts from blog content * Prepare briefing docs before meetings ### Monitoring and Alerts * Watch for specific events or changes * Flag anomalies in data or metrics * Alert when certain conditions are met ## Tips for Success **Start smaller than you think** Your first worker should do less than you imagine. You can always expand later. **Provide examples** Show the worker 2-3 examples of the work done well. This clarifies expectations better than long explanations. **Plan for iteration** Your first version won't be perfect. That's expected. You'll refine as you see it work. **Measure the time saved** Track how long this task used to take you. Seeing those hours add up is motivating. ## Next Steps Learn more about how workers function Give your workers the context they need Connect workers to your tools Learn more about hiring and managing workers ## Questions? The best way to learn is by doing. Start with one simple task, and reach out to our support team if you get stuck. We're here to help!