Build vs. Rent

"Rent the parts anyone could sell you. Build the part that has to stay yours."

The First Question Anyone Asks

Wispr Flow works. It's polished, it's fast, and it drops cleaned text into any app. So the honest question about building Firekeeper is the same one every self-built tool has to answer: why build at all? If the answer is "mine is slightly nicer," you're rebuilding a red ocean for ego. There has to be a capability you literally cannot buy.

What You Can Rent, What You Can't

Split the needs. Most of a dictation product is a commodity — the same for every user — and should be rented or reused:

Need                        Verdict     Why
----                        -------     ---
Good ASR model              Reuse       Whisper / WhisperKit are open, on-device
System-wide hotkeys         Build-thin  OS APIs; small, not novel
Text insertion              Build       OS-specific, but not a product moat
Voice never leaves my Mac   BUILD       No cloud product can offer this
My own cleanup brain        BUILD       Pippa-flavored, not a generic model
Works with wifi off         BUILD       A subscription is dead without network

The Rows You Can't Buy

Three rows carry the whole app. Wispr Flow's own data-controls page says transcription happens in the cloud — so "my voice never leaves my Mac" is a capability their architecture cannot sell you, no matter how good the product is. "My own cleanup brain" means the polish pass sounds like Pippa, not a generic assistant. And "works with wifi off" is the one that ends the argument: a cloud subscription is a brick on an airplane, and Firekeeper is not. Those three are the blue ocean. Strip them away and a monthly subscription would genuinely be the smarter choice.

Build only what can't be rented. If a need is a commodity — identical for everyone, satisfiable by a stored model or someone's SaaS — rent or reuse it. Build only the needs that must stay on your machine, sound like you, or survive with no network. For Firekeeper that's exactly three rows, and they carry the app.

Reuse funds the build. Firekeeper doesn't train its own ASR — it stands on WhisperKit. Reusing the commodity (the speech model) is precisely what frees the budget to build the non-commodity (local-only, Pippa-flavored, offline-capable). Refusing to reuse the boring parts is how solo projects die before the interesting part ships.

Conceptual Open-Sourcing

One honesty note: Firekeeper's code is private. What's shared in this quest isn't a repo to clone — it's the shape of the decisions. Why on-device STT, why an insertion ladder, why offline has to be real. That's deliberate. The reusable thing about a tool like this was never the source; it's the reasoning, and reasoning ports to any stack and any OS. That's why there's no git clone at the end of this lesson — take the reasoning and build your own.

Code

Rent the commodity, build the three rows you can't buy·text

Need                        Verdict     Why
----                        -------     ---
Good ASR model              Reuse       WhisperKit is open + on-device
System-wide hotkeys         Build-thin  OS APIs; small, not novel
Text insertion              Build       OS-specific, not a moat
Voice never leaves my Mac   BUILD       no cloud product can offer this
My own cleanup brain        BUILD       Pippa-flavored, not generic
Works with wifi off         BUILD       a subscription dies without network

# The build is justified by the three BUILD rows.
# Delete them and a monthly subscription wins outright.

Exercise

Take a subscription tool you pay for and list its needs in two columns: 'commodity (rentable, same for everyone)' and 'must-build (has to stay mine, sound like me, or work offline)'. If the must-build column is empty, keep paying — you don't have a reason to build. If it has one or two hard rows, those rows are your blue ocean.

Hint

The must-build test for a voice tool: would a privacy-conscious user or an offline user be strictly unable to use the rented version? If yes, that's a capability no subscription can sell, and it justifies the build on its own.

The First Question Anyone Asks

What You Can Rent, What You Can't

The Rows You Can't Buy

Conceptual Open-Sourcing

Code

External links

Exercise

Progress

Comments 0