1,250-HP Chevrolet Corvette ZR1X Hybrid Runs The Quarter-Mile In Under 9 Seconds

The new Chevrolet Corvette ZR1 is only just now reaching dealerships in the U.S., but that twin-turbo monster is already being usurped by a new even-higher-performance version of the C8 Corvette. Long rumored to be called Zora, this new variant is actually dubbed ZR1X, and it takes the ZR1's powertrain and adds on a similar hybrid system to the one in the E-Ray for a truly ridiculous amount of power and speed.
General Motors senior vice president Ken Morris says the C8's platform was designed from the start with the ZR1X's powertrain in mind — that's probably why we started hearing rumors about it before the C8 even debuted. With 1,250 horsepower and all-wheel drive, the hybrid ZR1X is quicker to 60 mph and in the quarter-mile than any roadgoing Corvette before it, and its on-track performance is sure to be just as impressive. The standard ZR1 will soon be setting an official Nürburgring lap time, and ZR1X prototypes have already been spotted at the 'Ring as well, with the Ford Mustang GTD directly in its sights.
Read more: These Cars Are Police Magnets
At the heart of the ZR1X is the same 5.5-liter LT7 V8 that's in the standard ZR1, which is essentially the Z06's flat-plane-crank motor with a pair of turbochargers attached. All of the LT7's 1,064 horsepower and 828 pound-feet of torque are sent to the ZR1X's rear wheels through an 8-speed dual-clutch automatic transmission. Mounted at the front axle is an electric motor with 186 hp and 145 lb-ft of torque, an increase of 26 hp and 20 lb-ft over the E-Ray, with Chevy saying the ZR1X's motor has strengthened components but the same size and shape as the E-Ray's unit. The 1.9-kWh battery pack located in a central spine in the floor of the chassis has more usable energy and a higher peak operative voltage than the E-Ray's for better on-track capability.
There's no physical connection between the V8 and the electric motor — the former only powers the rear wheels, while the latter only powers the fronts. The electric motor also automatically disconnects once you reach 160 mph, having done its main job of nearly knocking you out with acceleration force. Chevy says the ZR1X will hit 60 mph from launch in under 2 seconds where the ZR1 and E-Ray need 2.3 and 2.5 seconds, respectively, and it'll run the quarter-mile in under 9 seconds at over 150 mph, versus 9.6 seconds in the ZR1 and 10.5 seconds in the E-Ray. That will make the ZR1X easily one of the quickest-accelerating cars you can buy, even among the most powerful EVs. A Lucid Air Sapphire will cover a quarter of a mile in just over 9 seconds, while a Dodge Demon will do it in just under 9 seconds. The standard ZR1 will hit 233 mph, and the ZR1X matches that.
Chevy says the ZR1X's eAWD system has "undergone a significant upgrade" compared to the E-Ray, both when it comes to on-road and on-track driving, and that it's constantly monitoring driver inputs to perfectly manage power delivery and traction. There are three different energy "strategies" for when on track, activated by a button on the steering wheel: Push-to-Pass for maximum power on demand, Qualifying for optimal lap times, and Endurance for longer lap sessions and consistent eAWD output. All 2026 Corvettes have a new PTM Pro setting for the traction management, which disables the traction and stability control systems, but in the ZR1X the regenerative braking torque vectoring remains on, as does the front axle pre-control that "actively manages inside front brake pressure to enable maximum corner-exit traction."
Optional on the normal ZR1 but standard on the ZR1X is the J59 carbon-ceramic brake package, which has Chevy's largest rotors ever at 16.5 inches front and rear paired with 10-piston front calipers and 6-piston rear calipers. Chevy says it's the most resilient braking system ever tested by GM, and engineers saw 1.9G of deceleration from 180 to 120 mph. The standard touring-focused chassis setup uses magnetic ride control and Michelin Pilot Sport 4S tires, but you can option a ZTK Performance package that has firmer springs and grippier Pilot Cup 2R tires.
You'll be able to get the ZR1X in both coupe and convertible body styles, and it'll have the same updated interior design as other 2026 Corvettes, but sadly its exterior doesn't look any different from a normal ZR1, badges aside. Real nerds will be able to spot an extra intercooler in the front bumper. The ZR1X will be available with the same Carbon Aero package as other ZR1s, which adds a gigantic rear wing, dive planes on the front bumper, a gurney lip in front of the hood vent and underbody strakes that all combine to give you 1,200 pounds of downforce at top speed.
Chevy isn't ready to talk money yet, but the ZR1X will surely command a hefty premium over the standard 2026 ZR1's $189,195 starting price. We don't know when it will go into production yet either, but it'll be built at the same Bowling Green, Kentucky, assembly plant as all other Corvettes, with the LT7 being hand-assembled there.
Want more like this? Join the Jalopnik newsletter to get the latest auto news sent straight to your inbox...
Read the original article on Jalopnik.

