Institutional memory for credit committees, designed and built in code. The four-page website, the identity for its product alfa+, and three whitepapers rebuilt on one print template.
The home page. On the live site, pick an audience and the headline and the rendered scene beneath it change.
Creditspective is a credit intelligence platform founded by former bank credit officers. We designed and built its four-page website in code, drew the identity for its product alfa+, and rebuilt its whitepapers on one print template. Every review happened on the running site, never on a mockup.
The site, the product identity and the print library, built together so a change in one never meant a redo in another.
From first commit to launch.
One stylesheet, no framework.
Three whitepapers and an overview, rebuilt from HTML.
Every image made for the site.









One argument across the site: the institution already holds the judgment it needs, and the platform puts it in front of every decision.












The memory cycle, the mantle and the product fragments are HTML and SVG on the page, so a copy change never meant redrawing a picture. On the live site you click through the stages.

alfa+ is the engine inside Creditspective, and it needed a mark of its own. We set it in a pixel face so the software reads apart from the company, which stays in a grotesque. Alpha is the goal, alfa+ is the engine.
/alfa+
/alfa+Each audience has a short rendered scene keyed onto white, so it sits on the page with no frame. The line field under the solutions headline is a canvas animation that follows the cursor and rests when it scrolls out of view.

Every section reflows for a phone. Nothing is hidden on small screens, it is reordered.










Three whitepapers and a one-page overview, rebuilt from HTML on one template with the site's typefaces, blue and diagrams. Together they went from 33 MB of exported PDFs to about 3 MB, and a wording fix now takes minutes.









Institutional memory for credit committees, built in code.
The first commit was a working site, and every review after that happened at a link, on the client's own screen. Changes went live the same day they were agreed, sometimes within the hour, because the site is static files deployed straight from the repository.
The diagrams and product fragments are code, so copy from No Middle was set straight into the pages as it arrived. The whitepapers work the same way: each one is an HTML document rendered to PDF by a script.