Skip to content

alicreates/Projects

Get in touch

Portfolio

Clients and products.

Open a client to read what was delivered, where it ran, and which interface shipped. Each client also has its own page.

A German listing still needs an exposé: rooms, energy data, location, and photos that do not look like a phone dump. ImmoTools24 packages that work for agencies in Hamburg. The product side I worked on covers exposé generation, image editing for listings, and a surface agents can call, including an agent-readable tool endpoint on the public site. The live site is the product, not a brochure about a product that never shipped.

Client
ImmoTools24
Location
Hamburg, Germany
Role
Product builder
Stack
Exposé generation, Listing images, Agent tools

What changed

  • Exposé generation instead of a fresh brochure for every listing
  • Image tools aimed at listing photos, not a general editor
  • A public Hamburg site an agency can open and use

Interface

Live ImmoTools24 site: real-estate exposés, images, and agent tools.

  • ImmoTools24 interface, view 1. Live ImmoTools24 site: real-estate exposés, images, and agent tools.

Open the case studyVisit the live site

LiveHive is a London coaching platform. A coach should not send a client from a form, to a calendar, to a payment link, to a video app. I worked on the Bubble product so booking, Stripe billing, and Whereby sessions sit in one path. The operational bits around reminders follow the same booking, so the coach is not chasing confirmation by hand. The public site is the product front; the working screens are the booking and session flow.

Client
LiveHive
Location
London, United Kingdom
Role
Product builder
Period
2021 – 2022
Stack
Bubble.io, Stripe, Whereby

What changed

  • One booking path instead of a chain of links
  • Stripe and Whereby inside the session, not beside it
  • Fewer manual reminders for the coach

Interface

The 2021 coaching workspace is not on a public URL anymore, so there is no live screen. The current livehive.io site is a different product and is not this engagement.

Open the case study

Pharmacy wholesale is not a shopping cart with a bigger font. A buyer needs a catalogue they trust, a price that does not change between the screen and the order, and a path from request to confirmation. Farmarke puts the day-to-day UX in Bubble and the catalogue, pricing, and order rules in Xano. I worked on the data model and the ordering path so back office and buyer see the same line. Early notes called the brief Pharmarke. The public product is Farmarke.

Client
Farmarke
Location
Belluno, Italy
Role
Product builder
Period
2022 – 2023
Stack
Bubble.io, Xano

What changed

  • Catalogue and price rules held in Xano, not in the page
  • An order path a non-technical buyer can finish
  • The same line item in the buyer view and the back office

Interface

Farmarke product screens for B2B pharmacy ordering. The public site is farmarke.com.

  • Farmarke interface, view 1. Farmarke product screens for B2B pharmacy ordering. The public site is farmarke.com.
  • Farmarke interface, view 2. Farmarke product screens for B2B pharmacy ordering. The public site is farmarke.com.
  • Farmarke interface, view 3. Farmarke product screens for B2B pharmacy ordering. The public site is farmarke.com.

Open the case studyVisit the live site

Conflux replaces the HR spreadsheet. The app is internal, so there is no marketing site. Bubble is the workspace employees and people ops open. Roles decide who sees a request, a record, or an admin view. AWS holds files and the jobs that should not live inside a page workflow. I shaped the permissions and the weekly admin screens. The images are product screens from that workspace, not a public homepage.

Client
Conflux
Location
Rome, Italy
Role
Product and no-code engineer
Period
2022
Stack
Bubble.io, AWS

What changed

  • Requests and employee records out of mail and spreadsheets
  • Role-based access for staff, managers, and people ops
  • Files and heavier jobs on AWS, not inside the page

Interface

Private Conflux HR screens. There is no public marketing site for this tool.

  • Conflux interface, view 1. Private Conflux HR screens. There is no public marketing site for this tool.
  • Conflux interface, view 2. Private Conflux HR screens. There is no public marketing site for this tool.
  • Conflux interface, view 3. Private Conflux HR screens. There is no public marketing site for this tool.

Open the case study

A professional EV buyer does not trust a photo and a price. Cardino is the B2B marketplace for that stock. Bubble is the commercial front end. Supabase holds accounts and listing data. DAT supplies the vehicle identity and specs a German buyer expects. OpenAI is used only where a repetitive text task is faster than typing, not as a layer over missing vehicle data. I tied those parts into a desk a dealer can run during the day. The screens mix the public site and the working marketplace.

