Keene Systems has built custom business software since 1987. Clients stay with us for years, some for more than a decade, and the reason is not a particular technology. It is the way we do business: we tell the truth, we do careful work, and we charge fairly for it. This page sets out what that means in practice, so you know what to expect before you ever speak to us.

Software projects go wrong when people are told what they want to hear. We would sooner lose a project than win it with a promise we cannot keep.
Too many companies discover that the software running their business belongs, in practice, to whoever wrote it. That does not happen with us.
If you are in the opposite situation today, see what to do when a developer is holding your code hostage.
We believe a client should pay for the work that was done, see what it produced, and be free to leave. Our terms are built on that.

Quality is not a slogan. It is a set of habits, and you can watch every one of them.
Our guide, How to Plan a Software Project, describes the method in detail.
Our approach is both entrepreneurial and technical. Software is only worth building if it makes the business run better, so we start with the business problem: where time is lost, where errors come from, what management cannot see. Then we design the system around the way you work. That is the difference between custom software and a product that forces you to work its way. The problems we solve are business problems first.
Building your software means seeing how your business really works. Everyone on our staff is bound by the non-disclosure agreements we sign with our clients, so your data, your processes and your intellectual property stay yours.
When a project is complete, we make sure your people know the system: how to use it, how it is put together and where everything is kept. The aim is a client who chooses to keep working with us, not one who has to.
We are a veteran-owned firm of 50+ professionals, so your system never depends on one person being available. The people who build your software are the people who keep developing it, and many of our client relationships have lasted more than a decade. We have delivered systems for companies including Hormel, McCormick, IBM and Dartmouth-Hitchcock. See our client list and read our case studies.
We have been building web applications since 1999 and working in Microsoft ASP.NET since 2002. That depth is what lets us give you a confident answer about what will work.
The next step is a short, no-pressure conversation. Schedule a project exploration call or use the form on this page.
You do. Our contract assigns the code and the intellectual property we write for you to your company. You hold the source code, and hosting and other accounts are set up in your name.
We bill hourly for the work actually done, after giving you an estimate. There are no minimums and no monthly commitments, and you see working software every two weeks, so you always know what your money has bought.
You can. Because you own the code and are not tied to a long-term contract, you can slow down, pause or stop at the end of any two-week sprint and keep everything that has been built.
We document the requirements before writing code, build in short sprints that you review, and have quality assurance testers check the software before each delivery. The code is written and documented so that other developers can maintain it.
Yes. If an off-the-shelf product or a smaller fix would serve you better, we will say so. A straight answer at the start is worth more to both of us than a project that should not have been built.
Tell us what you need