How a Tiny Team Ships Like a Big One
Welcome to Aithon Engineering
Who we are, what we build, and why a team of six builders decided to write an engineering blog.
Aithon is a small company that builds an AI-native go-to-market platform: software that reads the signals around a B2B sales team - filings, news, meetings, email, CRM - and tells them where their next deal is and how to move it. Our customers are enterprises, which means real compliance reviews, real data-residency requirements, and real consequences when something breaks. We run on AWS, with Claude on Amazon Bedrock inside our own VPC doing most of the thinking.
The part that surprises people is the size of the team: six builders. Not six builders plus a platform group and an SRE rotation - six, total, running the product, the data pipelines, and the infrastructure.
That gap between surface area and headcount forced us into an unusual way of working, and it's the reason this blog exists. Over the past year, agents took over most of the toil here. They write our code, review our pull requests, watch production, file bugs before customers hit them, and fix the ones that slip through. People still decide what gets built, argue about the specs, and click merge on every single change. We didn't plan the whole thing up front; we built one tool at a time, each one because something hurt that week, and one day we looked up and the way we ship looked nothing like it did a year ago.
We kept notes and numbers along the way. This blog is where we share them.
What to expect
We publish twice a week (Tuesdays and Thursdays), rotating through three tracks: the build track - how we ship (the agent fleet, the rails, the gates) - the product track - what we ship (the AI inside the product, minus the secret sauce) - and the partner track - what a working AWS partnership looks like, for us and for our customers, from co-sell to funding. Every post covers one system, and each follows the same shape: the problem as we actually hit it, what we built, a diagram, the real numbers, and a section called "Where the humans sit" - because the honest answer to "did AI replace your engineers?" is always about where the people are standing, not whether they're there.
Some of what's coming:
- The SRE agent fleet that turns a production error into a reviewed, tested pull request in about twelve minutes (published today, alongside this note).
- The QA agent that files bugs for code that has never failed in production.
- How 100% of our code came to be written by AI, and the review gates that make that a boring fact instead of a scary one.
- Dollar budgets, scope guards, and why our agents have an explicit way to say "I need a human."
- The deliberately boring deploy rails everything above depends on.
What not to expect
No product pitches - the product has its own website, and this isn't it. No AI hype either; we'll tell you what broke, what it cost, and which of our clever ideas we ended up deleting. Where a claim has a number behind it, you'll get the number.
If you want these posts as they come out, there's an RSS feed. If reading them makes you want to work this way too, talk to us.
The first real post is live now: Anatomy of our SRE fleet.
Building at Aithon.