babaVC we help you turn tokens into revenue

AI Transformation · babaVC

Hire an AI team that works 24/7. Watch the work compound.

We design an AI team around how your business works, build it into your tools and lead it until it runs. Bring David in as your Fractional Chief AI Officer, or run it as a fixed-scope Transformation project.

Why now

AI is already in your company. Give your team a platform.

Today each person prompts on their own and starts from zero, so what one of them learns stays with them. On a platform the work, the context and the skills are shared, so each run can build on the last. In McKinsey's State of AI 2026, 80% say AI improved their productivity, but only 37% of organisations report any EBIT contribution.

Time back.

Tickets, reviews, drafts and checklist runs leave your builders' desks.

Spend you can see.

One view of agent spend, under a cap you set.

Around the clock.

The work keeps moving overnight. Anything you gate waits for your people in the morning.

Under control.

Nothing you gate ships without a person.

Start where the work already repeats.

An AI team takes on the repeat work in five lanes, from the first support reply to the weekly report.

Slack · #support

Customer can't log in after a password reset. Same thing as yesterday.

Support

Drafted a reply with the reset steps for their plan and a link to the help page. This matches yesterday's ticket, so I opened a bug for Builder with the steps to reproduce. The reply is waiting for your OK.

Waiting for review · Support lead

What the industry sees

  • 85% of customer service leaders are expanding human agents' responsibilities as AI takes on contact volume; just 31% are planning frontline layoffs.

    Gartner, Apr 2026
  • 87% of customers say a company using GenAI for service must still give them access to a human.

    Gartner, Aug 2026

What the agent team does

  • Triages new tickets from Slack, Teams, email and more, and routes them with the customer's history
  • Drafts replies from your help docs and past answers
  • Spots repeat issues and opens a bug for the build team
  • Proposes help page updates when the same question keeps coming in

Three steps to a team that works.

Either way it starts the same: context first, agents on real work from week two. After that, David keeps driving it as your Fractional Chief AI Officer, or your team raises tickets and we support it.

  1. Weeks 1–2

    Context sprint

    We map how work gets done across your tools and write it down, so the agents know your company before they start.

    • Interviews with the people on your team
    • Your company's context, written down for agents to work from
    • The workflows that could give the most time back, ranked
    • A fixed-scope quote for the build
  2. From week 2

    Build & iterate

    The first agents work on real tasks from week two, and we test, evaluate and tune them weekly against your work until they're reliable.

    • Agents connected to your tools (Slack, Teams, GitHub, Linear, Jira, Google Workspace, Notion and more)
    • Weekly evaluation on real work
    • Review gates on what your team chooses to approve
    • Budgets and spend caps on your own provider keys
    • A walkthrough for your team on approving and sending work back
  3. Ongoing

    Drive or support

    As your Fractional Chief AI Officer, David keeps driving the team, the roadmap and the rollout across the company. On a fixed-scope project, your team raises a ticket when something needs to change and we fix, tune or extend.

    • Support: fixes, tuning and new agents when you want more
    • Support: you decide what access we get, ticket by ticket
    • Fractional CAIO: David in your leadership meetings, owning AI across teams
    • Fractional CAIO: the roadmap, the hard calls and a clean handoff when you hire

Platform

Built on Paperclip, the open-source platform for AI teams.

Paperclip runs agents the way a company runs people: each one has a role in an org chart and a budget of its own, your company configures the approval gates, and runs are written to an audit log. It works with the agents you already use, Claude Code, Codex, Cursor and more, and it's open source under the MIT licence.

We set it up in your own environment, connect your stack, build the team and support it.

GitHub stars since March 2026
103k
forks
17.2k
contributors
234
commits in the last 30 days, with weekly releases
874
npm downloads a month
191.5k
Discord members
7.7k

GitHub and npm as of . Discord as of .

What the industry is saying

“Those 75,000 employees will be working with 7.5 million agents.”

