06-reference/research

mac build vs buy price threshold

2026-08-18·research-brief·source: deep-research·by Ray Data Co (deep-research synthesis)
macpricingbuild-vs-buyexpense-thresholdteam-sku

The build-vs-buy math never breaks on ROI — it breaks on wallet identity, and $350 is the worst point on the curve

The question

"At what price does MAC's build-vs-buy math stop resolving toward buy for an IC data engineer expensing it personally vs. putting it on a team card?"

Surfaced as an open follow-up from [[2026-07-23-executable-agentic-info-product-pricing-scan]], which found MAC's decided $350 sits 75% above the highest verified self-serve installable comparable and proposed $200-250 as the evidenced landing zone. This brief tests whether the buyer's funding source changes that answer.

What we already know (from the vault)

What the web says

Convergences and contradictions

Synthesis for RDCO

The literal question has no single answer, because there are three price regimes and MAC's $350 sits in the seam between the first two. Regime one is the unreimbursed personal wallet: the engineer pays and never files anything. Regime two is the reimbursement regime — personal card then expense report, or a team card the engineer or their lead already holds. Regime three is procurement, and the evidence says it starts around $5k-$10k, which means MAC will never touch it at any price the founder would consider. So "avoid procurement" is not a real design constraint on MAC's pricing, and any argument for $350 that leans on it should be dropped.

Inside those regimes, the build-vs-buy math itself never stops resolving toward buy — the ROI is 5-35x at every price under discussion. What breaks is the buyer's authority to decide alone. My best reasoned estimate of the transition band, built from the $20/month personal anchor, the $200/$199 verified installable ceiling, and the absence of any personal-wallet comparable above $200: an IC data engineer buys unreimbursed and without hesitation at ≤$100; buys unreimbursed with real deliberation from $100 to roughly $200-250; and above roughly $250 flips to assuming the company should pay — which means asking. In the reimbursement regime the ceiling is far higher and much fuzzier: $1,000-$2,500 is where I would expect an expense report on a one-time software purchase to start attracting a conversation, and I want to be explicit that this range is inference from the $100-200/month employer-funded anchor ($1,200-$2,400/yr) and the ~$5k procurement floor, not a documented policy number. Nobody publishes the number this question asks for. A brief that hands over a precise crossover point here would be manufacturing it.

The actionable consequence is that $350 is the worst available point on the curve, and this is a stronger argument than the parent brief's. [[2026-07-23-executable-agentic-info-product-pricing-scan]] argued $350 is too high because no verified comparable clears above $200. That is a market-ceiling argument and it is contestable — MAC is more verticalized and better outcome-anchored than a Realtor skill pack, and being at the top of an observed curve is defensible. The wallet argument is different and harder to wave away: $350 is above the price an IC can decide alone, and below the price at which you would bother building anything for the person they'd have to ask. It buys the friction of the manager conversation without buying any of the upside of a team sale. It also puts that conversation directly at odds with the "level up, not replace" frame — the engineer now has to explain to their lead why they need purchased expertise, which is precisely the sentence positioning principle 2 exists to avoid.

The fix is a two-SKU split, not a price cut, and the category has already run this experiment. Put the single-seat SKU at the top of the personal-decision band — $199 is the defensible number: it lands in the parent brief's $200-250 evidenced zone, sits at the verified installable ceiling, clears the $15-49 prompt-pack cluster by 4-13x, and critically stays under the threshold where the buyer stops feeling entitled to decide. Then add a self-serve 5-seat team SKU in the $500-$900 range ($100-180/seat) aimed squarely at the reimbursement wallet, where the ROI story is strongest (8-40 hours × $200-300/hour × every model the team owns) and where the observed ceiling is 4-10x higher. This is not an enterprise motion and does not violate the "no book a demo" rule — CLSkills sells a five-person pack through the same checkout as its $15 cheat sheet, and Epic React resolves it with a two-word toggle. It also converts the revenue objection into a non-issue: $350 → $199 is only a 43% cut if the team buyers disappear, and the whole point is that they were never being sold to. Passion.io's 41% lift from laddering over a flat $349 is independent, if imperfect, support for the same move. The single caution worth stating plainly: I am recommending a structure with high confidence and specific numbers with moderate confidence, and the first 100 sales remain the only real test — which is exactly the revisit condition [[2026-05-14-mac-pricing-intent]] already wrote down.

Why this is in the vault

This resolves the last open pricing question standing between MAC and launch: it converts the $350-vs-$200-250 argument from a single-number dispute into a two-SKU design decision, and it directly triggers the "buyer use patterns reveal a clear higher-touch tier candidate" revisit condition in [[2026-05-14-mac-pricing-intent]] before launch rather than after. If accepted, it adds a pricing-page tier item to [[2026-05-14-mac-prelaunch-readiness-checklist]], which currently assumes one price and one buyer.

Open follow-ups

Related

Sources