Level 1, Use: people use an AI assistant well.
Forward Deployed AI from QuantSpark

Level 1, Use

Licences, prompts, simple automations

At level 1, Use, a Forward Deployed AI engineer handles licences, prompts and simple automations. Your people learn to write clear prompts, check the output and share what works.

From £10,000 a month plus VAT, full-time

What this engineer does

Licences, prompts, simple automations

  • Works out which assistant licences the business needs and who should hold them, so people work in a configured company account.
  • Writes the prompts and reusable skills that carry your company's own terms and templates.

What you get

Write clear prompts, check the output, share what works.

Typical first six-week goal

The first six-week sprint produces five things: a configured AI assistant with your skills, templates and house rules, simple automations in daily use, a usage baseline, a short list of next opportunities and a handover pack.

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

  • Works out which assistant licences the business needs and who should hold them, so people work in a configured company account.
  • Writes the prompts and reusable skills that carry your company's own terms and templates.
  • Builds small automations on tools you already run.
  • Sits with teams and measures who is using what.

What the first six-week sprint produces

The first six-week sprint produces five things.

  1. A configured AI assistant with your company's skills, templates and house rules loaded, set up for the teams that will use it.
  2. Simple automations in daily use, each with a named owner on your side and a one-page description of what it does and what it must never do.
  3. A usage baseline: who has a licence, who uses it and how often.
  4. A short list of the next opportunities, ranked by time saved and by how hard each is to build.
  5. A handover pack.

An example of a sprint goal: your finance team drafts its monthly management commentary with an assistant instead of from a blank page. It is an illustration, not a client result.

Signs you are at this level

  • People are not yet using the tools every day.
  • Few people use an AI assistant for real work most weeks.
  • A team below level 1 starts with a level 1 engineer.

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 1 questions

What does a level 1 engineer do?

A level 1 engineer sets up licences, writes prompts and builds simple automations. The engineer works out which assistant licences the business needs and who should hold them, writes prompts and reusable skills that carry your own terms and templates, builds small automations on tools you already run, and sits with teams to measure who is using what.

How much does level 1 cost?

A full-time level 1 engineer starts from £10,000 a month plus VAT. The minimum is three months, then the retainer runs monthly with one month's notice. You pay model and tool providers directly on your own accounts. Anything QuantSpark buys for you is passed on at cost, with no mark-up, within a cap agreed in each sprint goal.

Why do bought licences go unused?

A licence gives access, not a habit. No public source measures licences bought against licences used, so we quote no share. Level 1 starts from a usage baseline of who has a licence, who uses it and how often, then configures a company account, writes prompts and skills from your own templates, and sits with teams until use is daily.

How do you measure adoption?

The first sprint produces a usage baseline: who has a licence, who uses it and how often. 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. Progress is read against that baseline and target, not from opinion.

What do we need to provide?

You pay model and tool providers directly on your own accounts, and you name an owner on your side for each automation the engineer builds. The engineer works inside your team, full-time, on a monthly retainer, so the team needs to make room to work with them. Everything built is handed over on the last day.