# Wavect GmbH

> Build Software That Ships & Sells. No Bullshit. The Software Agency That Thinks Like a Founder.

We build software that makes money, not just software that ships. 75+ products shipped in 5+ years. Based in Ampass, Tyrol, Austria. Working internationally across 17 countries. Google 4.7 stars, Trustpilot 4.5 stars. We respond within 4 working hours, usually within 1.

This file is the full data dump. Curated index lives at https://wavect.io/llms.txt.

---

## Organization

- Legal name: Wavect GmbH
- Founded: 2020
- HQ: Häusern 6a, 6070 Ampass, Tirol, Austria
- VAT: ATU77948526
- Tax ID: FN 575337 i
- Email: office@wavect.io
- Phone: +43 650 30 566 44
- Languages: en, de, es, zh
- Founders: Kevin Riedl (Managing Director), Christof Jori (Managing Director)
- Wikidata: https://www.wikidata.org/wiki/Q139795658
- LinkedIn: https://www.linkedin.com/company/wavect
- Clutch: https://clutch.co/profile/wavect
- Trustpilot: https://www.trustpilot.com/review/wavect.io
- Book a call: https://zeeg.me/wavect/call

### The No-Bullshit Guarantee
Cancel any week. No notice. No exit fee. If we don't blow you away, we refund the last week, no questions. We don't track hours. We sell outcomes, not time. Fixed-price engagements are signed SoW (Werkvertrag), legally bound on scope and deadline.

---

## Services

### Fractional Co-Founder
- URL: https://wavect.io/services/fractional-cofounder/
- Price: €400 per week
- Terms: Cancel any week. Refund last week if not blown away. No hours tracked.
- For: Pre-PMF founders, startups
- What: A product-minded technical co-founder in the trenches. Product strategy + engineering under one operator.

### Full-Stack Software Development
- URL: https://wavect.io/services/software-development/
- Price: €10,000 to €30,000 per month retainer, or €3,500+ fixed-scope
- Engagement modes: Fractional CPO/CTO, MVP & PoC, Complete Project, Extended Team, Technical Consulting
- For: Startups, scale-ups, enterprises
- What: End-to-end delivery. Web, mobile, AI, blockchain. Senior engineers, signed SoW.

### Software Quality Assurance
- URL: https://wavect.io/services/software-quality-assurance/
- Price: €750 per week, 75% off the first week
- Outcome: Finds 40-70% more issues than internal teams in the first 30 days
- For: Product teams, engineering orgs
- What: Manual, automated, and managed testing. Outside eyes that catch what your team learned to live with.

### Discovery Phase
- URL: https://wavect.io/services/
- Price: €3,500 fixed (deducted from final invoice if you continue with the build)
- Duration: 2 to 3 weeks
- Deliverables: Software architecture, milestone plan, technical flows, launch plan, fixed-price build offer
- For: Founders, startups, enterprises de-risking a build

---

## Specialized Capabilities
- AI Integration: RAG, fine-tuning, agent orchestration. We start by asking if AI is the right tool here.
- Blockchain: EVM and Solana, Cosmos, Polkadot, Near, Ton, ICP. Smart contracts, DApps, wallets, ERC-4337 account abstraction, cross-chain bridges, ZK.
- Web Apps: NestJS, NextJS, React, Angular, Vue. Production-grade, zero to scale.
- Mobile Apps: React Native, Flutter, native iOS and Android. Shipped to App Store and Play Store.
- IoT: LoRaWAN, smart-city deployments, sensor networks, hardware-to-cloud pipelines.
- Zero-Knowledge: Privacy-first apps, ZK identity, private transactions, ZK rollups.

---

## Who This Is For
- Pre-PMF founders and operators who need a co-founder-grade partner before they can hire one.
- Scale-ups that need product and engineering under one roof, not stitched together from 3 vendors.
- Web3 and AI product teams shipping into hostile, undocumented territory.
- Tech-forward enterprises that want senior delivery without the staffing-agency markup.

## Who This Is Not For
- Teams that already have a CTO and just need more hands.
- Founders who cannot commit at least 4 hours per week to the engagement.
- Already-profitable companies that just need raw engineering capacity.
- Anyone looking for an equity swap instead of paying for the work.
- Anyone betting on a market that does not exist yet (we will tell you).
- Anyone insisting on hourly billing. We sell outcomes, not timesheets.

---

