The Team Behind StreamFuse
Muhamad Hamza Khan
CO-FOUNDER & CTO
70% · 9,000,000 shares
First-time founder and former streamer. Codes everything — full-stack, matching algorithm, backend infrastructure, real-time systems. Built the production MVP solo in 8 days — before the founding team assembled.
Founded StreamFuse off his own experience of streaming to no audience. 50 alpha users, 0% churn, 168% viewership lift — before raising a dollar. Previously built production systems including Investify (investment platform) and an HFT trading bot in Rust — proof of production-grade systems engineering capability.
Hamza Kamran
CO-FOUNDER · PRODUCT
15% · 1,928,571 shares
Owns UI/UX direction and feature testing. Stress-tested every feature before public release — push notifications, real-time chat, matching logic. Currently a full-time Product Manager at a US company, working remotely — operates in US time zones and builds product in a professional context.
Head of Creator Relations. Manages onboarding, retention, and community health across the creator base.
Areeb Durani
CO-FOUNDER · BUSINESS
15% · 1,928,571 shares
Built and stress-tested StreamFuse's full financial model — revenue assumptions, conversion projections, five-year growth forecasts. Background across startups and businesses in data science, client-facing, and business development roles — commercial range that spans both analytical and relationship-driven work.
Market-facing co-founder. Leads advertiser outreach, brand partnerships, and owns the commercial strategy that activates at 12,000 creators.
CAP TABLE — FOUNDING ROUND
All shares subject to 4-year vesting · 1-year cliff · Delaware C Corp · Incorporated January 14, 2026 · 20% employee option pool to be carved out post-investment
The 70/15/15 structure reflects the pre-team build: the CTO founded StreamFuse, built the full production MVP solo in 8 days, and validated 50 alpha users with 0% churn before the founding team assembled. Differential equity reflects differential contribution at formation — not differential commitment going forward. All three founders are full-time and fully vested over 4 years.
Allison Bruckman
DESIGN ADVISOR · NO EQUITY
Designed StreamFuse's visual language from the earliest wireframes — the same design system that achieved 0% churn in alpha.
Muhamad Hamza Khan is based in Dubai, UAE and operates on US Eastern time zone hours full-time. Hamza Kamran is based in Pakistan and is a full-time Product Manager at a US company — he already works US EST hours as his primary working schedule. Areeb Durani is based in Pakistan and works across US-facing business and client roles. All three founders are committed to the full Techstars Anywhere program schedule on US Eastern time. Operating across time zones is not a constraint — it is how StreamFuse has run from day one, and it is proof of concept for a product built to solve exactly these kinds of coordination gaps.
Team Architecture — Lean by Design
DESIGNED LEAN · NOT DEFAULTStreamFuse is a deliberately lean founding team of three co-founders. Hamza is the technical co-founder — he codes everything: product architecture, backend, and infrastructure. Hamza Kamran is the product co-founder — he owns UI/UX, stress-tests features before release, and keeps the product grounded in creator reality. Areeb is the business co-founder — he owns the financial model, advertiser growth, and revenue strategy. There is no advisory layer standing in for missing founders; the work is done by the three people building the company. This is a team that has lived the problem — Hamza streamed for years to empty rooms before building the solution.
Team architecture: technical, product, and business are each owned by a dedicated co-founder with direct professional experience in that function. Hamza ships the product and infrastructure, Hamza Kamran shapes and tests the experience with creators, and Areeb builds the commercial engine and advertiser relationships. This is a small team by design — every core function is covered by a co-founder, so velocity stays high while accountability remains clear.
Technical Grit
Solo-built production MVP in 8 days. Full-stack ownership: backend, matching logic, real-time infrastructure, and front-end — no outsourcing, no agency.
Proven Execution
Built Investify for Wiseview Dubai — a Python data engine that automated real estate ROI bundling using historical transaction algorithms. Applied that same data engineering instinct to StreamFuse's Discoverability Tool: filtered Twitch bot activity (concentrated in gambling categories), removed dead lurker data from tag metrics, and developed a proprietary weighting formula to turn noisy platform data into actionable tag recommendations. The category recommender was dropped mid-build when the data showed tags delivered 10x the signal — a product decision made from evidence, not assumption.
Founder-Market Fit
I streamed. I felt the isolation. I built the tool I wished existed — because this problem is real, and the solution works.
When the Data Says Cut It, Cut It
Mid-build, the Discoverability Tool had two components: a category recommender and a tag engine. Data analysis revealed the category layer was polluted — Twitch's gambling categories are overrun with bots, and raw viewer counts included thousands of dead lurkers. Rather than ship a broken feature, the category recommender was dropped entirely. The tag engine — cleaned, weighted, and validated — shipped alone. This is how StreamFuse makes product decisions: data first, ego never.