Jason Berwanger, CEO, HubiFi: My mic was off, so you didn't get to hear my great speech. Welcome! I think we're live. We'll give folks about two minutes to join, and then we'll get started. You can't come off mute or on camera until the networking afterwards, but we'd love for you to use the chat. Say where you're from and maybe your favorite whiskey.
Chris, thanks for joining. I know rosé and the wine event weren't your thing, but hopefully whiskey is. Lindsay from NYC is also the designer of this event. Thank you, Lindsay.
A few housekeeping items. You'll be on mute and off camera during the event. Afterwards we'll do networking in breakout rooms. Questions in the chat or Q&A, whether for the whiskey expert or the speakers, are completely welcome. We'll do some whiskey tasting, and we'll talk with Will and Max about their experience with accounting automation, their careers, and problem-solving at some pretty cool organizations: Miro and Cursor. Max and Will, would you give a quick introduction and anything you'd like the audience to know?
Max Winsberg, Miro: I'll start. Hi, I'm Max. I've been at Miro for about five years, and I head our revenue accounting and operations team. It's great to be here and talk with you all. I really love working with HubiFi, Jason and the team. I'm happy to answer any questions and share some of the experiences I've had in my career.
Will Smerdon, Cursor: Thanks, Max. I'm Will. I joined Cursor about four months ago. Before that I was at Fivetran, and before that, Stripe. I lead our revenue accounting and order-to-cash operations team. I'm looking forward to having some whiskeys and talking about AI and data. And to echo Max, I've really enjoyed working with Jason and Cody, so thanks for having me on.
Jason Berwanger, CEO, HubiFi: Wonderful. Without further ado, let's invite Steve, who'll walk us through the whiskey side. We'll do some tasting and some chatting, so Steve will come and go. Steve, a quick introduction?
Steve, Bourbon and Banter: Thanks, Jason. I'm Steve, a spirits educator. As someone pointed out, there are a lot of spirits over my shoulders. This is my office. I get to teach it and drink it, and it's a lot of fun. I'm glad we get to share some of the bourbon gospel with you tonight.
We call this "bourbon in the blind." Not because you drink yourself blind or drink blindfolded, but because you don't know the brands, the labels, or the characteristics of these spirits. You just nose and taste them and get to understand them a little better along the way. It's experiential.
If you haven't opened your kit, open it and pour your whiskeys into the cups. Let the spirit relax and release a little of the ethanol; it'll perfume your room while we talk. You also have a bourbon flavor wheel to help identify aromas and flavors. Trust your memory. You'll smell and taste things and think, "I've experienced that before." Glance at the flavor wheel, put two and two together, and educate yourself the fun way.
A couple of pro tasting tips before we start. With wine, we're used to sticking our noses deep into the glass. With spirits that can be uncomfortable, because of the high proof and the ethanol vaporizing up toward your nose. Try this while you listen to the HubiFi presentation: draw the aroma in through your mouth, a little retronasal inhalation. That's a more comfortable way to introduce it to your nose. I'm used to sticking my nose in there, and it still stings sometimes.
Do everything you'd do with wine. Hold it up to the light, swirl it around and have a look. You can gauge the body by what are called tears or legs. I was at a tequila presentation in Mexico once, and a young man said, "If you see legs, you're single. If you see tears, you're married." My wife of 30 years found that as hilarious as I did.
We want to introduce these to you neat. If you're not used to drinking whiskey neat, it's the fullest expression: you get all the flavor and aroma. If you add water, be aware it may actually make it a little hotter. The alcohol and water molecules don't get along, which creates a slight exothermic reaction that raises the temperature in the glass by a couple of degrees. Or add some ice if that makes you happier. No judging whatsoever. It's your whiskey, so drink it the way you like, but we hope you try it neat.
Let's pause there and hand it to Jason, because I know he has important stuff to talk about. We'll get back to the bourbon in a moment.
Jason Berwanger, CEO, HubiFi: I would not say what we have is more important than bourbon, so I'll correct the record on that one.
Jason Berwanger, CEO, HubiFi: Let's do a deep dive into the Cursor use case. To frame it up: Cursor is one of the fastest-growing companies in the world, definitely one of the fastest-growing AI companies. You have some of the greatest technology known to man at your fingertips, and you're doing it with a handful of people on the accounting and finance team. That's a lot of very efficient growth. Will, tell folks about the journey: what Cursor was doing when you joined, how you think about systems supporting order-to-cash, and some landscape context.
Will Smerdon, Cursor: Thanks for framing that up. What's interesting about Cursor's business is that it really took off in the developer and engineering space, so it's heavily product-led. It's pretty amazing that we reached the revenue we did almost entirely on Stripe. Our self-service business was the primary driver of revenue growth through early 2025, when we were at around $700 to $800 million in ARR. Our sales-led business really took off from around the start of last year.
Stripe is a fantastic product, and you can grow very quickly on it. It abstracts away the complexity of payments, invoicing, billing and so on. But with the volume we had, it starts to break how Stripe functions for reporting and data. Basic reports out of Stripe, we just can't run anymore. If you try, they fail. So adding a transformation layer between Stripe and an ERP is really important, and that's where HubiFi came in. Getting to the scale we're at now was much more straightforward than it would have been in a more complicated or heavily sales-led business.
Jason Berwanger, CEO, HubiFi: You nailed it. For self-serve order-to-cash scaling, there's nothing better than Stripe in terms of ROI for your engineering team to ship a product and monetize it. But you highlighted the key differentiator: volume creates a very different problem. We often contrast it with sales-led, where complexity is about breadth and depth: any number of contract types with little consistency between them. As the order-to-cash lead, part of your job there is driving consistency and saying, "We can't customize everything." On the PLG side, it's a volume game. There are about 30 to 35 transaction types in Stripe, so the breadth is capped, but you're processing billions of transactions that become tens of billions of journal entries. That's the not-so-novel problem every high-volume Stripe company runs into.
Will Smerdon, Cursor: And the people you need to run a fully PLG revenue function versus a more nuanced, customized sales-led function are totally different. You could theoretically run the self-service side with someone overseeing policy and then data reconciliation, because that's ultimately what it's become. The sales-led side brings in much more complexity, and it's more typical of what you'd see in a traditional revenue accounting function.
Jason Berwanger, CEO, HubiFi: Right, where a human has to make an intentional decision, often a judgment based on fairly bespoke contract terms. That makes sense for that problem.
Jason Berwanger, CEO, HubiFi: At HubiFi, we're primarily automation: tooling built specifically for high-volume Stripe companies. And Cursor is one of the best AI tech companies out there. How do you think about automation in solving rev rec, and how does that help or hinder you from an AI perspective? It's an interesting question for you, because you could build almost anything in a sprint. Why not build some of your own stuff?
Will Smerdon, Cursor: It's a really interesting topic right now. There's been a lot of discussion about AI, but less about automation and data. You need to get the deterministic layer right before you can leverage the true benefits of AI. I was at a conference last week where they talked about exactly this: the first step to using AI well is getting your data and automations in place and well understood before layering AI tooling on top.
At the same time, we've reached the point where we can build pretty much anything. So the question isn't "Do I have time to build something?" It's "Should I build something? What are the trade-offs?" Not building for the sake of it, but building what actually makes sense. I feel like we've almost become mini product managers.
Jason Berwanger, CEO, HubiFi: Totally. That's exactly what a product manager does: evaluate the problem and the value of solving it, then weigh the trade-offs of different approaches. And you said it well: deterministic automation first. That builds trust for the compliance and reporting layer. Then AI on top is the fun part everyone wants to get to. For finance and accounting, there's a hard prerequisite, though not for every use case. Prototyping will never be the same: you've proven that, putting things together overnight. I was impressed by the speed when we talked.
Ben Murray, whom a lot of us follow on LinkedIn as the SaaS finance guy, shared something similar: starting with AI is the mistake. You need to start further back, with automation and centralizing your data, building trust first. It's a call to action for CFOs, finance leaders and order-to-cash leaders not to jump straight to AI, even though it's really hard not to, because the technology is so exciting and addictive to work with.
Will Smerdon, Cursor: When I first got here and started playing with our product, there was a glitz and glamour to building things with Cursor. I was probably building more than I should have, or more than made sense. Then I took a step back and focused on where my time would have the highest ROI, and where I had the most detailed understanding of a process or area. That's where we started to see real value.
Jason Berwanger, CEO, HubiFi: That's a true product management decision. So automation is critical, and on its own it isn't the full solution, but it's the prerequisite for applying AI and getting a full end-to-end solution. Can you walk through some examples of how you and the team use automation and a reporting layer you can trust, and then get benefits from AI?
Will Smerdon, Cursor: I was going to talk about something else, but I worked on something last night that I shared with Cody this morning, and it's a better example of how this fits together.
You have all your Stripe data. HubiFi applies the logic and our GL mappings, and we use that to get to journal entries at the end of a period. But there's inherently a reconciliation between what's happening in Stripe, what's happening in HubiFi, and how it ultimately lands in your GL. We have a Databricks instance with all our Stripe data. Our HubiFi data is now flowing in on a regular basis, and our NetSuite data feeds Databricks too. So all the raw information is available. The question is how you reconcile everything to make sure that, at period end, everything you expect to be recorded has been recorded and looks correct.
Typically, you'd go to Stripe, pull a report, screenshot or download it, put it in a spreadsheet, then do the same with HubiFi data and reconcile manually. Or you'd work with a data engineer or analyst to write SQL to validate it and identify variances and reconciling items.
What I did last night was take the work we'd done onboarding HubiFi, including the example reconciliations we built, and tell Cursor: "Look at all our Stripe data and all our HubiFi data in Databricks, and tie it back to our journal entries in NetSuite. Here are examples of how we built this during onboarding. Build me a dashboard I can look at live whenever the data lands, that shows me the reconciliations and lets me dive in."
I spent maybe an hour on it and built an entire live reconciliation dashboard that updates every week when our data lands. I don't have to go to Stripe or pull any reporting out of HubiFi, and I still have all the automation. It just runs consistently. I can interact with it, it breaks down variances, buckets them, and helps me identify what I actually need to follow up on, rather than spending all the time building it.
Jason Berwanger, CEO, HubiFi: It's your trust-building exercise. It constantly proves you can trust the data, which makes you and the team much more likely to make decisions based on it and know you're compliant.
Will Smerdon, Cursor: Exactly. Now we might spend two minutes taking a quick look at the dashboard, and that's it. We're not spending time manually reconciling this activity. We did it using Cursor as a product: it went off and reconciled millions of transactions on its own with the parameters I gave it, and I back-tested it as we went until I understood it.
Jason Berwanger, CEO, HubiFi: It's incredible. We calculate billions of transactions, and you found a way to build composite reconciliations proving you can trust it across all the systems. That's pretty epic at that scale. Funnily enough, capturing the Stripe total and the ERP total and comparing them is on our roadmap for next quarter, and I'm super stoked about it. So I'm not surprised your mind went there. You were like, "I'm not reconciling any of this."
Will Smerdon, Cursor: That's the thing. A lot of accountants, especially revenue accountants, feel like they spend too much time on this type of work.
Jason Berwanger, CEO, HubiFi: In some sense the job is the reconciliation. You never get out of it.
Will Smerdon, Cursor: Exactly. And it's not necessarily value-add, and it's not what people want to be doing either.
Jason Berwanger, CEO, HubiFi: Well said. Let's take a quick question before we hand it back to Steve for the second whiskey.
Question (Anthony): What do you consider high volume?
Jason Berwanger, CEO, HubiFi: It's open to interpretation. To me, high volume means a manual process will be particularly painful compared with lower volume. Accountants with Excel, and now AI and other tooling, can do quite a lot on their own. But it becomes high volume when the volume creates an additional problem beyond calculating the answer: managing inception-to-date reporting, what you reported last month versus this month, with enough accumulated volume that it inhibits you. Then you become, as Will said, almost a slave to the reconciliation process.
I've talked to customers with 900 customers in Stripe who consider that high volume and painful enough to invest. I've also talked to companies in the millions who are still weighing whether it's high enough volume to care, and whether it's really breaking Excel yet. So, Anthony, it's up to you, though I'd say tens of thousands is probably the most common answer.
Will Smerdon, Cursor: I'd agree. We have over a million customers on our self-serve model, and that gets to the point Jason described, where it's too time-intensive to reconcile manually. It's just not worth the time anymore.
Jason Berwanger, CEO, HubiFi: Exactly. Awesome. Steve?
Steve, Bourbon and Banter: Everyone's thirsty. Let's get into it, starting with a really quick sixty-second education: the rules of bourbon, or what makes it bourbon.
Bourbon has to be a product of the United States. In 1964, bourbon sales were low and didn't look like they'd come back. We're in a market correction now, but back then it was bad news. The industry went to American legislators and said, "We need protection for our native spirit. We need to tell the rest of the world: you can make whiskey, but you can't call it bourbon." These are the rules they laid down:
Legally, there's no age requirement for bourbon. You could take it off the still, proof it down to 125, slosh it around in a new charred oak container, and legally call it bourbon. It wouldn't be good bourbon, but it would be bourbon. Age only has to be disclosed when it's under four years old, say two or three years. That's decent whiskey, but not great, and the label works almost as a warning that it won't be the best experience. Past four years, nobody has to disclose age, but it becomes a marketing tool: "This is ten years old" says we've had it a long time and taken good care of it.
Let's get to the booze. Pick up sample one, swirl it around, and do that retronasal inhale to draw the aroma in. I'll tell you what I'm smelling, and you can roll your eyes. I have only one palate, and everybody's different. That's what's so cool about a group of drinkers tasting the same thing and picking up completely different notes.
There's a big dried cherry note, and a high grain note; we'll talk about which grain that is. There's also a little of what I'd describe as slightly aged chocolate: a combination of chocolate and oak aromas. It's pretty light-bodied, without much clinging to the glass. My guess is it's lower proof. Well, it's not a guess, I know what they are. But it doesn't have a ton of body because it's lower proof. It's still really fruity, which I like. That's the distiller's choice of yeast, which gives it fruit character, and there's some citrus in there too, maybe orange.
Here's how I like to taste. Take a small sip first to condition your mouth. Work it around, but don't do the mouthwash; that'll burn. Then take a second sip and gradually move it around your mouth. There's a lot going on. This is a well-made whiskey. I get toasted oak and toasted bread. A little of that lemon carries over. There's white pepper and maybe a bit of baking spice: clove, nutmeg, cinnamon, the things you find in desserts.
Anybody want to guess before the reveal? There are only about 1,100 bourbons on the market, so your odds are good. It's Wyoming Whiskey, made in Wyoming, at 88 proof as a little marketing nod to statehood. I think it tastes good at that proof. The distiller's notes say floral, vanilla bean and caramel pudding; I'd agree. Floral with baking spice and brown butter, which is a pretty cool note, plus vanilla crème, caramel and a hint of cinnamon. We're tracking pretty well.
The finish describes the flavors that remain after you swallow and what you feel as it goes down. This one is lightly warm, not scorching. It's not what we call the Kentucky hug here, where it can burn. The vanilla and spice fade as it goes.
What's interesting is that it's a wheated bourbon, meaning wheat is the flavor grain. Most of the grain in bourbon has to be corn, and bourbon typically uses malted barley, which helps with the enzymatic reactions during cooking, mashing and fermentation. In between are the flavor grains. Traditionally that's rye, but these folks chose wheat, which presents softer and leans toward baking spice. Once you get past 100 proof, wheat really finds its mojo: more fruit, more cinnamon, all kinds of goodness. But this still presents well at a lower proof. It's five years old, so not an old whiskey; it has a long way to go in maturity if they want to age it further.
Let's compare sample two. The nose is very different. It's still bourbon, but there's a lot more oak influence. A little campfire, maybe an older home, grandma's attic: older, drier wood. I want to say deeper, darker chocolate, but that's not quite it. Sometimes I get a bit of black licorice in the background. It's a darker note overall. Leather, that's what it is. If you ride horses, you might call it horse tack. Can you believe all that comes from grain and distillation? There's also a mild fruit note, a little cherry cough syrup. Whatever you pick up, say it. Always personalize it, and don't just listen to what the other person says.
Let's sip again, a short one. It's much sweeter, but still darker and deeper than the first, with some spice character that wasn't in the Wyoming. Take another sip. I'm not a smoker, but growing up in Kentucky around tobacco barns, you know what drying tobacco smells like, like a cigar leaf. I really get that on the nose and the palate. There's also some chocolate cake: not birthday cake, but deeper, darker, maybe espresso cake.
Here's the reveal: Russell's Reserve, made by Wild Turkey Distillery. It's 90 proof, a touch higher than the first, and ten years in the barrel. That's quite a thing. Too long, and if it gets too hot in the barrel over time, it can go too far; too little heat, and it won't develop. Taking a whiskey that long and making sure it's treated well is much more than chance. There's real strategy behind it. It also enriches the whiskey. The distiller says citrus notes with butterscotch, maple and oak, and I'd agree. They also say vanilla, which I'm not picking up today. You don't taste the same thing every day: the air you breathe, the food you've eaten and what you've been drinking all influence what you do or don't taste. I've only had water today, but it still happens.
The taste is rich and spicy, with caramel for sure. Smooth and sweet, with toffee and spice lingering, and a mild, pleasant warming finish. I love it. In Kentucky this bottle is about $35, which is fantastic for a ten-year-old bourbon. The Wyoming is probably closer to $45, at half the age. Age sometimes means a lot and sometimes doesn't. I love this whiskey and hope you do too. Back to Jason for the serious stuff.
Jason Berwanger, CEO, HubiFi: Max, you have a lot of transactions on Stripe, plus NetSuite, and from what you've shared, you've been through the wringer. You tried a lot of approaches, mainly pushing transactions into your ERP and trying to keep Stripe and NetSuite in sync. What went right, and what went wrong?
Max Winsberg, Miro: We have several years of experience with this. For background: we translate every single Stripe transaction, including invoices, payments and credit memos, into NetSuite. That's hundreds of thousands of transactions a month, millions a year. As you can imagine, keeping that data in sync and reconciled is a full-time job, maybe two.
We use NetSuite's SuiteSync, which I believe is the standard out-of-the-box connector. You find problems: scenarios where it isn't behaving the way you want or producing the correct accounting. So you dig in and ask how to fix it. Most of our fixes were NetSuite scripts. Transactions sync from Stripe to NetSuite, and we work with our technology team to write script logic to fix one specific issue. The problem is, you fix one issue and another pops up. You solve that one, and another appears.
It felt like a full-time job just managing the translation between Stripe and NetSuite, a dumb translation that wasn't helping in any way. We spent a huge amount of time maintaining the status quo, just making sure we could close with accurate numbers, without providing real value to the business.
Jason Berwanger, CEO, HubiFi: It feels like a pattern. We talk about this as a team, and you and I have discussed it: the unbundling concept. You have a general ledger and finance hub, and then you have where your customers transact. Once those are unbundled, I don't care how good you are, the cost of getting it all back into the ERP has diminishing returns. As you said, it becomes reconciliation for the sake of getting data into NetSuite, without much benefit, and arguably more cost than benefit once you count payroll hours and NetSuite's direct cost for managing the data.
You also hit another key point: there are a lot of edge cases that don't go in there. You, Cody and I spent a lot of time on customer balance transactions and other things SuiteSync and NetSuite simply had no home for, which we worked with you to codify.
Max Winsberg, Miro: Absolutely. I'm not sure how everyone's SuiteSync is set up, or if everyone's familiar with customer balance transactions. It's basically a black hole, a bucket where Stripe puts everything into a customer balance: for example, unused time credits when a customer downgrades. That doesn't work well with the SuiteSync connection to NetSuite.
Our specific problem: we allowed customers to downgrade. You could buy ten seats, then partway through the contract downgrade to five. When the customer downgraded, that information didn't come over from Stripe to NetSuite. So we were overstating revenue unless someone intervened manually. That wasn't a small issue. It took my team weeks and weeks to reconcile. I don't want my team spending their entire jobs on this just to get the numbers right.
That was the main issue. And like the earlier discussion, you try to understand why you have the issue and whether it's the best way to operate as a business. You unpack the impact on revenue and hours spent, and take it to your CFO and leadership: "Maybe it's not worth letting customers downgrade in this instance." That's what we did. We could have solved that specific issue through HubiFi, but we also realized it didn't make sense for the business, and we were able to drive change through that.
Jason Berwanger, CEO, HubiFi: That's my favorite part of your project. There was clearly a big benefit for your team from the investment you made, both the effort and the HubiFi partnership. But the level of connectivity to how your operation works, being able to make recommendations and show your operational team how customers actually transact, with data that ties back to your P&L and balance sheet, is really cool. That's the strategic accountant's dream. We were stoked for the outcomes you and your team got: not just the automation, but the seat at the strategic table, because you had the data to see the patterns. And to Will's point, you're not spending time on reconciliations, so you can figure out how you really want to run the business, because it was costing you. The answer was no. That question would never have been raised if you and the team had stayed stuck managing SuiteSync.
Max Winsberg, Miro: That's one example we went through. The cool thing about implementing a new system is that you take inventory of all your existing processes. In the implementation, Jason and Cody really ask, "Why are you doing it this way?" And you say, "I don't know," or "This is how it's always been done." That's when you start investigating why you do certain things, and whether you could change them for the better, not just for your team, but for the business.
That wasn't the only item. We had an outdated way of giving credits to startup companies: we'd put a credit on the customer balance. The problem is that it's really hard to track how those credits get applied. So we went back to the business and said, "Why are we doing it this way? Let's offer a coupon instead." HubiFi can track that for us, and we can put time limits on the coupons. So it's not just automating things; it's making the business run better.
Jason Berwanger, CEO, HubiFi: Spot on. You have to do both. First figure out compliance and reconciliation, then move on to the fun stuff. It's a hard prerequisite, because you can't ignore your accounting responsibilities. But once it's automated, you can use it as a superpower.
Max Winsberg, Miro: I'd point out that when you're not reconciling, you have time to put together a presentation explaining why a change is needed, and to try to change how the business operates. When you're heads-down making sure the numbers close accurately, you don't have time for anything else.
Jason Berwanger, CEO, HubiFi: Huge. One more data point: we added it up, and there are 34 different Stripe endpoints and transaction types, not just balance transactions but other records too. SuiteSync, NetSuite and Stripe's own tools haven't kept up with every operational effect a payment, billing or subscription event can have. That's what catches a lot of folks: it doesn't map cleanly to the ERP. You have to think through the accounting use cases as the product evolves, and that's the role we play with Stripe: keeping up on the accounting side with all the operational changes. Because we track everything in and out of Stripe, we can surface things like, "You're doing a lot of these downgrades. Why?" and let you operate the way you want.
Max Winsberg, Miro: With a team of, I think, two other people besides me who are really in the weeds on Stripe, it's great to have partners like you and Cody. We can ask why Stripe works a certain way, and you seemingly have all the answers. It's good to have someone to bounce ideas off: are we doing this the right way, and how are other companies doing it well? HubiFi is a real thought partner.
Jason Berwanger, CEO, HubiFi: It's impressive that you handle that volume, figured out how to automate all of it, and still have time to make strategic recommendations, with a tiny team and hundreds of thousands of transactions. That's something you should be proud of.
Max Winsberg, Miro: Thanks to you all. I think the overall theme, from hearing Will and going over our use cases, is that you can't build on bad processes and bad data. You want to get that groundwork and foundation strong first.
Steve, Bourbon and Banter: That's right.
Jason Berwanger, CEO, HubiFi: Steve, more thirst.
Steve, Bourbon and Banter: All right, Jason, let's go. Everybody thirsty again after a little break? Pick up whiskey number three and treat it like the others. Hold it up and look at the body: a little more, medium-bodied. The aroma is definitely different. Very herbal: a little dill, a little mint, maybe wintergreen candy. Here's a hint, and if you're an experienced whiskey drinker you may already know where we're going: it's very candied, with some peppermint as well.
Go ahead and do the two-sip. It's like a dance: the two-step with the two-sip. This is my jam. I like spicy, herbal whiskeys. There's not a lot of sweetness, but there's some. This is a Kentucky-style rye. Rye works like bourbon: bourbon needs at least 51% corn, and rye needs at least 51% rye grain in the mash bill. The dominant grain gives the whiskey its name. This one has quite a bit of corn after that, so it has a big mouthfeel. It's kind of honeyed; that comes from the corn, not the rye, and a bit from the malted barley in the mash bill. I like this a lot. It coats the mouth really well, and it would pair so well with steak, because it cuts the fat and cleanses the palate. Some people say they don't like rye. Hopefully you like this one.
It's Michter's US*1 Rye. It's lower proof, 84.8, but I think it presents much higher and richer. They don't disclose their mash bills, but it's at least 51% rye, which makes it a rye. It's aged only five to seven years, but some of Michter's aging techniques and barrel entry proofs, technical talk we don't have time for, affect the whiskey in a very positive way and make it rich and luxurious. The notes say oak, vanilla, spice and a bit of dark fruit on the nose; rye spice, citrus, vanilla, oak and butterscotch on the palate. Absolutely. The corn delivers that butterscotch. And peppery spice on the finish, which comes from the rye grain, the aging and the fermentation.
Here's my thirty-second tutorial on fermentation. Once the grain is cooked and the complex carbohydrates break down into sugars that can be easily fermented, fermentation turns that sugar into alcohol and CO2. That process contributes as much to the spice character in this rye as the rye itself. Pretty cool. Keep this rye in mind, because the next bourbon is going to be very different.
Sample four has a very different nose. There's a lot of wood: dark oak, meaning a heavily charred barrel. It's kind of ashy, with a campfire note I find really pleasant. Some people nose this and, maybe conflating memories, say s'mores and marshmallow. Confectioner's sugar shows up a lot in good whiskey as a barrel characteristic, but I'm not getting it. I get the burned wood and charred oak, plus some of the butterscotch we found in the rye.
It's a very full-bodied whiskey. Hold it up to the light and you'll definitely see the legs, and I promise you I'm not single. I enjoy being married; we're in it for the long haul. If you noticed, it doesn't even make noise in the glass when you swirl it. That's how heavy-bodied it is. I'm getting toasted bread again, like in the first sample. And if you've never been in a rickhouse, the giant wooden warehouses where whiskey ages, this is exactly what one smells like.
Let's do the two-sip. Big fruit character, especially banana, like dried banana. Can you tell I've been playing with banana chips? I do a lot of food and whiskey pairings. There's fruitcake, a good one, not a bad one, and a moist chocolate, not pudding, maybe a half-melted candy bar. It all sounds crazy, but that's what I taste and smell. A little leather, though not a lot; the Russell's Reserve definitely had more.
Before the reveal: this one is double oaked. It aged five to seven years in a charred oak barrel, then went into a second charred oak barrel for about another five months to amplify the oak. If that gives you a hint, here it is: Woodford Reserve Double Oaked. A lot of people like Woodford Reserve. I remember when it was created in 1996, and it's now a two-million-case brand, which is big. Jack Daniel's, by comparison, is about sixteen and a half million cases. It's a little low proof for me at 90.4, but it has a lot of flavor, so proof doesn't matter much here.
The mash bill is 72% corn, 18% rye and 10% malted barley. That's a lot of corn, and it comes through nicely. The notes say honey, chocolate and marzipan (almond paste) with toasted oak. On the palate: full-bodied, with vanilla, dark caramel, hazelnut, apple and spices. Is it a dessert whiskey? Kind of. It's not sweet like some dessert whiskeys, but it would complement a heavy cheesecake or apple pie. The finish is long and creamy, with lingering honeyed apple. I'll buy that, especially the honeyed part.
That concludes my part of the presentation. I hope you enjoyed it and found it informative, and that you have a little whiskey left to get you through the rest. Back to you, Jason.
Jason Berwanger, CEO, HubiFi: Steve, wonderful job. I learned a lot. Thank you so much for joining and hosting with us tonight.
Steve, Bourbon and Banter: It's my pleasure. I get to do this for a living, remember? This is fun.
Jason Berwanger, CEO, HubiFi: The Kentucky hug. I'll never forget it.
Steve, Bourbon and Banter: All right, everybody. Thank you so much.
Jason Berwanger, CEO, HubiFi: Thank you, Steve.
Jason Berwanger, CEO, HubiFi: All right, gents, final round. You've both helped scale some not-so-small organizations hyper-efficiently. What advice do you have for building an efficient accounting org and solving rev rec?
Max Winsberg, Miro: I'll go first. Don't be afraid to dive in. We all know where things could go wrong: that one thing in the back of your head that keeps you up at night. Don't run from it forever, because it will eventually catch up with you. Every business should try to scale; you want more revenue and more transactions. So what are the faulty foundations that won't scale if you just keep building on them? People will always want you to close faster and get information quicker. Look at your entire process as a whole. Ask yourself: if volume doubled tomorrow, which processes would break down or fail? Then attack those, with a mindset a little further out than your day-to-day.
Jason Berwanger, CEO, HubiFi: So automation matters for two reasons. One is risk mitigation, the sleep-at-night protection of knowing something will be done consistently without a manual process. The other is getting information more often, daily or more frequent trustworthy revenue data, so you can be real business partners. Those are the two themes I'm hearing. Did I miss anything?
Max Winsberg, Miro: No, you're absolutely right. We want to be more than the typical accountant. I want to work on better problems than closing the books. And as a leader, I see my team get frustrated doing the same thing over and over. I want to give my team growth, and they won't grow by repeating the same manual process. Beyond helping the business with better information faster, it gives the team personal growth: time to focus on strategic initiatives and real growth opportunities. That's another big reason we haven't talked about yet today.
Jason Berwanger, CEO, HubiFi: Great for your people and retaining talent, great for the overall finance team, and sleep-at-night accounting. That's reason enough for me.
Will Smerdon, Cursor: I wrote down a few points while thinking about this.
What you build today won't necessarily be an enterprise product; the things we're building aren't, and that's not the point. The point is progress over perfection. Let's relieve some pain today through automation and AI, and let that guide where we go tomorrow.
Jason Berwanger, CEO, HubiFi: I like it. Both of you made the same point from different angles. Max: the foundational investment in automation gets people out of manual processes. Will: that same foundational automation is what enables AI. It's the universal first step if you want to take your team and your technology to the next level. You have to make that foundational investment. It's not sexy, but you both said it.
Will Smerdon, Cursor: Definitely.
Jason Berwanger, CEO, HubiFi: Awesome. Max, Will, you're both awesome. Thank you for taking time out of your day, Will, and your night, Max, and for sharing your insights and stories with the audience. I greatly appreciate it, and I know a lot of folks did. We had some good questions, and if you have any others, drop them in the chat or Q&A.
We're going to wrap up the event. There's breakout networking on the event platform that Christine will kick off behind the scenes. As we close in the next minute or two, after any final Q&A, hit Join and you'll be placed into breakout rooms where you can come on camera and chat. The three of us will be there, plus others from the audience. We usually have some good conversation afterwards, so feel free to stick around. Just hit Join so you're not left out.
Let's check for any other questions. Chris, thanks, I appreciate the support. It looks like there's nothing else in the Q&A. Christine, cue the awkward countdown.