HANGAR · RAW MATERIAL: SOMEONE ELSE'S IDEA · DWG MM-001
How an award-winning idea became a platform with foundations this market does not have.
Case study: MyMajster — someone else's raw material in my workshop. And a test of whether the Method works both ways.
PASSAGE PROTOCOL · KARBONADO METHOD · MACHINE ON THE HOIST
01RAW MATERIAL ON THE TABLEA 2021 award-winning idea, four years in a drawer, a market offering two bad options✓ 02WILL IT FLY?Dozens of questions before any quote; an analysis of why everyone else failed✓ 03STRUCTURAL BLUEPRINTAn investor-grade Blueprint: model, finances, rollout maps, system architecture✓ 04BUILD IN THE WORKSHOPVisual layer complete; application architecture in final polishingin progress 05ENGINE AND TICKET MACHINEFounding community and participant economics — designed on the drafting table, before any codedesigned 06FLIGHT AND HANGARField phase — the runway belongs to the pilotbefore take-offIn this hangar I only show machines I can vouch for with my signature or my stake — two of my own, and one, brought in, where I am the architect of the whole and a co-owner.
The best ideas rarely lose to the market. Most often they lose to something far more banal: the absence of someone who can build them.
In 2021, a practitioner from the installation-and-construction trade — a man who professionally stands between the client, the supplier and the installation crew, and knows this market from daily work in the field — won a regional competition for the best business project. The idea: a portal connecting clients planning renovations with verified contractors. The jury had no doubts. Neither does the market: everyone in Poland knows the problem of finding an honest tradesman.
And then came what happens to most award-winning ideas. Nothing.
For four years the project did not move. Not because the originator lost faith — because the market offered him only two options, both bad. Option one: agencies and freelancers who will quote the job, deliver the milestones and disappear — leaving a product that looks like the idea but does not think like a business. Option two: build it yourself — which means not building it at all, because nobody constructs the architecture of a transactional platform after hours, learning on the way. The award-winning idea went into a drawer. Where most great ideas in this country end.
On the neighbouring machine in this hangar — SoundDNA — it took me three years to mature into my own idea. Here, four years were eaten by a drawer. The difference is fundamental: your own material matures in that time. Someone else's only waits.
Great ideas do not die because they were bad. They die because between an idea and a product stands a competence that cannot be bought by the hour.
We met in 2025 — over a matter that had nothing to do with this project. That is how it usually goes with important things. After some time, once trust had been built, I heard a sentence I have heard many times in my career, but rarely with such a history behind it: “I have an idea that once won a competition. Can you help me build it?”
I could have answered like a contractor: ask for a specification, quote it, build exactly what was requested. Thirty years in IT — from running IT in one of Poland's largest banks, through corporate systems that have no right to fail, to my own ventures in Poland and abroad — taught me that this is the worst possible favour. Because I would have received the specification of a classifieds portal. Another one. And the market of tradesman-classifieds portals is a graveyard: they all work the same way and none has solved the problem.
So instead of a quote, we started with questions. Dozens of questions. Why do the existing portals fail? What does a contractor feel when he has to underbid the cheapest? What is the client really afraid of? Where in all this is the money, and where is the trust — and why has nobody connected the one with the other?
In the Method, these are stages 01 and 02: first all the raw material on the table, then the wind-tunnel trial — before the first line appears on the drafting film. Material laid down in 2021 passed its trial only in 2025. And rightly so — because the trial changed the aircraft.
And here is the heart of this case study — the thing I have seen in every successful project and missed in every failed one: ideas develop during execution. The idea brought into a collaboration and the product that comes out of it are never the same — if the person across the table is a partner, not a contractor.
A contractor builds what is in the specification. A partner with grounded, multi-industry experience asks the questions the specification did not anticipate — and it is those questions that change the project. A few examples from this collaboration, at the level I can disclose:
One question about participant economics — “what will this company get for its money in the first, hardest year?” — rebuilt the platform's entire value model and the way it treats its first partners. Out of a “portal collects fees” model grew a founding-community model, in which the first participants grow together with the platform on terms nobody will get later. This is stage 05 of the Method in its pure form: the engine and the ticket machine designed on the drafting table before a single line of code — because growth should be built into the structure, not glued on after launch.
An analysis of other people's failures — instead of asking “what shall we build?”, we asked “why did everyone fail?”. The answer: because everyone was building software, while the problem lies in trust — and trust cannot be installed with an update. Thus was born a foundation no platform on this market has: a person in the field who personally verifies contractors and signs off completed work with a protocol, in every region of operation.
Experience with financial systems — translated into a transaction-security architecture designed in layers, with a clear division of legal responsibility — and into detecting, ahead of time, several regulatory traps this project would have run into at full speed had it been built by someone who knows only code.
Modelling discipline — every element of the model passed an internal-consistency test: revenue streams, retention mechanisms, growth structure. Wherever the numbers did not hold, we changed the model, not the numbers.
The result: an idea that entered the collaboration as “another classifieds portal for the renovation trade” left it as a platform with foundations unavailable on this market — with solutions nobody in this industry has implemented before. Not because the originator was wrong. Because the idea finally landed in conditions where it could grow.
It is not enough to hire just anyone to build. Ideas develop during construction — but only when built by someone who has something to develop them with.
The architect's role in such a project does not end with technology. The scope of this collaboration covered the full spectrum — from strategy to delivery:
Business architecture: rebuilding and stress-testing the model — revenue streams, retention and self-regulation mechanisms, growth structure, defences against copying.
System architecture: a platform designed to scale in stages — from a minimal-cost start to infrastructure ready for growth, without burning capital in advance.
Complete investor-grade documentation: a strategic document of several dozen pages with a full financial model and scenarios, rollout maps with decision gates and metrics, negotiation materials and the project's public narrative. In the language of the Method: this is the stage-03 Blueprint — in its heavier form, because a transactional platform needs a design not only of its structure, but of its money flows and responsibilities.
Product layer: the platform's complete visual layer, with the application architecture in final polishing.
One thing I will say plainly, so nobody has to discover it on their own: in this project I am not a service provider with an invoice. I believed in this venture enough to enter it with my work as architect — as a co-owner. It is one of the few partnership paths I ever agree to (the rules are described on the Collaboration page), and that is exactly why this story hangs in my hangar: I vouch for it not with an opinion, but with a stake.
The platform's visual layer is complete, the architecture underneath is in its final polish, and the project has entered the field phase — the one that belonged to the originator from the start, and where he is at his best. Each of us doing what he is a master at. Exactly how it should have looked since 2021.
And here this venture tests something no other has tested: the symmetry of the Method. I answer for the machine — up to the hangar door. The take-off, the fuel on his side and the first passengers belong to the pilot. The Method works both ways or it does not work at all — and this page will be an honest record of that, whatever the outcome.
STATUS: FIELD PHASE · THE RUNWAY BELONGS TO THE PILOT · 2026-07-22
An idea without a builder is not an asset — it is a liability. It reminds you of itself for years and costs more nerves than the build would have cost. Four years in a drawer is four years of market conceded by walkover.
A contractor will deliver the schedule. A partner will develop the idea. The difference shows not in the quote, but in the questions asked before the quote. If nobody challenges your assumptions — you do not have a partner, you have a vendor.
Look for multi-industry experience, not just technical skill. The best decisions in this project did not come from knowledge of code — they came from the intersection of banking, corporate systems, own businesses and an understanding of people. An idea grows at the crossings of experience, not inside a single specialisation.
Do you have an idea that deserves more than a drawer? Before you ask for a quote — let us talk about the questions your idea has not heard yet. Sometimes one conversation changes a project more than a year of building.
The first conversation costs nothing and promises one thing: I will tell you honestly whether I will build a machine that flies.