Jensen HuangCEO, NvidiaGTC 2026, as reported by Fortune, 19 Mar 2026 ↗

“If those systems are fragmented, the agents will scale the fragmentation.”

Dan GottliebVP Analyst, GartnerGartner, Jul 2026 ↗

“The real advantage comes from combining AI efficiency with human judgment, empathy and experience.”

Eric KellerGartnerGartner, Apr 2026 ↗

Approval gates you set.

Humans approve whatever you choose to gate: outbound email, merges, publishing. Change the list whenever you want.

Your bill.

Model usage is billed by the provider straight to your account. Spend caps and stop switches live in the org.

Your stack.

Slack, Teams, GitHub, Linear, Jira, Google Workspace, Notion and more, plus the harness your builders already use.

Your data.

Your data stays in your own environment, and the agents run on AI provider keys you hold.

Who you're working with.

babaVC · 2026 Series
David Babayan
Founder, babaVC
12 yrs Leadership
15 yrs Engineering
10 yrs Product
3 yrs AI strategy
About
David Babayan

Fifteen years in tech, building products and scaling organizations. Jack of all trades: tech, product, business.

Co-founded EasySize (AI for fashion sizing, from scratch to PMF and profitability over eight years). Most recently ran tech, product and strategy at Cludo (site search product, company-wide AI rollout, the best-selling quarter in the company's history).

Click or tap to flip

You work with David Babayan: fifteen years building products and scaling organisations, EasySize co-founder, most recently tech, product and strategy at Cludo.

Good fit

  • Agencies, SaaS companies and studios growing faster than they can hire
  • Repeat work in support, growth, QA, prototyping or automations
  • Ready to connect agents to your real tools and data
  • Someone who can give feedback a few hours a week in the first month

Not a fit

  • Wants a chatbot, not a team
  • No repeat work: every job is a one-off
  • Needs months of procurement before a first pilot

Straight answers.

What if an agent gets something wrong?

Anything you gate waits for a human, who can approve it or send it back with a note. The agent redoes the work from that note. If the same mistake keeps coming back, raise a ticket and we tune the agent.

Which tools do you connect to?

Slack, Teams, GitHub, Linear, Jira, Google Workspace, Notion and more. If a tool has an API or an MCP server, it's likely in. If you use something unusual, we'll check it on the call.

Do we need new software?

Just Paperclip, and we set it up for you in your own environment. Your people stay in the tools they already use, and the agents work there too.

Who decides what needs human approval?

You do, per agent and per action. During the build we recommend gates, such as outbound email, merges and publishing, and you set them. You can add or remove a gate at any time.

How long until the first agent is working?

The first agents work on real tasks from week two, and the build-and-iterate phase runs to about week six. You see their output on your own work while the build goes on.

What does it cost?

A Transformation project gets a fixed-scope quote at the end of the context sprint, once we know which work the team will take on. A Fractional Chief AI Officer engagement is a monthly retainer, agreed on the call. Model usage is billed straight to your own provider account. You set a spend cap per agent, and work pauses at the cap until someone raises it.

What if we already pay for Copilot or ChatGPT?

Keep them. Those are assistants one person drives, one chat at a time. The AI team adds shared context, roles and gates on top, so work is picked up from your tools, handed between agents and checked. Your builders keep Cursor, Claude Code, Codex and more inside it.

What happens after the build? Do you keep access?

No standing access unless you want it. The team runs in your own environment on your keys, so it doesn't depend on us. Support runs on tickets you raise, and you decide what access we get for each one.

Is Paperclip safe to run?

We set it up in your own environment, with your access controls. Runs are logged and the code is open source, so your team can read it.

Can we stop?

Yes. The team lives in your own environment, so you keep the agents and their setup whether or not you raise another ticket with us.

Find the first job to hand over.

  • You walk us through where the repeat work piles up.
  • We name the first workflow we'd give an agent, and what the sprint would cover.
  • You leave with a clear next step, or a clear no.
Book a 30-minute call →