## Case Studies

Every case below shipped to production. Full structured data per case lives at the URL.

### Twinsoft AI
- URL: https://wavect.io/case-studies/twinsoft-ai/
- Year: 2026
- Industry: Enterprise AI
- Engagement: Fullstack Build
- Client stage: Seed
- Size: Compact sprint · 3 weeks · €
- Status: Live

**Headline:** Vibe-coded prototype to enterprise pilot-ready in two weeks.

**Background:** Twinsoft AI extracts, authors, and deploys Expert Digital Minds, enterprise-grade AI twins that carry deep domain knowledge and act on it across agents, avatars, and whole organizations.

**Challenge:** Enterprise pilot calls on the calendar. Vibe-coded scaffolding works on the happy path; enterprise buyers probe every other path on contact. Two weeks to hit production quality and meet a high UI/UX bar. No room to slip on either.

**Outcomes:**
- 2 weeks, To Sellable MVP
- Enterprise, Pilot-Ready

**Tech stack:** Python / Flask, LLMs, Terraform, Dawple

**Tags:** AI Agents, LLM, Enterprise

**Learnings:** Vibe-coded prototypes carry hidden debt: logic often right, structure not production-defensible. The fastest path is rarely a full rewrite. Triage what to keep, refactor the demo path, rebuild the rest properly. Ship the WOW first.

**Live:** https://staging.twinsoft.ai/

### Hyperstate AI
- URL: https://wavect.io/case-studies/hyperstate-ai/
- Year: 2025
- Industry: Music Tech AI
- Engagement: Fullstack Build
- Client stage: Seed
- Size: Extended retainer · €€
- Status: Wind Down

**Headline:** Broke up the GPU monolith. Lower latency, lower bill, deploys that don't need a war room.

**Background:** Hyperstate AI ran an AI-assisted music production platform. Creators uploaded audio and worked with a producer-style assistant (the Louis Bell persona) that kept full context across sessions. The startup ran out of funding after launch.

**Challenge:** A single GPU-heavy server handled audio processing, lyrics, transcription, MIDI generation, and the producer agent. Deploys were manual. The compute bill grew faster than usage. The architecture carried a demo but couldn't carry the launch. No horizontal scaling, no failure isolation, one bad deploy took the whole product offline.

**Outcomes:**
- GPU Monolith, → Microservices
- Latency & Cost, Both Down

**Tech stack:** Python / Django, OpenAI API, Neo4j, PostgreSQL, Docker

**Tags:** AI, Music Tech, Audio

**Learnings:** Heavy ML work doesn't belong in your web request path. The moment audio, lyrics, and transcription each pull a model into the same box, every load spike takes the whole product down with it. The win is boring infrastructure: separate services for separate compute profiles, orchestrated deploys, hosted alternatives for the libraries you have no business owning.

### PromptID
- URL: https://wavect.io/case-studies/promptid/
- Year: 2026
- Industry: EdTech AI
- Engagement: Fullstack Build
- Client stage: Seed
- Size: Extended retainer · €€€
- Status: Live

**Headline:** 0 to production in 6 weeks. Pilot-ready and investor-demo-ready.

**Background:** PromptID is an AI-native EdTech platform for employers and universities. It examines learners by analysing the train of thought, not by rewarding memorisation. A proprietary algorithm drives the assessment engine.

**Challenge:** The market moved mid-build and the timeline shrank by a month. Pilot conversations and investor demos sat on the calendar. LLM agnosticism, intuitive UX, production-grade from day one, none negotiable. The month had to come from scope, not quality.

**Outcomes:**
- 6 weeks, 0 to Production
- Pilot + Investor, Demo-ready under market pressure

**Tech stack:** NestJS, NextJS, LangChain, Kubernetes, Terraform, Typescript

**Tags:** AI, EdTech, LLM

**Learnings:** Model agnosticism pays off fast. The landscape keeps shifting and LangChain's abstraction turned model swaps into a config change. Kubernetes autoscaling earned its keep too, no overprovisioning, but the system absorbed load spikes in seconds.

**Live:** https://promptid.com/

### LivLive
- URL: https://wavect.io/case-studies/livlive/
- Year: 2025
- Industry: Blockchain / RWA
- Engagement: Fullstack Build
- Client stage: Seed
- Size: Fixed price · €€€
- Status: Live

**Headline:** $2M+ raised through the product, 1,000+ concurrent users, from zero in 6 weeks.

