← Back to browse

Redox

by Nico SkavarskyLaunched 2014via Nathan Latka Podcast
See all API companies using community →
MRR$400k/mo
Growthcommunity
Pricingsubscription
Built inabout 1 year
The Spark

Nico Skavarsky spent years in corporate roles before going to graduate school for economics and then joining Epic, the large electronic medical record company. He went to Epic to get access to health data, hoping to find ways to use it to improve care. What he found was that the data was not in the cloud. It sat in basements and data centers that health systems managed around the country. Meanwhile, co-founder James had been helping startups connect to health systems and repeating the same integration project each time. The two saw the opportunity to build one engine that could do this at scale.

Building the First Version

The founders spent their first year without revenue. They worked out of a co-working space they had helped start, lived on savings and consulting work, and eventually committed to the scalable interface engine idea. They raised a small seed round of $350,000 at the end of 2014, hired their first developers, and paid all founders and early staff the same salary of about $35,000 per year. Nico said the pitch to investors was about potential rather than traction. Redox was selling the idea of being the infrastructure that developers would use to sell into hospitals.

It took about a year from late 2014 to go live with the first site. The first live integration connected an iPad app that measures blood loss in the operating room with Hackensack University Medical Center, sending C-section blood loss data into the electronic medical record through Redox. That first live customer, along with a few hundred developers who had signed up to build on the APIs, helped the company raise a $3.5 million Series A at the end of 2015 when monthly recurring revenue was only about $1,000 to $2,000.

Finding the First Customers

Redox's main early strategy was to win developers first. Nico described it as selling pickaxes to the developers fighting to innovate in healthcare. Those developers would then bring Redox into health systems as they sold their products. Redox avoided adding an extra contract to the sales cycle. Instead, it became a subcontracted layer in the developer's stack, with pricing per health system connection at roughly $1,000 each.

What Worked (and What Didn't)

The pricing model worked because usage-based billing was impractical. Health systems send huge volumes of messages, so Redox charged per connection instead. Retention also held up: only two of about 200 live connections were lost, both when a health system chose not to extend a pilot. Growth stayed largely inbound.

The gap was in measuring acquisition. Nico admitted Redox had not done the math on customer acquisition cost, including the hours spent on content and onboarding. Much of the capital went to headcount, not marketing, with most of the team working on engineering, DevOps, and documentation.

Where They Are Now

By the interview, Redox had raised about $14 million including a $9 million Series B and a strategic investment from Intermountain Health System. It had around 35 employees, about two-thirds in Wisconsin, with others spread across Portland, Austin, and Chicago. Roughly 200 applications were live across about 100 health systems, and the host estimated monthly recurring revenue at about $400,000. Nico said the focus was on getting into more health systems faster. He also said Redox would not sell to large pharmaceutical acquirers because it did not believe they could solve the problem as quickly.

Why It Worked
  • •Redox was built around a real infrastructure gap that the founders understood firsthand from working inside Epic, which made their pitch credible to developers and investors.
  • •Charging per health system connection rather than per API call matched how healthcare data actually flows, so pricing stayed predictable for customers and simple to sell.
  • •Winning developers first created a pull-through effect in which each developer brought Redox into health systems without adding a separate procurement step.
  • •Very low churn, with only two lost connections out of about 200, suggests the product became embedded in customers' technical stacks.
  • •Growth came mostly from inbound interest, which indicates the market was actively looking for the solution once it was visible.
How to Replicate
  • 1.Identify a data or integration problem you understand from direct experience in an industry, then validate that developers or buyers are actively trying to solve it.
  • 2.Build the first integration with one real customer before raising, using that live deployment as proof that the platform works.
  • 3.Price around the way customers' costs scale, such as per connection, instead of usage metrics that are hard to predict or control.
  • 4.Make developers your first customers and design the product so they can resell it into their own buyers, removing an extra contract from the sales cycle.
  • 5.Track customer acquisition cost from the start, including content and onboarding time, so you can decide when to invest in marketing versus headcount.

Similar Companies

Nexosis

$1.0M/mo

Nexosis is an AI/ML API platform founded in 2015 that helps developers and enterprises build accurate forecasting and impact analysis applications without deep data science knowledge. The company monetizes through a freemium developer model (charging $0.10 per 1,000 predictions) and enterprise consumption-based plans averaging $10,000/month, currently serving 100+ enterprise customers with over 1 million predictions per month and doubling month-over-month growth.

90.io

$250k/mo

90.io is a bootstrapped SaaS platform built by veteran entrepreneur Mark Abbott that provides an integrated suite of tools (meeting, planning, goal-setting, feedback, process management) designed to help companies build on the EOS (Entrepreneurial Operating System) framework. With 1,920 paying customers at $140 average monthly revenue and $250K MRR, the company has achieved impressive unit economics ($3M ARR from a bootstrapped model with only 50% net burn between $50-100K monthly) and exceptional retention with 136-140% net revenue retention, primarily driven by organic growth within entrepreneurial communities like EOS coaching networks and organizations like Vistage and YPO.

Maverick 1000

$150k/mo

Yannick Silver is a serial entrepreneur who bootstrapped seven businesses to seven figures and is now building Maverick 1000, a peer-to-peer member-driven organization of 120+ game-changing entrepreneurs paying $1,500/month ($150/month of which goes to impact initiatives). The group has deployed over $2 million in impact funds while generating $1.8M+ ARR, combining business growth, experiential retreats, and social impact through a carefully curated ecoverse of entrepreneurs.

SafeWo Labs

$130k/mo

SafeWo Labs built a passwordless authentication plugin SDK that enables banks, e-commerce platforms, and cryptocurrency exchanges to authenticate users without passwords or one-time codes. Starting from zero in February 2021 with first code written in July 2020, they grew to $130,000 MRR in 12 months through product-led growth and community engagement, primarily via their 12,000-developer Discord and Slack communities. The company raised $1M total across pre-seed and seed rounds and is closing a $9M Series A at a $65M valuation.

Client Attraction

$80k/mo

Johnson Emanuel, a Lagos-based marketing consultant, grew Client Attraction from about $32,000 in its first year (2013) to roughly $231,000 in 2015. Clients pay $5,000 to $20,000 per month on six-month minimum retainers, and by 2016 he had reached about $800,000 in revenue after shifting to fewer, ideal clients and heavier paid media.

Related Guides

Read original source
Source quote for monthly revenue
So you're doing about 400,000 bucks in monthly recurring revenue, 200 developers building these things.

AI-extracted from the linked source. Monthly revenue can include one-time sales or donations, and may describe a later stage than the first-customer story.