Business analysis is the work of finding out what a piece of software must do before anyone builds it. A business analyst studies how your company really operates, writes down the rules and the exceptions, and turns them into a specification that developers can build from and you can check. It is the least glamorous part of a software project and the one that decides whether it succeeds.
When a software project fails, the programming is rarely to blame. The usual cause is that the wrong thing was built, and built well. Somebody described what they wanted, somebody else heard something slightly different, and the gap only showed when the finished system met real work.
Business people and programmers speak different languages. An owner says “we need to track jobs.” A developer needs to know what a job is, who creates one, what states it passes through, what happens when a customer changes their mind halfway, and who is allowed to see the margin. A business analyst is the translator who asks those questions before they become expensive.
Skipping this step is like starting a five-story building without a blueprint. By the fifth floor you find the things that should have been done on the first.

The result of a business analysis is a set of documents you own, whoever builds the software afterwards:
With that in hand, an estimate means something. Without it, any figure you are given for a project is a guess wearing a suit.
The right time is before you commit to a build. Analysis is worth doing when:
The analysis feeds straight into software architecture and design, where the question changes from what the system must do to how it will do it.
A business analyst’s job does not end at the specification. During development the analyst answers the questions that come up and keeps the project pointed at the original goal. At delivery, the analyst checks that the business is getting the benefit it was promised, and helps with training and job aids so that people use the new system the way it was designed to be used.

Our analysts use AI to turn interview notes, existing screens and sample reports into a structured first draft, and to check that draft for gaps and contradictions: the case nobody mentioned, the two rules that cannot both be true. When a decision changes, every part of the document it touches is updated together.
The analyst edits and you approve. The conversations with your people are still held by a person, because that is where the real requirements come from. See how we use AI on a project.
The next step is a short, no-pressure conversation. Schedule a project exploration call or use the form on this page.
They are the work of studying how a business operates and defining what a software system must do to support it. The result is a set of requirements and process documents that a development team can build from.
For anything beyond a very small project, yes. It is far easier to change a requirement on paper than to change finished software.
Process maps, written requirements, sketches of the main screens, an outline of the data and a phased plan. The documents belong to you.
Yes. The specification is yours to use however you choose.
A business analyst works out what the system should do and why. A programmer builds it. Keeping the two roles separate means somebody is always looking at the project from the business’s side.
An experienced Keene Systems business analyst, who stays with the project through development so the knowledge is not lost in a handover.
Yes. We use AI to read and map existing code, to draft specifications and to assist our developers. Everything it produces is checked by an experienced developer, and you own the resulting code.
Keene Systems has built custom business software since 1987. We are veteran-owned, and our 50+ professionals have delivered systems for companies including Hormel, McCormick, IBM and Dartmouth-Hitchcock. See our client list.
Start with a conversation