Reputation, with receipts.
Not a logo wall. A public evidence ledger showing where Michał Piszczek has been quoted, where his ideas have been independently applied, and how original work travelled across markets and languages.
Original insight. External propagation.
The strongest reputation signal is not the first mention. It is what happens after an independent editor publishes the idea and other communities carry it further.
Named, quoted, attributable.
These are the flagship records: an editor selected Michał as a named expert and published his argument under the outlet's own editorial responsibility.
AWS Introduces CloudFormation Express Mode for Faster Infrastructure Deployments
Michał is introduced as CTO at Archdesk and quoted on rollback risk in AI-assisted infrastructure.
"Rollback disabled by default is the detail people will skip past."
Meta's new coding agent is cheap, but it will cost you your data
Three attributed observations on accepted-change cost, safe use cases and zero-data-retention boundaries for product code.
"The useful metric is cost per accepted change after review and repair."
Is Rapid AI Price Deflation A Gift Or An Existential Threat To SaaS?
A named CTO contribution on what collapsing model prices actually change for software economics and defensibility.
What Happens To SaaS Revenue When AI Works So Well Customers Stop Buying Seats?
A full expert contribution, headshot and attribution as Chief Technology Officer, Archdesk on pricing AI agents when automation reduces seats.
The idea left the source.
This is a stronger conceptual signal than a repost: another practitioner explains the framework, separates the original thesis from his own analysis, and applies it to a new operating context.
66%
Multiplying four 90% proof gates leaves roughly 66% accepted autonomy
The author names Michal Piszczek, Archdesk CTO, explains Verification Cost and the complete Proof-Adjusted Autonomy formula, then applies the framework to automation and quality control in Japanese e-commerce operations.
One independent essay, published on two platforms. Counted as one adoption event, not two.
Propagation without self-publishing.
These records repeat, translate or syndicate an editorial quote or an original benchmark. They demonstrate reach, but are deliberately not presented as new independent interviews.
Not everything is a press citation.
Vendor case studies and historical reporting still contribute to reputation when they are labeled honestly and link to inspectable evidence.
How Archdesk redesigned a complex Construction Tech SaaS application
A vendor portfolio case study containing a named testimonial from Michał Piszczek, CTO of Archdesk. Useful product-leadership evidence, not independent editorial coverage.
Sun Microsystem pouczony przez Polakow
An archived report documenting the responsible disclosure of critical issues affecting Sun Microsystems. It anchors the public technical record more than two decades before the current AI work.
The count means something.
A reputation page loses value the moment it treats every scrape, mirror and owned profile as an independent endorsement.
Included and labeled
- Named editorial quotes and interviews
- Independent applications of a published concept
- Translations and syndication with clear source lineage
- Case studies and historical records with context
Not inflated into coverage
- Owned cross-posts and personal profiles
- Articles with a similar thesis but no attribution
- Pitches that did not produce a public citation
- Multiple mirrors counted as separate adoption events
Need a source, quote or technical argument?
Use the media kit for bios and booking, or the citation center for DOI-backed concepts, software and formulas.