Software development · Chesterbrook, PA · Since 2012Software development · Since 2012

Senior engineers scope, build and run software.

They learn your business through calls, workflow maps and your code. AI agents speed up the build, and an engineer approves every change.

About three minutes, no email needed.

Discovery, before any build

  1. 01A few project questionsQuestionnaire
  2. 02Calls with your teamCalls
  3. 03How work moves todayWorkflow map
  4. 04Your code and dataRead access
  5. Written notes on how things runEngineer checked
  • Neeraj Vir
  • Ryan Ward
  • Parul
  • Jub
  • Lisa
Our senior engineers lead discovery

Teams we’ve worked with

How we work

Four steps, from the first call to running software.

Read our approach

01 Discover

An engineer checks every finding

We learn how your business runs before anything gets drawn.

Why it matters

  • Disagreements show up on a map, where they’re cheap to settle
  • You see where work stalls between people and tools
  • We learn what to fix and what to leave alone

What we do

  • A short questionnaire before the first call
  • Calls with the people who do the work
  • A map of how one job moves today
  • A read of your code, data and documents

Where AI helps

  • Agents gather research and draft the first maps
  • They read only the sources you approve
  • An engineer checks every finding with your team
  • Questionnaire
  • Calls
  • Workflow maps

You keepWritten notes on how things run today

02 Plan

You choose the option

We lay out two or three options and agree the plan with you.

Why it matters

  • You see the trade-offs before you pay for a build
  • Scope and price are agreed before work starts
  • Milestones give you dates you can hold us to

What we do

  • Options mapped with you on shared Miro boards
  • Two or three options, with what each assumes
  • A one-page brief and a milestone plan
  • One shared Google Drive for briefs, notes and decisions

Where AI helps

  • Agents compare options and surface edge cases early
  • Agents draft prototype variations for you to compare
  • Choosing the option stays with you
  • Miro
  • Google Drive
  • Brief

You keepRanked options, a brief and a milestone plan

03 Build

An engineer signs off each change

We design and build in phases, with a working demo at each one.

Why it matters

  • You test working software at every phase
  • Problems show up early, in a demo
  • Each decision is written down as the work happens

What we do

  • User journeys and wireframes before code
  • A design system that keeps every screen consistent
  • Builds in sprints or milestones you agreed
  • Code review, tests and CI on every change

Where AI helps

  • Agents draft code and tests in a limited role
  • Automated security checks run on every change
  • A named engineer signs off each change
  • User journeys
  • Wireframes
  • Design system

You keepWorking software and its documentation

04 Run

You approve each release

We hand over cleanly, or stay on to run and improve it.

Why it matters

  • Real users and real load test it every day
  • A clean handoff means you’re never locked in
  • Small issues get caught before they grow

What we do

  • Deployment notes and a list of open risks
  • Handover to your team, or managed services
  • Maintenance, security updates and new features
  • A plan review each quarter

Where AI helps

  • Agents run checks within limits you agree
  • Anything outside those limits goes to a person
  • Your team approves each release
  • Release notes
  • Managed services
  • Quarterly review

You keepDeployment notes and a clean handoff

Case studies

All case studies

What clients say

  • CleanItSupply

    We’ve worked with many consulting firms, but finding one that delivers strong results and genuinely cares about our success is rare. The Amalgam team was responsive and easy to work with.

    Mike MooneyChief Technology Officer
    Read the CleanItSupply case study
  • John Templeton Foundation

    Amalgam has developed business applications for the John Templeton Foundation that enable us to better understand and communicate the impact of the academic research grants we have funded.

    Steve FitzmierDirector, Planning and Evaluation
    Read the John Templeton Foundation case study

Packages

Three ways to work with us

Smaller teams get the same guardrails we use under bank and insurer rules.

Compare packages
  • 2 to 4 weeks

    Maestro

    Product scope and build plan

    Founders and early teams with an idea, pitch or prototype.

    More about Maestro
  • 6+ weeks

    Most used

    Forge

    Your MVP, built and launched

    Teams ready to build a first version, or rebuild a prototype that isn’t working.

    More about Forge
  • 12+ weeks

    Dynamo

    Modernization and ongoing support

    Companies whose software needs fixing and upgrading.

    More about Dynamo

XESO · A product by Amalgam

Answers from your own documents

Ask in plain language. XESO answers from the documents you choose and cites the passage behind each answer. It does not use your content to train AI models.

Knowledge In use today

XESO Knowledge answering “What did we agree on annual discounts?” The answer cites its sources, and each source card quotes the passage it used.
XESO Knowledge · design shown with sample data

Let’s talk about what you’re building

Answer a few quick questions and get a suggested place to start.

Ryan WardNeeraj Vir

Ryan or Neeraj will reply within one business day.

Contact us