> ## Documentation Index
> Fetch the complete documentation index at: https://guides.runner.now/llms.txt
> Use this file to discover all available pages before exploring further.
# Runner for professional services
> Build a fleet of AI employees for proposal follow-up, client onboarding, and delivery.
A \$25,000 proposal goes out Tuesday. Friday arrives. Everyone assumes someone followed up.
Nobody did.
That's the kind of job an AI employee should own. Not writing another generic email on command. Checking the real pipeline every morning, finding the proposal that went quiet, reading the thread, and preparing the right next step.
For agencies, consultancies, studios, and development shops, the first AI employees should sit close to revenue or client delivery.
Writes follow your [tool permissions](/connections/tool-permissions). Keep email sending on **Ask** while you test. Runner stages each send as an **Action Card** for review. **Allow** sends without asking. **Off** blocks the tool unless the Runner has its own override.
## Recurring jobs for professional services
| AI employee | What they own | Why the job matters | You stay focused on |
| ---------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------- | ---------------------------------------- |
| **Proposal follow-up** | Checks CRM and email for proposals waiting on a reply, then prepares the next message | Keeps good work from going quiet | The relationship and the close |
| **New lead response** | Finds untouched inquiries, reads the account context, and prepares the first response | Shortens the gap between interest and action | Qualification and the conversation |
| **Client onboarding** | Turns a signed deal into a welcome draft, checklist, and missing-input list | Gets delivery moving without another manual chase | Expectations and the client relationship |
| **Delivery risk** | Finds blocked work, missing approvals, and promises without an owner | Protects margin and client trust | Tradeoffs and hard conversations |
| **Account review** | Surfaces wins, risks, renewals, and the next useful conversation | Protects renewals and follow-on work | The relationship and judgment |
Each Runner works independently. Runners can read the same source apps, but they don't pass work or results to one another automatically.
You don't need all five AI employees. Add the one with the clearest number attached.
## Start with: proposal follow-up
This works because the state already lives in Gmail and your CRM. Every run can see who replied, what was promised, and whether the opportunity is still open.
```text theme={null}
Create a Runner named Proposal Follow-up.
Every weekday at 8:00am in my timezone, review open proposals in
[HubSpot or Salesforce] and the matching Gmail threads.
Include proposals that:
- were sent 3 to 14 business days ago
- have no client reply after the proposal was sent
- are not marked won, lost, paused, or do not contact
- no unresolved follow-up Action Card is already present for the proposal
Read the proposal in Google Drive and the full email thread before writing.
For each proposal, prepare a short follow-up with one specific next step.
Don't invent urgency, discounts, or facts that aren't in the source material.
Don't follow up with the same person more than once every 5 business days.
Stage each send as an Action Card. Then return a short report with the client,
proposal value shown in the CRM or "not recorded," days waiting, last contact,
and proposed next step. If nobody needs a follow-up, say that clearly and stop.
Before you create it, show me the final name, prompt, schedule, and timezone.
Wait for my confirmation.
```
**A user-created Runner becomes active as soon as it's created.** Open it, review the saved prompt and schedule, then click **Run now** for the first test.
Turn on **Carry unresolved Action Cards into new runs** so a still-pending follow-up can appear in the next run. A pending card still expires 24 hours after it was staged.
## Save the job rules
Use a Project for background such as your offer, audience, account owners, and source locations.
Put these in the Runner's saved prompt:
* The voice to use with prospects.
* Deal stages and exclusion rules.
* The minimum gap between follow-ups.
* What needs a partner or account owner to review.
Keep the live state in Gmail and the CRM. That's what tells tomorrow's run whether the client replied. The previous run's output doesn't carry forward automatically.
Start sends on **Ask**. Read the first ten Action Cards. Fix the saved prompt when you see the same mistake twice. Move a send tool to **Allow** only when you're comfortable letting that exact action happen without review.
## Other jobs to schedule
### New lead response
Run at the start and end of each workday. Find new inquiries with no owner or first reply, read the account context from connected sources, and stage a response. Stop when the CRM or email thread shows someone already handled it.
### Client onboarding
Run each weekday morning. Find newly won work, then prepare the welcome email, kickoff checklist, and list of missing inputs. Keep contract, payment, and scope decisions with a person.
### Delivery risk
Run before the team starts work. Find deliverables due in the next seven days, blocked tasks, and client questions waiting more than two business days. Draft the nudge and name the owner.
### Weekly account review
Run Friday afternoon. Pull what shipped, what slipped, open client questions, and the next milestone into a clean account summary. No green status based on vibes. Use the work and messages that actually exist.
## The point isn't more activity
A proposal follow-up Runner isn't valuable because it writes five emails. Measure how often a proposal waits ten days without a next step.
Fix that gap, then build the next Runner.
***
## What's next?
Save the job, schedule, sources, and review rules.
Go deeper on lead response, pipeline gaps, and next steps.
Decide which actions wait for review.