001 Who this is
Specialists in the systems you cannot afford to replace.
We repair, secure and modernize the business software a company already runs on — the systems with real customers, real revenue and no room for a rewrite. Not new products, and not marketing sites. That narrowness is what makes the work worth buying.
002 The practice
The engineers who read your code are the ones who own the practice.
Either principal takes the first call, reads the system and gives you the price. Somebody may help us get that call into the diary; nobody prices your system who is not going to be working on it.
Founded 2025
Greg Popov
Code and architecture
Holds the scope, the estimate and the schedule you are held to.
Thirteen years on systems that were already running when he got there.
Elguja Nemsadze
Code and infrastructure
Holds what it runs on, how it ships, and the plan for when it breaks.
Ten-plus years running infrastructure other people depend on and never think about.
You
Founding Sales / Business Development
Owns outbound — the approach, the tools, the messages, and the calls that come out of them.
Part-time to start, beside whatever else you do. Nobody is in this chair yet.
Join our team
Whichever one answers you owns the job from the first quote to the last release. There is no one above them to escalate to, and no one below them doing the work instead.
003 How the work is staffed
We take on few systems, on purpose.
Every firm says the same thing about care and attention. The difference here is structural.
At an agency, the person you meet is the person who sells. The work goes to whoever is free that month, and when they leave, what they knew about your system leaves with them. You pay for a firm and you receive a rotation.
Capacity here is held low deliberately. A system we take on is read end to end by a founding engineer, and it is the same engineer next quarter and the year after that. It means we turn work away. It is also the reason the work is worth what it costs.
Larger jobs get more hands — engineers we have worked with for years, and a specialist who does nothing but infrastructure. They work on your system. They never become your contact, and they are never the people accountable for it.
You will never be handed to someone else. No account manager to meet, no new face each quarter, no email telling you your account has moved. A founding engineer answers, and a founding engineer is accountable for everything anyone does to your system.
We are not generalists for hire either. When a job falls outside what we are genuinely good at, you get that in the first reply, with the name of someone better. It costs us the contract and saves you a month.
004 How this is built to fail safely
You should not depend on us either.
You are reading this because someone disappeared on you, or might. The way this practice is set up assumes the same thing could happen to us.
Everything lives in accounts you own. Your cloud account, your code repository, your domain, your card. We get invited in. We are never the owner.
Every change is written down in a place you control, with a note explaining why, that any other developer can read.
You get a handover document written so a new developer can pick your system up in a day — updated as we go, not promised at the end.
Your data stays your data. An audit is read-only. Where the work needs a copy to develop against, personal data is replaced before the copy is made, not after — the shape and the volume without the people in it. Credentials live in a store you own, never in our code.
Monthly, cancel any month. No annual lock-in, no notice period, no cancellation fee. If we stop earning it, you stop paying.
005 Honest limits
Things we don’t do.
We don’t build new products from scratch. We repair systems that already exist and already have users. Connecting one of those to an outside service is not a new product, and building that connection is part of the job.
We don’t do marketing websites, design or SEO. If your site is just brochure pages, you don’t need us.
We don’t take on .NET, Java or Ruby back ends. Everything else a business system is made of, we do: PHP most often, Node and Python services beside it, the front end, the hosting, and the move to a newer platform.
We won’t take the job if it isn’t worth doing. Sometimes replacing a system costs less than repairing it. You get that in writing.
We are not your compliance advisor. We establish what is true about your systems and fix what is broken. Whether that satisfies a specific regulation is a question for someone qualified to answer it. What we do sign is the paperwork: an NDA before anything is opened, and a Business Associate Agreement where the work touches health information.
Write to a person.
One inbox, one reply, within one business day. Everything here is handled by a person: no automated sequence, no mailing list, nothing sent to you that someone did not write. If you don’t reply, you never hear from us again.