--- title: "How we booked 983 enterprise meetings for a precision agriculture platform in 90 days. | Stone Haven Capital Group" description: "$113M of opportunity pipeline behind them, and $35.9M of signed contract value. Ninety days. A precision agriculture SaaS platform. No new sales hires, no trade show circuit, no waiting for a distributor to make an introduction." canonical: "https://stonehaven.capital/showcase/precision-agriculture-saas-platform" last-updated: "2026-08-22" --- > $113M of opportunity pipeline behind them, and $35.9M of signed contract value. Ninety days. A precision agriculture SaaS platform. No new sales hires, no trade show circuit, no waiting for a distributor to make an introduction. Stone Haven Capital Group Schedule a Call Case study · Precision Agriculture SaaS Platform # How we booked 983 enterprise meetings for a precision agriculture platform in 90 days. $113M of opportunity pipeline behind them, and $35.9M of signed contract value. Ninety days. A precision agriculture SaaS platform. No new sales hires, no trade show circuit, no waiting for a distributor to make an introduction. - $35,931,400 of signed contract value across 122 contracts, at an average of $294,520. - 2,831,607 emails to 707,902 growers, cooperatives and distributors in 90 days, producing 6,371 replies at 0.9%. - 1,403 positive replies became 983 booked meetings, 593 of them held. - Average contract value rose 3.1x from a $95,000 baseline, and 165 of the bookings were enterprise cooperatives. - What went wrong: the first list aimed a level too high. 01 ## Did they get a good result? Yes, and here it is without decoration. Before we started, enterprise adoption came from pilots, grants and regional distributor introductions, which produced a handful of new conversations a month and no way to forecast the next quarter. Ninety days later the platform had 983 booked meetings behind it, 593 of them held, $113,048,600 of opportunity pipeline, and 122 signed contracts worth $35,931,400. What happenedThe number Signed contract value$35,931,400 across 122 contracts Average contract value~$294,520, up 3.1x from a $95,000 baseline Booked opportunity pipeline$113,048,600 across 983 booked meetings, 593 of them held Enterprise cooperatives and distributors165 of those 983, including two of the five largest national cooperatives Earlier-stage interested pipeline$129,147,600 across 1,403 conversations Bounce rate1.8%, 50,969 bounces Emails sent2,831,607 over 90 days Leads contacted707,902, of which 704,318 were new Replies6,371, a 0.9% reply rate, or 21,653 and 3.1% counting out of office Positive replies1,403, 22.0% of all replies The full programme in the sending platform. 02 ## Did you get them in front of the right people? That is the question that actually matters, and volume does not answer it. Anyone can put 2.8 million emails in front of people with no budget and no season coming. 983 opportunities reached booked-call stage carrying $113,048,600 of pipeline, and 122 of those closed into signed contracts worth $35,931,400. 165 of the booked accounts were enterprise cooperatives and distributors, including two of the five largest national cooperatives. The proof of targeting is in the conversion rather than the volume. 6,371 replies produced 1,403 positive ones, 983 of those became booked meetings and 593 were held. Contract value tripled over the same period, which is the number that says the engine was reaching bigger operations rather than simply reaching more of them. Ninety days of booked meetings, against the ninety days before. The pipeline as the client sees it. 03 ## What worked, and why ### We moved every cold email off the platform's own domain. An agriculture platform cannot afford deliverability problems on the domain it uses to talk to 8,000 existing grower accounts. So no cold volume ever touched it. We stood up 1,429 dedicated sending domains carrying 4,286 mailboxes, every one authenticated on SPF, DKIM, DMARC and MX before a single email went out. Warmup ran continuously on all 4,286 for the life of the programme, and only half of them carried campaign volume at any point. The rest sat in reserve and rotated in as the older domains matured. The estate carried 2,831,607 sends across 90 days and finished at a 1.8% bounce rate, 50,969 bounces in total, inside the threshold where domains start to burn. At this volume that number is the whole game. Cross it and the domains die, and the programme dies with them. Every sending domain authenticated, and the platform's own domain kept out of it entirely. Why that works: the domain carrying every existing grower relationship stayed untouched, while the engine carried all the risk on infrastructure that was built to be replaced. ### We built the list around who is expanding, and excluded everyone who is not. The people who sign a platform contract are cooperative leadership, agronomy and operations directors, and the executives running large farming operations and distribution networks. The list was built on that profile across North America, then narrowed by acreage, crop programme and the signals an operation gives off publicly when it is expanding or re-tooling. The exclusions mattered as much as the inclusions. Equipment resellers, consultancies, hobby and lifestyle operations, and anything below a meaningful acreage threshold came out of the list entirely, which removed most of the original pool before a single email was written. Why that works: acreage tells you who could buy. The expansion and re-tooling signals tell you who is about to. ### We let the data do the personalisation instead of a person. Every email carried fields drawn from the record itself, so the message reflected the operation it was going to without anyone researching it by hand. At this volume that is the only way personalisation survives. A human writing one email at a time caps the programme at a few hundred sends a week. Plain text throughout, varied on every line, so two growers in the same county never saw matching wording. The live sequence and the opener behind it. Why that works: relevance is what earns the reply, and relevance can be assembled from data. What cannot be assembled is a reason to care, and that has to be written once, properly, by someone who understands the market. We ran a four-touch cadence on uneven waits and routed every positive reply to a booking desk. Four steps with three, four and seven day gaps, six variations on the opener and three on each follow-up, all A/B tested. A booking desk sat on the replies and worked them the same day, which is what turned 1,403 positive replies into 983 booked meetings rather than a backlog. Why that works: at this volume the constraint stops being how many replies you can generate and becomes how fast you can answer them. A positive reply left overnight is worth a fraction of the same reply answered inside an hour. ### We reviewed performance weekly and cut losers fast. Every week the angles were reviewed against reply quality rather than reply count. Losing angles were switched off within days and winning ones absorbed the volume. Across 90 days that is only twelve reviews, so each one carried real weight. 04 ## The four angles we test, in every market Nobody can predict which message a market will bite on. The honest position is that the market decides and you find out by asking it. So the opener runs four variations at once, one per angle, and the reply data picks the winner. The four hold up across sectors because they are built on how a decision gets made rather than on what is being sold. 05 ## 1. The timing hook Tie the ask to something that just changed for them. Works when the change is public and recent enough that mentioning it proves you looked. Saw the co-op added three counties this season. Does the agronomy team have a way to see all of it in one place yet? 06 ## 2. The benchmark Show them where they sit against comparable operations. Nobody knows their own percentile, and almost everybody wants to. We pulled yield variance across cooperatives your size in the same crop belt. Want to see where yours lands? 07 ## 3. The named problem Name one specific failure mode and ask whether it is theirs. Specific beats broad, because a broad problem is easy to say no to. Most co-ops we talk to are running four systems that disagree about the same field. Is that where you are? 08 ## 4. The referral sideways Ask who owns this if it is not them. Costs nothing to answer and often produces a warmer contact than the one you started with. If precision data sits with someone else on your side, happy to be pointed their way instead. 09 ## How we use them They launch together across a split list. A few weeks in, the reply data has already named the one or two the market wants, and the rest are switched off before they waste any more contacts. Which angle wins is genuinely unpredictable. That one or two of them will win is not. Running four at once is how we make that a certainty instead of a bet. The same frameworks port to LinkedIn with shorter wording and the same underlying angle. 10 ## What did not work, and what we did about it Three, written down because the corrections are the part that transfers. ### We aimed a level too high for the first month. The opening list went at chief executives and presidents, on the theory that a contract this size needs the top of the house. They did not answer, and the few who did forwarded the email without context, which is worse than silence because it burns the account and the referral at once. The first pull, aimed at the top of the house. What we changed: we moved a level down to operations and agronomy leadership, the people who feel the problem daily and own the evaluation, and layered acreage and expansion signals on top. Reply rate roughly doubled inside two weeks and the conversations started at a useful altitude. The same market after the seniority change and the acreage and expansion signals went on. ### We ramped the sending too fast in the first three weeks. A 90-day window creates pressure to get to full volume immediately, and we gave in to it. Domains that had finished warmup went to full send rate within days rather than climbing over weeks. Bounce rate crept up, a handful of domains started landing in promotions, and we spent time recovering ground we should never have given away. What we changed: the ramp was flattened into a four-week climb and new domains joined at a fraction of full rate. Bounce rate settled at 1.8% and held there for the rest of the programme. ### Positive replies sat unanswered too long once volume climbed. In week five the engine produced more positive replies in a day than the client's team could work in a day. Some sat for 48 hours. In a market where a season has a start date, a two day wait is enough for the conversation to go cold. What we changed: a booking desk was put in front of the client's team with a same-day response standard. Every positive reply after that point was answered inside working hours, which is the single change most responsible for seven in ten positive replies turning into a booked meeting. A positive reply, worked the same day. A programme this size never runs clean, and any write-up without a section like this one has edited it out. 11 ## Why this works in agriculture technology specifically Every platform we speak to in this market has the same shape of problem. The product works, the growers who use it are loyal, and enterprise adoption still depends on pilots and introductions nobody controls. That works until the board asks what next quarter looks like. Three things make outbound work unusually well here: - The buyer announces themselves. Acreage changes, new facilities, crop programme shifts and expansion news are public months before anyone signs anything. That signal is searchable, which means the timing problem solves itself. - The contract carries the cost. At an average signed contract of roughly $294,520 with renewal behind it, the programme pays for itself on a handful of outcomes. Very few channels have that arithmetic. - The data does the personalisation. Acreage, crop and region are already on the record, so an email can be specific to an operation without anyone researching it. That is what lets the programme stay relevant at two million sends. 12 ## Why would this work for your business? ### Possibly not, and the cheapest moment to learn that is before anything gets built. Read down. This works ifThis does not work if Growth depends on pilots, grants and distributor introductions you do not controlEnterprise accounts already come to you without being asked There are tens of thousands of operations you could serve and no way to reach them at onceYour entire market is a few hundred accounts a rep could work by hand A signed contract is worth six figures and renewsYour economics cannot absorb a programme that pays back across a season Something observable tells you an operation is expanding or re-toolingNothing separates an account that needs you this year from one that never will Someone can qualify a high volume of replies before they reach a sellerEvery reply has to land on the head of sales If you land on the left column, what transfers is the method rather than anything unusual about this client. A platform with a real product, a loyal existing base and no mechanism for reaching the accounts that move contract value. Everything above came out of process, and the process does not change for you. 13 ## One more thing worth understanding The 2.8 million sends is the least interesting number in this document, and it is the one everybody reads first. Volume is the easiest thing to buy. Any agency can put three million emails into a market next month, and most of what happens when they do is damage. The numbers that decide whether a programme works are the ones underneath it: how many of those contacts had a reason to care, how fast a reply got answered, and whether the accounts that converted were bigger than the ones the client was already reaching. On this engagement the volume was a consequence rather than a target. The market was large, the signal was public, and the arithmetic on contract value justified reaching all of it. Change any one of those and the right number would have been a tenth of the size. We would rather run a tenth of the volume into a list that deserves it. If your market is four thousand accounts, the programme that works looks nothing like this one, and we will tell you that in the first call rather than sell you sends you do not need. 14 ## Before and after Before After Route into enterprise accountspilots, grants and distributor introductions a repeatable engine running alongside all three New enterprise conversationsa handful a month, each hand-researched 983 meetings booked across 90 days, 593 held Signed contract valuenone from outbound $35,931,400 across 122 contracts Average contract value$95,000 $294,520, a 3.1x increase Outbound volumenone 2,831,607 emails to 707,902 leads 15 ## If you want to know whether your market has this in it Fifteen minutes is usually enough. Describe the operations you want as customers and what a signed contract is worth across its life. We come back with how many of those accounts are actually reachable, the conversation volume that is realistic against that pool, and a straight answer on whether outbound is the right instrument for you. If it is a no, you will hear it during the call. That is cheaper for everyone than learning it a season later. ## Want to know whether your market has this in it? The first conversation is short. You tell us who your buyers are and what one is worth to you. We tell you how many we can actually reach, what the meeting volume looks like, and whether outbound is the right lever for you at all. If we think it is not, we will say so. Book a consultation call → ## Read another one [Warehouse Automation Integrator](https://stonehaven.capital/showcase/warehouse-automation-integrator/)[How we closed seven automated facilities worth $8,381,800 for a warehouse automation integrator in ten months.](https://stonehaven.capital/showcase/warehouse-automation-integrator/)[AI Implementation Consultancy](https://stonehaven.capital/showcase/ai-implementation-consultancy/)[How we closed $4,320,000 of AI deployment work for an implementation consultancy in six months.](https://stonehaven.capital/showcase/ai-implementation-consultancy/)[All case studies](https://stonehaven.capital/case-studies/)