Try Our AI Features

Explore what Daily8 AI can do for you:

Learn with AIFact CheckingText to SpeechAI Summary

Related Articles

Forbes

14 minutes ago

• Forbes

20 Tech Leaders Share Lessons Learned From Failed Initiatives

Every technology leader has a project (or three) that didn't go exactly as planned. But wise leaders don't treat these moments as wholly wasted efforts, since they often teach more than the wins by exposing blind spots, shaky assumptions and opportunities to improve. The way a tech leader responds to a failed initiative often reveals their and their team's strengths more than the original plan ever could. Below, members of Forbes Technology Council discuss takeaways from their own project missteps that can help their fellow leaders navigate setbacks with greater clarity and confidence. 1. Maintain A Startup Mindset Setting up a team and structure too rigidly at the start can become a burden, not a foundation of success. We assumed early alignment would carry us forward, but it turned into an obligation, which was slowing decisions and working against change. Adopting a startup mindset—asset-light, adaptable and day-by-day focused—taught me that success comes from clarity, not fixed roles or plans. - Yogesh Malik, Way2Direct 2. Prioritize User Workflows Over Cool Tools A failed tech project showed me to focus on how users work, not just build cool tools. We made a great system, but users didn't use it because it didn't fit their needs. Now, I always ask users early to get it right. That means a user-centric and prioritized backlog for implementation. This has made me a better leader by keeping me practical and focused on what really helps people. - Rishi Kumar, MatchingFit Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify? 3. Don't Rely On Benchmarks Achieved In Isolation I shipped an early NLP voice agent before wiring in real-time, context-based hand-off to human CSRs. Accuracy benchmarks looked perfect in isolation, but customers got stuck and churned. That failure taught me to pair every model metric with a 'Can users finish the task?' metric. Now, new launches mandate shadow-mode pilots, field-tech feedback loops, and an instant human escape hatch. - Somil Gupta, Broccoli AI 4. Validate Assumptions Early in my career, I learned a key lesson: 'Don't assume; ask questions.' We launched a feature-rich solution that missed the mark because we didn't validate user needs. It led to poor adoption and wasted effort. Since then, I have focused on early stakeholder inputs, user impact and clear outcomes, shaping a more empathetic, communicative and outcome-driven leadership style. - Uttam Kumar, American Eagle Outfitters 5. Look Beyond Technology Technology alone isn't the answer. You need the business strategy, processes, data and skills to have a successful tech initiative. In fact, I would say that the tech is often the least important factor of that set of requirements. - Jason Kurtz, Basware 6. Anchor Decisions To Clear, Near-Term Priorities One key lesson I took from a failed initiative was to anchor every decision to the single highest-value problem I'm committed to solving within a one-year horizon. Since the world beyond 12 months is inherently unpredictable, I now use a simple rubric: Will this choice move us closer to that goal, or will it pull us off course? If it's the latter, I say 'no,' unless exceptions demand it. - Bharath Balasubramanian, Salesforce 7. Treat Interoperability As Nonnegotiable Early in my career, I saw clients invest millions in advanced enterprise systems only to abandon them because poor interoperability made real-world use impossible. It taught me early on that interoperability isn't optional. It is foundational to usability, adoption, long-term product success and future growth. - Ashish Singh, SeemaS, Inc. 8. Protect Your Integrity—Even If It Means Walking Away I learned that alignment matters more than revenue. In a co-managed IT setup, our security recommendations were ignored, putting both the client and us at risk. Walking away wasn't easy, but it reinforced the principle that protecting our integrity and setting clear boundaries is essential to long-term success and leadership growth. Parting ways professionally was a far better decision than trying to 'fix' it. - Ann Westerheim, Ekaru 9. Respect Cultural Context The definitions of right and wrong can vary dramatically from one country to another. This ends up being painfully evident on global projects that lack highly qualified PM oversight. Even the best software solution, if arrogantly configured from a myopic point of view (perhaps one that is right only in one location), can be viewed as a failure of the entire department, impacting IT's reputation. - Ken Feyder, Hermès of Paris 10. Find The Right Audience And Adapt To Their Needs I scaled a startup devoted to developing OCR technology to transcribe doctors' handwriting, but the market wasn't ready for it. So we pivoted to education: Teachers needed our solution to interpret messy student handwriting. The lesson I learned is that success is in finding the right audience and adapting to their needs. It shaped my leadership approach toward solving real problems for the right people. - Craig Crisler, SupportNinja 11. Set Clear Expectations With Customers Early On From a professional services perspective, every red account started its decline in the sales cycle. Mismanagement of customer capabilities and expectations is a key factor in failed initiatives. Change management and transformation are complex endeavors that require total alignment from leadership down to the line of business worker to ensure adoption and maximum ROI attainment. - David Pauli, Newton3 12. Do Your Homework Carefully It's important to get detailed information before beginning. There are always hidden stakeholders that we forget to account for in large tech initiatives. Solutions are often over-engineered and take more time to implement, only to fail due to misaligned expectations. Finally, it's essential to detect risks and manage them wisely. - Devendra Goyal, Think AI 13. Proceed With Curiosity, Not Just Conviction I learned not to fall in love with my own ideas. I built a product I loved, assuming others would, too, without validation. When no one used it, I realized the importance of customer feedback. It taught me to lead with curiosity, not just conviction. - Jason Penkethman, Simpro Group 14. Lead With Empathy A failed IAM rollout taught me the cost of skipping user engagement. We focused on technology, not user experience, leading to poor adoption. Since then, I have led with empathy, ensuring alignment between security goals and real-world user behavior. - Premsai Ranga, Price 15. Align Teams Around Purpose, Not Platforms One lesson I learned is that technology alone is not transformation. Early on, I focused too much on the technology as the solution and not enough on people and processes. That misstep taught me to lead with empathy and clarity, aligning teams around purpose, not just platforms. That shift made all the difference in driving real, lasting change with technology as the connector. - Lee Cage Jr., BDO 16. Recognize That Innovation Can't Be Outsourced I once led an initiative using a white-labeled product that wasn't designed for our specific needs—it was like forcing a square peg into a round hole. The experience taught me that innovation can't be outsourced and that clear, proactive communication is essential when managing client expectations during setbacks. - Chandler Barron, Barron Advisory™ 17. Establish A Realistic Strategy Early On To Guide Investments And Decisions I am passionate about developing sensitive biomarker detection technologies that will eventually be used for patient selection. These assays are often expensive and complex, making their implementation in prospective trials challenging. They must navigate regulatory processes. I've learned the importance of establishing a realistic strategy early on to make smart investments and decisions. - Rachel Tam, Bristol Myers Squibb 18. Fight Against Complacency Nothing will kill innovation faster than complacency. As a leader in the tech world, if you are more afraid of a deadline than you are of releasing a mediocre improvement, your company will fail. Somewhere out there is a company that is being forced to innovate in order to close the gap with you, and with every incremental improvement, you lose ground to their innovation. - Matthew Areno, Rickert-Areno Engineering, LLC 19. Value Early User Input And Iterative Improvement A failed tech initiative taught me that isolated development without early end-user involvement poses high risks. Our product launch failed to achieve its goals due to unvalidated assumptions. The experience taught me the importance of leading through curiosity while valuing user input and committing to iterative improvement. This experience taught me humility while helping me evolve into a collaborative and grounded leader. - Amit Ojha 20. Never Build In A Vacuum A failed tech launch taught me the hard way: Never build in a vacuum. We had a solid plan but skipped early user feedback—and it showed. The product missed the mark. That experience made me a stronger leader by showing the power of listening early and often. Now, I focus less on having the perfect answer and more on staying curious and connected to real user needs. - Bhupendra Singh, Marriott International

