KPIKIT Reaches HICOOL Beijing Semifinals | KPIKit
HICOOL SemifinalistCompany News<br>We Built a Ferrari Engine in Our Garage<br>How a bootstrapped Latvian RevOps and KPI optimization platform reached the semifinals of Asia's biggest tech entrepreneurship competition.<br>KPIKIT, a bootstrapped RevOps and KPI optimization platform built in a garage in Latvia, has reached the semifinals of the HICOOL Global Entrepreneurship Competition in Beijing - one of Asia's largest startup competitions - competing against 12,000+ global AI and tech startups without ever raising outside funding. This is the company's own account of how it got there.
Quick Facts for Press
CompanyKPIKIT<br>Founder & CEORihards Buks<br>HeadquartersLatvia<br>FundingFully bootstrapped
Public launchMar 5, 2026<br>MilestoneHICOOL Global Entrepreneurship Competition semifinalist<br>Competing field12,000+ startups<br>Websitekpikit.com
RB<br>Rihards Buks, Founder & CEO<br>Aug 13, 2026 11 min read
Follow on Google
What is the HICOOL Global Entrepreneurship Competition, and what did KPIKIT achieve there?
The HICOOL Global Entrepreneurship Competition is one of Asia's largest global startup competitions , held in Beijing and open to projects across 12 major tech verticals. It draws applications from tens of thousands of companies worldwide, and judges founders on substantive criteria: the founder and team, the innovation itself, the market opportunity, progress to date, financing, and a concrete plan for operating in Beijing.<br>KPIKIT applied in the Software and Information Services / Technology Services track. We did not treat it as a lottery ticket - we treated it as a design constraint. Could we explain our innovation clearly enough to impress judges who see new AI and SaaS projects every week? Could we articulate a credible plan for entering China, not just "someday" but in phased steps? Could we defend our unit economics under questioning?<br>When KPIKIT was selected and later reached the semifinals, competing against 12,000+ global AI and tech startups , it was not just a badge. It was a signal that the engine we built in a Latvian garage could sit on the same stage as some of the most ambitious tech projects in the world.
What problem is KPIKIT actually solving?
For more than two decades, our founder Rihards sat on both sides of the table: agency and client, C-level and operator, marketer and analyst. The pattern was always the same. Marketing teams celebrated +15% in clicks, rankings and traffic . Finance teams reported 0% revenue growth . Board members stared at dashboards that looked excellent next to a P&L that did not.<br>Tools like GA4, Search Console, heatmaps, experimentation platforms and BI suites did their job - more data, faster, in nicer charts. But when the conversation turned to "where exactly is this website leaking money" or "what do we fix first, ranked by financial impact, not just severity," there was usually silence.<br>We wrote our founding principle on a whiteboard and never changed it: "If you can't track your revenue leaks, you can't improve them. Stop fixing bugs. Start fixing your revenue."
What does KPIKIT do when you paste in a URL?
We did not set out to build another analytics tool. We set out to build something narrower and more opinionated: a system that turns SEO, UX, technical and content issues into priced revenue leaks . Practically, KPIKIT does three things when a URL comes in:<br>Scans 100+ KPIs across code, SEO, UX and content - including Core Web Vitals and structured data.<br>Benchmarks those signals by industry, geography and seasonality.<br>Estimates revenue impact and produces a ranked list of fixes - in money, not just severity scores.<br>Under the hood is a proprietary model we call the Clover Engine . It does not try to predict an entire business. It focuses on one job: estimating how much incremental revenue a site might recover from fixing a given issue, and how confident that estimate is. The result is not another health score - it is a financially ordered to-do list, the same lens behind our traffic prediction modeling and conversion scoring.<br>We call it a "Ferrari engine" not because it is flashy, but because we wanted race-car telemetry for the web - a way to see where you are losing speed and fuel, and which adjustments actually move the needle on lap time.
Why did the founder build KPIKIT in a garage, and why stay bootstrapped?
KPIKIT grew up outside the usual gravity wells of big tech hubs. From 2024 to early 2026, we made a deliberate choice: no external funding . That meant 18-24 months of product research funded from our own savings and consulting work, architecture decisions made for long-term maintainability rather than short-term growth at all costs, and the freedom to say no to features that did not serve the core mission of pricing revenue leaks.<br>Bootstrapping imposed constraints, and those constraints became design advantages. We could not afford a complex onboarding process, so KPIKIT starts from the simplest possible...