Service 03

AI programming consulting

We help your team build software with AI agents: with the right choice of models, protected data and a way of working that reviews AI code reliably.

AI agents now write a lot of code in a short time. What matters is what happens to that code: who reviews it, which data did the agent see, and how does the result stay maintainable? We advise from our own practice, because we develop with AI agents every day ourselves.

With external services, the agreement counts

Whether a provider uses inputs for training, how long it stores data and in which region depends on the product, the plan and the agreed settings. We check this with you before deployment. Even a locally started program can use an external model, so we always look at the entire data path.

Success criteria before the start

Before a pilot begins, we define how we measure success: correct results, time including review, cost per task and compliance with the data rules. Possible first tasks include searching internal documentation, working on a self-contained module or automating a recurring work step.

Local, external service or combined?

The task and the data you may use decide the choice. We measure quality on your own use case.

  • Local models

    Control over inference

    Suited to sensitive content, offline requirements and specialised tasks.

    Effort: hardware, model operation, updates and quality comparison.

  • External services

    Powerful assistance

    Tools such as Codex or Claude Code for approved development tasks.

    To clarify: data flow, plan, retention, tools and running costs.

  • Combined

    Limits per work step

    Unlock knowledge locally and pass only permitted excerpts to an external service.

    Effort: enforce and monitor the release boundaries technically.

Protecting sensitive data

  • Classify data

    Handle public content, internal information, personal data and secret algorithms separately.

  • Limit the context

    Provide only the files and excerpts needed. Keep keys and credentials out of working copies and logs.

  • Restrict access technically

    Isolated working environment, minimal file permissions and explicitly allowed network targets.

  • Trace data paths

    Include prompts, tool output, logs, embeddings and backups in the protection concept.

A pilot in four steps

  1. Choose a task

    A frequent, clearly scoped task from your everyday development work.

  2. Set the limits

    Agree on permitted data, roles, tools and operating environment.

  3. Run a comparison

    Test the current process and AI variants on the same tasks.

  4. Decide

    Assess benefit, quality, effort and risks together.

Does this fit your task?

Tell us about your use case and your data. We will get back to you personally.

info@masterbrain-bytes.com