Wavect GmbH

More than Engineers. We build Software products that hit Product-Market-Fit. We have processes and the experience to increase your odds of achieving PMF both tailored for startups from the idea to growth stage, and corporate venturing.

Managing Partner - Fractional Co-Founder ➝ Build (Software Development) ➝ Break (QA / Testing)

We develop Smart Contracts, DApps, Infrastructure such as Wallet solutions & Bridges and on-chain Protocols. But most Web3 projects don't lack Engineers, they lack Product experience to build something the market truly wants. We do both.

Managing Partner - Web3 Product Studio

Enterprise CSR (Corporate Social Responsibility) campaigns on scale.

Founder (Enterprise CSR)

Wavect Ventures GmbH

Holding Company

MCI | The Entrepreneurial School®

Teaching about Blockchain infrastructure, Smart Contracts etc at MCI: 
https://www.mci.edu/en/electives#digitalization

University Lecturer

Coding4Kids.at

Teaching 10-14 year old children in programming @ WIFI, Innsbruck. Seasonal courses for free (volunteer work).

Lecturer - Blockchain

NFBrands.X

My company Wavect went into strategic and operative partnership with NFBrands.X by providing technical consultation, smart contract and DApp development services.

Web3 Advisor

Quivr

Working in terms of Wavect's daily business.

Quivr is an interoperable validation and social endorsement protocol for users to verify and authenticate their digital narrative. Our mission is to create a secure digital identity- powered by you - for everyone to represent their most complete self, online and offline.

Lead Blockchain Engineer

DebtRay GmbH

Illuminating the Black Box of Bond Issuance: Empowering issuers with purpose-built issuance analytics and predictive tools for effective financial capital decision-making.

Partner - FinTech (TradFi)

Smart Data Analytics for Debt Capital Markets.

CTO & Active Partner - Traditional FinTech

NFT PROs? NFT BROs!

German Podcast fully devoted to NFTs. In super short episodes around 5-10 minutes, we explain NFTs and related topics as simple as it can be.

NFT PROs NFT BROs - Co Host

FTW DAO

Advising them in technical questions, best practices regarding future launches, etc. after supporting them of launching their MintPass collection by managing a small team of software developers. 

My personal mint pass: 
https://nft.coinbase.com/nft/ethereum/0x84f0dd91f3e77289fe4b938e42b619da5c7a7209/25

Advisor & OG Member

Managed the developer team remotely, matched requirements, aligned expectations, to get their initial NFT collection on the way.

Technical Project-Manager

Inevitable

Created the course "Smart Contracts for Non-Tech Professionals" - You can sign up here: 

https://www.becomeinevitable.com/course/smart-contracts-non-tech

Instructor

»𝗧𝗛𝗘« 𝗪𝗲𝗯𝟯 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗔𝗴𝗲𝗻𝗰𝘆 💻 ▪ Staff Augmentation - just like an employee, but without the hassle ▪ Smart Contracts, DApps & Co. ▪ Web3 Developer ▪ Speaker ▪ Podcasts with Web3 leaders ▪ 🍪🐌

💻 Fractional Co-Founder with Product/Engineering focus
🎤 Monthly Podcasts with industry leaders about Product-Market-Fit
🗣️ Passionate and energetic speaker
👧 Father of a little daughter
🤸 Bodybuilding & Calisthenics fanatic (especially handstand variations are my thing)

𝗛𝗼𝘄 𝗜 𝗰𝗮𝗻 𝗵𝗲𝗹𝗽 𝘆𝗼𝘂..
+ Workshops for your business, e.g. evaluating true business cases for your company,
+ Software Engineering in a variety of programming languages (most proficient: TypeScript)
+ Fractional Co-Founder, CTO or CPO
+ Leading developer or product teams
+ or just getting you started in building successful products by creating qualitative content. 

..more on 🔗 www.wavect.io/pricing


𝗟𝗶𝗻𝗸𝘀: 
+ Website: www.wavect.io
+ Github: @wsdt
+ YouTube: @wavect
+ TikTok: @wavect.io
+ Twitter: @wavect_eth
+ Instagram: @wavect.io 
+ Podcast on Anchor: @wavect
+ Facebook: @wavect

You might need a new CTO soon. 

If your CTO recklessly uses AI everywhere, you'll either 

(A) burn your customers
(B) get into maintenance & bug hell
or (C) don't save a single dime but instead put most of your resources on QA.

Be smart. Leverage AI, but don't do so recklessly. 

