TAMradar
An API needs its landing page to demonstrate, not describe
TAMradar is an API, and its landing page had to show the product rather than describe it. We built the brand, then the site, around getting and using an API key.
- Client
- TAMradar · IL-003
- Scope
- Branding · Web design · Development
- Year
- 2025
Where they started
TAMradar had no landing page that explained the product. For an API company that is a heavier problem than it sounds. Developers do not read marketing copy, they look for how the thing works. If a page cannot show that, it has not said anything at all.
What we did
We started with the brand, because the concept needed a shape before it could have a site. The identity came out of what TAMradar actually is rather than what category it sits in.
Then the site. We built it dark and forward-looking, a register that fits an infrastructure product without leaning on the usual developer-marketing tropes. The centre of the page is the API key: how you get one, and how it works. That is the thing a visitor came to understand, so we designed the page around understanding it rather than around persuading them first.