**Background:** LivLive brings the Pokémon GO experience to everyday life with RWAs, the only RWA platform with a global, immersive AR reward engine. $2M+ raised through the product.

**Challenge:** Zero codebase, zero infrastructure, six weeks. Scope: a multi-level on-chain referral system, fiat-to-chain NFT drops via Wert.io, crypto payments via NOWPayments, a full DApp checkout, and the observability to run real money through it.

**Outcomes:**
- +1,000, Concurrent Users
- $2M+, Raised through the product

**Tech stack:** Solidity, Typescript, React, NestJS

**Tags:** NFT, DeFi, Payments

**Learnings:** Under extreme time pressure, scope ruthlessness is the only path. We focused on what had to work perfectly, the on-chain referral logic and payment flows, and deferred the rest. The security audit confirmed cutting quality was never the trade we made.

**Live:** https://livlive.com/

### Bond Analytics Platform
- URL: https://wavect.io/case-studies/bond-analytics/
- Year: 2022
- Industry: FinTech / TradFi
- Engagement: Fullstack Build
- Status: Live

**Headline:** Zero to enterprise-ready in two months. Multiple funding rounds followed.

**Background:** An institutional analytics platform that scores bond issuance and stock debt health via a proprietary rating algorithm. Banks, asset managers, and enterprises use it to price corporate debt and run ex-post analysis against realised market outcomes. Multiple funding rounds closed.

**Challenge:** Two months, zero codebase, banks on the other end of the demo. The vendor API was out of budget, so the data path ran on quarterly Excel exports, manually downloaded, format-drifting, no API safety net. The proprietary rating logic had to be defensible enough for institutional buyers to stake decisions on, and ex-post analysis had to be first-class because that's what they actually buy.

**Outcomes:**
- 2 months, 0 to Enterprise
- Multi-round, Funded

**Tech stack:** NestJS, React, Typescript

**Tags:** FinTech, TradFi, Data Analytics

**Learnings:** When the licence budget pins you to Excel and the cadence is quarterly, the architecture inverts. You stop optimising for streaming freshness and start optimising for idempotent reruns, schema-drift resilience, and audit-grade ex-post replay. That is what institutional finance actually runs on.

### Polity
- URL: https://wavect.io/case-studies/polity/
- Year: 2026
- Industry: Enterprise SaaS
- Engagement: Software QA
- Client stage: Enterprise
- Size: Multi-year retainer + fixed prices · €€€
- Status: Live

**Headline:** Unified QA across seven microservices, hundreds of bugs closed, release gates held.

**Background:** Polity is an enterprise-grade platform running on seven microservices. Distributed, complex, and held to the standards enterprise clients demand, the kind of system where QA is not optional.

**Challenge:** Seven services, each with its own tooling, maturity, and failure modes. Multiple vendors shipping code in parallel, features in flight, and an enterprise client base that won't tolerate regressions. Unify it all into one quality model over 1.5 years, without slowing engineering down.

**Outcomes:**
- 7 services, Unified Testing
- Hundreds, Bugs Resolved

**Tech stack:** React, Java/Kotlin, Go, Python, Rust, Docker, CI/CD

**Tags:** Enterprise, QA, Microservices

**Learnings:** Quality across distributed systems is a coordination problem, not a tooling one. Holding seven services, multiple vendors, and continuous delivery to one standard took as much process design as it did technical work. The architectural judgment that mattered: move from centralised, manual, and fragmented workflows to scalable, ownership-driven, automated systems.

**Live:** https://polity.li/

### Scramble Pay
- URL: https://wavect.io/case-studies/scramble-pay/
- Year: 2023
- Industry: FinTech / Crypto Payments
- Engagement: Fullstack Build
- Client stage: Enterprise
- Size: Hourly rate · $$$
- Status: Live

**Headline:** Multi-chain crypto checkout, pilot-ready for merchant integration, shipped in 2 months.

**Background:** ScramblePay is a flexible online and Point-of-Sale payment system. Drops into online shops and handles on-site payments in restaurants, hotels, and bars, with a built-in DEX aggregator for paying in low-cap tokens.

**Challenge:** Build an enterprise-grade crypto checkout other companies could embed. PoS and web, multi-chain, wallet-agnostic, and ship it pilot-ready in two months. No off-the-shelf product covered the full scope, and writing a swap engine from scratch would have burned both the runway and the timeline.

