Contact
Describe your project

Our approach

Every project follows the same four steps.

We plan the work with you, then build it and keep it running.

What happens at each step

Not automated: a person decides

  1. Understand

    We interview your people, map how work flows today, read your code and ask a lot of questions.

    • AI agentsGather research, draft maps of how work flows
    • Amalgam engineerChecks every finding
    • Your teamAnswers our questions

    What you keep

    Written notes on how things run today, what limits you and what to leave alone.

  2. Plan

    We name what’s blocking progress and set out two or three options, with what each one assumes.

    • AI agentsCompare options
    • Amalgam engineerLays out two or three options
    • Your teamChooses one

    What you keep

    Ranked options with tradeoffs, a one-page brief and a build plan with milestones.

  3. Build

    We agree on the plan and who does what, then build in sprints or milestones.

    • AI agentsDraft code and tests
    • Amalgam engineerSigns off each change
    • Your teamTests each phase

    What you keep

    Working software or design work you can test at the end of each phase, with documentation for operations.

  4. Run

    We hand over to your team, or stay on through managed services for maintenance, features and support.

    • AI agentsRun checks within agreed limits
    • Amalgam engineerPrepares the release
    • Your teamApproves each release

    What you keep

    Deployment notes, a list of open risks and a clean transition to whoever runs it next.

Who checks the AI agents

How it works
Agents research, draft code and tests, and prepare changes for review, each in a limited role. They read only the sources you choose, with the access the task needs. A named Amalgam engineer approves every change.
In our own product
XESO rules out actions without human approval

Four guardrails on every project

We’ve worked under bank and insurer rules at TIAA, M&T Bank and Brighthouse Financial. Smaller teams get the same four guardrails.

  • Quality controls

    Changes go through code review, tests and continuous integration before they reach your users.

  • Decisions in writing

    We write down each decision as the work happens, with who made it and why.

  • Security and auditability

    We agree on access, permissions and data handling before anything touches your data, and changes leave a record.

  • Cost control

    We agree on the price of every change before we start it.

How we report progress

At the start
We agree on which systems, teams and questions are in scope, and how success is measured.
During build
A week-by-week plan your team can see, with reviews as often as your approval process needs.
Each milestone
A progress check and a demo of the work so far.
End of a phase
Release notes or operating instructions, plus a list of follow-on work for a next phase.
Each quarter
For ongoing work, we update the plan as priorities and budgets change.

See how this would run on your project

Answer a few quick questions and get a short summary of your project in about three minutes.

Describe your project
Contact us
Ryan WardNeeraj Vir

Ryan or Neeraj will reply within one business day.