Build, buy or compose: internal tools in the AI era
Build vs buy software was for a long time a choice of two: have your own tool written, or pay for a finished product. There is now a third way. To compose means to put together a tool that fits your way of working out of ready parts, on a platform that someone else keeps running. For most internal tools in a small company, composing gives a close fit without the upkeep of your own software.
The three options in plain words
An internal tool is software your own team uses, such as a list of equipment or a way to handle holiday requests. Think of getting a kitchen.
- Build. A carpenter makes the kitchen to measure. For software, a programmer or an AI coding tool writes it for you. It fits exactly. Every repair is yours.
- Buy. You take a finished kitchen from the showroom. For software, you subscribe to a finished product. It works on the first day, in the way its maker designed it.
- Compose. You plan the kitchen from standard units that fit together. For software, you describe your lists, forms and steps on a platform. The platform takes care of logins, safety and updates.
What AI changed, and what it did not
AI can now write a first working version of a program very quickly. It has not changed what comes after. The program must be kept running, kept safe and backed up. And the team will ask for changes every month. The first version was always the smaller part of the cost. That is the part that became cheap.
Side by side
| Build | Buy | Compose | |
|---|---|---|---|
| Fit to your way of working | Exact | As the maker designed it | Close |
| Time until you can use it | Days to months | Today | Hours to days |
| Who keeps it running and safe | You | The maker | The platform |
| Who can change it | A programmer | Mostly the maker | The team that uses it |
Four questions that decide it
- Is the job the same in most companies? Payroll and bookkeeping are. Buy.
- Is the tool what your customers pay you for? Then it is worth owning in full. Build.
- Is the way of working your own, but made of ordinary parts? Lists, forms, approvals, reminders and reports. Compose.
- Who will look after it in two years? If you cannot name a person, do not build.
Four internal tools, sorted
- Monthly payroll: buy.
- The software you sell to your own customers: build.
- A list of equipment with service dates and reminders: compose.
- Taking on a new supplier, with documents and two approvals: compose.
Before you build: the list for year two
Write a name next to each of these jobs.
- Install safety updates.
- Keep backups and test that they work.
- Add new colleagues and remove those who leave.
- Make the changes the team asks for.
If the list has no names, the tool is likely to be left behind, however good the first version looked.
How Worknano handles this
Worknano is a platform to compose on. Describe the module you need in plain English, and the AI Module Builder drafts it with its fields and links. A manual builder gives exact control where you want it, and anything the AI drafted can be edited in the Data Model designer. Either way the new module is a full part of the workspace. It uses the same permissions, works with workflows and files, appears in reports and can use AI agents. It sits in the same database as CRM, projects and HR, so the data it needs is already there.
- Module Builder: create the modules your business needs
- What if I need a module Worknano does not ship?
Create a free workspace and compose the internal tool you were about to build.