**Outcomes:**
- 2 months, Concept to Pilot-Ready
- Any DEX token, Payment Coverage

**Tech stack:** React, Typescript, NestJS, Google Cloud

**Tags:** Cross Chain Swaps, EVM & Non-EVM support, Desktop & Mobile

**Learnings:** Tight budgets force the right architectural bets upfront. Forking a battle-tested DEX aggregator and building a thin merchant layer on top reaches production faster than writing a swap engine. The client only cares about the checkout experience.

### Scramble Wallet
- URL: https://wavect.io/case-studies/scramble-wallet/
- Year: 2023
- Industry: FinTech / Crypto Wallet
- Engagement: Fullstack Build
- Client stage: Enterprise
- Size: Hourly rate · $$$
- Status: Live

**Headline:** Self-custody wallet for non-crypto users 50+, shipped to every common browser and both mobile platforms.

**Background:** Scramble is a multi-chain crypto wallet built to simplify self-custody. Buy, sell, and trade assets including NFTs, with cross-chain swaps and fiat on/off-ramp built in. Browser and mobile.

**Challenge:** Target user: 50+, not crypto-native. Seed phrases, gas fees, chain selectors were enemies, not features. Tight budget. We forked Enkrypt to skip foundational work and inherited its bug backlog. Tron in as the first non-EVM chain, extension across every common browser, the wallet on both mobile platforms.

**Outcomes:**
- 50+, Target User Age
- 5 chains, Supported Networks

**Tech stack:** VueJS, Typescript, NestJS, Google Cloud, Firebase, Kubernetes

**Tags:** EVM & Non-EVM support, Cross Chain Swaps, Desktop & Mobile

**Learnings:** Forking a production wallet beats building one, but the hidden cost is the debt you inherit, the original audit findings become yours. We now scope a mandatory audit pass and a multi-browser sweep into every wallet fork engagement.

**Live:** https://www.btc-echo.de/reviews/erfahrungen/scramble-wallet/

### LightBridge
- URL: https://wavect.io/case-studies/lightbridge/
- Year: 2022–2023
- Industry: Blockchain / L2 Infrastructure
- Engagement: Bridge
- Client stage: Enterprise · $115M raised
- Size: Monthly retainer · $$$
- Status: Live

**Headline:** Near-instant cross-chain bridge across 6 networks. $1M+ moving through it, continuously.

**Background:** Boba Network is a hybrid Layer 2 blockchain delivering native off-chain data and compute through Account Abstraction. An optimistic rollup rooted in Ethereum and BNB Chain for mass-adoption apps.

**Challenge:** Optimistic rollups secure value with wait periods; mainstream users want speed. The existing bridge UX was too slow and too complex for the audience Boba wanted to reach. Cross-chain transfers had to feel instant without breaking the trustless fallback, alongside an NFT launch and ongoing Gateway DApp work.

**Outcomes:**
- 6 chains, Network support
- $1M+ secured, Continuously

**Tech stack:** Typescript, Python, GraphQL, React, AWS, Solidity

**Tags:** Infrastructure, Layer 2, RollUp

**Learnings:** Optimistic rollup bridging has an inherent UX tension: security wants wait periods, users want speed. LightBridge taught us how to architect liquidity-provider layers that mask latency for most users while keeping the trustless fallback intact.

**Live:** https://gateway.boba.network/

### Account Abstraction
- URL: https://wavect.io/case-studies/account-abstraction/
- Year: 2025
- Industry: Blockchain / L2 Developer Tools
- Engagement: SDK Development
- Client stage: Enterprise · $115M raised
- Size: Monthly retainer · $$$
- Status: Live

**Headline:** Reverse-engineered Hybrid Compute, shipped 3 production SDKs, still live.

**Background:** Boba Network's Hybrid Compute lets smart contracts trigger oracle-like off-chain computations and receive results trustlessly on-chain, inside a single transaction. It anchors Boba's Account Abstraction model and differentiates it from standard L2s.

**Challenge:** Zero documentation, no specs, just raw node code. We reverse-engineered Hybrid Compute from the running system, patched live infra errors on the fly, and shipped three production SDKs against a moving target. Developers were waiting; the schedule wasn't.

**Outcomes:**
- 3 SDKs, Backend · Contract · Frontend
- Still live, On Boba Network

**Tech stack:** Typescript, Solidity, Hardhat, Ethers.js, Node.js

