— CONCEPT · 02 OF 04 · FROM BLANK TO BILLABLE

Day 1 to Day 7. Blank to billable.
No black-box magic.

A fresh Cyborg arrives empty. By the end of seven days it knows your SOPs, your tools, your tone of voice, your project conventions, and the names of your team. We document every step of how that happens — kyunki agar samajh nahi aaya, then you can’t trust it.

D 01KKickoff
D 02IIngest
D 03AAuthorise
D 04SShadow
D 05SSupervised
D 06RReview
D 07LLive
— 02 / DAY-BY-DAY

— SEVEN DAYS, IN DETAIL

What actually happens, day by day.

D·01KICKOFF

Contract signed · VM provisioned · intro call

The Cyborg’s dedicated VM gets provisioned in the agreed region. You and the Cyborg do a 30-min intro call — not a sales call, an actual onboarding kickoff. We collect: who’s the manager, what’s the first task to ship, where do daily reports go.

  • VM cyborg-{role}-{id}-{region} spun up · running within 15 min of contract signing.
  • Manager identified (the human the Cyborg reports to).
  • Slack/Teams channel created — Cyborg is added as a member.
D·02INGEST

The Cyborg reads your business.

You drop documents into the Cyborg’s onboarding folder. Or point us at a SharePoint / Drive / Notion. The Cyborg ingests them into its private memory store on the VM. No data leaves the VM.

  • SOPs, brand guides, codebase, past reports, contracts, project briefs.
  • Conversation samples (so it learns your tone) — optional but recommended.
  • Glossary of internal acronyms (saves a hundred clarification questions later).
D·03AUTHORISE

Tool authorisations · scoped, audited, revocable.

Connect the Cyborg to the tools it needs to do the job. Scoped OAuth flows from your dashboard. We never ask for full-account access where read-only or specific repos/channels work.

  • Engineer Cyborg: GitHub repo-scope, Linear/Jira project-scope, Slack channel-scope.
  • Marketing Cyborg: Drive folder-scope, GA4 property-read-scope, social posting via approval gate.
  • Every grant is logged + revocable in one click from the dashboard.
D·04SHADOW

Watch-only mode · no actions taken.

The Cyborg quietly observes a real workday. Reads PRs as they come in, watches Slack threads, follows ticket triage — but doesn’t act. End of day: it submits notes on what it observed, what it would have done, and what it’s confused about.

  • You read its “day in observation” report.
  • Correct any wrong inferences (“no, that’s not how we triage P2s”).
  • It updates its memory.
D·05SUPERVISED

First real actions — every move requires approval.

The Cyborg starts taking actual actions, but every action is gated by your approval. It proposes a PR; you approve the propose. It drafts a reply; you approve the send. By end of day you should have approved 5–15 actions.

  • Each approval also marks a trust level for that action type (T1 autonomous, T2 review, T3 approval, T4 never alone).
  • Some action types graduate to T1 by end of week. Others stay T3 until you say otherwise.
D·06REVIEW

Manager reviews everything the Cyborg did.

30-min review session with the manager. Walk through every action. Adjust trust levels. Refine memory. Add SOPs the Cyborg should have known but didn’t.

  • The Cyborg’s memory file is amended in your presence (transparent — nothing happens behind your back).
  • Any “don’t do this again” correction becomes a permanent rule.
D·07LIVE

Sign-off — Cyborg goes billable.

You sign off that the Cyborg is ready. Salary clock starts. The Cyborg now operates at its agreed trust levels — some autonomous, some reviewed, some approved. Daily report cadence kicks in.

  • Pro-rata salary applies for the onboarding week.
  • If you’re not satisfied, cancel anytime in the first 7 days — full refund.
— 03 / WHAT GETS INGESTED

— THE FIRST-WEEK READING LIST

Exactly what to feed it — on Day 2.

PROCESS · SOPS

How your team actually does things

Standard operating procedures, runbooks, escalation matrices, change-management playbooks. Real ones — not the wishful-thinking versions in last year’s wiki.

  • SOP docs
  • Runbooks
  • Style guides
  • Decision trees
DOMAIN · KNOWLEDGE

The tribal knowledge, written down

Glossary of acronyms, product wiki, customer segments, top-10 use cases, team org chart, who-owns-what map.

  • Wikis
  • Glossaries
  • Org charts
  • Past projects
CODE · ARTEFACTS

The actual work product

For an Engineer Cyborg: codebase + recent PRs + post-mortems. For a Marketer Cyborg: brand kit + last 6 months of content + analytics. Real outputs — not pitches.

  • Repos
  • PRs
  • Past campaigns
  • Reports
VOICE · TONE

How you actually talk

So the Cyborg sounds like your team, not like ChatGPT. Slack samples, customer email threads, public posts, internal memos.

  • Slack samples
  • Email threads
  • Public posts
  • Memos
— 04 / TOOL AUTHORISATION FLOW

— HOW SCOPES WORK

Every tool grant is scoped, logged, revocable.

No “give us full admin and trust us”. The Cyborg asks for the minimum scope it needs; you decide whether to grant it; you can revoke any time.

01
Cyborg requests a scope.Example: “I need read-write on repo acme/billing for the invoice work.” Stated in plain language + machine-readable scope token.
cyborg
02
You see the request in your dashboard.Diff view: what new permissions; what they unlock; sample API calls; revoke checkbox.
you
03
You approve via OAuth from the source tool.Standard flow: GitHub / Slack / Drive / Salesforce hosts the consent screen; Aliens never touches your password.
you
04
Token stored in the Cyborg’s VM keystore.Encrypted at rest with a per-customer key. Never leaves the VM. Rotated automatically.
aliens
05
Every API call is logged with the scope it used.Streamed to your audit log. Filterable by tool, time, scope, success/failure.
aliens
06
Revoke any time, in one click.From your dashboard or directly in the source tool. Cyborg loses access within 30 sec; affected workflows fail-fast and ping you.
you
— 05 / TRAINING CHECKPOINTS

— WHAT WE TEST BEFORE GO-LIVE

Three things we check before saying it’s ready.

01CHECKPOINT

Domain accuracy — does it know your business?

20-question quiz built from your ingested SOPs. The Cyborg has to answer correctly without re-reading. Misses get re-trained. Threshold: 18/20.

02CHECKPOINT

Tool fluency — does it know the buttons?

Live test in a sandbox repo / channel. Open a PR, comment a thread, run a CI job, file a ticket, close a ticket. End-to-end without breaking anything.

03CHECKPOINT

Voice match — does it sound like you?

Drafts 5 sample messages (PR description, customer reply, internal Slack, a memo, a daily report). You approve at least 4/5 without major edits before go-live.

— 06 / NEXT IN CONCEPT

— THE FOUR-PART CONCEPT WALKTHROUGH

Continue the walkthrough.

01Dedicated machineOne Cyborg, one VM. 02 · CURRENTOnboarding7-day training to your business. 03 · NEXTDaily workA working day in the life. 04ScalingFrom 1 to a full team.