Geek Wire

19 minutes ago

• Geek Wire

AI Agents Are Rewriting Developer Processes — Here's What's Next

For years, 'shift left' has been the mantra for development teams: catch bugs early, test often, and fix fast. The logic is simple: the earlier you catch a problem, the cheaper and easier it is to fix. In fact, depending on which report you believe, businesses now spend six to 100 times less time resolving bugs during design and development than in production. A new shift is underway. Not just left, but forward. Advances in AI are pushing us into a new era – one where software doesn't just detect issues sooner, but begins to fix itself. Intelligent agents are fundamentally transforming how software is built, deployed, and improved, giving rise to a new model: the Agent Development Lifecycle (ADL). From traditional development to the agentic model In traditional software development, the process begins with business goals — epics and user stories — translated into code by developers. But these stages are often fragmented: strategy here, code there. Feedback loops exist but need to be manually constructed, maintained, and operationalized. In the emerging agentic model, intelligent agents are given goals upfront and built to act on them throughout their lifecycle. The AI agent isn't just a feature — it's an autonomous or semi-autonomous system embedded with intent. It knows what it's trying to achieve. That matters. Because it enables a whole new set of behaviors: Agents can monitor their own performance, recommend changes, and in some cases, even implement improvements autonomously. What is the agent development lifecycle? In the Agent Development Lifecycle, agents evolve into autonomous, self-managing, and self-improving systems. Developers define the agent's objective, embed that intent into its design, and give it the ability to measure and evaluate its own performance. This means developers spend less time chasing bugs and more time designing adaptive systems, connecting agents to the right data, setting guardrails, and most importantly, driving impactful business outcomes. And that shift aligns with what developers want. In Salesforce's State of IT survey of more than 2,000 developers, 92% of them said they wanted to measure their productivity based on impact, rather than output. Where we are today Let's be clear: fully autonomous agentic engineering systems for business-critical work in enterprises aren't here yet. But the foundation is already in place and is evolving quickly. Today, agents are designing, testing, deploying, running, and measuring other agents at scale. They're suggesting improvements; not just what to change but also drafting a plan to implement the improvement (in low code, and in pro code). And, they're not just limited to back-office tasks. They're increasingly running autonomous frontline business operations. Take 1-800Accountant, the U.S.'s largest virtual accounting firm for small businesses. Their team used Agentforce, Salesforce digital labor platform, to autonomously resolve 70% of customer chat engagements during tax week in 2025. Without writing a line of code, 1-800Accountant quickly configured AI agents to meet specific needs using Salesforce's low-code tools and AI assistance. Preparing for agent-driven development To succeed in the agentic era, teams need more than smarter code. They need platforms built for a new development model, one where agents understand their goals and can act on them. And where developers can design, shape, monitor, and evolve these agents with confidence. It starts with the ability for the agent to understand its objective. It needs access to a rich metadata platform to evaluate its goal and the right data to implement it. To monitor, improve, and control the agent, engineering teams need telemetry, observability, and heuristic testing frameworks. And, in enterprise environments, they also need strong governance controls and guardrails to enforce company policies and stay compliant and secure. For example, a recent version of Agentforce, included a new set of AI-powered low-code and pro-code tools for developers to configure, test, and deploy agents faster. The future of development As agents take on more responsibilities, the role of the developer is shifting from writing code to designing intelligent systems with clear goals and adaptable behavior. To keep pace, organizations will need a new development philosophy. One where adaptability is built-in, outcomes drive design, and agents learn to deliver business value at scale. In this model, developers aren't just builders — they're trainers, architects, and orchestrators of intelligent, evolving systems.

