Seed round · 2026
Make millions of automated decisions — faster, and far cheaper.
Nassor Frazier-Silva · nassor<at>gmail.com
The problem
Is this card payment fraud? What price do you see? Which ad? Do you qualify for the loan? Is this post allowed?
Companies make millions of these decisions every second — and a piece of software has to check each one against a long list of rules.
Why it's a problem
Every extra millisecond is a customer waiting at checkout, or fraud slipping through.
It burns enormous computing power — one of the biggest lines on the cloud bill.
The solution
Same answers. Same rules. A fraction of the time and cost.
The payoff
Faster decisions win customers; cheaper decisions widen margins. Winnow does both at once.
Measured head-to-head against real databases — the numbers are on the next two slides.
Proof · measured, not promised
One real-time decision: a 10-condition rule across 10 columns, over 3,000,000 records, with no index — because real rule books reference too many column combinations to pre-index.
Answers from pre-built column summaries — it never reads the data row by row.
Must scan, plus milliseconds of fixed overhead on every query.
Reads every row to answer one decision.
Bars drawn to scale — shorter is faster. Winnow's is the green sliver: too small to see at this scale, which is the point.
And one machine sustains ~12 million decisions a second even while the data is updated live — no locks, no slowdown. Databases stall under that load.
Proof · the cloud bill
To sustain 100,000 decisions per second, around the clock, at typical cloud rates — what a year costs:
A rounding error on the cloud bill.
+$124K every year for the same work.
+$2.0M every year for the same work.
Bars drawn to scale — the year's bill for the same 100,000 decisions every second.
At a million decisions a second, multiply by ten — the database path runs to $20M a year.
Measured head-to-head at 3M records on a 16-core (32-thread) workstation, July 2026.
Market · where it matters most
Market · the sweet spot
Millions to billions of decisions a day — where a small saving per decision is an enormous saving overall.
Answers needed in milliseconds, in the live path of a payment, a page, an ad.
Thousands to millions of rules checked at once — exactly what old engines handle worst.
That's fraud, adtech, and pricing first — the workloads with the most decisions, the tightest time limits, and the biggest cloud bills.
Why now · AI
Each model score must pass business policy — thresholds, exceptions, legal bounds — on every event, instantly.
One request fans out into dozens of automated actions, and every action needs a permission check on the hot path.
The rules layer is where a business steers its AI — and it has to run in microseconds. That layer is Winnow.
Market · size
Bottom-up: every company making high-volume decisions already pays for this tier — in software licences and in the cloud compute to run it. Winnow sells into both budgets.
Sources: MarketsandMarkets (fraud detection & prevention, 2025→2030; BRMS, 2025), Market Data Forecast (real-time bidding, 2025→2033), Statista (programmatic ad spend, 2024). Third-party analyst estimates; sizes vary by definition.
Traction
A real, working engine with native libraries for Rust, Python, Java, Go, Node.js, C#, and C — teams adopt Winnow from the language they already use, no rewrite required.
Why now
Team
The ask
To turn a working engine into a company. Roughly:
Nassor Frazier-Silva · nassor<at>gmail.com