--

PS: We build software that actually scales and is being used.

Kevin Riedl

F*cked by Dev Shop? We fix Software, we build it and we stop you from building something nobody buys or WE PAY 💻 Fractional Co-Founder ➝ Build (Software Development) ➝ Break (QA / Testing) .

Sell your Product as a Service first. 

If you can, don't build a MVP. 
Don't spend 15k$ on a prototype. 
Don't waste weeks or months on devs to be ready. 

If you're building software, in 90% you can solve the pain point you think is worth solving through manual labour. 

Of course it depends on the industry you operate in, your resources, experience and the opportunity at hand. 

But the most likely reason for failure often times is building something nobody wants. 

This approach literally forces you to be resourceful, to sell without product the legit way, and you get REAL customer insights instead of polite nods. 

Try it. It's hard, that's why it is right. 

--

PS: We work as Fractional CTOs or Fractional Product Executive (CPO), making sure you build the right thing on time. DM me or comment "PMF" below to get honest feedback on your roadmap.

Couple years back I attended a workshop from a bread sommelier.

Why? 
I thought it would be a fun idea to bake great bread. 

Did I do it before once?
Hell no haha, did make it even more fun though

And when I listened to him talking, I immediately got humbled. 

I thought I would just follow some instructions, mix some stuff together and voilà here it is: my first bread. 

But I was shocked how much DEPTH there is to even something seemingly simple like baking bread. 

Yes you can bake a bread with little knowledge. Doesn't mean it's good or even eatable. 

The depth is what makes it great. The crust, the little neats and tricks to make it outstanding. Which flours you can take, the mistakes when putting into into the oven, ... the list is endless. 

And I sincerely believe we see the same mistake by people today when they talk about AI. 

We believe we are all developers now. 
We believe we are artists as we can generate songs, videos or images. 
We believe we are capable of automating and doing everything. 

Sorry to break it to you. 
Coming up with a bad or mediocre product was never a bottleneck. 

Doing great and outstanding work is, has been and always will be.

Lecturing at university in an AI era taught me these lessons.

1. Just because students can use ChatGPT, Gemini, Claude, .. doesn't mean everyone will get it right. There always have been and always will be students that go above and beyond, and the ones that do the bare minimum. Grades haven't improved since the introduction on AI (at least in our lectures).

2. Get more practical. Let them do things. Action beats shallow know-how any time of the day. They will ask AI for help, but it doesn't make it necessarily easier as they will ask before they think by default. 

3. Storytelling will never be obsolete. Teach with passion and let them feel why a subject has relevance. You will get full attention, and some will even develop a glimpse of curiosity. Some you will never reach, but that's okay. 

4. Be human. More important than ever. Let them know how you grade, and that AI is ok & expected. But tell them that you'll grade accordingly. Grade for understanding & effort instead. 

--

PS: We lecture for fun. We build software for a living.

Vibe coders don't want to believe this:

It usually costs less to build Software right to begin with instead of hacking/vibing it together and fixing the mess afterwards. 

The real solution to building software faster & cheaper is the same as 20 years ago: 

Narrow the damn scope, by focusing on an URGENT PAIN and leaving everything for a potential v2 once customer feedback flows in. 

This way you save tons of money on development while having a strong foundation you can scale with, and all that without sacrificing quality, security and reliability. 

--

PS: We build software the right way. Software people actually keep using.

When building Software, don't start with the Requirements. 

Start with the Desired Outcome. 

WHO wants to do WHAT? (choose 1 single thing first to focus)

Then map out the steps this user has to take to achieve that in your software.

Then simplify the steps. 

And try simplifying again while not sacrificing comprehensibility. 

Now you got your real software requirements. But without all the fluff. 

Simple, but actually doing it saves tons of money & time. 

--

PS: We help you build software that scales and is actually being used.

For a long time Founders worshipped Decentralisation in Blockchain as the holy grail. And many still do. 

Fact is, that the majority of the market doesn't care (enough) to put their money where their mouth is. And Decentralisation to date only appeals to those people who have a super strong reason to need it. 

People in censoring countries, unbanked people, sanctioned people/countries, etc. etc. 

As so often people mistake a "vitamin" (something people want or might want) for a real, URGENT pain. Something that would make people accept the pain of change. 

--

PS: We build software people keep using. Building software? Hit me up to move 5x faster on your roadmap.

It's really hard to build something people want. 

