Adaptable Software

What the client receives

The result of the work is a functioning system together with everything required to operate, maintain, and extend it: the application source code, the infrastructure configuration that defines where and how it runs, the database and its schema, written documentation of the system's design and behavior, a test suite, a deployment pipeline, and a development environment that another engineering team could use immediately. Where artificial intelligence is part of the system, the client also receives the agent instructions and the evaluation framework that govern how those components behave.

The system is built so that someone who did not build it can understand and modify it. Documentation, consistent naming, test coverage, and the structure of the code are treated as part of the work rather than as items to be completed afterwards.

Software that changes with the organization

An organization's processes do not stay fixed. It adds products and services, changes suppliers, enters new markets, and revises how work is reviewed and approved. The software that supports those processes needs to change with them.

Software the client owns can be changed when the client needs it to change. Firmcraft builds it to be adapted: it is documented, tested, and structured so that a change can be made safely and quickly, whether by Firmcraft under its managed services, by the client's own staff, or by AI coding agents working under an engineer's direction. The software is expected to change over its working life, and it is designed and delivered on that basis.

How ownership works

The client owns the source code, the data, and the infrastructure configuration for software Firmcraft builds for it. The software is proprietary to the client, and its ownership is set out in the engagement agreement. Where an engagement uses a component from Firmcraft's own library of previously built solutions, that code is handed over to the client on the same basis.

Where the software runs depends on the client. Some clients host it in their own environment and operate it themselves. Others ask Firmcraft to operate it as part of its managed services. In either case the client owns the software and can move it to an environment of its choosing.

The client can also change the software without Firmcraft's involvement. There is no contractual restriction on who may work on the code. The client may assign its own staff, engage another engineering firm, or direct AI coding agents to make changes.

Firmcraft remains available for further development and support through its managed services, which give the client continued access to the people who built the system. That arrangement is not a condition of continuing to use the software.

Why custom software is now a practical choice

Many organizations pay for subscription software of which they use a small part, and adjust their processes to fit what that software was designed to do. Where a workflow can be handled by software built for it, working alongside the organization's existing financial and customer systems, the result is often simpler for staff to use and less expensive to run. Firmcraft makes that comparison during the process redesign and recommends a subscription product where it is the better answer.

The larger cost of custom software has historically been maintaining and changing it over time. Organizations often found that they could not change a custom system without returning to the original builder, because no one else understood it well enough to work on it safely. AI coding agents, working under the direction of an engineer, can now perform much of that work on code that is well structured, documented, and tested. Firmcraft builds with that in mind and delivers the documentation and agent instructions that make it possible.

Relationship to data sovereignty

Software ownership and data sovereignty are separate questions that support each other. Owning the code is of limited value if the data it works on is held in an environment the client does not control, and control of the data is incomplete if the software that processes it can be withdrawn by a third party. Firmcraft's default position on both is that the client retains control. How Firmcraft handles client data, including where it resides and what may be sent to hosted services, is set out in Data Sovereignty.

Ownership in the engagement agreement

The transfer of source code, infrastructure configuration, documentation, and related materials to the client, including any component drawn from Firmcraft's library, is written into the engagement agreement.