$499/MONTH · PERSONAL SETUP · 10 COMPANIES

AI employees for the work on your plate.

Investigate support issues, research sales leads, and improve your content with AI employees that use your company’s tools. Assign the job, review the result, and let Yodu handle the recurring work.

$499/month from the first month. Personal account and AI employee setup with Shashank included.

$499/month from day onePersonal setup callYour tools. Your control.
YoduSupportInvestigate
Your business toolsExplore more tools
SlackinLinkedInGoogle Search ConsoleSearch ConsoleGoogle AnalyticsAnalyticsGmailGmailNotionNotionGitHubGitHubStripeStripe
Your companyGoals · instructions · shared files
SupportInvestigate issues
SEO & growthFind opportunities
Sales & GTMPrepare outreach
Review drafts and proposed actions
THE WORK YOU REVIEW
A billing issue investigated. A customer reply drafted.
One company. A connected AI team.Illustrative workflow · not live customer activity

PERSONAL SETUP INCLUDED

Let’s get your first AI employee working.

Choose a job your team needs help with. Shashank will help connect the tools, set up the employee, and review its first result with you.

Sign up · 10 limited seats

$499/month from the first month. Personal setup included.

See your first week

WHAT YOUR AI EMPLOYEES CAN DO

Get help with the work that takes hours.

Investigate a support issue, improve a search page, or research a sales lead. Each example shows the tools an employee uses and the result you review.

THE RESPONSIBILITY

Investigate the issue before writing the reply.

Have a support employee check the customer’s payment, database record, and production logs. It finds the likely cause and prepares a response for you to approve.

Database · read onlyProduction logsStripeStripe

Illustrative examples. Tool access, permissions and approval rules are configured during setup.

Incident evidence

Payment · paid
Access · stale
Webhook · failed

Payment succeeded. Access did not update.

The charge is paid, but the workspace still has its old entitlement. The webhook log points to a failed synchronization.

What the employee checked
  • Stripe: payment succeeded; no duplicate charge.
  • Database: workspace entitlement is still on the previous plan.
  • Production logs: billing webhook failed before access updated.
  1. 1Check the charge and subscription
  2. 2Compare the workspace entitlement
  3. 3Match the webhook failure in logs
Customer reply · ready for approval

Your payment went through, but a billing-sync issue delayed your access. We’ve identified the failure and prepared the next step for our team.

What happens nextApprove the customer reply. Track the access repair as a separate task.

Illustrative work · no live actions

Get help with a job like this

API.market · Inside a working team

How API.market finds its next API sellers with Yodu.

Search data can reveal an API developers need but the marketplace doesn’t offer. See how our AI team investigates those gaps, researches providers, and prepares outreach for review.

Read the API.market case study
API.market× Yodu
  1. Search demand
  2. Catalog gap
  3. Seller research
  4. Outreach & replies
47.8%Taux moyen de réponses positivesSur trois étapes de campagne

AN EXAMPLE OPERATING DAY

Start the day with work ready to review.

Schedule recurring jobs and review their results throughout the day. Here’s what that could look like for your team.

09:00

Check priorities and approvals.

Open the overview for blocked work, approvals and recent results.

11:00

Review a customer reply.

Read the draft, check its sources, and approve it or ask for changes.

15:00

Unblock a task.

Answer a question or restore missing access so the task can continue.

17:00

Check what’s done and what’s next.

Review completed tasks, unresolved questions, and upcoming scheduled jobs.

INSIDE YOUR WORKSPACE

Messages, tasks, files, and approvals in one place.

Give instructions in chat, track progress on the task board, and review drafts with their sources. Open the tabs to see how a support request moves through Yodu.

YoduYour companyInteractive example · fictional tasks and messages

Conversations

Support employee
Y
You

Help this customer invite a teammate. Check our help center before drafting the reply.

Support employee

I’ve created a task and picked up the customer’s question.

Support employee

I found the Members guide. The draft and source are attached to the task.

Support employee

Ready for your review. I’ll wait for approval before sending.

FROM A REQUEST TO A RESULT

From a customer question to a reply you can approve.

See how an employee finds the answer, prepares a reply, and waits for your review.

01

Assign the support request.

Tell the employee which inbox to check, which sources to use, and whether it should draft or send replies.

01 · Brief receivedReview new support questions and prepare replies grounded in the approved help center.
  • Inbox: A customer asks how to invite a teammate.
  • Instructions: Use the help center. Draft a reply; do not send.
  • Expected output: A clear answer with a source.
02

Find the answer in your help center.

The employee checks the documents and tools it can access, attaches the relevant source, and flags any missing information.

02 · Context gatheredFind the relevant help article. Keep the source attached to the proposed answer.
  • Found: “Invite a teammate” in the approved help center.
  • Checked: Instructions describe Settings → Members.
  • Gap: Do not assume the customer’s workspace permissions.
03

Review the proposed reply.

With Ask first selected, check the recipient, message, and source before approving the send.

