techpotions.com
Challenge
This is our own studio site, and it had a harder brief than most client work. techpotions sells bespoke software on the argument that most software today is generated, templated and predictable. A studio making that argument cannot ship a site that looks like everyone else's, so the site itself had to be the proof. It also had to do real commercial work: explain three quite different service lines without diluting any of them, present a portfolio that spans web, AI and design across several languages, and convert founders who are comparing us against agencies many times our size.
This is our own studio site, and it had a harder brief than most client work. techpotions sells bespoke software on the argument that most software today is generated, templated and predictable. A studio making that argument cannot ship a site that looks like everyone else's, so the site itself had to be the proof. It also had to do real commercial work: explain three quite different service lines without diluting any of them, present a portfolio that spans web, AI and design across several languages, and convert founders who are comparing us against agencies many times our size.
Solution
We built it on Next.js with Payload CMS so the team publishes lab posts and portfolio entries without a deploy, and hosted on Vercel. The structure is organised around three service lines presented as three potions, which gives each of web, AI and mobile its own space while keeping one identity across all three.
The site leans on motion and typography rather than stock imagery, and every section is written to a fixed voice rather than assembled from marketing filler. A Lab section carries technical writing that earns organic traffic, a Products area presents shipped work, and a Start a Project flow captures enquiries with the minimum friction. Because the studio ships multilingual and right-to-left builds, the front end was structured for internationalisation from the start.
We built it on Next.js with Payload CMS so the team publishes lab posts and portfolio entries without a deploy, and hosted on Vercel. The structure is organised around three service lines presented as three potions, which gives each of web, AI and mobile its own space while keeping one identity across all three.
The site leans on motion and typography rather than stock imagery, and every section is written to a fixed voice rather than assembled from marketing filler. A Lab section carries technical writing that earns organic traffic, a Products area presents shipped work, and a Start a Project flow captures enquiries with the minimum friction. Because the studio ships multilingual and right-to-left builds, the front end was structured for internationalisation from the start.
Results
The site is now the studio's primary sales asset and the reference point every directory listing and proposal points back to. Running it on Payload CMS means the team publishes and updates without developer time, which is the same argument we make to clients about owning their own content.
It also serves as a working demonstration of the stack we recommend most often: Next.js and Payload on Vercel, built from scratch rather than assembled from a theme. Shipped in two months alongside client work, which is a fair reflection of how a small senior team actually operates.
The site is now the studio's primary sales asset and the reference point every directory listing and proposal points back to. Running it on Payload CMS means the team publishes and updates without developer time, which is the same argument we make to clients about owning their own content.
It also serves as a working demonstration of the stack we recommend most often: Next.js and Payload on Vercel, built from scratch rather than assembled from a theme. Shipped in two months alongside client work, which is a fair reflection of how a small senior team actually operates.