Client
Cardino
Location
Berlin, Germany
Role
Product and integrations lead
Period
2023 – 2024
Stack
Bubble.io, Supabase, OpenAI, DAT

What changed

  • Listings backed by DAT vehicle identity, not free-text specs
  • Account and search data on Supabase
  • A dealer desk that runs on the stock, not on a demo script

Interface

Cardino marketplace screens and the public cardino.de site.

  • Cardino interface, view 1. Cardino marketplace screens and the public cardino.de site.
  • Cardino interface, view 2. Cardino marketplace screens and the public cardino.de site.
  • Cardino interface, view 3. Cardino marketplace screens and the public cardino.de site.

Open the case studyVisit the live site

A QR menu fails if the guest can read it and the floor cannot. Easy Menu is built for Venice service: the guest opens the menu, the venue still has to take payment and keep the books. Stripe handles cards. Supabase holds menus and orders. The Italian side connects to Agenzia delle Entrate where electronic invoicing is part of the sale, not a Monday export. I kept the screens short enough to use at a table. The shots are the phone interface. There is no separate public marketing site.

Client
Easy Menu
Location
Venice, Italy
Role
Product builder
Period
2023 – 2024
Stack
Bubble.io, Stripe, Supabase, Agenzia delle Entrate

What changed

  • A QR menu the floor can operate during service
  • Payments and orders in the same product
  • A path toward Italian e-invoicing instead of a later spreadsheet

Interface

Easy Menu phone screens: the QR menu used at the table.

  • Easy Menu interface, view 1. Easy Menu phone screens: the QR menu used at the table.
  • Easy Menu interface, view 2. Easy Menu phone screens: the QR menu used at the table.
  • Easy Menu interface, view 3. Easy Menu phone screens: the QR menu used at the table.

Open the case study

Lalista is the operating app for a Venice venue, not another QR menu. Next.js on Vercel is the staff interface. Supabase holds auth and the operational data. The flows cover the floor: what the room is doing, what the pass needs, and what front of house has to see before service starts. I built those operational screens so a manager is not reconstructing the shift from messages. The gallery is the product. The linked deployment is the running app.

Client
Lalista
Location
Venice, Italy
Role
Product and full-stack engineer
Period
2025 – 2026
Stack
Next.js, Vercel, Supabase

What changed

  • Floor, pass, and front of house in one Next.js app
  • Auth and operational data on Supabase
  • A deployment the venue staff actually open

Interface

Lalista staff interface for restaurant operations in Venice.

  • Lalista interface, view 1. Lalista staff interface for restaurant operations in Venice.
  • Lalista interface, view 2. Lalista staff interface for restaurant operations in Venice.
  • Lalista interface, view 3. Lalista staff interface for restaurant operations in Venice.

Open the case studyVisit the live site

A parts warehouse fails on the wrong reference. The Treviso work is warehouse management for car and truck parts: what is on the shelf, which vehicle it fits, and which dealer order it can fill. The public Partsbit marketplace is the customer-facing catalogue of new and used parts. I treated the engagement as the operational layer under that trade: stock, compatibility, and fulfilment, not a reskin of the homepage. The live site shows the catalogue a buyer searches. The warehouse screens sit behind it.

Client
Partsbit
Location
Treviso, Italy
Role
Product builder
Stack
Parts catalogue, Warehouse stock, Vehicle compatibility

What changed

  • Stock tied to a part reference, not a shelf nickname
  • Compatibility checked before a dealer order is promised
  • A public catalogue that matches what the warehouse can fulfil

Interface

Public Partsbit catalogue. The Treviso delivery was warehouse stock and compatibility behind it.

  • Partsbit interface, view 1. Public Partsbit catalogue. The Treviso delivery was warehouse stock and compatibility behind it.

Open the case studyVisit the live site

A fabrication quote dies when the spreadsheet and the workshop copy disagree. Fabbrika is the quotation maker for a Padova manufacturing and trade operation. Bubble is the screen where a quote is built. Supabase holds the lines, costs, and customer record. n8n moves the quote between supplier, production, and the person who has to send it. I led the operational flows so a quote is a record, not a file in someone’s downloads. fabbrika22.it is the public face. The gallery is the working tool.

Client
Fabbrika
Location
Padova, Italy
Role
Product manager and no-code engineer
Period
2025
Stack
Bubble.io, Supabase, n8n

