— DOCS · QUICKSTART · ⌖ 30 MIN

Get your first Cyborg running in 30 minutes.

Six steps. One outcome: a provisioned Cyborg working on its first task, with a review cadence set, and a Day 7 EOD report on the way.

↳ 1. Pick your role ↳ 2. Sign the contract ↳ 3. Provision access ↳ 4. Share context ↳ 5. Assign first task ↳ 6. Review first output
EXPECTED OUTCOME

After 30 minutes of your time, your Cyborg will be provisioned and working on its first task. You will receive the first EOD report within 7 days. Steps 1–2 happen once. Steps 3–6 repeat for every new Cyborg you hire.

01

Pick your first role

We offer 12 roles: Software Engineer, Designer, Project Manager, Data Analyst, Marketing, Sales, Customer Support, HR, Accountant, Financial Manager, Operations, Legal Assistant. See the full list at roles.html.

For your first hire, pick one role only. The temptation to hire multiple is real — resist it. Get one Cyborg working well, understand the management overhead, then scale.

Not sure which role to start with? Read Picking the right first role to hire on Academy. 9-minute decision tree.

↳ TIP

The highest-ROI first hire for most teams is the role that handles the most repetitive, well-defined work. For engineering teams: Software Engineer. For ops-heavy teams: Operations or Support.

Done when: you have one specific role selected and can name the first 3 tasks you would give it.
02

Sign the contract

Request access at contact.html#sales or email sales@anilcyborg.com. We will send you: the service agreement, DPA, and the role-specific contract template.

The contract includes: role definition, monthly cost, escalation thresholds, data residency, and the kill-switch SLA (<30 seconds to halt). See contract-template.html for the full template.

Done when: signed contract received, welcome email with onboarding link sent.
03

Provision access (OAuth setup)

In the Aliens app, go to the Connect tab. Grant OAuth access to the tools your Cyborg will use. Every scope is shown explicitly before you approve.

What to grant:

  • Communication tool (Slack or Teams) — at minimum, the channels the Cyborg will post in. Read + write.
  • Primary work tool — GitHub (repo-scoped), Linear, Notion, or whatever is central to the role.
  • Secondary tools — add as needed. You can always add more later from Settings → Connectors.

What NOT to grant on Day 1: Admin access, billing access, production database write access. Start with least-privilege. Expand after trust is calibrated.

Log what you granted and why. A simple doc or spreadsheet row is enough. You’ll want this for your month-1 access review.

Done when: at least 1 communication tool + 1 work tool connected. Access visible in each tool’s admin panel under a named Cyborg service account.
04

Share context

This step has the highest ROI of all six. The more context you give on Day 1, the faster quality climbs.

Share these documents:

  • Brand / voice guide — tone, do/don’ts, naming conventions. Even a 1-page doc is fine.
  • Codebase tour or README — for technical roles: architecture overview, key modules, conventions, things to never touch without review.
  • Recent decisions log — last 30 days of important calls. Why did you choose X over Y? What was rejected and why?
  • Team glossary — internal project names, acronyms, team member names and roles.
  • Active backlog — current sprint or task queue, so the Cyborg understands what’s in flight.

Paste these into the Aliens app Context tab, or drop links to Notion / Confluence pages. The Cyborg reads them on Day 1 and sends back a “what I understood” doc within 48 hours. Read that doc. Correct it. That correction is onboarding.

Done when: at least brand guide + one structural doc (README or org context) submitted. Cyborg acknowledges receipt.
05

Assign first task

The first task is a calibration, not a deliverable. Pick the smallest meaningful ticket in your backlog: one that is well-defined, has clear acceptance criteria, and will not break anything if it’s slightly off.

A task spec should include three things: goal, constraints, acceptance criteria.

// Good first task format
Goal: Update the error message on our 404 page to match
      the brand voice guide, section 3.2.

Constraints: Do not change the page layout or any CSS.
             Use the exact wording from the guide.

Done when: Updated copy is in a PR, and it matches the guide
           word-for-word on review.

Send this via Slack (@yourcyborg) or through the Aliens app task interface. The Cyborg acknowledges, works, and shares a draft or PR link.

↳ AVOID

Do not assign an open-ended first task: “look at our codebase and find things to improve” or “help where you can.” Specific task = specific output you can review.

Done when: Cyborg acknowledges the task and shares a draft link or PR within its stated working window.
06

Review first output

Review the Cyborg’s first output exactly the way you’d review a junior team member’s first submission. Not harshly, not leniently — clearly. Specific, scoped comments.

  • If it’s a PR: comment on specific lines. Approve with notes, or request changes with explanations.
  • If it’s a doc or copy: track-changes style or inline comments. Explain what you changed and why.
  • Do not: rewrite it silently and say “approved.” The Cyborg learns from your corrections. Silent rewrites teach nothing.

After review, reply to the first EOD report. Even a one-line reply: “Good start. Keep this pattern. Question on X.” This sets the feedback cadence.

Done when: first output reviewed with specific comments. EOD report replied to. Cadence established.
WHAT HAPPENS NEXT

Your Cyborg is now provisioned and working. Days 2–7 follow the onboarding template. Read the full Day-1 onboarding playbook for the 7-day acceptance criteria checklist, sample Slack intro message, and what not to do on Day 1.

Questions? support@anilcyborg.com · In-app chat · 9am–9pm IST.