App Development
Custom software usually starts as a spreadsheet somebody maintains by hand and ends as the system a business runs on. The hard part is not the first version. It is whether the thing can still be changed two years later, by someone who was not there.
- SaaS
- APIs
- Databases
What it covers
SaaS platforms
Multi-user products with accounts, permissions, billing, and the unglamorous operational work that decides whether they are still running a year after launch.
Internal tools
The system that replaces the spreadsheet. Built around how the work is actually done, which is rarely how it gets described in the meeting where it is commissioned.
APIs and integrations
Software that has to talk to other software. Documented interfaces, predictable errors, and failures that announce themselves rather than being discovered in a reconciliation months later.
Data and databases
The schema designed before the code, because the shape of the data is the thing most likely to stand in the way of the feature after next.