Interview: How finance is shaping Wisk’s next aircraft with acting CFO Drake Berglund
In the first of two articles, Wisk’s acting CFO Drake Berglund speaks to eVTOL Insights and explains how commercial requirements, battery decisions and early testing are influencing the development of Gen 6.
For Berglund, helping develop Wisk’s Gen 6 aircraft means working closely with engineers on choices that will shape both its performance and its commercial prospects.
“There are major decisions early in an airplane program like Wisk’s Gen 6 that have an enduring impact on company financials,” He tells eVTOL Insights. “Getting to help shape them has been deeply rewarding.”
One of those decisions concerned the aircraft configuration. Wisk considered adapting an existing design for commercial certification before choosing changes to better meet market requirements.
“We adjusted it to support market requirements, including potential future derivatives, which meant a larger fuselage, additional passenger capacity, and an updated propulsion configuration that supported greater speed and range.”
The changes brought additional development costs and time, but Berglund says they were the right choice for the market Wisk intended to serve.
Bringing finance into design decisions
Starting with a clean-sheet aircraft gave Wisk an opportunity to bring commercial and technical thinking together early.
“That’s the beauty of a clean-sheet airplane design. We did not inherit an earlier design or have to tweak decisions made years or decades ago,” Berglund says.
“It’s a challenge, but it’s important that everyone has a seat at the table early. Early stage product development is a very collaborative effort, and in a technologically ambitious airplane, with significant technical, market, and programmatic risk, there’s a healthy tension.”
That collaboration includes finance and strategy, production systems, certification specialists and Integrated Product Teams. Aircraft-level commercial requirements are translated into engineering targets and decisions about what Wisk develops internally or buys from suppliers.
The company assesses major engineering and programme decisions against an estimated cost target of $4 per passenger mile.
“Oftentimes, the changes are in the cents, but at scale, that matters very much. This ensures we’re building a viable product and clearly ties everything we do to something that matters to a customer. Not only an airline or operator, but the end customer, who everyone across the value chain needs in order to succeed.”
Reconsidering the battery strategy
Battery development illustrates how those discussions can change the direction of investment. Wisk assessed cell formats and its approach to developing the modules used in its battery packs.
“Ultimately, we chose to partner with a supplier at the module level to accelerate technical maturity, because we felt we could leverage their insights from supporting the broader ecosystem,” Berglund says.
“That was a hard decision. There was a lot of benefit to staying vertical in that domain, with the development in-house and close by. But after talking to multiple potential suppliers and conducting a detailed make-buy analysis, we decided to change our strategy.”
Testing helped inform the decision, alongside the increasing maturity of potential suppliers.
“We struggled with battery thermal runaway tests. You’re running small-scale tests repeatedly on different design iterations, and we weren’t reaching a level of maturity we felt would scale into the product. That test result drove a different funding decision and a different approach to supplier selection, which changed where we spent that money.”
Investing in learning before production
Wisk’s Block Zero non-conforming prototype reflects another deliberate investment choice: spending more upfront to learn how the aircraft’s systems work together before progressing to a conforming design.
“It was a higher-cost upfront strategy to do more integrated testing. We did it at the airplane level and explicitly said these airplanes are not for conformity. They are for technical learning and integration,” Berglund explains.
“That costs more in bill of materials, early labor, and tooling on the production side, and a lot of that tooling will ultimately have to be repurchased for the conforming design.”
Dedicated design-build teams also contribute to that early investment, bringing manufacturing, production, systems engineering and programme management expertise into the work.
“What you get in exchange is a far higher level of learning, technical rigor, and integrity in the system design, and much earlier identification of the real problem spots you could potentially gloss over in a paper design. You also get technical maturity that’s evidenced by a flying airplane, which of course you cannot fake.”
Learning alongside the engineers
Berglund’s enthusiasm is particularly clear when he reflects on the people behind the programme.
“I’ve learned a tremendous amount from working so closely with our Wisk engineers, and it’s been a real pleasure to be part of such a tight-knit program, largely based at one site here in Mountain View, California, where you can see the progress firsthand.”
He cites chief engineer Geoff Long’s rule of five: the view that novel systems need repeated attempts to reach maturity. Berglund sees lessons in that approach for finance and programme planning too.
“For anything that hasn’t been fully developed before, whether it’s a business case or a program schedule, the more iterations you can have, the better. Perhaps five really is the magic number.”
Finance, in turn, encourages engineers to take ownership of budgets and understand the business case behind their work.
“What I hope we’ve also imparted to the engineering team is the importance of delivering a product, keeping promises, and investment discipline. Those can feel like they slow engineering progress, but they’re ultimately what creates value: harnessing engineering ingenuity in a way that meets customer needs within a disciplined investment approach.”
For Berglund, giving engineers that visibility also creates a shared sense of purpose.
“Bringing them into the fold, satisfying that curiosity, getting their feedback, and then having them take ownership of their piece of the puzzle is very satisfying. It fits into the broader idea of actively managing the airplane program, with everyone pulling in the same direction to accomplish something larger than themselves.”

