Skip to content
chris piskorz

I develop B2B products
from interview to release

I talk to users, design, and see changes through until they use them. Over 10 years in B2B.

Let’s talk for 15 minutes

Does this sound familiar?

The product slowly becomes the topic nobody wants to touch.

  • CEO

    What about the new module? Clients keep asking.

  • Product

    The backlog has 200 items and everything is urgent.

  • Sales

    Clients say they still can't find where to click.

  • Dev

    Works on my machine. The mockup looked different.

What it looks like in practice

A product people
use every day

Task list with the contractor and site manager in Voltiq
A new tool from scratchVoltiq · project lead

The office and the crew work on the same data

A construction management system, from tender to warranty. It runs a live contract in Krakow. The interface is in Polish because Voltiq is built for Polish contractors.

198
tasks in the contract
360
cost items
1,565
photos in one task
7
people using the mobile app
Read the case study
Clients and teams I've worked with
  • tieto
  • comgy
  • pg
  • quppy
  • moonite

Fewer handoffs, more working product

UsuallyWhen we work together

Research, design and delivery pass between teams

One person from the user conversation to a working product

Mockups wait for developers

I test ideas on real data

The loudest opinion sets the direction

How people work sets the direction

The topic ends at launch

I stay and improve it based on real use

From checking the problem to your own tool

Diagnosis with a prototype

When you know something isn’t working, but not yet what to build.

  • Interviews with the people doing the work
  • Problem map and a recommended scope
  • Clickable prototype to show your team

Product sprint

When you know what to improve in your product and want it in a working version.

  • Analysis of one area, such as onboarding or checkout
  • Prototype tested with users
  • Change in the product, or a ready spec for your team

A tool for your company

When a process needs its own app and today runs on spreadsheets and email.

  • Working app for one specific process
  • Data moved over from your current files
  • Rollout with your team and fixes after launch

I quote every scope after a short call, once I know what you are bringing. Price and scope are confirmed in writing before we start.

What working together looks like

  1. Conversation

    15 minutes about the problem. If it's not for me, I'll say so right away.

  2. Understanding the problem

    I talk to the people who work with the product. Together we agree what should change and by when.

  3. Working versions

    You regularly see something you can click and check. After launch we improve it based on real use.

Work on other products

Comgy panel with tenant history
Improving an existing productComgy · senior product designer

Changing a tenant without guessing what to click

Rebuilding a manager's flow around one obvious action. In tests, 11 of 11 people found it.

Read the case study →
Map of oil flows in Chokepoints.io
Chokepoints.io · independent project

Why fuel gets more expensive, explained on one map

Global oil flows down to the price of a litre of fuel in each EU country. The data updates itself.

Open the map →
Calenday app with a trainer's schedule
Testing an idea before buildingCalenday · founder

Schedules for trainers: from interviews to the first licences

16 interviews, a failed first version, a rebuild and the first sales.

Read the case study →

What people I've worked with say

“Working together with Krzysztof means being on a journey to understand your users, the use cases and their pains.”

Franziska Kaiser · Product manager, Comgy

Watch the recording
“He approaches challenges from a broad perspective, ensuring his solutions align with both design and business objectives.”

Aneta Rejdych · Product designer, Tieto

Watch the recording
“He has a talent for explaining complex ideas in a simple and understandable way.”

Marcin Wluka · Product Owner, GSC

Watch the recording
Chris Piskorz
Who does the work

You talk to the person who designs and builds

For over 10 years I have been creating B2B software: data platforms, ERP and MES systems, and tools for teams' daily work. I talk to the people, design and take it to a working version myself, so nothing gets lost between teams.

10+ years
in B2B software
6 apps
ERP and MES for the paper industry
2 × first place
HackYeah and Aquathon
MEDT advisor
government working group
More about me

Questions before we talk

Who owns the code and data?

Once the project is paid for, the code and data belong to your company. We put that in the contract.

What if you stop working on it?

I hand over the code with setup instructions so another developer can take it over.

Where will the data be stored?

We agree on that before the start, along with who has access and how backups work.

Do you use AI?

Yes, for design and building, because it lets me work faster. I am responsible for how it works and for its quality. Client data goes into such tools only if we agree on it first.

Do you write the code yourself?

I started as a frontend developer, but I no longer spend my days in code. I build with AI tools, and my experience lets me judge what comes out of them. I am responsible for the result. If a project needs an additional developer, I say so right away.

Can you join an existing product and team?

Yes. I start by learning the product, the team and the users, then work with your team or on my own, depending on what you need.

How long will it take?

We set the deadline once I understand the problem, because before that it would be an empty promise. We put it in writing with the scope and price.

How does payment work?

We agree on scope, deadline and price in writing before the start. 50% is due at the start, the rest on acceptance.

How much of my team's time will it take?

A few conversations at the start with the people who work with the product. After that, short reviews of what has been made.

Will you sign an NDA?

Yes, if the project needs one. We can do that before we discuss details.

Do you work with companies outside Poland?

Yes. I work remotely, in Polish and in English.