**Tags:** Account Abstraction, Hybrid Compute, SDK, Layer 2

**Learnings:** Undocumented infrastructure forces you to treat the running system as the spec. Test harnesses that interrogated live node behavior before any SDK abstraction paid off every time the infra changed without notice.

**Live:** https://boba.network/

### MetaMask Snap
- URL: https://wavect.io/case-studies/metamask-snap/
- Year: 2025
- Industry: Blockchain / Wallet Integration
- Engagement: Fullstack Build
- Client stage: Enterprise · $115M raised
- Size: Monthly retainer · $$$
- Status: Live

**Headline:** Boba's Account Abstraction stack, native inside MetaMask. No new wallet to learn.

**Background:** Boba Network's Account Abstraction enables smart wallets with Hybrid Compute, executing complex on-chain/off-chain logic in one flow. The Snap brings this natively into the world's most-used Web3 wallet.

**Challenge:** MetaMask Snaps are powerful and tightly sandboxed. Strict permission model, opinionated execution context, and a boundary that runs straight through what Boba's Account Abstraction needed to do. Make smart wallet management feel native, without fighting the sandbox or teaching users anything new.

**Outcomes:**
- MetaMask, Native Integration
- Smart Wallets, Hybrid Compute Enabled

**Tech stack:** Typescript, MetaMask Snaps, Solidity, Ethers.js

**Tags:** Account Abstraction, MetaMask Snap, Smart Wallet, Layer 2

**Learnings:** Snaps are powerful but opinionated. Their permission model and sandbox force careful interface design early. The integration pushed us to build a clean abstraction layer between Boba's AA stack and the Snap runtime, which made the whole system more testable.

**Live:** https://boba.network/

### Quivr
- URL: https://wavect.io/case-studies/quivr/
- Year: 2023–2024
- Industry: Blockchain / Consumer Crypto
- Engagement: On-chain Protocol
- Client stage: Seed · raised $4.05M
- Size: Monthly retainer · $$$
- Status: Wind Down

**Headline:** Designed and shipped the protocol from scratch, then re-platformed Polygon → Solana mid-flight.

**Background:** Quivr was an AI-driven data verification protocol that helped brands identify their most authentic fans. Launched on Polygon, migrated to Solana for compressed NFTs. Ran out of runway in April 2024.

**Challenge:** Novel concept: on-chain fan identity verified by AI. Zero blockchain infrastructure to start with. Full protocol to design, build, and ship from scratch. Mid-engagement the client pivoted from Polygon to Solana for compressed NFTs, so the whole on-chain stack had to be rebuilt without breaking what shipped.

**Outcomes:**
- Day 1, Engagement Start
- 2 chains, Polygon to Solana

**Tech stack:** Typescript, Flutter, React, Solidity, Rust (Solana)

**Tags:** EVM & Non-EVM, AI, Mobile App

**Learnings:** When a startup runs out of money, the tech usually still worked. Quivr died on runway, not product. Challenge fundraising assumptions early, design for the minimum viable chain. Multi-chain complexity is scope a seed-stage startup rarely needs.

**Live:** https://alexablockchain.com/quivr-digital-identity-badges-nfts/

### FTW Ventures
- URL: https://wavect.io/case-studies/ftw-ventures/
- Year: 2022
- Industry: Venture Capital / DAO
- Engagement: Rescue
- Client stage: Seed
- Size: Fixed price · $
- Status: Wind Down

**Headline:** Stalled NFT mint and CMS rescue, shipped, handed off, no devs needed for content.

**Background:** FTW.DAO was a venture DAO building toward a $1B ecosystem fund for diverse-led teams, training talent to find top founders and connect them with investors. The project has since wound down.

**Challenge:** A stalled in-house dev team. An NFT mint page off-design and unable to ship. A website with no CMS, so every paragraph edit required engineering the org didn't have. Finish what someone else started, then hand back a site the team could run themselves.

**Outcomes:**
- NFT mint, Shipped
- 0 devs needed, Post-launch CMS edits

**Tech stack:** Typescript, React, Solidity, Butter CMS

**Tags:** Venture Capital, DAO, Social Impact

**Learnings:** Taking over a half-built project is always messier than starting fresh. The real cost is decoding undocumented decisions. We now start every rescue with a 2-day codebase audit before committing to a delivery timeline.

