Every service page suggests a second service because the work overlaps

At the bottom of each service page, just before the testimonials, sits a glass card with a question and a link. The software page asks whether you need accessible software and links to the accessibility page. The accessibility page asks whether you need software built with accessibility baked in and links back to the software page. The cross-link is always a single sentence, a short explanation, and a coloured anchor tag using the target service's accent colour — fuchsia for accessibility when viewed from the software page, purple for software when viewed from the accessibility page. The colour is hardcoded in each page file because the cross-link is hand-picked, not generated. It would be possible to build a config object mapping every service to its complement and render the cross-link automatically. I chose not to because the phrasing matters. Need accessible, inclusive software reads differently from Need software built with accessibility baked in, and both of those are better than a generic You might also like followed by a service name. The cross-link sits after all the content sections — What I Build, Case Studies, Why Work With Me, Tech Stack — because by that point the visitor has absorbed the full picture of the current service. If their project sits at the intersection of two disciplines, the link catches them at the moment they are most likely to think about it. One glass card, one sentence, one accent-coloured link, and the site quietly says you do not have to choose between two things that work better together.