— CONCEPT · 04 OF 04 · ADDING THE NEXT CYBORG

From one to a team.
And the rare case where you shouldn’t.

Most customers start with one Cyborg. Almost everyone who’s happy after 60 days hires a second. Scaling honestly means we tell you when not to add the next one. The decision tree is on this page — not buried in a sales call.

— 02 / SCALE LADDER

— FOUR REAL TEAM SHAPES

Where most customers end up.

A typical curve: solo founder hires one Cyborg, sees value, adds a second around month 2, settles into a 3–4-Cyborg shape by month 4. Above 10, you’re structurally a different kind of customer.

1 START

One Cyborg, one role.

The pilot. Pick the role that hurts most. Engineer for solo technical founders; Customer Support for SaaS PMFs; Accountant for self-funded SMBs.

90% start here
3 SHAPE

Three Cyborgs, core trio.

Engineer + Designer + Support. Or Marketing + Sales + Support. The minimum viable digital department for a one-founder company.

10% disc.
10+ SCALE

Ten Cyborgs, multiple departments.

Two engineers, two support, plus marketing-trio, plus operations. You’re running a small company with one human at the top.

10% disc. + tools
50+ ENTERPRISE

Fifty Cyborgs, org level.

You’re a real enterprise customer. We deploy on your cloud, assign a dedicated CSM, and treat you like a partner — not a self-serve account.

custom pricing
— 03 / SCALE SIGNALS

— HOW TO TELL IT’S TIME

When to add the next one — and when not to.

Yeh page sales pitch nahi hai. We’d rather you keep one Cyborg for 6 months than add a second that struggles. Here’s the honest test.

Add the next Cyborg if…

  • Your current Cyborg is over-utilised. Daily reports show queue backlog growing for 2+ consecutive weeks.
  • You’ve crossed a function boundary. The Engineer is being asked to write marketing copy — that’s a Marketer job, not a stretch goal.
  • Trust levels have stabilised. Most action types graduated to T1 / T2. Adding a second won’t double your management overhead.
  • The pilot Cyborg saved measurable hours. You can point to the daily report and say “these specific tasks now take zero of my time.”
  • You hit a process bottleneck a Cyborg can solve. Tickets piling up, social posts behind, books unreconciled, inventory unaudited.

Hold off if…

  • The first Cyborg is still in supervised mode. Most actions are T3. Doubling means doubling your approval queue — not freeing your time.
  • Your SOPs aren’t written down yet. The first Cyborg taught you which SOPs were missing. Fix that before hiring the second one to repeat the fight.
  • You’re scaling out of fear, not capacity. “Let me hire a Sales Cyborg in case investors ask” — bad reason. Customers always know.
  • The first Cyborg’s reports are unread. You don’t need a second; you need to start reading the first one’s daily summary.
  • You’re trying to replace a human you should keep. Re-read manifesto declaration #07.
— 04 / CROSS-CYBORG COORDINATION

— HOW TWO+ CYBORGS WORK TOGETHER

They talk — like real teammates.

Each Cyborg lives on its own VM, but they share a project channel and a shared task graph. Handoffs happen explicitly, with a written brief.

— SAMPLE HANDOFF: A FEATURE FROM IDEA TO PRODUCTION

Marketing → Designer → Engineer

Marketing Cyborgwrites brief + acceptance criteria
→
Designer Cyborgspec · figma · review
→
Engineer Cyborgbuilds, tests, ships PR
Handoff protocol · Each handoff is a written message in the shared project channel with: (1) a 1-line ask, (2) acceptance criteria as bullets, (3) link to source artefacts, (4) the @next-cyborg explicitly tagged. The receiving Cyborg either accepts or asks clarifying questions before starting. No telephone-game. No assumptions. Audit trail intact.
— 05 / SHAPE

— SPECIALISATION VS GENERALISATION

When to add a narrower Cyborg — and when to add a broader one.

[ AXIS · DEPTH ]

Add a specialist when…

The work has a clear boundary that a senior human would specialise into.

  • Volume is enough to keep one Cyborg busy on that domain alone.
  • The domain has its own stack · tools · vocabulary (e.g. financial reporting vs general bookkeeping).
  • Mistakes in this domain are expensive enough to warrant a focused operator.
  • You’d hire a senior human for this if Cyborgs didn’t exist.
[ AXIS · BREADTH ]

Add a generalist when…

The work is a thin layer across many areas — coordination, ops, “keep things moving”.

  • Tasks span 4–8 different tools / functions in a typical week.
  • The actual work is judgement + sequencing more than depth in any one tool.
  • The team needs a “chief of staff” presence rather than a domain expert.
  • A single project / ops manager would cover the same ground if hired human.
— 06 / VOLUME PRICING

— WHAT SCALING DOES TO YOUR BILL

More Cyborgs of the same role · cheaper per Cyborg.

No surprise — same as how human teams work. Volume comes with discount. Same role, same VM template, less per-instance overhead.

Tier 01 0% 1 of any role standard salary
Tier 02 0% 2–9 of any role standard salary each
Tier 03 −10% 10–49 of same role discount per Cyborg in that role
Tier 04 custom 50+ of same role enterprise pricing

FULL PRICING ON /PRICING · ROI CALCULATOR INCLUDED · NO HIDDEN TIERS

— 07 / END OF CONCEPT WALKTHROUGH

— YOU’RE AT THE END

Concept walkthrough complete.

If you’ve read all four pages, you understand exactly how A’nil Cyborg works mechanically. Next stops: see the actual roles, or talk to A’nil directly.

01 · DONEDedicated machineOne Cyborg, one VM. 02 · DONEOnboarding7-day training to your business. 03 · DONEDaily workA working day in the life. 04 · CURRENTScalingFrom 1 to a full team.

— READY?

Browse all 12 roles — or talk to A’nil directly.

See all roles Talk to A’nil