The company profile had eight services. The website had five. That is a content bug, but fixing it by appending three cards would have been the wrong fix.
Different software, different reader
The first five build the product you sell. The last three build the systems you run on. A founder buying a mobile app and an operations lead replacing a hospital's patient records system are not the same person, do not have the same sales cycle, and should not be asked to scan one undifferentiated grid of eight.
So services.html splits into two named families, and the profile's own
transition line does the work:
The previous page builds the product you sell; this one builds the systems you run on.
What business systems have to answer that product work does not
A new mobile app replaces nothing. An ERP replaces something that already works, badly, and that people are trained on. So the section carries three commitments the product side never needs:
- Deployed where you need it: cloud, on-premise, or hybrid
- Migrated, not restarted: reconciled against your books before go-live
- Handed over properly: training, documentation, and a support window