Case studies

Real projects,
start to finish.

What each client needed, the decisions I made, the hardest part, and what changed after launch.

FicoTradingHub

22+ traders now
publish their results.

Filip's trading community kept its trades in Excel sheets. I planned, designed and built a Webflow website and a trading journal in Next.js that replaced them.

Client
FicoTradingHub, Filip (founder)
My role
Architecture, design, Webflow build, app development
Timeline
2.5 months of building, 1 month of testing
Stack
Webflow, Webflow CMS, Next.js, Claude Code
The FicoTradingHub site, as it runs today.

Context

Filip and I met through social media. He runs FicoTradingHub: a 90-day mentorship for beginners, a VIP group, 1-on-1 coaching, and a free Discord and YouTube community.

He came with two goals: a website that gives new members the basics in one place, and a web app that brings transparency to the community he already had. There was no hard deadline, and I didn't promise one. Filip followed every step; near the end he got the finished result for one last review, and a week later, after my own final check, we went live.

Problem

The community tracked its trades in Excel sheets. A spreadsheet gives no simple overview, and it keeps every result locked in a private file. Filip wanted the opposite: a clear picture for each trader, and a place where anyone who wants to can publish their results for the whole community to see.

Process

The site

We chose Webflow together. It is a no-code platform Filip can edit himself, and its CMS leaves room for the content he plans to add. I built every page with SEO in mind from the start.

The journal

The journal is its own Next.js app, linked from the site: Webflow runs the public pages, the app handles members and their data. The architecture, the idea, the design and the plan are mine; I wrote the code with Claude Code as an assistant.

The hard part

Understanding what traders actually want to log and follow. I did thorough research into how serious traders keep their records, and that opened the door to smarter features: ones that let a trader analyse their strategy in more depth than a spreadsheet ever could.

Solution

The website

A home page with the programs and an FAQ, a ten-chapter learning section that goes from market structure to trading psychology, and a direct way into the journal.

Result

22+active members publish their results, and more use the journal privately

3.5months from start to launch: 2.5 of building, 1 of testing

Less hassle and more transparency than spreadsheets gave, and a site that brings steady traffic thanks to careful SEO.

Extremely professional from start to finish, communication was top-tier the whole way, and I'm genuinely happy with the end product.
FilipFounder, FicoTradingHub

Running a community that still lives in spreadsheets?

Servee

2.5 months from idea
to a live café.

Servee lets guests order from the table with one scan, and sends every order straight to the waiter, the bar and the kitchen. The idea, the design and the build are mine.

Type
My own product, for cafés and restaurants
My role
Idea, product and UI design, architecture, development
Timeline
2.5 months from the idea to the first café
Stack
Next.js, Supabase, Claude Code, Figma, Affinity
servee.ba, the product's own site.

Context

The idea came from my own night out. I waved at the waiter and called him, and in the rush he never saw me. I wasn't in the mood to talk to anyone that evening either. Ordering straight from the table would have solved both, and hospitality is full of moments like that.

Problem

In a busy café, guests wait to be noticed, waiters walk back and forth taking orders by hand, and scribbled notes ("table 5, two coffees, one without sugar, the other maybe iced?") turn into mistakes. The owner only knows what is happening while standing in the room.

Process

A QR code, not an app

A code on the table is the fastest way in: the guest scans, orders and enjoys, with nothing to download.

Supabase and Next.js

Supabase is fast, reliable and simple to connect, and it replaces a stack of extra servers that would likely have run worse. Next.js serves the pages quickly on a phone, straight after the scan.

The hard part

Making the system take a large number of orders at once without delays, errors or stalls. Optimisation was the key, so that every step stays fast and smooth for everyone: the guest, the waiter, the bar and the kitchen.

Solution

Guests scan, browse the menu, order and swipe to confirm. Waiters know about the order at once. The bar and the kitchen each get their own part of it. Owners see orders, tables and takings live, from anywhere; adding a table and printing its QR code takes a minute, and any item can be featured in one click.

Result

2.5months from the idea to the first café using Servee

That first café became the case study that opened the door to a café chain.

The system is excellent and the idea is top-notch. It speeds up everyone's work and everyone is happier. I like having my own owner dashboard, where I can see the full analytics of the café, even from home.
Owner of the first café using ServeeTranslated from Bosnian

Have an idea for a product that fixes an everyday problem?