Completed projects and working products

Task

An AI demo is not a business. The conversation, the account, the trial limit, the payment, the consent record and the people who operate it all have to work as one product.

What was built

A full AI SaaS: a customer app in three languages with accounts, trial limits, subscription and consent controls — plus an operations console for activation, subscriptions, AI cost, system health and support lookups.

Task

Tutors and students lived in chats and spreadsheets — no single place to browse by subject and language, apply to teach, or keep requests in order.

What was built

A tutor marketplace: a filterable catalog, tutor profiles, a structured application flow, an admin review layer, lesson-package logic and a multilingual structure.

Task

Conversation work depended on manual tracking: an operator had to remember who needed attention, what happened last and when to follow up.

What was built

A CRM prototype with profile context, contact threads, unread-state visibility, follow-up logic and an admin/moderation layer.

Task

Car enquiries die in DMs and phone tag — someone browses, has no way to state a budget, and the lead is lost to a slow reply.

What was built

A vehicle catalog with full specifications and a buyer-request flow that captures contact, budget and requirements from any page.

Task

Calls go unanswered and callers aren't routed to the right place fast enough.

What was built

A voice assistant that answers and routes callers in natural speech — with a working audio demo.

Task

The brand needed a clear public landing that presents its offer and routes visitors toward registration.

What was built

A responsive public landing: information architecture, offer and access presentation, and a single conversion route to registration.

Task

A specialist local service needs to explain what is repaired, where the team works and how to request help before a visitor loses intent.

What was built

A focused service website with a visual hero, repair categories, local positioning, proof-oriented sections and direct Request / Call paths.

Task

A broad detailing service can feel generic unless the site quickly anchors the core transformation, service area and booking action.

What was built

A live service site centred on Surface Restoration & Protection with a mobile-service proposition, service list, phone CTA and appointment CTA.

Task

Cash-on-delivery sellers lose money in the gap between the order and the doorstep: unconfirmed leads, stock nobody tracks, courier statuses in four dashboards and payouts reconciled by hand.

What was built

A marketing site plus an operations dashboard: orders, stock, invoices, sourcing requests, lead sources, call-centre confirmation stats, shipping status across couriers, and seller / affiliate account models.

Task

A multi-agent product becomes confusing when users see technology instead of clear roles and outcomes.

What was built

A clean agent-selection interface with use-case cards, named agent personas and a dedicated voice-call entry point.

Task

Acquisition is expensive and app installs are a wall. A Mini App removes the install, but only earns attention if there is a reason to return and a reason to invite.

What was built

A Telegram Mini App: a collection timer with a claim action, a finance area for top-up and withdrawal, a referral system paying a share of invited users' activity, and a shop of upgradeable packages.

Task

Clothing brands lose the sale between the photo and the checkout: unclear collections, prices that hide, and a catalogue that reads like a folder rather than a shop.

What was built

A bilingual storefront: an editorial home, a bestseller carousel with prices, a wedding and evening collection section, catalogue navigation, search and cart.

Task

A bidding flow fails quickly when price, countdown, history and the place-bid action compete instead of forming one decision hierarchy.

What was built

A mobile live-auction concept with current bid context, countdown, bid history and a focused place-bid interaction.

Task

Marketplace discovery becomes noisy when collections, creators and assets compete for attention without a clear browsing hierarchy.

What was built

A focused discovery experience using visual hierarchy, grouped marketplace content and mobile-first navigation.

Task

Collectors need to understand a group before drilling into a single asset; flat grids lose that relationship.

What was built

A collection browsing surface that groups assets into a recognisable marketplace structure and keeps the mobile hierarchy compact.

Task

B2B blockchain sites talk to engineers and lose the person who signs. The buyer never learns what changes in their operation.

What was built

A B2B site translating the technology into business outcomes — a secure-and-safe section, a trust argument, and an enterprise-facing contact route.

Task

Depositing into a yield product is irreversible. If the boost mechanism, the withdrawal rules and who audited the contracts are not on the first screen, a cautious depositor leaves.

What was built

A staking landing presenting deposits for boosted yield, explicit withdrawal terms, the token model and a named third-party security audit.

Task

Self-custody is the whole promise, and most wallets bury it. Users cannot tell what is collected, who audits the code, or what happens if the company disappears.

What was built

A wallet product with swap and source/destination network selection, buy-crypto and add-chain entry points, plus explicit transparency and security sections covering open source, regular audits and what data is never collected.

Task

Chains compete for developers, not end users. A builder decides in one screen whether the fees, interoperability and routing are worth rewriting for — and whether anyone will fund the attempt.

What was built

A chain site covering core features around fees and scalability, interoperability and blockchain routing, an ecosystem showcase and a builder grant path.

Task

Service businesses hide behind "contact us for a quote", so the customer cannot compare and does not call. Meanwhile the competitor who published a price list gets the booking.

What was built

A service website with a dark automotive hero, service tiers presented as packages across exterior, interior and full detailing, and a booking route.

Task

Electric mobility is a considered purchase with real anxiety attached — range, build quality, what happens after the sale. A page that lists specifications without comparing them leaves the buyer to do the work, and most will not.

What was built

A product landing introducing the range, a why-choose-us argument, feature discovery, and a model comparison leading into the collection.

Task

Wearables all list the same specifications. The buyer cannot tell them apart, so the category collapses into a price comparison.

What was built

A device landing with a product hero, a feature breakdown across training, health monitoring and analytics, and an in-use section showing the device reporting real activity.

Task

Furniture is bought by imagining it in a space. A grid of cut-out products on white gives the buyer nothing to imagine with, and the sale moves to whoever shows the room.

What was built

An ecommerce storefront with an editorial hero, a filterable product catalogue across seating, tables and storage, room-context photography and a contact route.

Task

Skincare buyers are sceptical and informed. A page of soft photography and vague promises gives them nothing to decide with, so they leave before the price.

What was built

A conversion landing with a product hero, an ingredient-and-benefit breakdown, a route into the range, and brand product photography as the supporting layer.

Task

Supplements live or die on trust, and a range multiplies the problem: each new SKU needs the same proof rebuilt, so quality drifts and the brand starts to look inconsistent.

What was built

A reusable product-page system applied across whey protein and creatine — product hero, a why-it-is-good-for-you argument, ingredient and usage detail, and a best-sellers grid.

Task

A range confuses more than a single product. Without a clear reason to pick one item over its neighbour, the buyer picks nothing.

What was built

A range-led landing: the hero introduces the line rather than one item, a why-it-works section grounds each claim in an ingredient, and a best-sellers grid splits the range by the need it answers.

Task

Coffee buyers know what they like and hate being made to guess. Hiding roast level and format behind product pages turns a quick reorder into a chore.

What was built

A brand landing with a bestseller range showing roast variants and formats side by side, a brand story section and a lifestyle layer.

Task

At a luxury price point the objection is not cost, it is doubt. If warranty, craftsmanship and provenance are not immediate, the buyer assumes they are absent.

What was built

A luxury storefront with a dark editorial hero, warranty and craftsmanship credentials placed immediately under the headline, a collection grid and a brand-story section.