1. Create an account
Go to any.win and choose Create an AI Employee. Sign in with Google or Microsoft. You get a workspace on the Free plan (3 employees, 150 runs / month). Creating an account means you agree to the Terms, Privacy Policy, and Acceptable Use.
2. Hire an employee
Open Employees → Hire. Start from a proven employee. Describe your own if you already know the job.
Template (fastest)
- Pick a job (Marketing, Sales Research, SEO, Research, Support, Recruiting, or Operations).
- Review the employee (goal, tools, intended KPI targets, schedule).
- Edit name, what they should accomplish, and memory if you want.
- Choose Hire this employee.
Describe the job
Paste what you would tell a new hire. Example:
I own a SaaS product. Create a marketing employee that researches competitors, writes a LinkedIn post and an X post every weekday morning, generates a graphic, and emails me the pack for approval.
Check goal, models, skills, memory, schedule, and approval, then hire. After hire you land on a first-run card: add a model key, connect Gmail if the job drafts email, then Run now. When the run is waiting, approve the pack on that brief. After the first succeeded pack, turn on weekdays from the card (Pro) or upgrade, and optionally make the page public so the homepage can show the pack. Setup is still there for the rest.
Which employee to hire
- Marketing — weekday LinkedIn and X drafts, plus a graphic.
- SEO — a keyword, competing pages, and an article draft. It does not publish.
- Sales research — a company name in, an outreach draft out.
- Recruiting — a shortlist with reasons. It does not email applicants.
- Support — a Tier-1 reply from your knowledge, with an approval before send.
- Research — one question, a sourced briefing.
- Operations — a proposed day from the calendar, after you approve.
Compare them on the template gallery, or read the FAQ if you are choosing between an AI employee and a chatbot.
3. Connect models and tools
On the first-run card, or later in Settings → Keys, add an API key for at least one of OpenAI, Anthropic, Google, or OpenRouter. Use Health check on the Keys page to confirm it works. Keys are stored encrypted and never shown again.
Integrations you may connect: Google (Gmail, Calendar, Drive), Slack (after approval), GitHub, and an optional Stripe key to pull counts into Outcomes (your product account, not Any.win billing). A Research employee often needs only web search and a write model.
4. Teach brand and knowledge
Open the employee → Memory. Edit COMPANY entries (voice, products, words to avoid). Add knowledge: paste a URL or upload a PDF. Delete anything that should not persist. The next run sees this. There is no hidden memory.
5. Run once
Type the job input if the employee needs one (company, ticket, question, or keyword), then click Run now. Marketing and Operations can run with the box empty. Watch the timeline: plan, model, tool, approval. Each step shows tokens, cost, and duration. Images and documents appear as artifacts.
A failed tool or model call retries once. Continue from checkpoint picks up the remaining plan. Replay starts over with the same input.
6. Approve work
Approve from the employee brief when a pack is waiting, or open Approvals / the run. Approve runs that exact payload, then leftover plan steps. Reject stops the run. Nothing is sent. Approvals expire (default 48 hours). You still publish social posts. You decide in Setup which actions require approval.
7. Outcomes and lessons
Set a target (for example 5 approved packs / week). Optional: a deadline, a labor budget (new runs stop when it is spent), and constraints. When a run finishes, review the proposed lesson. Kept lessons become memory. Open Outcomes to log a result, pull Stripe or an HTTPS JSON URL, or download an ROI one-pager of labor you measured — not revenue Any.win invented.
8. Schedule (Pro)
Upgrade in Settings → Billing if you are on Free. After the first succeeded pack, use Turn on weekdays 8:00 AM on the employee brief, or open Setup → Schedule for daily, weekly, or a custom cron. The employee reuses the last job input. Pause the employee to stop the schedule.
9. Share or fork
In Setup → Visibility: Private (Pro+), Unlisted (link only, noindex), or Public (indexable). Visitors can Fork or Run on their keys. Public pages show the latest pack from a succeeded run. Your API keys are never used for their runs. There is no store checkout in V1.
10. Plans
| Need | Plan |
|---|---|
| Try templates and BYO keys | Free |
| Daily schedules, private employees, more runs | Pro · $29 / month |
| API keys, webhooks, higher limits | Builder · $79 / month |
Duplicate copies the employee without credentials or history. Archive removes it from the workforce. Manage billing in Settings → Billing.
11. Builder API (short)
Create a key in Settings → Webhooks & API (Builder only). It is shown once. POST /api/v1/agents/{id}/runs with Authorization: Bearer aw_live_…. Subscribe a webhook and verify X-Anywin-Signature.
If something fails
| What you see | What to do |
|---|---|
| No API key for … | Settings → Keys, add that provider |
| Plan limit reached | Wait for next month or upgrade |
| Labor budget is spent | Outcomes → raise the labor budget |
| Run waiting forever | Open Approvals — leftover steps run after you approve |
| Schedule toggle disabled | Upgrade to Pro |
| LinkedIn would not publish | By design — approve the draft, then you post |