What changed

  • Quotes built as records, with cost and customer attached
  • Handoff between supplier, production, and sending via n8n
  • A Padova team that is not retyping the same line into a sheet

Interface

Fabbrika quotation and operations screens, plus the public site fabbrika22.it.

  • Fabbrika interface, view 1. Fabbrika quotation and operations screens, plus the public site fabbrika22.it.
  • Fabbrika interface, view 2. Fabbrika quotation and operations screens, plus the public site fabbrika22.it.
  • Fabbrika interface, view 3. Fabbrika quotation and operations screens, plus the public site fabbrika22.it.

Open the case studyVisit the live site

Schüco quotes break when someone prices a system from memory. A window is a frame series, a glass build-up, hardware, and a size. Change one and the total moves. I built the Padova quotation maker around those lines, so a fabricator configures the system and gets a total they can send, instead of rebuilding the same offer in a sheet. The tool is private. The global Schüco marketing site is a different product, so it is not shown here as if it were the quote screen.

Client
Schüco
Location
Padova, Italy
Role
Product builder
Stack
Frame and glass lines, Hardware options, Quote totals

What changed

  • Frame, glass, and hardware priced as one configuration
  • A total that updates when the system changes
  • Quotes a Padova fabricator can resend without a fresh spreadsheet

Interface

Private Schüco quotation workspace. No public quote screen.

Open the case study

The brief was a better way to save information, not a shorter URL for its own sake. Public teams need a link they can hand over and a record of what it pointed to. Ancode keeps the target, the short link, and the click history in Supabase. Flutter is the device surface. Next.js on Vercel is the console where someone who is not a developer can still see where a link went. I worked on both surfaces so saving a reference and proving it later are the same product. ancode.it is the public entry.

Client
Ancode
Location
Udine, Italy
Role
Product engineer
Period
2024 – 2025
Stack
Flutter, Next.js, Supabase, Vercel

What changed

  • A short link that still has a stored target and a click record
  • The same behaviour on Flutter and in the Next.js console
  • A console a non-developer can use when someone asks where a link went

Interface

Ancode console and device screens for saving and sharing a reference.

  • Ancode interface, view 1. Ancode console and device screens for saving and sharing a reference.
  • Ancode interface, view 2. Ancode console and device screens for saving and sharing a reference.
  • Ancode interface, view 3. Ancode console and device screens for saving and sharing a reference.

Open the case studyVisit the live site

Placing a C-level consultant is a sourcing problem with a long CV and a short list of real fits. Ultra, on ultrastrategy.com, is that platform for enterprise and public-sector clients in Burgundy. I led the product and the AI path: Affinda and the model stack parse a resume, a matching agent lines an executive up with an opportunity, and the operating workflows cover timesheets, invoicing, and proposals once a project is live. Sourcing time on a consultant moved from about five hours to about one hour, and the matching pass from about five hours to about twenty minutes. The platform grew from zero to more than 1,300 users. Bubble, Supabase, and n8n carry the workspace, the data, and the handoffs.

Client
Ultra
Location
Burgundy, France
Role
Product manager and AI engineer
Period
Nov 2024 – present
Stack
Bubble.io, Supabase, n8n, Claude, OpenAI, Affinda

What changed

  • Consultant sourcing cut from about five hours to about one hour
  • Matching a profile to an opportunity cut to about twenty minutes
  • From zero to more than 1,300 users on the live platform

Interface

Ultra sourcing workspace on ultrastrategy.com: search, match, and delivery.

  • Ultra interface, view 1. Ultra sourcing workspace on ultrastrategy.com: search, match, and delivery.
  • Ultra interface, view 2. Ultra sourcing workspace on ultrastrategy.com: search, match, and delivery.
  • Ultra interface, view 3. Ultra sourcing workspace on ultrastrategy.com: search, match, and delivery.

Open the case studyVisit the live site

Qomodo sells B2B buy-now-pay-later to Italian vendors, including appointment businesses that send a pay-by-link rather than a card terminal. I designed the multi-role vendor desk: a merchant can grant branch access without sharing one login, see sales on payment links and BNPL, and run confirmation and reminder mail through SendGrid. Bubble is the desk. The Qomodo backend is the source of the payment. Supabase and n8n connect them. The launch reached more than 2,000 users, with hundreds of payment links a day. The screens are that desk. qomodo.it is the public product.

