Kendrick Horeftis
OverlayAnalyticsJun 2019 - Feb 2022

Bringing Fortune 500 Visibility to the Middle Market

Mid-market companies generated the same financial complexity as enterprises ten times their size, but lacked the institutional knowledge to turn their data into decisions. I helped co-found OverlayAnalytics to close that gap: a turnkey platform that replaced six-week reporting cycles with intraday visibility, without requiring clients to hire specialists or understand data engineering. Bootstrapped to a $3.3M seed round and acquired in under three years.

Stage
Pre-seed B2B SaaS
Scale
50+ onboarded companies, 3-person founding team
Challenge
Real-time financial visibility was inaccessible below the Fortune 500
Role
Co-Founder / Technical Architect
Stakes
Bootstrap to product-market fit or fold
AWSSnowflakedbtCube.jsReactKafkaKubernetesTerraformAirflow
6 wk → 4 hr
Reporting Latency
$3.3M
Seed Round Raised
Acquisition
Exit Outcome
Near Zero
Marginal Client Cost
01

The Problem

Mid-market finance teams were making critical decisions on data that was already six or more weeks old. Controllers and FP&A leads spent the bulk of their time manually compiling numbers from disconnected systems, reconciling everything in spreadsheets, and distributing reports that were stale on arrival. Leadership could not answer basic follow-up questions without kicking off another manual cycle.

  • Companies doing $100M+ in revenue were consistently slower to spot cash flow problems, react to margin shifts, and course-correct on operating plans
  • Fortune 500 companies solved this years ago with dedicated data engineering teams. Mid-market companies did not even know what that hire looks like
  • The barrier was not budget. It was a knowledge gap: these companies could not buy their way to better visibility because they did not know what they were buying

The market did not need another dashboard. It needed someone to deliver the output without requiring the client to understand the machinery behind it.

02

The Approach

Every architectural decision was driven by one constraint: zero external funding. Every infrastructure dollar had to produce measurable client value.

  • Compute costs stayed near zero during idle periods by processing data only when clients needed it, eliminating the fixed overhead that would have killed margins before reaching scale
  • Strict tenant isolation for sensitive financial data, with elastic scaling that required no dedicated infrastructure per client
  • A proprietary transformation layer allowed a single set of financial models to run across 50+ isolated client environments simultaneously, driving marginal onboarding cost to near zero
  • Purpose-built reporting with pre-computed caching for sub-second dashboard response, avoiding third-party per-seat licensing that would have destroyed unit economics

Three months from first line of code to a working product. A paying customer in month one.

03

The Impact

The architecture built for bootstrap economics turned out to be the product's strongest competitive advantage. Near-zero marginal onboarding cost let the platform scale across 50+ companies without proportional infrastructure spend, validating the unit economics that attracted institutional capital and ultimately led to acquisition.

  • Reporting latency compressed from six weeks to intraday updates every four hours
  • Finance teams and company leadership gained real-time visibility to act on emerging problems instead of reacting to stale reports
  • Won the inaugural Snowflake Startup Challenge, judged by Snowflake's co-founder, Sequoia Capital, and Sutter Hill Ventures
  • Raised a $3.3M seed round from institutional investors
  • Exited via successful acquisition
04

The Lesson

Capital efficiency is not a startup constraint to be overcome. It is a permanent architectural principle.

  • Every design decision forced by bootstrap economics produced a platform that remained cost-efficient at scale
  • Revenue concentration is a structural vulnerability, not a growth strategy. The system must be resilient to losing any single dependency
  • Both lessons now shape how I evaluate architecture decisions in any context: the system must survive the loss of any customer, vendor, or funding source