Tool · Chapter 10
The honest objections
A founder who knows the eleven cracks in their own project —and has an answer for each one— inspires far more confidence than one who only repeats that everything will work out. Here they are, no makeup. Tap each one to see the objection… and the answer.
01 “Ranchers won't adopt technology”
The real bottleneck isn't whether you can build a website for thirty dollars. It's the generational inertia of a producer who has run his ranch by eye for forty years. Technology doesn't sell itself just because it's good; in the Mexican countryside, even less so.
This is the most important objection, and it's right about one thing: the cost of acquiring your first ten customers —measured in time, in cups of campfire coffee, and in miles of dirt road— is sky-high. But there's a known pattern: trust, once built with one person, transfers from you to the system. The day your satellite recommendation saves a producer tens of thousands of pesos in hay bales, the next season he no longer needs the handshake: he needs the notification. That's why the validation method starts with the lighthouse ranch and with mud on your boots, not with a mass email.
02 “Physical friction breaks the exponential math”
If every sale requires a human to travel, get their boots dirty, and shake a hand, your marginal cost doesn't trend toward zero. It's like laying an internet network where every connection forces you to show up in person to run the cable. Human friction breaks the exponential math.
You have to be precise about what you're selling. You're not selling the service of moving cattle —you're not a ranch-hand agency—: you're selling the intelligence system that tells the producer where and when to move them, and that is code, pure information, with a marginal cost near zero. The physical execution is supplied by the ranch's own structure. The producer isn't paying you to go move the cow; he's paying you for the certainty of where and when to move it.
03 “All that legal structure dismantles the "one person" idea”
Going from a thirty-dollar MVP to a Delaware holding company, convertible notes, and liquidation preferences written in English is no longer a one-person job: you need a battalion of expensive lawyers.
Granted, and it's worth saying plainly: the one-person company describes the validation and product phase, not the institutional-capital phase. When you reach the SAPI stage or jurisdictional arbitrage —if you reach it— of course you surround yourself with advisors; that's what you raised capital for. (The SAPI is Mexico's investment-promotion stock corporation; look up your own country's equivalent.) What doesn't change is who steers: you remain the only one who understands the animal, the pasture, and the producer. Legal sophistication is the tool of an advanced stage, not the starting point.
04 “Global capital doesn't understand the smallholder”
The quick-return expectation of a fund in a New York skyscraper collides head-on with the reality of a Veracruz ejido smallholder running on razor-thin margins. Those two worlds don't understand each other.
True —until the data reconciles them. The ranch that used to be an opaque asset to capital becomes auditable and predictable once you turn it into data: biological risk gets tamed with mathematics. You become the translator between two worlds, the paddock and the skyscraper —and that bridge, today, doesn't exist without someone like you.
05 “And why you, and not a Silicon Valley programmer?”
If this is such a good idea, what makes me think I can pull it off and not an engineer in California with more capital and more code? Who am I to do this?
This is the objection you carry inside: impostor syndrome, and the answer is short. Artificial intelligence already writes the code —that stopped being scarce—. What it can't do is recognize a parasite infestation, read a cow's body condition, or run a forage balance in the humid tropics. The scarce input of a livestock startup isn't knowing how to program: it's knowing livestock. And that's what you have, not the engineer in California.
06 “What if I depend on a foreign corporation that controls the AI?”
This whole AI-native company runs on the API of a foreign corporation. They can raise the price on you, change the rules, or cut off your service; you pay in dollars and your ranch's data lives on someone else's servers. You're building on rented land.
It's the most serious objection in the bunch, and you have to grant it: depending on a single foreign provider is a real risk —of cost in foreign currency, of changing terms, and of data sovereignty—. The answer isn't to ignore it, but to design against it. Today there are open-weight models you can use and even run yourself: Llama, Mistral, DeepSeek, Qwen, Gemma. The discipline of the sovereign founder: don't marry a single provider, keep your data exportable, and treat compute like any other input —with a plan B—. Your asset isn't the model of the moment; it's your clinical knowledge and your herd's data, and those are yours.
07 “And when you have two thousand ranches? The human bottleneck doesn't scale”
It sounds very zen at ten ranches: you review two alerts with your coffee and approve. But at two thousand ranches you won't have two alerts, you'll have two thousand exceptions waiting on your ethical sign-off. Your closed loop becomes a noose around your neck.
You have to grant part of it: you're right that it isn't infinite —a business that touches biology and ethics doesn't scale like a row in a spreadsheet—. But it's wrong about one thing: it assumes the exceptions grow with the network, and it's the reverse. By Metcalfe's Law and the data moat, the network learns from each of your decisions: when you resolve an outbreak on ranch A, the system neutralizes the same alert on ranch B by itself. The exceptions thin out as the model matures. The ceiling exists —maybe a hundred times higher than the linear clinic's, not the infinity of the Petri dish—, and that human bottleneck isn't a flaw: it's your supreme quality control, the thing that makes your moat indestructible.
08 “What if the AI learns to have your same clinical eye?”
Your whole thesis rests on your clinical eye being the scarce input an engineer can't copy. But what happens when the AI does replicate it and that judgment becomes a subscription service anyone rents for a few dollars a month? That's when your moat collapses.
It's the deepest objection in the book, and you have to grant the core of it: the AI will likely democratize the knowledge. The 'what' —what a parasite infestation looks like, what threshold triggers an alert— will stop being the monopoly of someone who studied six years; that knowledge tends toward a commodity. But the moat doesn't evaporate, it moves, and three pillars survive: the physical interface between bits and atoms (the AI in the cloud doesn't reach its arm into a dystocia at three in the morning), the collective data you already hold (the Waze-style network isn't bought in a subscription), and the trust of the trade and your local roots. When the knowledge becomes a commodity, the moat moves from knowledge to position: the physical, the network, and the trust. And the winner is whoever already built that position, not whoever just rents the model of the moment.
09 “Isn't the profitable niche just settling?”
All this talk of exponential startups, and in the end you tell me a profitable niche is fine. Isn't that giving up, putting a ceiling on ambition?
You have to separate two things you're conflating. A niche with a moat —a brand, a specialty, a defended product— isn't settling: it's ownership. It gives freedom, margin, and a price you set. What this book fights isn't smallness, it's the role of price-taker. That said, I'll grant the other part: yes, the book's goal is to convince you that the exponential is within your reach, and that's why it pushes you upward. Choosing the niche is legitimate; choosing it out of fear, without ever peering at what you could build, would be the only real way to settle.
10 “The physical doesn't scale: this only works for apps”
Software gets copied a million times at no cost, but a cheese, a biodigester, or a vaccine are atoms: you need plants, logistics, capital. That's not a Petri dish, it's a factory. Your exponential only applies to the one who codes.
I'll grant half: the physical scales differently —with capital, process, and logistics, not with servers—, and its curve climbs more slowly. But the other half I refute with facts: the largest meat processor in the world bills tens of billions; a free-range egg brand grows at double digits; an integrated tropical ranch exports to Japan. The physical scales too, and when you add brand, traceability, by-products, and a network, its moat is sometimes deeper than software's, because it can't be copied by downloading a repository. Scaling isn't multiplying free copies: it's capturing more and more value, and that's done with atoms or with bits.
11 “This is all livestock; I'm not a field person”
Your examples are cows, pastures, ranches. I work in a dog clinic, or in a lab, or with fish. This book isn't for me.
This book's terrain is livestock because that's where its author's feet are, and where the waste of value is plain to see. But the method —see, validate, build, capture, scale— doesn't care about species. Remember the colleague from the first page, who applied it to bees and became a national authority; and remember that the largest veterinary market in the world is pets. If your field isn't livestock, you're not left out: you're standing before a terrain less explored than ours, with the same method in hand.
Honesty about your limits doesn't weaken your pitch: it armors it. In front of an investor, a professor, or a rancher, knowing your cracks and having an answer for each one is worth more than a thousand promises that everything will work out.
The book develops each one in depth —with its nuances and concessions— and brings ten more chapters. Take a sample chapter and start validating your idea.
No spam, truly. We only write when there's something worth your time —series news and resources—. Unsubscribe anytime.