Techpotions is a small software studio building custom web apps, AI products and mobile apps for founders who care about craft. Based in Lahore, working remote-first with clients worldwide. The site is the studio's own proof of work, built in-house on Next.js, Payload CMS and Tailwind, with a warm coral-and-clay palette and a light apothecary thread running through it, distill, brew, pour. Every section earns its place, the work speaks through real projects and real numbers, not claims.

Distill, brew, pour, it lives. Four stages, each with its own piece of art, revealed one at a time as the page moves rather than stacked in a static list.

Process sections are the part of an agency site everyone skims. Turning it into a sequence makes it the reason to keep scrolling instead, and the last stage does real work: it lives, meaning the software keeps earning without the studio attached. That's a promise most agencies avoid making.

Web apps, AI products, mobile, migrations, platforms, growth labs. Each gets a custom illustration and a description with a real technical claim inside it, Next.js with type-safe APIs, agents with eval suites, React Native shipping weekly.

Sixteen tools, each labelled with what it's actually used for, app router, rag index, typed rpc, workhorse db. Not a logo wall, a working inventory.

Technical founders check for this before they book a call, and vague phrasing about modern technologies tells them nothing. Stating the stack plainly also filters: the section says the studio brings it where it fits and skips it where it doesn't, which reads as judgement rather than a checklist.

Most agencies point at client work and ask you to trust it. This page does something harder to fake: it shows what the studio builds when nobody is paying it to. One live product, Leads, an AI agent that hunts the open web for businesses showing a buying signal that week, plus five Claude Code packs given away MIT-licensed with no email gate. The free downloads are the strategy. Developers evaluating a studio don't read a services page, they check whether the team has shipped anything they'd actually use, so the page hands them five things and asks for nothing back.

The blog is framed as a lab notebook rather than a content channel, recipes and retrospectives and the occasional rant about software we wish was different. One entry gets the spotlight with a cover illustration, then twenty-eight more sit in a dense numbered archive with category, date, and read time on every row and no thumbnails at all. The design is built for scanning a body of work rather than scrolling through hero images, and the mix, practical build guides next to security incidents and cost breakdowns, reads as a working studio publishing what it runs into instead of a keyword calendar.

A warm studio photo, linen, terracotta, coral laptop glow, paired with mono-label stat tiles and a Crimson Pro italic pull quote.

An intake page built on the assumption that the form is the least interesting thing on it. Before the five fields, it publishes the whole process: a reply within 24 hours from an engineer rather than a salesperson, a 30-minute call to decide whether the fit is real, and a written proposal with phases, prices, risks, and what gets cut first if the budget moves. Under the submit button sit three guarantees, code ownership from the first commit, one human reply with no CRM sequence, NDA on request, each aimed at a specific reason people abandon agency forms. The FAQ then answers the five questions that normally eat the first call, including a real price range, so the conversation can start past the qualifying.

"Let's brew something that fits" The metaphor holds to the last line, set large enough to work as a sign-off rather than a footer. Small studio, big ideas, brewed slow.