**Live:** https://www.ftwdao.com/

### ZybraMoney
- URL: https://wavect.io/case-studies/zybra-money/
- Year: 2025
- Industry: FinTech / Africa
- Engagement: Software QA
- Client stage: Seed
- Size: Weekly retainer · $$
- Status: Live

**Headline:** Weekly release gates held through a mid-flight FinTech rebuild. Hundreds of defects closed.

**Background:** ZybraMoney is an Africa-focused FinTech backend handling group savings (ROSCA flows), wallet-linked journeys, payments, transfers, referrals, and the security and compliance controls financial workflows demand.

**Challenge:** We joined mid-modernization. Architecture in flux. Service boundaries getting redrawn. Defect density high. Security and functional issues bleeding into each other across auth, session, and transaction surfaces. QA held release safety weekly while engineering rebuilt the foundations underneath.

**Outcomes:**
- Weekly, Release Gates Held
- Hundreds, Defects Closed
- ~0, Support Tickets After Cleanup

**Tech stack:** Node.js, Typescript, PostgreSQL, Redis, Express

**Tags:** FinTech, QA, Africa

**Learnings:** Refactor-heavy environments need QA as continuous signal, not a checkpoint. Tying closure quality to weekly release gates kept regressions from compounding while architecture moved. The discipline isn't in the tools, it's in the closure criteria.

**Live:** https://zybra.money/

### Afoma
- URL: https://wavect.io/case-studies/afoma/
- Year: 2024
- Industry: Web3 / Marketplace
- Engagement: Web3 Integration & Consulting
- Client stage: Seed
- Size: Fixed price · $
- Status: Live

**Headline:** Added Web3 to a live marketplace without the user ever seeing crypto.

**Background:** Afoma is a live marketplace expanding into Web3. The client wanted on-chain primitives layered onto the product without breaking the experience for users who don't know what a wallet is.

**Challenge:** Adding Web3 to a live marketplace is rarely the hard part. Making it feel native to non-crypto users is. The integration had to lower the onboarding barrier: social login that just works, wallet creation hidden behind familiar auth, zero crypto jargon in the flow. Without disturbing what already worked.

**Outcomes:**
- Web3 Social Login, Live in Production
- Non-Crypto, Friendly UX

**Tech stack:** Typescript, Solidity, Ethers.js

**Tags:** Web3, Marketplace, Social Login

**Learnings:** The fastest way to lose a non-crypto user is to make them feel like they're using crypto. The Web3 layer has to disappear into the existing UX, not bolt onto the side. Social login was the right entry point: marketplace flow intact, on-chain door quietly open.

**Live:** https://afoma.io/

### Soundromeda
- URL: https://wavect.io/case-studies/soundromeda/
- Year: 2025
- Industry: Games / Audio
- Engagement: Software QA
- Client stage: Seed
- Size: Weekly retainer · $$
- Status: Live

**Headline:** Vibe-coded prototype hardened to production. Further grants unlocked.

**Background:** Soundromeda is a music action-adventure game. A creative-first studio, small team, big ambition, and a vibe-coded prototype that had to become a real product.

**Challenge:** Vibe-coded scaffolding: main path works, everything else breaks. Small creative-first studio, no budget for a rewrite. Grant committees about to look at the build. QA had to find the bugs that mattered, surface the real risk, and harden the product into something a funder would back, without forcing a refactor the studio couldn't afford.

**Outcomes:**
- Production, Vibe-Coded → Hardened
- Further Grants, Unlocked

**Tags:** GameDev, QA, Audio

**Learnings:** Vibe-coded products fail predictably: the hot path works, everything else doesn't. The trick is bug triage that maps to user-visible risk, not codebase tidiness. Closing the right hundred bugs is worth more than refactoring around them.

**Live:** https://www.soundromeda.com/

### SKD Dresden
- URL: https://wavect.io/case-studies/skd-dresden/
- Year: 2023–2024
- Industry: Cultural Institutions / Strategy
- Engagement: Workshops & Strategy
- Client stage: Enterprise
- Size: Fixed price · $$
- Status: Live

**Headline:** Ruled out the wrong blockchain ideas before they cost a museum a budget cycle.

**Background:** Staatliche Kunstsammlungen Dresden (SKD) is one of the oldest and most prestigious museum networks in the world. They wanted clarity on what blockchain could realistically do for a cultural institution.

