Twenty-two products in one TypeScript file

Every service package on the site lives in a single TypeScript file. Twenty-two products across five services. Each one is a typed object with an id, a name, a description, a price in pence, a feature list, a delivery estimate, and a service category. Fixed-price packages store a real pricePence value. Quote-based packages store null and a label like Get a quote instead. A helper function called isPurchasable checks whether a product has a valid price — if it does, the checkout page renders a full Stripe payment flow. If it does not, the page shows a contact form instead. That one boolean check is the entire branching logic between a purchasable product and a quote request. Adding a new package to any service means adding one object to the array. The sidebar picks it up. The checkout page picks it up. The service page picks it up. No migration, no API call, no admin panel update. The TypeScript compiler checks every field at build time so a misspelled property name or a missing feature list fails the build before it ever deploys. Twenty-two products, five services, one file, zero runtime errors.