A clear starting point for our collaboration.
Good collaboration starts with shared expectations. This guide explains how I combine product design, working prototypes created with AI, and visuals tailored to the brand — and how we organise scope, communication and billing.
Whether you are building a new product, improving an existing one, or exploring an idea through a working prototype, these details will help you prepare for a conversation about your project.
01. Expertise and scope
From business goals to designs you can see and explore.
Product design connects user needs with business goals. My work develops UX architecture, interfaces and visual direction together. Depending on the project, I also create working prototypes or visuals with the help of AI.
We can work on a complete experience or a specific part of a product. The starting point is what you need: a structured design, a way to explore interactions, or a stronger visual direction.
Websites and online platforms
Corporate websites, product landing pages, and marketing or social platforms. We define the purpose, organise content and user journeys, and translate them into a coherent interface. Where we need to explore how the website behaves, the scope can include a working prototype.
Web and mobile applications
From SaaS platforms to mobile applications, I help organise complex functionality and make it easier to use. The project can cover key flows, individual modules or a complete experience. A prototype can demonstrate selected interactions and states before further implementation.
E-commerce
Online stores, marketplaces and custom commerce experiences. I connect product discovery, product pages, cart and checkout into a clear purchasing journey. The design can be supported by a prototype of selected steps and visuals consistent with the brand.
Design systems and implementation support
I work with existing design systems or create project-specific foundations and components. I collaborate with developers and branding specialists to keep design decisions consistent through implementation. A prototype can help explain interactions, but it does not replace technical planning.
AI visuals & vibe coding
I create visuals tailored to the brand and turn designs into working prototypes using AI and vibe coding. This lets us explore layouts, interactions and visual direction in action rather than reviewing static screens alone. We agree on the scope and level of refinement according to the project's purpose.
02. The design process
Understand. Design. Deliver.
The process stays consistent whether the outcome is a Figma design, a working prototype or a set of visuals. We start with the goal, develop the solution, and hand over the agreed deliverables with the context needed for the next stage.
Understand
We clarify business goals, users, the current situation and constraints. I review the materials you provide and, where useful, we work through workshops. We decide what needs design, what is worth exploring in a prototype, and where AI visuals can support the visual direction. This informs scope, priorities and the estimate.
Design
I develop UX structure, flows and the interface, using an existing design system or creating the foundations we need. Within the agreed scope, I also develop visuals and a working prototype with AI. We review the outcomes together, explore interactions and refine the solution through feedback.
Deliver
I organise the agreed outputs: Figma designs, visuals or a prototype. I explain what has been developed, its limitations and what needs further work. If the project moves into implementation, I collaborate with developers to preserve design decisions and define the next steps.
These are not isolated stages. We can revisit decisions when a review or prototype reveals new needs. Prototyping supports decision-making; it is not, on its own, proof of effectiveness or readiness for release.
03. Deliverables and handoff
Clear scope. Deliverables you can build on.
Not every project needs the same outputs. Depending on the agreed scope, deliverables may include UX flows, interfaces and components in Figma, visuals tailored to the brand, or a working prototype demonstrating selected features and interactions.
Before we start, we define what you will receive, in which format and for what purpose. For a prototype, we also clarify which behaviours are functional and which use demonstration data or simulation. If handing over code is part of the scope, we agree on how it will be shared and developed further.
A working prototype is not automatically a release-ready product. Integrations, real data, authentication, payments, security, accessibility and maintenance require a separately defined scope and appropriate verification. Responsibilities for further development are agreed with the implementation team.
For visuals, we agree on their intended use, formats and handoff. Usage conditions also depend on the source materials and selected tools, so we discuss them before using the assets in the final product.
04. Collaboration models
Flexibility when you need it. A defined budget when the scope is clear.
I work in Time & Materials and Fixed Price models. These cover design as well as agreed work on prototypes or visuals. We choose the model based on how clearly the scope is defined and how much the solution may evolve.
Time & Materials
You are billed for actual hours worked. This suits evolving requirements, visual exploration and iterative prototyping, where each review can influence priorities.
I track time in Toggl and share reports. Using AI does not replace design, selection, refinement or checking the outcome — these activities remain part of the work.
Fixed Price
We agree on a specific scope and budget. The price is based on the upper end of the estimated hours multiplied by the agreed rate. This suits clearly defined deliverables, prototype features and acceptance criteria. We discuss changes beyond the agreed scope before carrying them out.
How estimates work
If a task is estimated at 20–30 hours, the Fixed Price calculation uses 30 hours at the agreed rate. For prototypes, estimates also consider interaction complexity, how data is handled and the level of refinement. For visuals, they consider intended use and the work required. Examples are references, not fixed-price packages.
Hourly rate
- per hour · Polish clients
- 220 PLN
- per hour · international clients
- 60 USD
If a project needs paid tools, assets or external services, we agree on access and how costs will be covered before using them. We do not assume they are included in the hourly rate or add them without agreement.
The examples in Notion provide additional context. Current scope and rates are agreed using the information on this page and a conversation about your project.
05. Communication and reporting
Clear communication — including when the design comes to life.
I work closely with you and your team. We keep project discussions together and administrative matters separate. The review format follows the outcome: discussing screens, exploring a working prototype or comparing visuals.
Project communication
I prefer a dedicated Slack channel and recommend weekly check-ins. We discuss progress, gather feedback and agree on next steps. For prototypes, feedback is most useful when it identifies the view, action and expected behaviour, helping us distinguish a design decision from a bug or a demonstration limitation.
Tools and work reviews
Figma remains the main workspace for interface design. I share prototypes and AI visuals in the format agreed for the project. Tools are selected according to the goal and the team's requirements; I can also work with Jira, ClickUp or Asana. We agree on how data and materials may be used in AI tools before sharing them.
Time reports and invoices
For Time & Materials, I share detailed Toggl reports every two weeks and a monthly summary with the invoice. Reports cover agreed design work, visuals and prototyping. Fixed Price payments follow agreed instalments. Administrative matters are handled by email.
06. Getting started
Start with the goal. We will choose the right format together.
You do not need a finished specification or a decision about whether you need designs, a prototype or AI visuals. Tell me what you want to achieve, where you are now, and what needs to be seen or explored to move forward.
Suggested preparation checklist — an aid, not a contractual requirement:
- The business goal or problem to address.
- The product's audience and their key tasks.
- Your current website, application, design or other available materials.
- Areas of support: UX/UI, a design system, visuals, a working prototype or a combination.
- Interactions and scenarios you want to explore in a prototype.
- Brand materials, references and restrictions on using photography or data.
- Known budget, timing and technical constraints, including requirements for AI tools.
- People responsible for reviews, decisions and further implementation.
We use this context to define the outcome, scope and acceptance criteria. I prepare an estimate, and we agree on the collaboration model and initial payment before starting. If you need a product for release, we distinguish prototyping from further implementation work from the outset.
07. Questions and answers
Questions and answers
What kinds of projects do you work on?
Websites, online platforms, web and mobile applications, and e-commerce. I also work on design systems, AI visuals and working prototypes created through vibe coding. We tailor the scope to the project's goal.
What does vibe coding mean in your work?
It means creating working prototypes with AI, guided by design decisions and iteration. It lets us explore interfaces and interactions in action. It does not automatically mean production-ready software or skipping technical verification.
Is a prototype ready to release immediately?
We do not assume that. A prototype may use demonstration data or simulated features. Before release, we need to define and verify implementation requirements, including integrations, security, accessibility and maintenance.
Can you work on just part of a product?
Yes. We can focus on a particular flow, module, set of visuals or interaction prototype instead of designing the entire product.
Can you work with our design system and developers?
Yes. I use existing systems or create the foundations we need. Designs and prototypes help communicate decisions, while we agree on implementation and further work with your developers.
What will we receive at the end?
The outputs agreed before we start — for example, Figma designs and components, visuals or a working prototype. Handoff format, any code delivery and the outcome's limitations are defined in the project scope.
How do you use AI for visuals?
I create visuals tailored to the brand and the project's direction. We agree on their use, formats and application. Usage conditions also depend on source materials and tools; we do not assume unrestricted rights to every generated image.
Which collaboration model should we choose?
Time & Materials suits exploration and iteration. Fixed Price suits clearly defined scope and deliverables. This applies to UX/UI design, visuals and prototypes alike.
What is your rate, and does AI change how work is estimated?
The rate is 220 PLN per hour for Polish clients and 60 USD for international clients. Estimates reflect agreed work and complexity, not simply the number of generated screens. Any tool or external service costs are agreed separately.
Are the Notion examples a current price list?
No. They provide reference material and may not cover the latest service scope. Current information is on this page, and I prepare an individual estimate from your goals and project scope.
What should we prepare, and how do we handle confidential data?
Goals, brand materials, key scenarios and known constraints are useful. Before using confidential data or materials in AI tools, we agree on what can be shared. For demonstrations, we can define sample data instead of using real data.
How can we follow progress and share feedback?
Through ongoing communication and agreed reviews of the design or prototype. I prefer Slack, recommend weekly check-ins and can adapt to your team's tools. For Time & Materials, I share Toggl reports every two weeks and a monthly summary with the invoice.
Looking for more context?
Additional materials and examples in Notion.
Notion contains further documentation and examples of earlier estimates. Treat these as context, not a current price list or a complete description of today's services. The latest collaboration scope is described on this page.
Explore additional materials (opens in a new tab)