**Challenge:** Cultural institutions get pitched blockchain ideas constantly. Most don't survive contact with budget reality, audience expectations, or the institution's actual mandate. SKD needed an outside team that knew the technology deeply enough to separate real use cases from marketing material, and willing to say no to the latter, on the record.

**Outcomes:**
- Multiple, Workshops Delivered
- Honest, Strategy Calls

**Tags:** Strategy, Workshops, Cultural Institutions

**Learnings:** The most valuable thing you can give a non-tech client is the courage to say no to bad ideas. Most of our workshop time wasn't spent teaching blockchain. It was spent ruling out use cases that wouldn't survive their first year. Strategy is mostly subtraction.

### Offlinery
- URL: https://wavect.io/case-studies/offlinery/
- Year: 2024-2025
- Industry: Mobile / Real-time Geo
- Engagement: Fullstack Build
- Client stage: Pre-seed
- Size: $
- Status: Wind Down

**Headline:** Real-time, sub-second matching on hostile mobile OSes, built end-to-end.

**Background:** Offlinery was a dating app built against swipe culture. A proprietary matching algorithm surfaced nearby people who actually wanted to meet in person. Shipped on iOS and Android. Wound down in 2025.

**Challenge:** Surface the right nearby person inside a minutes-long window so a real-world approach actually happens. Two compounding constraints: a proprietary algorithm doing sub-second proximity and mutual-intent filtering, and reliability against iOS and Android killing background tasks the moment they lose interest.

**Outcomes:**
- Real-time, Proprietary Matching Engine
- Sub-second, Proximity Queries

**Tech stack:** React Native / Expo, NestJS, TypeORM, Typescript, Firebase, Sentry

**Tags:** AI / Matching, Real-time Geo, Mobile App

**Learnings:** Real-time in-person matching lives or dies on signals the OS actively kills. Half the work is algorithm, half is platform fight. Motion-driven triggers, smart deferral, graceful degradation, fallbacks when accuracy gets capped. On a moving phone, speed and resilience are the same problem.

**Live:** https://github.com/wavect/offlinery

### MyMerch
- URL: https://wavect.io/case-studies/mymerch/
- Year: 2023-2026
- Industry: eCommerce / Shopify
- Engagement: Process Automation
- Client stage: Enterprise
- Size: Hourly rate · $$
- Status: Live

**Headline:** ~50% efficiency gain on a working Shopify business. No rewrite. Just the right moves.

**Background:** MyMerch is a German merchandise and print-on-demand brand based at the Chiemsee. They sell custom apparel and branded goods through Shopify across more than 10 storefronts.

**Challenge:** MyMerch was losing money in two places. Delivery had recurring human errors that cost real money per wrong shipment. The Shopify storefront leaked conversion. They needed outside eyes to decide what to fix first, not a vendor pitching a six-month rewrite of a business that already worked.

**Outcomes:**
- ~50%, Efficiency Gain (Client-Reported)
- Reduced, Human Errors in Delivery

**Tech stack:** Shopify, Shopify Liquid, JavaScript, Node.js, ZenDesk, Webhooks

**Tags:** eCommerce Operations, Process Automation, Customer Support

**Learnings:** On a working Shopify business the best outcomes don't come from a rewrite. They come from picking two or three places to apply effort: kill the manual handoffs causing delivery errors, lift storefront conversion with surgical changes, keep an outside voice in prioritisation.

### IKB
- URL: https://wavect.io/case-studies/ikb/
- Year: 2019-2023
- Industry: IoT / Smart City / Public Sector
- Engagement: IoT Infrastructure
- Client stage: Enterprise
- Size: Hourly rate · $$$
- Status: Live

**Headline:** City-wide IoT backbone for Innsbruck. Built it, ran it, handed it off, still on call.

**Background:** IKB (Innsbrucker Kommunalbetriebe) is the municipal utility of Innsbruck, Austria, water, energy, waste, telecom. They needed someone to build their Smart City programme, not write another slide deck about it.

**Challenge:** Greenfield IoT at city scale. Real streets, real devices from real vendors, none speaking the same dialect. LoRaWAN backbone on Kubernetes. Multi-manufacturer hardware to evaluate and integrate. Per-device uplink and downlink payloads to decode. Connectivity drops, divergent gateway firmwares, datasheets that lied.

**Outcomes:**
- City-wide, Connectivity
- Multi-vendor, Research & Integration