You hear it all the time: 
- Talk with your customers
- Test, test, test
- Build a MVP or even vibe-code
etc.

And all of them are true. But..

The reason still most people fail is not, not knowing these. 

It's not putting one's ego aside when you think big or going too fast when urgency hits. 

Going through the motions is NOT trying to really know the answer. Wanting to know means facing a lot of very uncomfortable truths, getting your conviction tested and crushed. And then trying a new angle. 

Real validation hits differently. 
It's crushing. 

I heard this quote a while ago: "The most successful person has the most accurate view of the world". 

And I kind of like it, although there is always nuance to it. 

--

PS: We build software that actually is being used.

Building Software was never about writing code. 

If it would have, then we wouldn't see such an insane amount of smartly engineered but useless software. 

The widely underrated piece is Product Management. 

Aka building something people love. And then expanding from there. 

If you're building software, don't have a single signed contract or paying customer after +6 months then you're in trouble. You likely wasted time on the wrong stuff. (if you're selling to enterprise or operate in highly regulated environments this may be different)

Everyone has heard about this at least once, but yet almost everyone makes the same mistakes over and over again. 

KEEP IT SIMPLE. 
FOCUS ON ONE, YES ONE, URGENT PAIN. NOT A BIG PAIN, AN URGENT SOMEWHAT BIG PAIN FOR A NARROW GROUP. 

(yes I hate caps too, but maybe this way it sticks)

--

PS: We build software people keep using.

Finding a Pain Point is *not* enough to build something people want. 

You need to find the Right Pain Point, for the Right People (aka "Ideal Customer Profile"). 

You find Problem-Solution-Fit once you know WHO cares about WHAT pain. Choose the biggest pain you actually can reasonably solve. 

One way to do this is by testing different communication angles through Social Media or Paid Advertising using Waitlists. 

I usually suggest selling your idea as a service first & then productise. But for Enterprise or Exited Founders the Waitlist approach can also be very appealing because it saves time. 

---

PS: We work as Fractional CTO and Fractional Product Officer (CPO) to make sure you don't waste your resources and hit your goals faster.

You have to make a Choice when building Software. 

A Choice between
(1) Scope
(2) Cost
(3) Time
(4) Quality

Focusing on one will negatively influence some others. 

Building software for little cost almost always results in either Smaller Scope or Lower Quality. 

Focusing on Software Quality will usually force you to either keep your Scope tight, take much more time or/and to spend more. 

Trying to go to market as fast as possible almost always increases the likelihood of bugs & vulnerabilities, might be more expensive as more resources are needed and usually forces you to prioritise features. 

Choose wisely. 

--

PS: We help you figure out which of the both are important to you & then build it within those constraints. DM me for more infos & references.

You know what completely destroys user trust? 

It's the same thing everyone on the planet hates, no exception: 

BUGS. 

Encounter 3, and users have a 88% chance of churning forever [1].

While building and launching fast to test is important to get users. 

Keeping users is equally important. Especially since customer acquisition becomes more and more expensive. 

User Retention becomes the final frontier when building software. 

Look at Lovable, and all the big startups of the last 10 years. Many have risen to incredible ARR just to encounter retention issues. 

Some through bugs, some through vanishing hype - the issue stays the same: Build something people enjoy using. 

[1] NIST 2018, IBM/IEEE, Qualitest 2021, Salesforce 2022.

How long until people learn it: 
The world got so complex. Even backing bread for god's sake is a science. 

If you really think AI can code your app, do it. 

Developers around the world, including ourselves, would have been faster building it right to begin with. 

Would love to show you the BS some vibe "coders" generated which we have to fix every day. 

--

PS: We build and fix software at a fixed price or through retainers (cancel anytime & money back guarantee).

Building Software? 
Start with these 2 things before you write a single line of code:

(1) Software Architecture v1
A Bird's Eye View of the Software Components. 

(2) User Flow / Sequence Diagrams
How do Users interact with your product?

It doesn't (just) help with planning or scoping a project but it helps build ALIGNMENT between teams. 

And alignment is oxygen for larger projects. The less aligned you are, the more iterations you will need and the more resources you waste. 

--

PS: We build software that doesn't break once you hit thousands of concurrent users. Message me for references and more details.

Build 1 feature that is Urgent and a big Pain. 

If it's a big pain, but not urgent -> Long sales cycles

If it's urgent but not a big pain -> Lots of leads, low conversion. 

If it's none, you are where most startups are: Left without customers. 

