Skip to content

The system installed in your repository, under version control

INSTALLATION · FIXED SCOPE

We turn one repository into an AI-Native operation. Context, rules, patterns, decisions and agents land as pull requests and go through your team’s review. It is not a report: it is code.

updated

AI-Native Repository Foundation

from US$ 19,000
per repository or product · ongoing execution quoted separately
4 to 8 weeks
estimated timeline
who it is for
Teams that already know where it hurts and want the system installed in one product before scaling to the rest.

AI reads your company’s architecture before it generates code. Knowledge that lived with two or three people now lives in the repository, readable by humans and by agents.

What is included

  • repository analysis
  • context structuring
  • architecture documentation
  • rule authoring
  • agents with a defined scope
  • skills configuration
  • pattern rollout
  • workflow definition
  • integration with the AI tools your team already uses
  • initial team training

Deliverables

  • versioned core system context
  • architecture rules and reusable patterns
  • agents with scope, limits and quality criteria
  • AI development workflows
  • recorded technical decisions
  • agent-readable runbooks and guides

What you get in your repository

  • ARCHITECTURE.md

    Core system context

    Domains, boundaries, glossary and owners: the file that explains the whole system to any agent.

  • .rules/ · patterns/

    Versioned rules and patterns

    The architecture contract AI reads before generating code, and the patterns it has to reuse.

  • agents/ · workflows/

    Agents with a defined scope

    PR reviewer, test generator and bug analysis running inside the pipeline, with a merge gate.

  • decisions/ · runbooks/

    Knowledge that does not live in people

    ADRs and routines under version control, readable by humans and agents. No more single points of failure.

Timeline

  1. WEEK 1Kickoff and repository analysisgoals · scope · responsibility matrix · reading the code and its history
  2. WEEKS 2-3Context and architecture documentationdomains · boundaries · glossary · recorded technical decisions
  3. WEEKS 3-5Rules, patterns and agentsversioned architecture contract · skills · agents with scope and limits
  4. WEEKS 5-7Workflows and integrationPR review · test generation · integration with the AI tools you already use
  5. FINAL WEEKEnablement and handoveryour team takes over · quality criteria · how to evolve the system
  6. AFTEREvolutionnew repositories, new agents and follow-up: Transformation or Advisory

Every artifact lands as a pull request and goes through your team’s review. Nothing runs on AIUBY servers, and nothing is delivered in a format you cannot version.

What is not included

It is written here so it does not become a conversation after you sign. Anything left out that you need is quoted separately, with its own scope.

  • AI tool licenses
  • building features for your product
  • ongoing operation after delivery

Frequently asked questions

Does this replace Copilot or Cursor?
No. It makes them pay off. The tool stays the same; what changes is the repository it reads and the pipeline it works in.
Why does it take anywhere from 4 to 8 weeks?
The timeline depends on the size of the repository, the number of domains and how much knowledge lives outside the code. A documented monolith lands close to 4; a codebase with many services and scattered documentation lands close to 8. Scope and timeline are locked at kickoff.
How much of my team’s time does it take?
About 6 hours a week between the CTO and two tech leads while we structure the context. After that, the cost is reviewing pull requests.
What if my team pushes back?
Pushback usually comes from rules imposed without context. We build the artifacts with your leads, starting from the patterns they already use: the system formalizes what the team already does well and fixes the rest.
Will one repository fix my whole company?
It fixes one product. If the problem is consistency across teams and systems, Foundation works as the pilot and Transformation is the expansion. Starting with one product is deliberate: it produces evidence before you commit a bigger budget.

About the price

Prices are entry points in US dollars and exclude applicable taxes. The final price depends on the number of repositories, teams, architectural complexity, integrations, security requirements and training volume. Customers in Brazil are billed in BRL.

The next step

After the Foundation, the natural next step is AI Engineering Transformation, for organizations with many teams and repositories, where the bottleneck is structural, not local.

The full path is on the services page.

The first conversation is technical and takes 30 minutes.

No sales pitch: we talk about your repository and your bottleneck.