Choose your first workflow
Pick a recurring responsibility, write a useful application and define the result you want to measure.
Start with work that happens repeatedly, has accessible inputs and produces an output someone can review. One well-defined responsibility is enough for the Founding 10 application.
Three starting points
These examples describe possible workflows, not promised customer results. Adapt the tools, frequency, volume and boundaries to your company.
| Responsibility | Input | Reviewable output | Starting boundary |
|---|---|---|---|
| Support triage | Support tickets and approved help articles | Draft replies with sources and escalations | Ask first; no automatic sends |
| Prospect research | Your ideal customer profile and approved research sources | A sourced shortlist and outreach drafts | Draft only; no outreach sent |
| Weekly operations report | Task board and approved company documents | Completed work, blockers and decisions with evidence | Read and draft; review before sharing |
A useful brief names the trigger, action, output and exception rule:
Every Friday, review our task board and prepare a weekly operations report. Include completed work, blockers and decisions needing an owner, with source links. If a status cannot be verified, say so. Draft the report for my review before sharing it.
Describe your current process
Tell us who does the work today, which systems they use and where time is spent. You do not need a formal process document. For example:
Our operations lead checks the task board every Friday, asks team members about missing updates and writes a report. Collecting the context takes the most time.
Choose one measure of value
Use a baseline you can compare after 30 days. Good candidates include review hours per week, time to a first draft, corrections per reviewed output or the share of tasks completed with usable evidence.
If you do not have measured data, label the number as an estimate and agree how to measure it during setup. A faster draft is not a success if checking or correcting it takes more time than the old process.
Be specific about access
List the tools needed without sending credentials or confidential customer records. Say whether you are comfortable starting with restricted or read-only access. Provider scopes, employee tool switches and employee permission modes are separate controls; we review them together during setup.
Applying with examples
The application has four sections: your company, the job, tools and boundaries, and setup fit. Example buttons insert an editable answer only when you choose them. Replace sample company details and numbers with your own before submitting. Choosing a workflow starting point replaces that responsibility answer.
Budget, setup availability and concerns help us assess fit. There is no preferred answer to manufacture. Applying does not charge you; selected companies pay $499/month from the first month before onboarding, with personal account and AI employee setup included. There is no free trial. Model and connected-service costs are separate.
Continue with Your first AI employee and Connecting a tool safely.
Getting started
Follow the shortest path from a new Yodu account to a useful first AI employee with company context, model access, tools, tasks, and review.
Your first AI employee
From Founding 10 selection to a useful recurring responsibility, with personal setup included and $499/month paid from the first month.