The process
We map the role
Before Jobr builds anything, the team learns exactly how the work happens inside your business today. That means understanding your process end to end, the tone and voice your business uses, the policies and rules the employee needs to follow, and the edge cases that come up in real situations.This mapping stage is what makes the difference between a generic tool and an AI employee that actually fits your operation. Everything built in the next stage is grounded in what Jobr learns here.Typical timeline: Week 1
We build your AI employee
With the role mapped, Jobr builds your AI employee from the ground up — custom to your business, trained on your processes, and configured with the guardrails you’ve approved. This is not a template being filled in; it’s a purpose-built worker designed around how your business actually runs.You’ll have a chance to review and refine before anything goes live. The guardrails you set at this stage — what the employee can and can’t do, when it escalates to a human, what it reports — are yours to control.Typical timeline: Weeks 2–3
We deploy and go live
Jobr deploys the AI employee and connects it to the relevant systems and channels. From this point, it’s handling real work — responding to customers, processing documents, following up on payments, or whatever role it was built for.Your team doesn’t manage the deployment or monitor the infrastructure. That’s Jobr’s job. You simply stop doing the work the AI employee is now handling.Typical timeline: Week 4
Ongoing management
Going live is not the end of Jobr’s involvement — it’s the beginning of the ongoing relationship. Jobr keeps the AI employee running, monitors its performance, and handles any tuning it needs as your business evolves.You receive daily reports summarising what the employee handled, what it escalated, and how it performed. If your processes change or you need to update a rule, you can adjust the guardrails at any time.Timeline: Continuous, from Week 4 onwards
Timeline at a glance
| Week | What happens |
|---|---|
| Week 1 | Role mapping — Jobr learns your process, tone, rules, and edge cases |
| Weeks 2–3 | Build — your AI employee is custom-built and refined with your input |
| Week 4 | Deployment — the AI employee goes live and starts handling real work |
| Week 4+ | Ongoing management — Jobr runs it, you receive daily reports |
What you need to provide
Jobr handles the build and the running. Your job is to share the knowledge Jobr needs to build an employee that actually fits your business. Plan to provide:- Process documentation. How the work is currently done — whether that’s a written SOP, a recorded walkthrough, or simply a conversation with your team.
- Tone and voice guidance. How your business communicates with customers, leads, or vendors — including any language you always use or always avoid.
- Escalation rules. What situations should be handed off to a human, and who should receive them.
- Access to relevant systems. Depending on the role, this may include your inbox, CRM, invoicing platform, or scheduling tool.
Your AI employee always works within the boundaries you set. It escalates anything outside those boundaries to a human on your team — so you stay in control of the decisions that matter.

