How We Engage

Three Ways to Work With Us

Every engagement starts with a written scope. Pick the model that fits how your team plans and pays for work.

Embedded Team

Our engineers join your planning, work in your repositories, and ship against your roadmap.

Best for: Teams with a clear roadmap and more work than headcount.

  • Joins your sprint planning and code review
  • Works in your tools, repositories, and channels
  • Scales up or down between sprints

Billed per sprint.

Fixed-Scope Build

One defined system, a written specification, and a price agreed before work begins.

Best for: A single system with clear boundaries and a target date.

  • Discovery produces a specification you approve
  • Milestones with a working demo at each one
  • Handoff with documentation and a walkthrough

Fixed price, agreed in writing before the build starts.

Support Retainer

Ongoing ownership of a production AI system, whether we built it or inherited it.

Best for: Systems in production that need monitoring, fixes, and steady improvement.

  • Monitoring of quality, cost, and uptime
  • A monthly block of engineering time for fixes and improvements
  • A written report on what changed and why

Billed monthly.

Included

Included in Every Engagement

These commitments hold whichever model you choose.

You Own the Code

Everything we write lives in your repositories, under your accounts, from the first commit.

Measured, Not Assumed

Each system ships with an evaluation set and the numbers that show it works.

Observable in Production

Tracing, logging, and cost reporting are part of the build, not an afterthought.

Documented for Handoff

Architecture notes, runbooks, and a walkthrough with the engineers who take it over.

Questions

Engagement Questions

Every engagement starts with discovery and a written scope. From there we work as an embedded team billed per sprint, as a fixed-scope build at a price agreed in advance, or on a monthly support retainer.

Compare engagement models

Pricing depends on scope, team size, and timeline. We agree on it in writing before any build work begins.

You do. Everything we write lives in your repositories under your accounts, and the handoff includes documentation and a walkthrough.

Discovery starts as soon as we schedule the first scoping conversation. Build work starts once you approve the written scope.

Not Sure Which Model Fits?

Tell us about the work. We will recommend a model and explain why.

Or email quinten@aeonintelligence.net