Product Designer. I prototype
and ship in code projects that work.

Overview

Future Processing - a software house with 800+ people - was shipping every client pitch from a slightly different file. Sales reps kept local copies of the old template, logos and brand identity assets lived in chat threads and shared drives, and a new deck usually meant rebuilding from scratch. No two decks looked the same and nobody knew which one was current.

Solution

With the team I designed a deck system: a single PPTX Master file split into nine sections, each solving a specific job in a sales conversation with its own layout rules and component library. By our estimate a new pitch takes about 20 minutes to assemble, without opening a design tool.

The system in numbers:

1. 60+pre-designed slides covering every sales scenario.
2. 9section types with strict layout rules and live components.
3. 800+employees with access to one Master file.
4. ~20 minto assemble a new pitch, no design tool required (estimate).

Inside the system

• Designer's note - the brief behind the brief
• Main slides - workhorse layouts across 9 sections
• Documentation, inside the file (Read Before Use section)
• The result - adoption, scale, speed

Reflection

One PPTX file carries the asset library, the icons, the palette and the writing rules, with a short "Read Before Use" section right at the front so a new user sees how to use it before they see the cover.

The outcome: a system in use since 2024, refreshed every six months alongside the company identity (adoption), one source of truth available to 800+ employees (scale), and fewer revision requests with faster client delivery (speed).

Tools & Technologies

• PowerPoint
• Figma
• Illustrator
• Photoshop
• PPTX Template
• Design System
• Documentation

Overview

After a visit to the allergist with my son, the doctor asked me to keep a log - symptoms, reactions to pollen, meds taken - and bring it back next visit. I did not want another paper notebook, so I decided to properly get to know Claude Code and build the tool I actually needed. No team, no big budget - a few late evenings and a few burned tokens.

I wanted something simple:

1. 1Info about what is pollinating in my area today and how strong it is.
2. 2A fast calendar entry with overall mood and the meds given.
3. 3Monthly reports I can print for the doctor.
4. 4Bonus feature: chat with an in-app AI assistant about entries and correlations with meds.

Solution

Built solo end-to-end with Claude Code. The PRD (product requirements document) and the first working build shipped the same day - roughly 3 hours from PRD to a working MVP. Then regular evening sessions across a few weeks: steadily adding features and testing.

The daily loop is intentionally tiny: one screen, one entry, mood + meds, done in seconds - so I can log while my son is in the room. Pollen levels for my area load automatically from Open-Meteo (no good free Polish API). A monthly report view exports everything the allergist needs, in the order they asked for it.

On top of that sits an in-app AI assistant that answers questions about the entries and can correlate them with the meds taken. The same assistant is also reachable from the outside via API or MCP (the protocol other AI tools use to connect to apps) with your own token, so future integrations do not depend on me touching the code.

Inside the app

• Home - today at a glance
• Fast entry: mood + meds
• AI assistant, answers about your entries
• Calendar overview
• History timeline
• Plans: Stripe subscription (test mode)

Where the AI got it wrong

The AI checked its changes on desktop. Two bugs only showed up on a real phone:

• The mobile menu did not navigate. The AI built separate headers for phone and desktop, and the close-on-outside-click logic tracked only the desktop one, so every tap closed the menu before the link fired. I pointed at the phone vs desktop difference and the fix took under an hour.
• The calendar opened on the wrong month. When reopened, it showed the month it was last closed on instead of the right one.

Data and business model

• The database (Supabase) is hosted in the EU, in Ireland.
• The AI model (xAI) receives the entry history: mood, meds and pollen, so the assistant can compare, say, the same period a year ago.
• The demo runs on made-up entries. Only the current pollen data from Open-Meteo is real.
• Business model: a Stripe subscription, in test mode for now.

Reflection

I work with Claude Code like with a developer I hand tasks to: with a solid PRD it ships, while I own the product decisions and check the result on a real device.

Tools & Technologies

• Claude Code
• Notion
• GitHub
• Vercel
• xAI
• Next.js
• React
• Tailwind
• Supabase
• Prisma
• Open-Meteo API

Overview

