Štefan Toporcer
Get in touch

Štefan Toporcer · product designer

From idea to finished product.

I've been designing digital products since 2009. Today, with AI, I also build them myself, without a development team: small software tools for boring, bureaucratic problems, for local and global markets.

Engine room17 engines

Running · 3

All engines

Engine room

Boring engines

Every project is an engine: a small automated machine for one boring problem. Some are running, some are warming up, others stand and wait their turn. This is the whole engine room.

Permit SignalRunning

59,721

events in the database

Livechecked every day

13970059123329
New events by week
12,826facilities tracked
0AI tokens per customer
Poriadok.aiRunning
36regional public health offices in Slovakia
14regional hygiene stations in Czechia
2verified document types
Feed FactoryWarming up
27manufacturers in the research
8confirmations needed to go ahead
Retrofit CERunning
12questions in the free screening
3possible verdicts: substantial, not substantial, borderline
490€ excl. VAT for the optional pre-filled draft dossier

How I build

  1. DesignInterfaces and complete product flows in Figma
  2. Vibe codingI write code with AI in Claude Code and Cursor
  3. Automation and databasesMake.com, SQL in Supabase and payments
  4. LanguagesProducts in several languages from day one; this site has 11

Running3

Live and in use.

Warming up9

Not sold yet, on purpose. Each one is testing whether enough companies want it, most with a free output you can try now. The paid version starts only once they do.

Tested, demand was too low for now. Ready to restart when the market moves.

Closed. Its parts and lessons live on in other engines.

Workshop operating rules

Why I build boring engines

I want to build my own income from my own products. Today I no longer need a development team for that, and I want to make the most of this opportunity. I do business both locally and globally: some engines solve problems in Slovakia and Czechia, others serve customers anywhere in the world. I start with small engines that tackle a clear problem at low cost. I learn something from each one, even the ones that fail, and work my way up to bigger, more complex projects. These are the rules I use to choose and build every engine.

Boring problems are the best problems.

Hygiene regulations, compliance records, product data stuck in Excel. Nobody enjoys this work, so few people do it properly. Companies are glad to pay for a fix, because the alternative is a fine, a lost distributor or a weekend with a spreadsheet.

An engine has to run without me.

I have 10 to 20 hours a week for this. So I only build things that run on their own: the data gets pulled, the document gets assembled, the alert goes out. One more customer must not mean one more hour of my time.

The number decides, not the mood.

My first projects didn't fail on technology. They failed because nobody got in touch. Now every engine has a number, set in advance, that decides whether it continues or stops. Feed Factory, for example, only continues if at least 8 of the 27 manufacturers in the research confirm the problem.

Design is an unfair advantage.

In industries that still run on PDF forms, a clear questionnaire and a well-typeset document are enough to put a product a class above the competition. This is where my years in design pay off the most.

Accuracy before speed.

A mistake in a legal document would mean a problem for the customer, so I leave nothing to chance. I check every mandatory point of a regulation word for word against the official text. I'd rather not support an option than guess its wording. Every document also goes through a human check before it is sent. Where regulations require it, the relevant authority approves it too, in Slovakia for example the regional public health authority. Every project has its own specific requirements.

About

A designer who also builds his products

Štefan Toporcer
Štefan ToporcerProduct designer · since 2009
Get in touch

I'm Štefan. I've worked in design since 2009: I started with graphic design and motion design, moved on to digital products for fintech and made my way to healthcare.

Alongside design, I spent years in sales and tried running my own businesses several times. Some worked for a while, others not at all. B2B sales in Slovakia, Czechia and Cyprus taught me that a great product isn't about code, it's about a solved problem. And that someone has to want it and someone has to sell it.

Every idea ran into the same wall: without a development team, I couldn't build the product. With AI, I now can. That's how the boring engines started: small products I can build myself, meant to earn money.

I do vibe coding: I build products with AI tools like Claude Code and Cursor, from the interface through the database to payments, and I test and verify every output. The goal is clear: work my way up from small tools to my own app or software that solves a bigger problem.

Why Projekt Argo?

The Argo was the ship on which the Argonauts set out for the Golden Fleece. It was built with the help of the goddess Athena, and in some versions of the myth it was the very first ship. Projekt Argo is my business ship. Where the Argonauts had Athena, I have AI. And my Golden Fleece is my own income from my own products.

Type
Product designer who builds
In service since
2009
Languages
SK · CZ · EN
Markets
SK · CZ · CY · US · UK/IE
Team
led teams of up to 10
Tools
Figma · Claude Code · Cursor · Make.com · Supabase · SQL · Cloudflare
Education
UX Design Institute; School of Applied Arts Prešov, graphic design
Based in
Slovakia

I design

Interfaces, design systems and complete product flows for healthcare, fintech and B2B tools. I know where people get stuck in a form and how to fix it.

I sell

B2B sales in three countries, including EdenHaus fleet management. Cold emails, follow-ups, negotiations.

I build

With Claude Code and Cursor I build complete products: data pipelines, Make.com automations, document generation and payments. No team, minimal budget.

How I think

Two halves, one engine

Splitting the brain into a logical and a creative half is a metaphor, not neuroscience. But it is exactly how I think about my work: every engine needs both.

Left: analysis

  • Processes, data and automation
  • Numbers and measurable goals
  • B2B sales and negotiation
  • Legislation and word-for-word accuracy

Right: design

  • Interfaces and complete product flows
  • Motion and visual language
  • Brand and story
  • A feel for where people get stuck
An engine only comes to life when both halves work together.

Design without a number is decoration. A number without design is something nobody uses.

Collaboration

Who I can help

This site has two purposes: to show what I build and to find the people it will help. I am looking for those who will use my engines and automations, finished ones and the ones still taking shape, and those it makes sense to work with. If you recognise yourself in one of the three points, write to me.

You have an idea but no team

I will turn it into a working product, from the design to the finished thing. With AI instead of a development team, so it is fast and needs no agency budget. First we check that someone wants it, only then do we build.

You need a product designer

Interfaces, product flows and design systems for fintech, healthcare and B2B tools. For a single project or long term, and if needed, I build what I design.

You want to use or grow an engine

Does one of the engines solve your problem or fit your market? Try it among the first, or become a partner who can sell or knows the industry from the inside. Terms to suit, with no big commitments at the start.

Write to meI usually reply within two working days, in Slovak, Czech or English.

Contact

Got a boring problem?

Write to me if you need a product designer who also builds what he designs, if you have a boring problem that should run on its own, or if you'd like to be the first to try one of the engines.

Describe it in a short formA short form. I usually reply within two working days.

E-mail

toporcer.stefan@gmail.com

I reply in Slovak, Czech or English.