Services
Most software works on the day it is delivered. Then a source changes its markup, a token expires, a job stops firing — and the failure is quiet. Everything below is built so that it is not.
Customer-facing or internal, connected to the database, the CRM and the APIs that actually hold your data — with the boundaries of what it may read, say and do written down and covered by tests.
The operational tasks somebody currently does by hand every morning: triggered on a schedule or an event, retried when the failure is transient, and stopped loudly when it is not.
Numbers assembled once, correctly, and delivered on a schedule — with the freshness of the underlying data shown next to them.
Scheduled collection from sites and APIs, merged into a database you can query. Rows are counted before and after every merge and the merge is rejected if any went missing or duplicated — silent data loss is the failure nobody notices, so it is the one that gets checked for.