Skip to content

I Find What's Broken. I Build What's Missing.

I'm Eric Reid. 25 years of building and fixing products, two acquisitions, and I still ship code every week. Companies bring me three kinds of problems.

$4B EXIT · 13X TEAM GROWTH · 57% REVENUE GROWTH · 2M USERS

02 — THE RECORD

Real outcomes, real companies.

Not resume lines. These are specific results from specific engagements.

$ 4 B

PAYPAL ACQUISITION

I hired the Android team at Honey, built the mobile infrastructure, and launched to 2 million users. When PayPal acquired Honey for $4 billion, that mobile stack held up under diligence.

13 x

ENGINEERING TEAM GROWTH

I took Alo Yoga engineering from 5 to 65 people. I built the hiring process, team structure, and architecture to support revenue growth from $350M to $550M.

$ 3 M+

ANNUAL SAVINGS

I redesigned Alo Yoga's infrastructure with a serverless architecture that cut over $3 million per year in operating costs. Sometimes the biggest wins are in what you stop paying for.

2 M

USERS IN SIX MONTHS

I went from zero to a shipped Android app with 2 million active users in six months at Honey. I hired the team, defined the architecture, and shipped it.

03 — WHO YOU'RE HIRING

Two acquisitions, 25 years of building.

I was the first employee at Gnip, where I built the core product before it got acquired by Twitter. Then I built Honey's Android team from nothing to 2 million users, which became part of PayPal's $4B acquisition. Two startups, two acquisitions. That doesn't happen by accident. Before all of that, I wrote satellite firmware and communication systems for the space shuttle program. I've been building iOS apps since the iPhone came out. Founded a company. Taught programming because I genuinely like explaining hard things simply.

The through line: figuring out what actually needs to happen and making sure it gets done.

And I still write code every week. Right now I'm building an MVP for a client: a privacy-first behavioral health platform. Native iOS app, web dashboard, backend, statistical alerting engine. Four codebases, one engineer.
YEARS BUILDING
25
ACQUISITIONS
2 — TWITTER, PAYPAL
COST CUT
$3M+/YR
CURRENT BUILD
4 CODEBASES, SOLO
Eric Reid
Eric Reid writing code at a cafe table

04 — THE RATE CARD

How we work together.

Five ways in, depending on where you are and what you need. Real prices, because guessing helps nobody.

E1

Rapid Teardown

Focused diagnostic. I audit your code, your architecture, your team — including the app you vibe coded. You get a prioritized action plan your team can execute immediately.

Best for — You suspect something is wrong but need someone to pinpoint it.

~$9.5K

The guarantee: if the teardown doesn't tell you something you didn't already know, you don't pay for it.

E2

Deep Audit

Everything in the Rapid Teardown, plus I go deeper into your architecture, your team, and your competitive position. You get a phased roadmap your board can actually understand.

Best for — Preparing for a major investment or platform decision.

~$25K

E3

90-Day Growth Sprint

I embed with your team for 90 days. Hands-on leadership, not advisory. We pick the metrics that matter and move them. This isn't consulting. It's doing the work.

Best for — You need results now, not a report.

~$75K

E4

Fractional CTO

Ongoing technical leadership. Architecture decisions, team structure, vendor calls, code reviews, incident response, hiring. Part of your leadership team.

Best for — Between CTOs or not ready for a full-time hire.

$4K-$20K+/mo

A full-time CTO runs $300K and up before equity. This buys the part you actually need.

E5

Zero-to-One Build

You have a product idea and no engineering team. I design it, build it, and ship it. Production grade, not a prototype. The current one: a privacy-first health platform, four codebases, native iOS app to the data science, built solo.

Best for — Founders who need version one shipped by someone who has done it before.

Scoped per project

05 — STRAIGHT ANSWERS

The questions people actually ask.

How many hours do I actually get?

It depends on the engagement, and we set it together up front. The lower end of the fractional range is a few hours a week of advisory. The upper end is me in your standup, acting like your CTO. What you never get is a junior consultant subbed in behind the scenes.

Do you write code or just advise?

Both. I still write code every week, and right now I am shipping a four-codebase health platform solo. If your problem needs hands on a keyboard, mine are available.

Why is the teardown $9.5K?

Because it is two weeks of my full attention, and you get every finding, not a teaser for a bigger contract. It also comes with a simple guarantee: if it does not tell you something you did not already know, you do not pay for it.

What if we already have engineers?

Good. Keep them. I am not here to replace your team, I am here to make the calls they should not have to make alone, and to leave them stronger than I found them. If you already have senior technical leadership that is working, then I am not the right fit.

What happens when the 90 days end?

You keep everything: the roadmap, the processes, the hires, the momentum. Some clients move to a lighter fractional arrangement. Plenty just shake my hand, and that is the point.

Can you fix my vibe coded app without judging me?

Yes. You shipped something people actually use, which is more than a lot of beautifully engineered codebases can say. I will meet the app where it is and make it production grade without starting over.

Do you only do mobile?

Mobile is where I made my name, but the work is broader: web platforms, backends, data pipelines, AI features. The build I am shipping right now runs from a native iOS app all the way back to the statistical engine behind it.

06 — THE TEARDOWN

Two weeks. Every finding. No jargon.

In two weeks, I'll give you what your team can't: an honest, outside view of your situation. Your code, your architecture, your team. This isn't a technical audit full of jargon. It's a clear answer to the questions keeping you up at night.

Should you rebuild or fix what you have? Where is the next outage hiding? Which changes will actually move the needle? You walk away with a roadmap any competent team can execute.

  • Stack and architecture review
  • Security and data review
  • Conversion or activation funnel analysis
  • Team and process evaluation
  • Prioritized roadmap

08 — NEXT STEP

Let's figure out what's going on.

30 minutes. I'll tell you the three things I'd fix first. No pitch, no runaround. Just a straight conversation about what's happening and what I'd do about it.

RATHER EMAIL? [email protected]

Open for new engagements · Replies within one business day