03 · Awaiting reviewThe draft is ready for review. The controls here demonstrate an approval; they do not send a message.
  • Hi! Open workspace settings and choose Members.
  • Select Invite, enter your teammate’s email and confirm.
  • If you cannot see Members, ask your workspace owner to help.
04

Save the result and schedule the next check.

The task keeps the draft and its sources. After testing the process, schedule the employee to check the inbox regularly.

04 · Result recordedThe task keeps the outcome and evidence. The next run follows the schedule you configure.
  • Saved: The proposed reply and its help-center source.
  • Next decision: Review and send, or request a correction.
  • Repeat: Schedule inbox review once you trust the first run.
SUPPORT / EXAMPLE
01 · Brief received

Assign the support request.

Review new support questions and prepare replies grounded in the approved help center.

The job to be done
  • Inbox: A customer asks how to invite a teammate.
  • Instructions: Use the help center. Draft a reply; do not send.
  • Expected output: A clear answer with a source.
Responsibility assigned

Illustrative workflow · not live customer activity

USE YOUR EXISTING MODEL ACCESS

Power Yodu with your Claude subscription.

Connect a supported Claude subscription and use it to power your AI employees. Yodu adds no extra token charges for work using that connection. Your Claude subscription fees and usage limits still apply; API models and third-party tools may cost extra.

See supported model options
Claude subscription + Yodu

Claude subscription → Yodu employees → work in your tools

  • Connect your supported Claude subscription during setup.
  • Power employees using that connection, within your plan’s limits.
  • No additional Yodu token bill for subscription-routed work.
Subscription availability and limits are verified during setup.

Already use Claude or Codex as your assistant? You can also connect Yodu through MCP to manage supported tasks and settings.

Explore the MCP connection
Workspace-bound accessPermission controlsReviewable work

Built around the tools your company already uses

Gmail, Slack, GitHub, Notion, Stripe, HubSpot, Custom MCP, Google Calendar, Airtable, Shopify, Zendesk, Resend, Mailchimp, PostHog

Explore tools and connections

Availability, account permissions and provider costs vary. We confirm the tools needed for your first workflow during setup.

Set up your team. Assign the work. Review the results.

01

Tell Yodu about your company

Tell your Chief of Staff what your company sells, who your customers are, and what you need help with. Add the documents your team should use.

02

Build your AI team

Choose an employee’s role and explain the job and expected result. You can have up to five active employees, including the Chief of Staff.

03

Connect their tools

Connect supported apps or a custom MCP server. Give each employee access to the tools its job requires.

04

Decide what they can do

Choose Draft only, Ask first, or a defined level of autonomy. Review the permissions before the employee starts using your accounts.

05

Put them to work

Assign a task or set a schedule. Employees can research, prepare drafts, delegate to teammates, and report back.

06

See what needs you

Open completed work, approve proposed actions, and answer questions blocking a task. Adjust the instructions when a result needs improvement.

You choose the access. You set the approval rules.

Connect your accounts, choose which employees can use them, and decide when they must ask permission. We’ll walk through each setting with you.

Explore the setup guides

Connect the right account

Authorize the services your workflow uses. Provider scopes determine what the connection can access.

Choose who gets access

Grant tools to the employees that need them. Review permissions when you add a new responsibility.

Decide how actions happen

Start with Draft only or Ask first. Enable more autonomy deliberately after reviewing the work and its risks.

YOUR TEAM, IN ONE WORKSPACE

Try an example Yodu workspace.

Read the team’s conversations, inspect tool access, and explore scheduled jobs. These sample tasks are inspired by how we use Yodu at API.market.

Yodu.aiExample companyInteractive product tour · sample data
Conversations

Chief of Staff

Guided example

Sample history inspired by API.market’s workflow · scroll to explore

You

Look at search demand for API.market. Where are people finding us but not finding the API they need?

CS
Chief of Staff

I’ll ask SEO Content to inspect search queries and landing pages, then compare the categories against the catalog. I’ll keep content improvements separate from missing-seller opportunities.

Tasks · Create research task

Assigned to SEO Content. Deliverable: query clusters, page CTR, catalog coverage and source references. Status: In progress.

CS
Chief of Staff

The search brief is ready. One example category has relevant search demand but no confirmed catalog match. That is a seller-research lead, not evidence of a conversion problem by itself.

Tasks · Delegate seller discovery

Assigned to Seller Outreach. Attached search-demand-brief.md and catalog-gap-notes.md. Research providers; prepare outreach without sending.

You

Keep the first campaign small. I want to review the provider fit and all five messages before anything goes out.

CS
Chief of Staff

Added that approval boundary to the handoff. Seller Outreach will return a shortlist and five-message sequence. The review task will include the proposed recipients, evidence and copy.

Open attached work

review-checklist.md • Provider has a documented API in the missing category. • Contact source and company match are recorded. • Five personalized messages are attached. • Human approval is required before launch.

Choose a message, then send it

What needs my review?

Sample replies. Changes stay in this demo and reset when you reload.
SET UP DIRECTLY WITH THE FOUNDERShashank Agarwal, founder of Yodu