Problem: Transport Garda moves motorcycles, bikes, equipment and business deliveries across Poland by van. Customers land on the site in a hurry, on a phone, looking for three things: will this company take their load, will it arrive in one piece, and what is the fastest way to get in touch.

Solution: A single screen with no scrolling: three slides on the offer and the tie-down system, a strip of real past jobs, a panel with the van's specs and contact details always at hand. The site runs in Polish and English, and all of its JavaScript is about 3 KB.

Contact in one click

The phone number and email address are on every screen. Clicking the number starts a call straight away, and the icon next to it copies it to the clipboard, confirmed with a "Copied to clipboard" message. The email address works the same way.

• The quote slide lists what to have ready before calling.

• A slide on tie-downs answers the worry that the bike will shift on the way.

• The "Past jobs" strip shows seven real runs without leaving the page.

• Each job has its own address, so it can be sent to a customer as a link.

• Load space dimensions let customers check whether their load fits before they call.

On a phone the same content stacks into one column: phone number and email stay on top, slides switch with arrows, and a wide "Past jobs" button stays at the bottom of the screen, under the thumb. Job and spec panels open full screen, photo on top and details below, so they can be browsed one-handed.

Tools & Technologies

• Claude Code
• GitHub
• Astro
• TypeScript
• HTML / CSS
• Schema.org

Overview

Iceberry is a Swedish IT and QA consulting firm (iceberry.se) that came to us at Future Processing wanting to attract new clients and stop looking like every other consultancy on the market. The brief was a full refresh: a rebranded logotype, a new colour system, and a completely different breath for the website - with one hard requirement, it had to stand out with something genuinely original.

Solution

I built a key visual that fused real photography with hand-drawn doodles and marker illustrations - a human layer laid on top of a business photograph, so a B2B company could speak in a language B2B usually does not. On top of that, I drew a full custom icon set by hand and carried it through the whole site as one consistent visual system.

What made up the rebrand:

• A new logotype and refreshed colour system.
• A key visual combining real photography with hand-drawn doodles and marker strokes.
• A full custom, hand-drawn icon set carried across the entire site.
• Lottie animations for the key visual and selected icons, playing in the browser.
• End-to-end delivery by a two-person team: design (me) and development (Marcin).

Custom hand-drawn icon set

Zoomed in - the hand behind the line stays visible.

• Leadership
• Quality Testing
• UX & Product

Reflection

In 2022 we wired every animation into the page by hand with the developer. I drew the icons by hand, split them into smaller parts in SVG and animated them in Lottie, so they kept the feel of a hand-drawn line in the browser.

The outcome: a site that stood out from other consultancies, an illustration system the client could reuse beyond the website, and a project that went live for the client.

Tools & Technologies

• Illustrator
• Photoshop
• After Effects
• Figma
• Lottie
• SVG Animation
• HTML / CSS
• Hand-drawn Illustration

I have 18 years of experience across branding, UI, websites and print. For the last 10 years I worked with Future Processing, a B2B software house, where I built a presentation system used by 800 people and designed products and websites for clients in Norway and Sweden. See the Pitch Deck System case →

Before that, from 2008 to 2016 at the GONG / AMP Media agency, I delivered campaigns, key visuals and websites for Żywiec, Knorr, L'Oréal, Aviva, Algida, Maspex and Ecco.

Outside client work I have run my own brands, such as Szkicopis - under that name I made a notebook in collaboration with OFF Festival. Polisze is a craft studio I founded in 2015: hand-finished second-hand clothes with prints based on my own and my kids' ideas.

One of my first interactive projects was an ActionScript module listing race tracks and their locations for Red Bull As w Karcie, a nationwide campaign featuring Sebastian Vettel in 2010.

Today I direct Claude Code through the full build, from scratch to production, using React + Next.js (shadcn, Tailwind, GitHub, Vercel). My first product built end to end is the Allergy Diary App, which is still in development.

Skills

• Product Design
• UI Design
• Prototyping
• Design Systems
• Branding
• Web Design
• HTML / CSS
• Motion Design

Tools

• Figma
• Photoshop
• Illustrator
• After Effects
• Premiere
• PowerPoint
• Claude Code
• Cursor
• GitHub
• Vercel
• Notion
• React
• Next.js
• Tailwind
• shadcn/ui