Client
Qomodo
Location
Milan, Italy
Role
Product and low-code lead
Period
2024 – 2025
Stack
Bubble.io, n8n, Supabase, SendGrid, Qomodo API

What changed

  • A multi-role vendor desk adopted by more than 2,000 users
  • Branch access without a shared login
  • Pay-by-link and BNPL analytics on the daily payment volume

Interface

Qomodo vendor desk: roles, pay-by-link, and BNPL sales.

  • Qomodo interface, view 1. Qomodo vendor desk: roles, pay-by-link, and BNPL sales.
  • Qomodo interface, view 2. Qomodo vendor desk: roles, pay-by-link, and BNPL sales.
  • Qomodo interface, view 3. Qomodo vendor desk: roles, pay-by-link, and BNPL sales.

Open the case studyVisit the live site

Plota.app is the eSIM shop I founded in Milan. A traveller should see the country, the data allowance, and the price, then pay and install, without a plastic SIM in between. Next.js on Vercel is the storefront, fast enough to open on a hotel network. Supabase stores plans, entitlements, and usage. Stripe covers the checkout. The same account model has room for a business buyer, so the product is not stuck as a one-person checkout. The live site and the product screens are both the shop.

Client
Plota.app
Location
Milan, Italy
Role
Founder
Period
2026 – present
Stack
Next.js, Vercel, Supabase, Stripe

What changed

  • A checkout that ends in an eSIM install, not a plastic SIM order
  • Plans and entitlements stored where the app can read them
  • Room in the account model for a business buyer

Interface

Plota.app storefront and product screens for buying a travel eSIM.

  • Plota.app interface, view 1. Plota.app storefront and product screens for buying a travel eSIM.
  • Plota.app interface, view 2. Plota.app storefront and product screens for buying a travel eSIM.
  • Plota.app interface, view 3. Plota.app storefront and product screens for buying a travel eSIM.

Open the case studyVisit the live site

Most SEO tools hand over a list. Fix SEO Today is built to hand over the next edit. The product crawls the site, maps keywords to pages that exist, checks schema and an llms.txt, and writes the fix as a sentence someone can ship. Classic technical SEO and the signals answer engines use — clear pages, honest structured data, a file an AI crawler can read — sit in one diagnosis instead of three subscriptions. I worked on that product in Milan. fixseotoday.com is the public product. It does not promise a ranking.

Client
Fix SEO Today
Location
Milan, Italy
Role
Product builder
Stack
Technical crawl, Schema and llms.txt checks, Keyword-to-page map

What changed

  • One crawl for technical SEO and answer-engine signals
  • Keyword notes tied to pages the site already has
  • Fixes written as edits, not as a code list

Interface

Fix SEO Today product site: crawl, schema, and plain-language fixes.

  • Fix SEO Today interface, view 1. Fix SEO Today product site: crawl, schema, and plain-language fixes.

Open the case studyVisit the live site

A missed call is a lost booking. Kalled.app is an AI receptionist: a voice agent that picks up inbound calls and can place outbound ones. The job of the first conversation is intake and qualification, then a concrete next step, not a transcript nobody reads. I worked on the product in Milan so the call has a script the business can trust and a handoff when a person should take over. kalled.app is the public product. The interface is the agent configuration and the call, not a dashboard of vanity metrics.

Client
Kalled.app
Location
Milan, Italy
Role
Product builder
Stack
Voice agents, Inbound calls, Outbound calls

What changed

  • Inbound calls answered without waiting for a person
  • Qualification in the call, with a handoff when it needs one
  • Outbound calls on the same agent, not a second product

Interface

Kalled.app, the AI receptionist for inbound and outbound calls.

  • Kalled.app interface, view 1. Kalled.app, the AI receptionist for inbound and outbound calls.

Open the case studyVisit the live site

About this portfolio

What kind of projects does Ali Imran ship?
Print production for retail and FMCG brands, then software: B2B marketplaces, operations tools, payments, hospitality, and AI products.
Where was the work delivered?
Karachi, Dubai, Hamburg, London, and cities across Italy, plus a C-level sourcing platform for Burgundy. Ali is based in Milan.
Are the screenshots the products that were built?
Product shots are interfaces from the engagement. For print clients, the image is the brand’s public website, shown as context. The case study says which is which. Private tools have no public screen.
Which languages is this site available in?
English, Italian, German, and French. Each language has its own URL, title, and case-study text.
Projects by Ali Imran — clients, products, and print