Shashank Agarwal

Founder of Yodu, API.market & Noveum.ai · Ex-AWS SageMaker launch team

Meet me on LinkedIn
API.marketNoveum.aiEx-AWS SageMaker

“I’ll get on a call and help you set it up.”

I’m Shashank Agarwal, founder of Yodu. I’ll help you choose the first job, connect your tools, and configure your AI employees. We’ll run a task together so you can see how it works.

I also founded API.market and Noveum.ai, and previously worked on the AWS SageMaker launch team. We use Yodu at API.market for seller research, outreach, support investigation, and reporting. That experience shapes how I help you get started.

  • A personal setup call to choose the first job and define a useful result.
  • Hands-on help connecting your tools, model account and employee permissions.
  • A first task we can review together, then a recurring schedule when it is ready.
Sign up · 10 limited seats

We’ll set up the first job with you.

Shashank helps you choose a starting point, connect your tools, and test the first task. The setup pace depends on your workflow and integrations.

01

Define the job

Choose a recurring job, agree on the expected result, and decide which actions need your approval.

02

Connect and test

Connect your model and tools. Run a small task together and check that the output and approval settings work as expected.

03

Review and improve

Review the output and adjust the instructions. When you’re happy with the result, set a schedule for the next run.

Get help with tools, models, and setup.

Step-by-step guides to connecting accounts, choosing model access, setting permissions, and scheduling tasks.

Explore the setup guides

Five AI employees. Personal help getting started.

Get one company workspace with up to five active AI employees, including your Chief of Staff. Tasks, files, schedules, approvals, standard integrations, and personal onboarding are included.

$499/month from the first month. Personal account and AI employee setup with Shashank included.

Your $499 subscription starts with payment for the first month, before onboarding. There is no free trial. Model providers and third-party tools may charge separately.

Yodu does not charge per chat, task, or standard scheduled run. Hosted usage is subject to fair-use safeguards. Your model providers and premium tools have their own fees and limits.

Sign up · 10 limited seats

GET STARTED

Sign up. 10 limited seats.

Fill out the form to get started.

01

Tell us about the job.

Fill out the form with the work you want help with, the tools involved, and the result you need.

02

Book your setup call.

If your workflow is a fit, we’ll email a Calendly link. Pick a time to meet directly with Shashank Agarwal.

03

Set up your team and try Yodu.

On the call, we connect your tools, configure your AI employees and run the first task. Your $499 first-month payment is required before we begin setup.

$499/month, including personal setup.

For the first 10 selected companies. Personal setup is included. Pay $499 for the first month before onboarding. There is no free trial. Model-provider and third-party tool costs are separate. No charge for applying.

Sign up · 10 limited seats

Questions about getting started

When do I pay?

Your selected workspace costs $499/month from the first month, including personal account and AI employee setup with Shashank. Payment is required before onboarding; there is no free trial. Applying does not charge you. Model providers and connected tools may charge separately.

Can I use my Claude subscription?

Yes, with a supported subscription connection. Yodu adds no extra token charge for work using it. You still pay for your Claude subscription and stay within its limits. Paid API models and third-party tools may have separate charges. We’ll check your connection during setup.

How many employees are included?

Up to five active AI employees, including the Chief of Staff. You can replace or archive employees as your needs change.

Does Yodu charge for each task or conversation?

No. Chats, tasks, and standard scheduled runs do not have individual Yodu charges. Fair-use safeguards apply to hosted usage. Your model providers and connected tools may have their own usage fees and limits.

Can employees send emails or change data?

Yes, when the connected tools and permissions allow it. You can choose Draft only or Ask first to keep external actions under review. We help you test those settings before running the workflow.

Can I connect our own tools?

You can connect supported business apps and custom MCP servers. List the tools you need in the form, and we’ll check whether the workflow is a fit before setup.

Do I need technical knowledge?

We’ll help you with setup. Plan for a 60–90 minute call and ask someone on your team to spend 10–15 minutes a day reviewing results during the first week.

Can I use Slack?

Yes, where a Slack connection is configured. During setup, we check the Slack app, channel access, and whether the employee can receive work and post updates.

What happens after I apply?

We review your workflow and tools. If there’s a fit, we email a Calendly link so you can book a setup call with Shashank Agarwal.

Can I use Claude or Codex to control Yodu?

Connect Yodu’s Platform MCP to Claude or Codex to inspect employees, create tasks and manage supported workspace settings. There is no extra Yodu fee for this connection. Your assistant subscription and model usage remain separate. Billing and approval decisions stay in Yodu.

Is Yodu built on OpenClaw?

Yes. OpenClaw runs the agents. Yodu provides the company workspace, employee management, tool permissions, approvals, and managed infrastructure. Each workspace’s runtime runs in a separate Docker container on shared infrastructure.

Sign up. 10 limited seats.

Tell us which job you want help with. We’ll review your workflow and invite selected teams to a setup call.

Sign up · 10 limited seats