A small team with a model of its own.
FeynCode started in Pune in 2023 with three engineers and a habit of reading other people’s operations closely. Kaeonix came out of that work, and the client work now runs on it.
How we got here
The first two years were service work: an HR platform for an agency drowning in group chats, production tracking for a manufacturer, invoicing for a food trader. Different industries, one recurring shape — people spending their attention on moving information between systems.
We started training a model to do our own share of that work: read a repository, propose the change, run the tests. It turned out to be better at the loop than at describing it, which is how Avatar became a product rather than an internal tool.
Today Kaeonix pays for its own development, and the team takes on client work where the two reinforce each other. Every client project teaches us something about how agents behave in a business that has to close its books on Friday.
How we work
Teams of two to four, each engineer holding the whole picture. Decisions happen in conversation, with the person who will maintain the result in the room.
We write things down: architecture notes in prose, a changelog anyone can read, a runbook that assumes the reader is tired. Documentation is the part of the work that survives us.
And we tell you when software is the wrong answer. Two of the last ten enquiries ended with a two-page note and no invoice, which is a better outcome for everyone than a project nobody needed.
What we hold to
If a model sits in the path, we measure it on your data before anyone draws a screen around it. Accuracy that arrives after the interface is a renovation; accuracy that arrives first is a design input.
Source code, infrastructure, model weights where we trained them for you, and the documentation. From day one, in your accounts. Lock-in is a business model we would rather not have.
Nobody on the project knows only their layer. It keeps handoffs cheap, makes estimates honest, and means the person answering your question on Thursday wrote the code on Tuesday.
One database, one queue, one cache, chosen because we can debug them at midnight. Novelty is reserved for the part of the system where it earns something.
Come and work on the loop.
We hire twice a year, slowly. Send something you built and a paragraph on the part you would do differently now.