Capewesley
Cape Wesley builds core-banking and regulatory software for institutions that answer to regulators. It is work that is genuinely difficult to explain to anyone outside a compliance department. The brief was a website. The actual problem was legibility.
- Client
- Cape Wesley Consulting
- Sector
- Financial software infrastructure
- Role
- UI/UX Design, Information Architecture
- Year
- 2025
- Platform
- Web
The problem
A consultancy with deep technical credibility and no way to communicate it. The product range spanned core banking, automated regulatory filing, policy intelligence and credit-union software. Each one substantial, all of them reading as an undifferentiated list. Meanwhile the buyers are among the most risk-averse in any market: people who need evidence before they need enthusiasm.
Approach
I stopped treating it as a company website and started treating it as an argument. Institutional buyers don't scan for adjectives, they look for proof. So the structure leads with what the software actually does and the cadence it runs at, and lets the company description come after the evidence rather than before it.
What I did
- Restructured the information architecture around products and proof rather than around the company
- Established a hierarchy that lets a technical buyer verify capability without a sales conversation
- Designed the interface and responsive behaviour across the full site
- Built a visual language sober enough for a regulated sector without being forgettable
What I'd do differently
I'd push harder for access to actual buyers. The structure was reasoned from the sector rather than tested against the people in it, and a handful of interviews would have turned a good argument into a verified one.