Entrepreneur

21 minutes ago

• Entrepreneur

How to Use Micro-Acquisitions to Scale Faster and Smarter

Opinions expressed by Entrepreneur contributors are their own. Most people assume that business acquisitions are reserved for massive companies with deep pockets and teams of M&A lawyers. But here's the truth: You don't need a war chest to buy and grow another business. In fact, you can scale faster, safer and smarter by using micro-acquisitions — small, strategic purchases of businesses that cost less than what most startups raise in a seed round. Micro-acquisitions aren't just a shortcut to growth; they're a powerful way to buy revenue, talent and capabilities without the slow grind of building from scratch. Here's how entrepreneurs can use them to scale without raising millions and without the typical risk that comes with starting everything from zero. Related: Entrepreneurship is Risky. Follow This Less Risky Path For Entrepreneurial Success What exactly is a micro-acquisition? A micro-acquisition typically refers to the purchase of a small business, often in the range of $50,000 to $500,000. These deals usually involve solo founders or very small teams and are often bootstrapped businesses. You'll find them in SaaS, ecommerce, media, digital services and even niche B2B verticals. Unlike larger deals that require complex due diligence and outside investors, micro-acquisitions can often be done quickly and creatively financed, sometimes even with seller financing or revenue-based payments. A great place to browse real-world examples is MicroAcquire (recently rebranded as which has become the go-to marketplace for buying and selling small internet businesses. Why micro-acquisitions make strategic sense When you build a business, you're investing time and money into acquiring customers, building a product and refining operations. But when you buy a business, even a small one, you skip ahead in the game. Here's what a micro-acquisition can instantly provide: Revenue : You're buying cash flow from day one. Customers: You inherit a base of users or clients without the CAC (customer acquisition cost). Product or tech : If you're in software, buying a product that's already functional saves months of development time. Team : Even one or two experienced people onboard can supercharge your capacity. SEO/traffic: Media sites or content businesses often come with valuable search rankings. This is why seasoned entrepreneurs often say, "Build if you have to. Buy if you can." Related: Is Acquiring a Business Right For You? Here's How to Know If You Should Buy a Business or Start From Scratch How to find the right micro-acquisition target The key to smart acquisitions is alignment with your goals, capabilities and existing infrastructure. Here are three practical ways to uncover acquisition targets: Marketplaces : Flippa and Tiny Acquisitions all list small online businesses for sale. You can filter by size, revenue, industry and growth. Your own network : Many small business owners would sell if they knew someone they could trust. Put out feelers in your LinkedIn network, communities and industry groups. Inbound interest: Once people know you're open to acquiring, founders may reach out directly. It happens more often than you think, especially if you're known in your niche. Look for businesses where you can add unique value. Maybe you have distribution they don't have or operational strengths that could increase margins. How to fund a micro-acquisition without VC money You don't need to raise millions — or anything, in some cases. Micro-acquisitions can be financed in surprisingly flexible ways: Seller financing : The seller agrees to let you pay a portion up front and the rest over time. It's common in smaller deals and shows the seller's confidence in the business continuing to perform. Revenue-based financing : Platforms like Pipe or Capchase let you borrow against predictable revenue, especially for SaaS. Cash flow from your existing business : If you already run a profitable company, you may be able to acquire a smaller one with internal cash flow. Partnership or joint acquisition: You can co-acquire a business with a partner who brings cash, skills or time. Because these are small deals, you don't need to be a finance wizard. Just ensure that the business you're buying can at least cover its own debt payments and ideally contribute profit from month one. What to look out for before you buy Not all micro-acquisitions are worth it. Some look good on the surface but are hiding churn, tech debt or founder-driven sales. Here are red flags to watch: No clear documentation : If the financials are murky or inconsistent, move with caution. Customer churn : In SaaS or subscription businesses, ask for cohort data. A leaky bucket is hard to fix. Overdependence on the founder : If the owner is also the top salesperson, developer and customer support agent, you'll have a lot to replace. Platform risk: Is all their revenue coming from a single ad platform or one ecommerce channel? Do your due diligence, even if it's light. Related: What You Need to Know to Buy the Right Business and Acquire Your Empire Post acquisition: Make the first 90 days count Buying the business is only the start. The value is in what you do after the deal closes. Here's how to make your acquisition pay off: Stabilize : Keep existing operations running smoothly and avoid major changes immediately. Communicate : Let existing customers and any team members know what's changing (and what isn't). Integrate : Plug the acquired business into your existing stack, whether it's tools, processes or branding. Optimize: Use your strengths to unlock growth. Can you improve pricing, add new marketing channels or reduce overhead? Think of your acquisition as a new product line or revenue stream and manage it like you would any core part of your business. If you're running a business, you already know how hard it is to build. Buying a business, even a small one, can be one of the smartest, most leveraged moves you make. Micro-acquisitions put growth within reach without the dilution, risk or grind of raising capital. You get to skip the messy zero-to-one phase and jump into something with traction. As more platforms and tools emerge to make small business deals accessible, this strategy is only going to get more popular. The earlier you start learning the playbook, the further ahead you'll be.