**Tech stack:** Kubernetes, LoRaWAN, Docker, JavaScript, Node.js, Linux, ChirpStack, MQTT, Grafana, PostgreSQL

**Tags:** IoT, Smart City, LoRaWAN

**Learnings:** City-scale IoT is a coordination problem dressed up as a hardware problem. Protocols are tractable. Datasheets are not. Every vendor lies a little, every payload is its own dialect. One team end-to-end is the only path that works.

**Live:** https://www.ikb.at/

---

## FAQs (from the case studies index)

**Q: How long does it take Wavect to build an MVP?**

A: Two to six weeks for most builds, depending on scope. Twinsoft AI went from vibe-coded prototype to enterprise pilot-ready in 2 weeks. PromptID shipped from zero to production in 6 weeks with 1,000+ concurrent users. LivLive launched in 6 weeks and raised $2M+ through the product. Speed comes from senior engineers who do not need to learn the job on your retainer.

**Q: What kinds of projects does Wavect build?**

A: Full-stack web and mobile, AI integrations (RAG, agents, fine-tuning), blockchain (smart contracts, wallets, bridges, ZK), IoT, and software QA. We have shipped across Enterprise AI, EdTech, FinTech, RWA, Crypto Payments, Music Tech, and Enterprise SaaS. 75+ products delivered since 2018. Browse the cases above to see the actual builds, the constraints, and what shipped.

**Q: Can Wavect deliver enterprise-grade quality on a startup timeline?**

A: Yes, and the case studies show it. Twinsoft AI hit enterprise pilot quality in 2 weeks under live demo pressure. Polity runs QA across 7 microservices for 1.5 years with hundreds of regressions caught before release. LightBridge secured $1M+ in production on day one. Senior engineers, signed SoW, fixed scope. No interns billed at senior rates.

**Q: How much does a Wavect case study project cost?**

A: Fixed-scope builds start at €3,500 (Discovery Phase). Full-stack retainers run €10,000 to €30,000 per month depending on team size and burn. Fractional Co-Founder is €400 per week. Every engagement is a signed SoW (Werkvertrag), legally binding on scope and deadline. Full pricing on the services pages.

**Q: What tech stacks does Wavect work with in production?**

A: NestJS, NextJS, React, Angular, Vue on the web. React Native, Flutter, native iOS and Android on mobile. Python, Django, Flask, Postgres, Neo4j, Docker, Kubernetes, Terraform on backend and infra. EVM, Solana, Cosmos, Polkadot, Near, Ton, ICP on chain. We pick the stack to fit the build, not the other way around. Each case study above lists the actual stack we shipped.

---

## Insights and Thought Leadership
- Blog overview: https://wavect.io/blog/overview/
- Podcast (Wavect): https://www.youtube.com/playlist?list=PLsZkl0r_l2kvaGllkk8PgzMUXK6zHkyU9
- Selected essays:
  - https://wavect.io/blog/why-agencies-are-bad/
  - https://wavect.io/blog/road-to-product-market-fit/
  - https://wavect.io/blog/agile-fixed-pricing/
  - https://wavect.io/blog/product-factory-kills/
  - https://wavect.io/blog/test-driven-development/
  - https://wavect.io/blog/software-a-breathing-organism/

---

## Agent Infrastructure
- MCP server card: https://wavect.io/.well-known/mcp/server-card.json
- Agent skills registry: https://wavect.io/.well-known/agent-skills/index.json
- Skills hub: https://wavect.io/skills/
- Markdown endpoint: any page returns clean markdown when called with `Accept: text/markdown`

---

## Resources
- Curated entry index: https://wavect.io/llms.txt
- This file (full dump): https://wavect.io/llms-full.txt
- Case studies index: https://wavect.io/case-studies/
- Services overview: https://wavect.io/services/overview/
- Pricing: https://wavect.io/pricing.md
- Testimonials: https://wavect.io/testimonials.md
- Imprint: https://wavect.io/imprint/
- General Terms: https://wavect.io/agb/

---

## Contact
- Book a free 30-min call: https://zeeg.me/wavect/call
- Email: office@wavect.io
- Phone: +43 650 30 566 44
- Kevin Riedl (Managing Director): https://linkedin.com/in/wsdt
- Christof Jori (Managing Director, QA lead): https://www.linkedin.com/in/jocr77/
- Company LinkedIn: https://www.linkedin.com/company/wavect