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.
- A configured AI assistant with your company's skills, templates and house rules loaded, set up for the teams that will use it.
- 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.
- A usage baseline: who has a licence, who uses it and how often.
- A short list of the next opportunities, ranked by time saved and by how hard each is to build.
- 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.
