Need an
e-commerce site?
Let’s build the right one.

I plan, design and build e-commerce around the way your business actually sells, from products and customer journeys to pricing, orders, payments and integrations. B2B is a particular strength, but not a requirement.
15+ years
in e-commerce
B2B, B2C & enterprise delivery
BigCommerce
Agency Partner
Based in Prague
Working across Europe

You don’t need to arrive with a specification.

You know your business. You shouldn’t have to know how an e-commerce platform should be built.

Tell me how you sell today, who your customers are, how pricing works, what happens after an order is placed, what your team still does manually and which systems need to talk to each other.
We’ll work out the rest together.
You bring
the business
Your products, customers, buying behaviour, operations, constraints and ideas, pricing, sales process, existing systems and the things that make your company different.


We work out what you actually need
The right platform, site structure, customer journeys, features, integrations and priorities. Without adding things just because somebody can build them.
Then we
build it
I can turn the plan into a real e-commerce site, work with your existing technical team or bring in specialists where they’re genuinely needed.

The technology comes after we understand the business. Not the other way around.

An e-commerce site
is rarely just a website.

The visible part is usually the easy bit. What matters is everything the site needs to understand about your business.
Products & catalogue
How customers find products, navigate large catalogues, compare options and get the technical information they actually need.
Customers & pricing
Different customer groups may need different prices, promotions, content or buying experiences. In B2B, that can also mean contract pricing and account-specific terms.
Orders & workflows
Orders need to reach the right place, trigger the right communication and remain manageable behind the scenes. For B2B, approvals, PO numbers and account workflows may come into play.
Stock & fulfilment
What is really available, where it is stored, what can be ordered and what should happen after the customer clicks “Place order”.
Systems & data
ERP, PIM, CRM, warehouse systems, payment providers and other tools need to exchange the right information at the right time.
What happens next
Your business will change. New products, customers, markets and processes shouldn’t mean rebuilding the whole thing every year.

You may need all of this. You may need only a small part of it.
The point is to work that out before we start building, not after.

From “we need an online store” to something that actually works.

We start with your business, not the platform. Then we work out what needs to be built, put it into a clear plan and take it all the way to launch if that’s what you need.
01
Tell me how your business works

We talk about your customers, products, pricing, orders, sales process, existing systems and what you want the new site to change.
No technical brief required

02
We work out what the site actually needs

I map the customer journeys, business rules, integrations and features that matter, and separate them from the things that sound useful but probably aren’t.

03
We turn it into a plan

You get a clear picture of the platform, structure, functionality, integrations, priorities and what needs to happen before development starts.
Something you can actually use, not a 90-page document nobody wants to open.

04
Then we build it

If it makes sense for the project, I can handle the implementation too, including configuration, development coordination, integrations, testing and everything needed to get the site ready.

05
We launch. And make sure reality matches the plan.

Before go-live, we test the important journeys and business rules, fix what doesn’t make sense and make sure your team knows how the new setup works.

Need only the planning part? That’s fine too. You don’t have to hire me for the build.
I’m not here to sell you more than you need.

E-commerce can get complicated quickly. But complexity by itself isn’t a reason to build more, buy more software or add another integration.

We’ll start with how your business actually works and make decisions from there.

If something is worth building, I’ll tell you why.

If it isn’t, I’ll tell you that too.

I work best with businesses where e-commerce actually matters.

You may have a large or unusual catalogue, complex fulfilment, several customer journeys, integrations, repeat customers, an existing store that has outgrown itself, or simply a product that deserves a much better buying experience.

Some of those businesses are manufacturers and distributors with complicated B2B requirements. Others are retail brands that simply want a better store.

What matters to me is that there is a real business to understand, not just a template to fill.

That’s part of my job.

You’ll always know what I think.

If BigCommerce is a good fit, I can build the solution there.

If another platform makes more sense, I’ll say so.

If a feature sounds impressive but won’t help your business, I won’t try to sell it to you.

And if something needs expertise I don’t have, I’d rather bring in the right person than pretend I know everything.

B2B or B2C?

The fundamentals are the same: customers need to find the right product, understand it, trust the business and complete the purchase without unnecessary friction.

B2B simply adds another layer: account structures, negotiated pricing, permissions, approvals, complex catalogues and system integrations.

I work with both.

You’ll work with the same person from the first conversation to launch.
No handover to an account manager. No disappearing after the sale. No need to explain your business from scratch every few weeks.
Just someone who already knows why the decisions were made and is there when the awkward questions start.

A bit about me, since we may end up working together.

I’ve spent more than 15 years around e-commerce, from running my own business to delivering complex B2B projects for international companies.
That means I tend to look at a project from both sides: what the business needs to achieve, and what customers and employees actually have to deal with every day.

I’m not a developer, and I don’t pretend to be one. My job is usually somewhere in the middle: understanding the business, working out how the commerce system should behave, and making sure the people building it understand why.

I ask a lot of questions before recommending anything. If something doesn’t make sense, I’ll say so. If I don’t know something, I’ll say that too. And if we need a specialist for part of the job, I’d rather bring in the right person than bluff my way through it.
I like projects where, by the end, I know your business well enough that you don’t have to explain the same thing twice.
15+ years in e-commerce
Enterprise & B2B delivery
Projects for global brands
From discovery to launch
SELECTED EXPERIENCE

Some of the problems I’ve worked on over the years.

01
From scattered requirements
to a buildable e-commerce solution
Enterprise B2B projects where customer groups, pricing, catalogue access, ordering rules and integrations had to be turned into something developers could actually build and test..
In practice: requirements, business rules, customer journeys, user stories, acceptance criteria and UAT.
02
From commerce symptoms
to the real operational problem
Stock, fulfilment and order-flow issues where the storefront was only the visible symptom, while the real problem sat somewhere in data, ownership, integration logic or the process behind it.
In practice: ERP and warehouse data, stock visibility, customer allocations, order flows and the awkward gaps between systems and teams.
03
From complex delivery
to something ready to launch
B2B implementations involving several teams, integrations, business stakeholders and UAT, where the job was to keep the pieces aligned until real customers could actually use the result.
In practice: discovery, delivery coordination, testing, launch readiness, escalations and the cases nobody noticed until someone tried the real journey.
Across projects, this has included
Product discovery & catalogue UX
Making products easy to find and understand through clear categories, search, filters, product information and navigation.
Customer journeys, pricing & promotions
Working out how different customers buy, what they need to see, and how pricing, promotions and account-specific rules should behave.
Checkout, orders & fulfilment
Designing the path from basket to payment, delivery and order handling, including the less visible processes behind the storefront.
ERP, WMS & commerce integrations
Making sure the storefront reflects what the business systems actually know about products, customers, stock, pricing and orders.
Complex B2B ordering & account rules
Customer-specific catalogues and prices, approvals, allocations, purchase orders, account structures and other rules that go beyond a standard checkout.
UAT, launch & operational troubleshooting
Testing how the whole thing works in reality, coordinating launch, and finding whether a problem sits in the storefront, integration, data or business process.

Much of this experience comes from complex B2B environments, but the same principle applies to any e-commerce business: the storefront only works when the customer journey and everything behind it work together.

Thinking about a new e-commerce site?

Whether it’s B2B, B2C or somewhere in between, tell me what you’re planning.
You don’t need a finished specification before we talk.
No pitch. Just tell me what you’re planning.