Level 2, Connect: the assistant is linked to the company's own data and tools.
Forward Deployed AI from QuantSpark

Level 2, Connect

Connects tools, runs adoption

At level 2, Connect, the engineer connects tools and runs adoption. Your people can link the assistant to company files, mail and systems.

Priced on the work

What this engineer does

Connects tools, runs adoption

  • Connects tools and gets more teams using them.
  • Connects the assistant to files and mail, and fixes files shared too widely.

What you get

Link the assistant to company files, mail and systems.

Typical first six-week goal

Agreed with you at kick-off: one measure, a baseline and a target, reviewed in week six.

What you keep, and who backs the engineer

Everything the engineer builds is handed over, and you own the code, prompts and workflows built for you. Senior QuantSpark engineers and senior product managers back the engineer at every level, so what is built is secure and ready for production.

The engineer’s work in full

  • Connects tools and gets more teams using them.
  • Connects the assistant to files and mail, and fixes files shared too widely.
  • Gives the assistant read-only links to finance or sales systems, with a named approver for any change.
  • Reads usage figures and plans how more teams start using AI.

Signs you are at this level

  • The assistant needs to read company files, mail and systems.
  • Adoption has stalled in some teams.
  • People work with the assistant on the company's own files, mail and systems, and help others start.

How clients move up

A typical path starts with one level 1 engineer. After one or two sprints, when the next opportunity on the list is a single-task agent, the retainer moves to level 3. When that agent needs to run in production, a level 4 senior engineer joins to own its quality. Some clients add a level 5 AI operating partner for the board conversation while the level 1 engineer keeps adoption moving.

Related guides

Level 2 questions

How does the assistant connect to company files, mail and systems?

A level 2 engineer connects the assistant to your files and mail, and gives it read-only links to finance or sales systems, with a named approver for any change. Our engineers connect your tools through the Model Context Protocol, the open standard for linking AI to company systems.

Can the assistant see files a person should not see?

Connecting an assistant makes any file shared too widely easier to find. For that reason a level 2 engineer fixes files shared too widely as part of the connection work, and connections start read-only. Any change to a connected system needs a named approver before it is made.

Who approves a change to a connected system?

A named approver signs off any change. The assistant is linked to finance or sales systems read-only first, so it can read the figures it needs without changing them. Naming the approver is part of the connection work, agreed before the link is made.

How do you track adoption at level 2?

A level 2 engineer reads usage figures and plans how more teams start using AI. The work runs in six-week sprints. Each sprint goal is agreed at kick-off, before the sprint starts, with a measure, a baseline and a target, and reviewed in week six of its sprint.