Tim Kreilkamp — sales meeting dossier

For: Luke Olson, in advance of Tim meeting Compiled: 2026-05-14 (v3 — incorporates Dan's intel after their pre-call) Source: Public sources + Dan's direct intel from Tim. Hotel intentionally scoped out per Dan + Luke's call.

Top-line shape of the meeting

• Pilot-scope conversation, not retainer. Don't pitch a monthly retainer. Frame: "we'd want to scope a defined pilot inside one slice of one business with clear success metrics, run it, and decide together from results." Tim's not buying a relationship today — he's deciding whether you're worth a $25–50K pilot to find out.
• The succession frame is load-bearing. Tim is ~5 years from handing the businesses to his son. He's not buying tools — he's building infrastructure his son inherits clean. Frame everything as: "this is what your son inherits running cleaner than the business you built."
• Confidence, not desperation. Luke walks in believing this is the right kind of operator to help and that OBB is the right kind of shop to help him. We're three partners, not Fortune 500. That's a feature for Tim, not a bug.
• Be honest about the friction layers. Farmers, drivers, and the front-desk staff who take their calls are professionally skeptical of AI. The dossier does not paper over this; Luke shouldn't either. OBB knows this and designs around it.
• The security-posture decline is a brand asset, not a deal-killer. Tim wanted financial-reporting access; Luke declined. "We won't take access to anything we can't afford to make a mistake on." That candor, delivered honestly, is the kind of thing a multi-gen operator reads as "this is a real partner, not a vendor." If it poisons the deal, you didn't want it.

Executive summary

• Tim Kreilkamp is President/CEO of Kreilkamp Trucking (~300 trucks, founded 1935) and Farmers' Grain & Feed ($30M+ Repete-automated mill opened Nov 2021). Sits inside WB Holdings + WB Warehousing & Logistics (1.6M sq ft, 150K cold-storage across WI, CA, NJ) + Brent Redmond Transportation (CA cold-chain carrier).
• John R. Kreilkamp (Tim's father) passed away ~2 years ago. Tim is now sole operator-decision-authority on these businesses.
• Tim is ~5 years from handing the business to his son. Succession planning is high on his mind right now. This shapes every conversation: he's building transferable infrastructure, not buying personal tools.
• Just divested Farmers' Implement to Johnson Tractor (eff. June 1, 2026) — held 20 years. Capital from that sale may be deployable now.
• Just acquired Gray Transportation's assets out of Iowa (March 2025). Opportunistic, disciplined.
• Tech posture: mature, not bleeding-edge. Samsara fleet-wide. Repete end-to-end mill automation. No verified AI-automation tooling deployed yet.
• Driver retention is a publicly stated, multi-year priority — co-founded the Wisconsin Regional Truck Driving Academy with Moraine Park Tech in 2022. 70% of his drivers have 10+ years tenure.

The operator — Tim's voice + style

Plain-spoken, builder-language, no-overselling. Public quotes: - On the Gray acquisition: "I don't want to go into too much detail, but certain assets were advantageous to our fleet moving forward." - On the Farmers' Implement sale: "The best path forward to ensure you continue to receive the highest level of service and equipment." - On the driver shortage: "I've been here 35 years and this is the worst it's been." - On the truck-driving academy: "We needed to provide an option with no upfront costs and access to equipment."

He talks about drivers, freight demand, family, community. Never on AI panels. He's an operator, not a tech-buyer.

Decision frame to mirror: - Continuity for the customer (his framing on the Farmers' Implement sale). - Operational fit (his framing on the Gray acquisition). - Capital deployment when convinced, never speculatively (the $30M mill). - Multi-generation horizon — he plans in decades. - Succession over self. He's building what his son will run.

Kreilkamp Trucking — deep dive

Operational profile

• Family-owned dry van + reefer + flatbed, founded 1935. HQ Allenton WI, terminal Edison NJ, additional location Horicon WI.
• Scale: ~300 tractors, 1,000+ trailers, ~140 employees, 251–300 drivers, 18M+ miles/year.
• Lanes: Midwest ↔ Eastern Seaboard. West Coast via Brent Redmond.
• Freight mix: refrigerated meats, cheese, spirits, paper, ag/manufacturing.
• SmartWay Transport Partner (EPA fuel-efficiency cert).
• Affiliated: WB Warehousing & Logistics, Brent Redmond Transportation (CA cold-chain).
• Dispatch operation: "a room full of folks with headsets" running logistics for the fleet (per Dan). This is a real, staffed operations center — not a shoestring back office.
• Named leadership: Jim Jansen (VP Logistics), Danielle Berndt (Controller), Bob Christie (Safety Director).

Tech stack

Verified: Samsara fleet-wide (telematics, GPS, ELD, driver safety, dash cameras). Forward-facing cameras on all tractors. Reefer monitoring with remote setpoint changes + out-of-spec alerts. WB Warehousing markets "state-of-the-art data center" for EDI compliance.

Samsara has a mature REST API — read access to vehicle locations, reefer telemetry, HOS, trip history, driver safety scores, documents (BOLs photographed in the Driver app), webhooks for real-time alerts. Included with Tim's existing Samsara plan; no extra cost to integrate.

Inferred: TMS likely McLeod LoadMaster (industry default at this scale). Dispatch is human-led, no AI optimization tooling visible. Customer-facing shipment visibility unclear. Fuel card Comdata or EFS. AR/billing TMS-native.

Automation opportunities (ranked by leverage)

1. Driver onboarding / academy ops. Tim already put real capital here. AI-assisted training content, multilingual onboarding briefs, automated DOT-physical + licensing paperwork chase, recruiter-side resume/lead triage. Pre-sold on the category.
2. Customer-shipment status responder. AI-drafted reply pulling Samsara GPS + reefer temp data to answer shipper "where's my load?" emails. Samsara API is the unlock here.
3. AR collections. Mid-market reefer carriers chronically chase 60–90+ day shippers. AI-drafted dunning sequences with payment-history-aware tone + exception queue for Controller Danielle Berndt. Compresses DSO without breaking relationships.
4. Reefer-incident triage + claim packet assembly. AI assembles the BOL + temp log + Samsara alert timeline + driver communications into a defense packet in minutes vs. days of clerk work.

Don't lead with: HOS / safety coaching (Samsara scores already; marginal AI lift).

Resistance / friction notes (truckers + a room of headsets don't trust AI lightly)

• Driver trust is the firewall. 70% of his drivers have 10+ years tenure. Frame AI tools as relieving driver paperwork, never as adding management oversight.
• The headset room is the second firewall. Dispatch + customer-service reps know they're augmentable-or-replaceable when AI shows up. Position AI as headset-team co-pilot, never replacement. Their participation in the pilot design is a hard requirement.
• Family-business velocity is slower than VC-backed shop floor. Pilot → observe → scale.

Farmers' Grain & Feed — deep dive

Operational profile

• LLC owned by the Kreilkamp family, acquired Jan 2006 from the original Hess-family co-op (founded 1913).
• Operations: grain storage, drying, cleaning, grinding, rolling, roasting, custom mixing; dairy nutritional consulting; seed, animal health, water softeners.
• New mill (Nov 2021) at 6868 Spruce Court Allenton — $30M+ investment, fully Repete-automated, 4x production capacity vs. prior. Currently expanding with additional storage and loadout bins.
• Hours: Mon–Fri 7:30 AM – 4:00 PM. Saturday closed.
• Phone: 262-629-4126. Orders flow through orders@fgfmill.com.
• OPERATING REALITY: two office ladies essentially run this business day-to-day (per Dan). They are the customer-service + order-intake + likely billing operation. Any pilot scope here lives or dies through them. Meet them BEFORE shipping anything that touches their workflow.
• Customer type: Dairy-heavy (explicit dairy nutritional consulting) + WI row-crop + small-farm patron base.

Tech stack

Verified: Repete Corporation end-to-end mill automation. AgriCharts for cash bid pricing + mobile market alerts. Online patron portal (customer.fgfmill.com). Email orders at orders@fgfmill.com.

Inferred: Back-office ERP likely AGRIS (Cultura Technologies) or Cultura Feed-Mill Manager. Truck/scale tickets integrated to Repete; load-out billing automated downstream.

Automation opportunities (specifics, not generic)

Production is the solved problem here. Leverage is office-side and customer-side — which sits outside Repete's domain regardless of how their interface shakes out:

1. Phone-order intake transcription. Most feed-mill orders still come by phone from farmers. AI-transcribed → structured-order intake with confirmation text-back to the farmer. Highest-leverage feed-mill automation in 2026 per industry press. The two office ladies will likely WELCOME this — less repetitive typing, more professional dignity, not threat.
2. Ingredient/inventory forecasting. Dairy consulting + custom mixes = high SKU complexity. AI demand forecasting reduces stockouts/overordering.
3. Patron-portal upgrades — conversational ordering, automated COA/batch-cert delivery, proactive low-bin alerts (BinSentry is the named-vendor incumbent here).
4. Dairy-consulting note capture. Field consultants do farm visits; notes get lost. AI-transcribed visit notes → CRM → automated follow-up.
5. Billing chase-down. Farmers pay on harvest/milk-check cadences, not net-30. AI-drafted harvest-cycle-aware AR sequences preserve relationships.
6. Patron onboarding — automated credit-application processing (currently a downloadable PDF).

Resistance / friction notes (farmers + the two office ladies don't trust AI lightly)

• Farmer tech distrust is real + load-bearing. A 65-year-old dairyman who's bought feed for 30 years will hang up on a chatbot. Every farmer-facing AI tool needs (1) a clear "you're talking to AI" identifier when AI is in the loop, (2) a human escape hatch on call one — a number that reaches one of the two office ladies who knows them by name, (3) a "coffee-counter ready" briefing so they can explain in 30 seconds what AI is doing.
• The two office ladies hearing about it second-hand is the failure mode. Talk to them BEFORE you deploy anything that touches their workflow. They likely have years of context on what farmers will and won't accept.
• Tim's Repete decision was not "let's try AI" — it was a $30M capex bet on industrial-grade automation with a proven vendor. His bar for new automation is "shows a clean ROI in production volume, labor, or compliance." Pair soft wins (chat) with hard operating-metric wins.

What's INTENTIONALLY out of scope

• Hotel + real estate. Confirmed (per Dan): hotel sits in Tim's lawyer's holding company; Tim plans to offload ASAP. Not a Relic surface. If Tim raises it, listen, don't pitch.
• Financial reporting / accounting access. Tim wanted OBB to replace his in-house accountants on month-day profitability reports. Luke declined — too much security exposure. "We won't take access to anything we can't afford to make a mistake on." This is a security-posture brand, not a sales weakness. Stand on it.

The security-posture frame — why the accounting decline IS the pitch

Most AI consultancies will say yes to financial-reporting access on a first meeting. Their incentive is to win the contract; the security blast radius is the client's problem when it goes wrong.

OBB's position: we will not take access to anything we can't afford to make a mistake on. That includes Tim's books. Not because we couldn't build the tool — because the consequences of an agent error on his finances are too high for the level of trust we've established with him on day one. Trust gets earned in increments; access scales with trust.

This is the frame Luke walks in with. Not "we can do anything" — but "we choose what we touch carefully, because every system we integrate is a surface we're responsible for if something goes wrong."

A multi-gen operator hears that and understands it. Tim runs a feed mill where one bad batch poisons cows; he runs a trucking company where one bad reefer-temp shipment poisons a Walmart load. He KNOWS what "we can't afford to make a mistake on" sounds like. Match his risk language.

If this poisons the deal, the deal was wrong. If it lands, it's the most credible thing Luke says in the meeting.

Cross-cutting signals — Tim's decision style

Acquisition pattern: buy-and-hold, sell when fit breaks. - 1935 founding → still family-owned - 2006 Farmers' Implement → held 20 years → sold Feb 2026 only because Johnson Tractor offered better customer service network - 2006 Farmers' Grain & Feed → still owned, expanded - March 2025 Gray Transportation → opportunistic acquisition

For a Relic engagement, this profiles to: - A scoped pilot inside ONE business (FGF office-side is highest-conviction). Define a 60-day window. Define what "working" looks like in advance. Run it. Decide together. - Outcomes framed in customer-continuity language + son-inherits language — not tech-feature language. - Don't pitch all his businesses at once. Pick one, win it, expand.

Industry examples — wins and failures

Worth referencing: - Standard Logistics × Optimal Dynamics — 70%+ of accepted loads auto-dispatched after AI evaluation. The kind of case study Tim would respect. - LoadAi (Optym) — driver-aware load matching. - LoadStop — markets driver-retention impact. - BinSentry — IoT bin-level inventory for feed mills. - Repete's own Generative AI Co-Pilot for feed mills, shipping in 2026. Don't lead with this — see Repete-interface red flag. But be ready if Tim mentions it.

Worth naming honestly: - Trucking + feed mill + hospitality are exactly the three verticals where 2025-2026 AI pilots have died loudest. Hallucinated load quotes. Farmer-facing chatbots that drove off long-tail patrons. Hotel-guest messaging that triggered chargebacks. Surface these failure stories yourself — or Tim will assume you haven't read the room.

Discovery questions — what to ask, what to listen for

Opener (low-stakes, gets him talking)

• "Dan mentioned you've been thinking about automation across your operations. Where's the conversation in your own head right now — is it a specific pain point, or more an open exploration?"
• "What's working well right now that you wouldn't want us to disrupt?"
• "You're thinking about handing this to your son in a few years — what's the version of these businesses you most want him to inherit?" (succession frame, opens the long-horizon conversation)

Trucking-specific

• "What's the single most expensive 'where's my load?' conversation your headset team has each week?"
• "How do you find new drivers today, and where does that pipeline break?" (bridges to the academy investment)
• "What does your TMS not do for you that you wish it would?"
• "When a reefer goes out of spec, walk me through the next 24 hours."
• "Who's your hardest shipper to get paid by, and what makes it hard?"

Feed mill-specific

• "Orders coming in by phone right now — what's the volume on a typical day, and how are your two front-office folks managing it?" (signals you know who runs it)
• "On the patron portal — how many of your customers actually use it, and what's it not doing for them?"
• "Your dairy nutrition consultants — how do their visit notes flow back into the mill's records?"
• "Are you happy with how Repete's automation has paid off? Where's it left you wanting more?"
• "Anyone trying to sell you BinSentry or similar IoT-bin tooling? What's stopping you from saying yes?"

Decision-style + relationship questions

• "When you made the call on Repete in 2021, what convinced you?"
• "Who else weighs in when you're making a 12-month commitment of this size?" (lets him bring up his son or operating staff naturally; do NOT preempt with John's name — John has passed)
• "What's a vendor relationship that's worked well for you over years? What made it work?"
• "What's a vendor experience that left a bad taste? What broke?"

Closing-shape questions

• "If we ran a 60-day pilot on one slice of one business, which slice would you want us to prove ourselves on?"
• "Who else on your team should be in the next conversation?" (you want introductions to the two office ladies + the headset-team lead before you build anything)
• "What would a 'this is working' signal look like to you 90 days in?"

Listen for

• Red flag: he names a previous AI vendor with frustration → ask what specifically broke, don't repeat
• Red flag: he can't articulate where AI would help → pilot scope needs to be even smaller
• Red flag: he wants OBB on his financial systems → restate the security-posture line; don't bend
• Buy signal: he name-drops Repete's GenAI co-pilot or BinSentry → he's been doing his own reading
• Buy signal: he asks about pilot structure or pricing → he's already evaluating fit
• Buy signal: he tells you a specific number ("my dispatch team takes 30 calls a day from shippers asking 'where's my load'") → he's letting you scope; capture it precisely
• Buy signal: he talks about his son or the next-5-years horizon → succession frame is landing

Service-shape frames — how OBB serves Tim

Frame 1: Pilot-first, scope-defined

60-day pilot inside one business line, fixed scope, fixed price, defined success metrics. Not a retainer. Not a hand-shake about "let's see how it goes." A specific deliverable with a number attached.

Pilot recommendation: Farmers' Grain & Feed office-side. Specifically: - AI-assisted phone-order capture for inbound orders (the two office ladies own this; they'll feel the upside immediately — less typing, fewer mistakes, faster patron response) - Patron portal upgrades that don't break the 65-year-old dairyman experience - Dairy-consulting note capture pipeline

Why FGF first (not trucking): - Smaller blast radius. A missed phone order isn't a $50K freight claim. - Two-office-lady team = small, identifiable, willing user base. Easier to win them over than a room of headsets. - Time-to-demonstrable-result: weeks 4-6 vs. 10-12 for trucking. - Lower exposure on customer-facing comm (a friendly farmer is more forgiving than a Fortune-500 shipper auditing carrier performance). - Repete interface still the red flag — but the office-side scope sidesteps Repete entirely. Pilot success doesn't depend on Repete.

Trucking comes next (NOT first): - After FGF wins, expand into customer-comms or AR for Kreilkamp Trucking - Touch the dispatch headset room ONLY after the FGF and customer-comms pilots have produced measurable outcomes - Driver-academy tooling is the third wave, not the first

Frame 2: Build vs. buy

• SaaS platforms (TMS, PMS, CRM, mill ERP) — OBB does NOT build from scratch. Tim's businesses already have these. We integrate.
• Custom AI agents — this is what OBB builds. Bespoke automation tuned to specific workflows.
• Websites / marketing sites — can build (Pages-deployed). Not the highest leverage; defer.
• API integrations — the glue between AI agents and existing systems (Samsara, Repete-if-interfaceable, AgriCharts, McLeod/TMS).

Frame 3: Anti-disruption posture for farmer- and driver-facing tools

Every patron- or driver-facing AI tool ships with: 1. A clear "you're talking to AI" identifier when AI is in the loop. 2. A human escape hatch on call one — a number that reaches a Kreilkamp/FGF staff person who knows them by name. 3. A "coffee-counter ready" briefing so the people who answer phones can explain it.

This is the OBB differentiator. Most AI shops don't think about the 30-year farmer relationship. OBB does because we operate in similar relationship-heavy contexts.

OBB credibility positioning — honest, not glaze

OBB Holdings runs AI agents across multiple businesses right now, for ourselves: - A talent/alumni-development practice with multi-audience report generation and annual-calendar tooling. - A Christian high school's operations — live with 175+ students, automated progress reports, attendance, AI-detection for teachers, ACT curriculum + practice materials. - An ERC appeals practice with a dedicated AI agent for client intake + qualification drafting. Live, paying clients.

This is not theoretical AI consulting. It's the same shape Tim runs — multi-business operator using AI to compound. We use what we sell.

The honest acknowledgment Tim deserves

• We are three partners, not a Fortune 500 consultancy. That's a feature for an operator like Tim — but Luke has to land it as a feature, not apologize for it.
• We have not yet built for trucking or feed mill specifically. What we have built is the underlying agent architecture — the same primitives that read documents, interface with APIs, draft tone-appropriate communications, escalate to humans when warranted. Those primitives apply across verticals; the domain knowledge gets layered on with operator partnership.
• We do not know Repete's interface posture yet. We're willing to find out as part of pilot scoping. We can't promise integration until we've done the research.
• We will not take access to your books or anything else we can't afford to make a mistake on. Trust gets earned in increments; access scales with trust.

What this lets Luke say in the room

"OBB Holdings is three partners. We started building AI agents to run our own work across a talent-development practice, a Christian school's operations, and an ERC-appeals firm. We discovered that nobody we hired to build this stuff understood our businesses as well as we did, so we built it ourselves. Now a small set of operators hire us to do the same for them. We're picky about who we work with because depth is the product — coverage isn't. Dan introduced us because he thought you'd find that interesting. I'm here to listen first and see if there's a piece of your operation where we'd be worth a 60-day pilot. If we are, we scope it tight, run it, and decide from results. If we're not, no harm done."

What NOT to say

• Don't list every tool stack item ("we use Cloudflare, OpenAI, Anthropic..."). That's IT-vendor talk.
• Don't promise enterprise references we don't have.
• Don't position against bigger AI consultancies.
• Don't name Dan as a commission partner. The arrangement stays silent.
• Don't pitch the retainer.
• Don't ad-lib on Repete's interface options.
• Don't surface John (deceased) unprompted.
• Don't say yes to financial-reporting access. Stand on the security-posture frame.

The "hit by a bus" question

Tim may ask: "What happens if one of you three gets hit by a bus?" The honest answer: - We're three partners, not three solo operators — the work runs against shared infrastructure and documented patterns, not in one person's head. - For the pilot scope we're discussing, the bus factor is manageable. The pilot has a defined end date; we're not asking Tim to depend on us for years before we've earned that. - If we earn a longer engagement and the bus-factor question becomes load-bearing, that's the conversation we have together — building a small bench, formalizing succession, or sizing the engagement to OBB's actual capacity. We don't pretend the question doesn't exist.

Dan at the meeting — updated position

Luke's preference: Dan does NOT attend. Reasons: - Tim's buy-and-hold operator profile rewards direct relationships. - The 15% commission is silent. Dan's presence makes that harder to maintain. - Tim may have context about Dan he won't share with Dan in the room.

Dan may insist on attending. If he does: - Brief him BEFORE the meeting on the silent-commission posture - Agree the line in advance: "If Tim asks point-blank about your role/relationship with OBB, you answer honestly. Otherwise the topic stays off the table." - Dan's commission doesn't change either way

This is integrity-first. If Tim asks and Dan has to disclose, OBB hasn't lied — we just haven't volunteered. The arrangement stands.

Open items to verify in the meeting

1. Which TMS does Kreilkamp Trucking run? McLeod is the industry default; not verified.
2. Customer-side shipment visibility — project44 / FourKites / portal / EDI only?
3. Farmers' Grain & Feed's office-side ERP — AGRIS / Cultura / Excel / custom?
4. Repete's third-party integration posture — the load-bearing red flag.
5. Brent Redmond Transportation's tech stack and integration depth with Allenton operation.
6. Tim's son's name + age + current role in the businesses — succession frame depends on this. Research before next meeting if not surfaced today.
7. The two office ladies' names + tenure at FGF — they're the FGF pilot stakeholders.
8. The "headset team" lead at Kreilkamp Trucking — they're the trucking-pilot stakeholder for the second wave.
9. Farmers' Implement sale proceeds — deployable capital; ask delicately, late in the conversation.

Compiled from FreightWaves, CCJ, gmtoday, Mid-West Farm Report, Discover Wisconsin, Repete Corporation, Feed & Grain, Moraine Park Technical College press, RocketReach, Dun & Bradstreet, WB Warehousing & Logistics, Brent Redmond Transportation, Kreilkamp.com, fgfmill.com + Dan's direct intel from Tim 2026-05-14.

Generated 2026-05-14 by OBB Holdings LLC / Relic313 dossier system. For internal use.