Focus all your resources on solving one urgent pain for one customer extraordinary well. That's it, don't make it complicated. 

--

PS: We help founders build software the right way. Stop wasting time and money, we got you.

Founders tell me all the time, they already validated the market. They talked with a lot of potential customers and got people waiting for the product. 🤡

And it's usually exactly those founders that did NOT properly validate the market. 

They got polite "I love this!". 
A handful of emails in their waitlist after asking people to sign up for it. 
No direct competitors, because revolutionary. 

And a Problem they identified, but not yet how it's actually solved best. 

These founders usually look at the market Top-to-Bottom instead of Bottom-Up. What this is and why it matters is in the video.

Kids nowadays. 
I finally found translations for all these weird acronyms. 

--

PS: We build software and help you achieve Product-Market-Fit with it. (there is so much to it what people miss often times)

Before AI: 
Hitting a very difficult problem as developer.

You know the fun begins once you hit some cryptic Chinese search results.

That's when you truly outgrow yourself as developer lol. 

Kind of miss those times. Now everyone, including myself, asks just AI and iterates that way until you find the solution. 

It's more efficient. 
It allows you (finally) to ask the right questions. 

But your learning curve is not as steep, which definitely harms your abstract thinking. And I would argue that abstract thinking is one of the biggest strengths of an engineer. 

--

PS: We build software, but the kind that is actually being used by people.

New Q&A around how to build software people trust. 

Especially in the AI age. 

You don't want to miss this one.

Habe eine erfolgreiche Web3 Software Agentur (Wavect) gebootstrapped, aktiver Gesellschafter @DebtRay (Data Analytics für Corporate Debt in TradFi) und habe ein paar Startups gecrashed. In Krypto seit 2016/17. 🪙

💻 Smart contract und DApp Entwickler spezialisiert auf EVM Netzwerke. 
🎤 Wöchentliche Podcasts mit Web3 Industry Experten
🗣️ Leidenschaftlicher Speaker
👧 Vater einer kleinen Tochter
🤸 Bodybuilding & Calisthenics Fanatiker (v.a. Handstand Variationen)

𝗪𝗶𝗲 𝗶𝗰𝗵 𝗱𝗶𝗿 𝗵𝗲𝗹𝗳𝗲𝗻 𝗸𝗮𝗻𝗻..
+ Workshops für dein Unternehmen, z.B. echte Web3-Businessmodelle auszuarbeiten,
+ Smart-Contract/DApp Entwicklung mit Solidity und TypeScript,
+ Technische Beratung,
+ Leitung von Entwickler- und Produktteams,
+ Speaking Engagements über technischere oder weniger auch weniger technische Themen,
+ oder dich einfach nur in die Welt der Blockchains einzuführen durch qualitativen Content. 

..mehr auf 🔗 www.wavect.io/#services


𝗟𝗶𝗻𝗸𝘀: 
+ Website: www.wavect.io
+ Github: @wsdt
+ YouTube: @wavect
+ TikTok: @wavect.io
+ Twitter: @wavect_eth
+ Instagram: @wavect.io 
+ Podcast on Anchor: @wavect
+ Facebook: @wavect

F*cked by Dev Shop? We fix Software, we build it and we stop you from building something nobody buys or WE PAY 💻 Fractional Co-Founder ➝ Build (Software Development) ➝ Break (QA / Testing). Fractional CTO/CPO (Product)

taplio

Kevin Riedl's Linkedin Analytics

Kevin Riedl

Performance ScoreKevin Riedl's LinkedIn Performance

What is Kevin talking about?

Who is engaging with Kevin

Kevin Riedl's Best Posts (last 30 days)

Ready to grow your LinkedIn presence?

taplio

.css-6ytdur{background-image:linear-gradient(284deg, rgba(39, 43, 72, 1) 0%, rgba(33, 47, 183, 1) 100%);color:transparent;-webkit-background-clip:text;background-clip:text;}Kevin Riedl's Linkedin Analytics

Kevin Riedl

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Kevin Riedl's LinkedIn Performance

What is Kevin talking about?

Who is engaging with Kevin

Kevin Riedl's Best Posts .css-1emoo84{font-size:var(--chakra-fontSizes-md);font-weight:400;color:var(--chakra-colors-gray-600);}(last 30 days)

Ready to grow your LinkedIn presence?

Kevin Riedl's Linkedin Analytics

Performance ScoreKevin Riedl's LinkedIn Performance

Kevin Riedl's Best Posts (last 30 days)