Autonomous Vehicles News | September, 2026 (STARTUP EDITION)

Autonomous Vehicles news, September 2026: discover where AV startups can win now with safer mobility, smarter logistics, and scalable fleet opportunities.

MEAN CEO - Autonomous Vehicles News | September, 2026 (STARTUP EDITION) | Autonomous Vehicles News September 2026

TL;DR: Autonomous Vehicles news, September, 2026 shows where startups can win now

Table of Contents

Autonomous Vehicles news, September, 2026 shows you that the real upside is no longer in flashy self-driving car promises, but in narrow, deployable AV services and the software, trust, and fleet tools around them.

The market is getting more practical. Robotaxis, delivery fleets, freight corridors, and industrial vehicles in controlled zones are moving first, while fully autonomous personal cars still face trust, cost, weather, liability, and city-rule barriers.

Your best startup angle may be beside the vehicle, not inside it. The article points to demand for fleet orchestration, simulation, mapping checks, cybersecurity, incident logs, insurance tools, digital twins, and passenger trust systems.

Commercial use beats consumer hype. Research and industry data show real driverless services exist in only a small number of cities, and Level 4 geofenced systems still matter more than “works everywhere” autonomy. See this AV factsheet and this review on public acceptance of autonomous vehicles.

The biggest founder mistake is confusing demos with real operations. If you are building in mobility, logistics, SaaS, insurance, property, or city tech, focus on one bounded workflow, prove it with real users, and build where trust and traceability are worth paying for.

If your business touches transport, delivery, fleets, or physical asset records, this is a good time to spot the messy middle and claim a useful place in it.


Startups in the United States News | September, 2026 (STARTUP EDITION)


Autonomous Vehicles
When your autonomous vehicle startup says the car can think for itself, and the investors ask if it can also pivot by Friday. Unsplash

Autonomous Vehicles news in September 2026 tells a very clear story: the market is growing up, the hype is thinning out, and founders now need to separate real deployable systems from expensive demos. From my perspective as Violetta Bonenkamp, a European serial entrepreneur working across deeptech, AI tooling, education, and compliance-heavy products, this month matters because autonomous mobility is no longer a futuristic talking point. It is becoming an operating model for ride-hailing, delivery, freight, industrial transport, and software-led infrastructure.

That shift changes the conversation for entrepreneurs. We are no longer asking whether self-driving systems can work at all. We are asking where they work, under what conditions, who captures margin, and which startups can build around the stack without burning cash on fantasy. That is where the real business signal sits.

The sources behind this article point to a market pushed forward by advances in artificial intelligence, cameras, radar, lidar, mapping, machine learning, and high-performance onboard computing. They also show a pattern that experienced founders will recognize fast: commercial and bounded use cases are moving first, while fully autonomous personal cars remain slower to arrive. According to the Union of Concerned Scientists self-driving cars explainer, only a handful of driverless ride-hailing services were operating in about half a dozen cities as of 2026, and no manufacturer had yet released a fully automated personal vehicle.

Here is why that matters. If you are building in mobility, logistics, smart cities, insurance, fleet software, education, cybersecurity, mapping, simulation, or compliance, September 2026 is not just another month of sector updates. It is a stress test for your market assumptions.


What is really happening in autonomous vehicles in September 2026?

Autonomous vehicles, or AVs, are vehicles that can sense their surroundings and perform part or all of the driving task without direct human control. In practical terms, that includes robotaxis, self-driving delivery vans, autonomous trucks on limited routes, and industrial vehicles operating in controlled sites. The technology stack usually combines cameras, radar, lidar, GPS, mapping, vehicle software, and real-time decision systems, as described by NVIDIA’s autonomous vehicles overview and the Britannica autonomous vehicle technology reference.

September 2026 fits into a broader pattern that had already been forming. Passenger mobility gets the headlines, but the commercial logic still favors constrained environments first. That means geofenced city zones, fixed freight corridors, industrial yards, ports, mines, warehouses, and repeatable delivery routes. Founders who confuse a controlled Level 4 service area with universal full autonomy are still making the same old mistake.

From a European founder viewpoint, I see three parallel stories unfolding at once. First, the software layer is becoming more valuable than the vehicle shell. Second, trust, compliance, and safety documentation are becoming product features, not legal side notes. Third, the winners may not be the companies that build the whole car. They may be the companies that own a narrow but painful part of the workflow around AV deployment.

  • Robotaxi and ride-hailing pilots keep proving demand in dense urban zones.
  • Delivery and logistics remain attractive because route structures are narrower and unit economics can be modeled more cleanly.
  • Freight and trucking still move carefully due to safety concerns, route limits, and public-road scrutiny.
  • Industrial and off-road autonomy often look more commercially mature than consumer autonomy.
  • Personal fully autonomous cars still face the hardest trust, regulation, cost, and edge-case barriers.

That last point is often underplayed in mainstream reporting. The shiny consumer narrative sells clicks. The money often forms elsewhere first.

Why should entrepreneurs care about autonomous vehicles now?

Because autonomous vehicles are no longer a single product category. They are turning into a business stack. If you are an entrepreneur, you do not need to build a self-driving car company to win from this shift. You can build around fleet orchestration, edge compute, data labeling, digital twins, sensor cleaning systems, insurance analytics, simulation, mapping validation, last-mile operations, passenger trust layers, accessibility services, in-car commerce, or compliance tooling.

This is where my own background shapes my reading of the sector. At CADChain, I spent years thinking about how protection, compliance, and trust must live inside technical workflows instead of being bolted on after the fact. Autonomous mobility will follow the same rule. The companies that hide legal and operational friction inside good tooling will beat the companies that expect users, city operators, or fleet managers to manually solve every governance problem themselves.

Put differently, AVs are not just a transport story. They are a workflow story. They are a software quality story. They are a machine-human trust story. They are also a procurement story, because city contracts, enterprise fleet deals, and insurance relationships can matter more than a flashy consumer launch.

What do the current facts say about the autonomous vehicle market?

Several source signals help frame September 2026.

  • Fortune Business Insights on autonomous vehicle market growth links market expansion to advances in artificial intelligence, sensor systems, and connectivity.
  • The same source notes that passenger cars held a dominant share in 2022, with ride-hailing and ride-sharing helping pull autonomous functions into passenger mobility.
  • It also points to Volkswagen’s previously stated plan to introduce self-driving vehicles for ride-hailing and goods delivery in Austin in 2026, which fits the commercial deployment trend.
  • Union of Concerned Scientists reports that a handful of driverless ride-hailing services were active in about half a dozen cities, showing that real deployment exists but remains geographically limited.
  • Britannica’s autonomous vehicle reference states that as of 2025 there were no fully autonomous cars for unrestricted consumer use, while Level 4 systems such as Waymo driverless taxis worked inside set operational bounds.
  • NVIDIA highlights applications across robotaxis, trucks, passenger vehicles, and autonomous delivery, which confirms that AV value is spreading across many business models.

The stat that should make founders pause is this one cited by A3 on autonomous vehicles and machine learning: 93% of crashes are due to human error. Even if the exact public debate around safety remains tense, that number explains why investors, cities, fleet operators, insurers, and logistics firms keep pushing the category forward. The addressable upside is not just convenience. It is fewer collisions, better traffic flow, lower labor dependency in some routes, and new mobility access for older adults and people with disabilities.

Which autonomous vehicle segments look strongest for startups?

Let’s break it down. A founder should think in terms of where autonomy meets repeatability, budget, and measurable pain.

1. Ride-hailing and robotaxi support tools

Robotaxis attract media attention, but support layers may be easier startup plays. Think dispatch software, incident review, passenger communication, accessibility interfaces, cleaning workflows, geofence updates, and local business partnerships. If a city has driverless ride services, someone still needs to manage the service fabric around them.

2. Autonomous delivery and last-mile commerce

This segment has cleaner founder logic. Routes can be repeated, payloads are narrower, customer expectation is clearer, and labor economics are easier to model. Startups can serve grocers, pharmacies, prepared meal brands, campus operators, and industrial sites.

3. Freight corridor tooling

Autonomous trucking remains constrained, but the support market is real. Think route intelligence, remote assistance software, compliance reporting, maintenance prediction, hub-to-hub orchestration, trailer-chain tracking, and incident reconstruction.

4. Industrial and off-road autonomy

This may be the least glamorous and most commercially sane segment. Mines, ports, warehouses, farms, and construction sites offer bounded environments. They have lower public-road chaos and often higher willingness to pay. Founders chasing fast revenue should look hard at this zone.

5. Compliance, safety, and trust infrastructure

This is my favorite category because it is usually underbuilt. AV companies need audit trails, software version traceability, event logs, digital evidence, insurance-grade records, and explainable governance. If your product helps prove what happened, when, where, and under which software conditions, you are serving a real pain point.

  • Safety case documentation
  • Data provenance tracking
  • Fleet event logging
  • Sensor calibration records
  • Cybersecurity monitoring
  • Regulatory reporting tools
  • Passenger trust and consent interfaces

That category fits a broader founder truth I keep repeating: boring infrastructure often beats glamorous surface products.

What is still blocking full autonomous vehicle adoption?

The answer is not “technology” alone. The blockers sit across cost, trust, regulation, edge cases, mapping quality, weather, cybersecurity, public acceptance, liability, and business model design.

  • Edge cases: rare road events still break clean model assumptions.
  • Weather and visibility: rain, fog, snow, dirt, glare, and road wear still matter a lot.
  • Sensor cost and compute cost: hardware stacks remain expensive in many setups.
  • Legal liability: fault, insurance, and responsibility are still messy.
  • Public trust: one visible accident can hit sentiment hard.
  • City-by-city regulation: deployment is patchy and local.
  • Cybersecurity: connected vehicles widen the attack surface.
  • Unit economics: a technically working system can still be a bad business.

As a founder, I would add one more blocker that people often avoid naming: narrative confusion. Companies mix assisted driving, conditional automation, geofenced autonomy, and true driverless operations into one blurry marketing story. That makes customers, investors, and public officials less informed. It also creates backlash when the product reality does not match the sales language.

My background in linguistics makes me unusually strict on this point. Language is not decoration. Language shapes risk perception, buying decisions, and policy reactions. In autonomous mobility, bad wording can create bad deployment.

How should founders read the levels of autonomy without getting fooled?

The Society of Automotive Engineers framework, often summarized from Level 0 to Level 5, matters because it prevents category mistakes. Level 0 means no automation. Level 2 means partial automation with human supervision. Level 4 means high automation in a defined area or context. Level 5 means full self-driving in all conditions. Sources such as Britannica and UCF’s overview of autonomous vehicle levels explain these distinctions clearly.

For business owners, the practical lesson is simple: do not invest, partner, or build based on vague claims of “autonomy”. Ask what level, in what operational design domain, under what supervision model, on which routes, in what weather, and with what remote fallback. If a founder cannot answer that cleanly, the company may still be selling aspiration rather than a working product.

What are the biggest opportunities for entrepreneurs around autonomous vehicles in late 2026?

Here are the opportunity zones I would watch most closely.

  • Fleet software for mixed autonomy environments, where human-driven and autonomous vehicles share routes and depots.
  • Simulation and synthetic scenario tools for testing rare driving events before public deployment.
  • AV cybersecurity products focused on connected vehicle surfaces and over-the-air software risk.
  • Sensor maintenance and calibration services for fleets that need uptime and safety evidence.
  • Insurance tech for autonomous fleets, including incident scoring and policy modeling.
  • Mapping validation and update services for geofenced operation zones.
  • Passenger trust layers, such as in-vehicle communication, incident alerts, and accessibility support.
  • Municipal tooling for city regulators managing permits, operating zones, curb use, and service standards.
  • Training and simulation education for fleet operators, dispatchers, remote support staff, and public servants.
  • Digital twin systems that connect software state, vehicle condition, and legal traceability.

I want to pause on that last point. Digital twins are especially interesting because they sit at the meeting point of software trust, physical asset history, maintenance, and liability. That logic strongly overlaps with what I have seen in CAD, IP protection, and blockchain-backed evidence systems. When a machine acts in the physical world, record integrity matters.

How can a startup enter the autonomous vehicle market without building a car?

This is the question smart founders should ask first. You do not need to become an automotive manufacturer. You need to find a painful job around autonomous mobility and solve it better than incumbents.

  1. Pick one narrow customer group. Start with city mobility operators, warehouse operators, freight hubs, insurers, campus fleets, or delivery networks.
  2. Name one painful workflow. Incident review, route mapping, compliance logging, passenger support, charging coordination, or remote operator handoff.
  3. Define your operating context. Public roads, industrial sites, campuses, ports, or private compounds are very different markets.
  4. Build the smallest testable product. I strongly prefer no-code and low-code early on, unless physics or hard compute demands custom engineering from day one.
  5. Get real operational data fast. Interview fleet managers, safety teams, dispatchers, insurers, and city staff. Avoid founder theatre.
  6. Design for traceability from the start. Every decision log, software event, and asset state may matter later in legal or safety reviews.
  7. Make trust visible. Good dashboards, plain language, and usable reporting can close deals faster than technical bragging.
  8. Pilot in one bounded environment. Campuses, depots, ports, and industrial zones often beat giant city ambitions as first entry points.
  9. Price around business pain. Save labor, cut incident handling time, reduce claim disputes, or shorten permit workflows.
  10. Stay human-in-the-loop where needed. Small teams can win by supporting machine systems, not replacing humans everywhere at once.

That method mirrors one of my long-held operating rules: default to no-code until you hit a hard wall. Founders waste years building giant systems before validating whether anyone will buy them. In AV-adjacent markets, that mistake gets even more expensive.

What mistakes do founders and investors still make in autonomous vehicles?

Some mistakes repeat so often that they deserve a permanent warning sign.

  • Confusing demos with deployment. A staged video is not a commercially repeatable service.
  • Ignoring operational design domain limits. A system that works in one sunny district may fail elsewhere.
  • Selling “full autonomy” too early. Overclaiming destroys trust fast.
  • Treating compliance as paperwork. In AVs, compliance can shape product architecture, not just legal review.
  • Underpricing safety operations. Remote support, cleaning, maintenance, and incident handling cost money.
  • Forgetting city politics. Public acceptance, unions, disability access, and curb management all matter.
  • Skipping cybersecurity. Connected vehicles are software systems on wheels.
  • Building for headlines, not procurement. Enterprise and public-sector buying logic often decides survival.
  • Assuming Europe, the US, and Asia behave the same way. Regulation, procurement, infrastructure, and public trust vary sharply.

I would add a more uncomfortable point. Many founders still love “vision” more than evidence. My own work in game-based founder education taught me that learning must be experiential and slightly uncomfortable. AV startups should apply the same standard to themselves. Put the product in reality. Put claims under pressure. Put the economics in daylight. If the system only looks strong inside a pitch deck, the company is still in costume.

What does September 2026 reveal about the business model behind autonomous mobility?

It reveals that autonomous mobility is becoming service-led before it becomes universally consumer-led. This is an old pattern in deeptech. Expensive systems usually enter through fleets, enterprises, industrial users, and constrained environments before they become mass-market consumer products.

Brookings on securing the future of driverless cars makes a related point by arguing that automated vehicles are likely to spread in niche markets before reaching broader consumer adoption. That logic remains highly relevant in 2026. It means founders should stop asking, “When will everyone own a self-driving car?” and start asking, “Which narrow mobility job is economically ready right now?”

That question opens better startup paths. It favors founders who know how to design around real constraints. It also favors people who can connect software, operations, regulation, and user behavior. This is one reason I believe mobility will reward multidisciplinary founders more than pure technologists. Machines do not sell themselves. Systems do.

How should small businesses prepare for autonomous vehicles even if they are not in mobility?

You may be more exposed to AVs than you think. If you run a retail chain, property business, logistics service, warehouse, restaurant brand, urban service company, insurer, education provider, or digital product studio, autonomous mobility can affect your operations indirectly.

  • Retailers may need new pickup and curbside handoff processes.
  • Commercial property owners may redesign parking, drop-off, and charging layouts.
  • Restaurants may partner with autonomous delivery fleets.
  • Insurers may create products tied to autonomous fleet behavior.
  • Training businesses may sell AV safety or remote operator education.
  • SaaS founders may build scheduling, maintenance, or trust interfaces around AV fleets.

Next steps are simple. Map which part of your business touches transport, delivery, access, parking, or urban movement. Then ask what changes if some of those flows become partially autonomous. You do not need perfect foresight. You need useful scenario planning.

My founder take: what should we watch next?

From where I sit, September 2026 is a month to watch five things very closely.

  • City-level expansion of driverless services, because geography still defines what is real.
  • Commercial fleet economics, because growth without workable margins is theatre.
  • Trust infrastructure, including audit logs, legal traceability, and explainable service behavior.
  • Human-in-the-loop operating models, because full removal of human oversight remains rare.
  • European positioning, because Europe could produce strong AV support layers even if it moves slower than some US or Asian deployments in raw visibility.

I am especially interested in the European angle. Europe often gets framed as slower, more regulated, and less aggressive. Sometimes that is true. Yet the same conditions can create very strong businesses in compliance tooling, industrial autonomy, fleet trust systems, digital twins, cybersecurity, and public-sector mobility software. Entrepreneurs who understand regulated environments can build durable companies there.

And yes, there is FOMO here. If you wait for universal full autonomy before acting, you will probably enter too late. The early money is often made by the builders who support the messy middle.

What should readers do with this autonomous vehicles news now?

Start with a hard question: where does your business touch movement, fleet operations, physical assets, safety records, logistics, or machine trust? If the answer is “somewhere,” then this category matters to you already. The opportunity in 2026 is not to repeat sci-fi slogans. It is to build useful picks-and-shovels for a market that is moving from spectacle to operations.

My final view is direct. Autonomous vehicles are becoming less magical and more commercial. That is good news for founders. Mature markets reward disciplined builders, not just loud storytellers. If you can solve one painful workflow around AV deployment, explain it in plain language, and prove it under real conditions, you may have a much stronger business than the company promising a driverless utopia on every road tomorrow.

That is the signal inside September 2026. The market is still hard. The costs are still real. The trust gap is still wide. Yet the window for smart, focused startups is OPEN right now.


People Also Ask:

What are autonomous vehicles?

Autonomous vehicles are cars or trucks that can sense their surroundings and operate with little or no human input. They rely on sensors, cameras, radar, LiDAR, software, and machine learning systems to detect roads, traffic, pedestrians, and obstacles while controlling steering, braking, and acceleration.

How do autonomous vehicles work?

Autonomous vehicles work by collecting real-time information from cameras, radar, LiDAR, GPS, and onboard computers. The system analyzes road conditions, identifies nearby objects, predicts movement, and then controls the vehicle’s speed, steering, and braking to travel safely.

Is a Tesla an autonomous vehicle?

A Tesla is not fully autonomous in the strict sense. Tesla vehicles have advanced driver-assistance features such as Autopilot and Full Self-Driving capabilities, but they still require a human driver to stay alert and be ready to take control when needed.

What are the levels of autonomous driving?

Autonomous driving is commonly grouped into SAE Levels 0 to 5. Level 0 means no automation, Levels 1 and 2 include driver-assistance features, Level 3 allows the car to handle some driving under limited conditions, Level 4 can operate on its own in set areas or situations, and Level 5 means full self-driving in all conditions without a human driver.

Do autonomous vehicles need a human driver?

Some autonomous vehicles still need a human driver, depending on their automation level. Lower-level systems only assist with parts of driving, while higher-level systems can handle more tasks on their own. Fully autonomous Level 5 vehicles would not need a human driver, but they are not yet common in everyday use.

Are autonomous vehicles the same as self-driving cars?

Yes, the terms autonomous vehicles and self-driving cars are often used to mean the same thing. Both refer to vehicles that use computing systems and sensors to perform driving tasks without constant human control, though the exact level of autonomy can differ.

What is the problem with autonomous vehicles?

The main problems with autonomous vehicles include safety in unexpected situations, trouble in bad weather, difficulty reading unusual road conditions, software errors, and legal or ethical concerns. They can perform well in controlled settings, but real-world driving still presents situations that are hard for machines to handle perfectly.

Do we really need driverless cars?

Driverless cars are seen by many as useful because they may reduce crashes caused by human error, improve mobility for older adults and people with disabilities, and support transport services. At the same time, some people question whether the benefits outweigh the costs, safety concerns, and job loss risks tied to widespread use.

Are autonomous vehicles safe?

Autonomous vehicles can improve safety in some situations because they do not get distracted, tired, or impaired. Still, they are not flawless, and safety depends on the quality of the software, sensor performance, road conditions, and how well the system handles rare or confusing events.

What technology is used in autonomous vehicles?

Autonomous vehicles use a mix of cameras, radar, LiDAR, ultrasonic sensors, GPS, mapping tools, and onboard computing systems. These parts work together to detect the environment, track objects, make driving decisions, and control the vehicle’s movement.


FAQ on Autonomous Vehicles in September 2026

How can founders validate an autonomous vehicle startup idea before building expensive tech?

Start with workflow pain, not vehicle ambition. Interview fleet operators, insurers, city teams, and depot managers to find repetitive, costly bottlenecks. Test with mock dashboards, no-code tools, and pilot data before hiring deep engineering teams. Use the Bootstrapping Startup Playbook for lean validation and review this Autonomous Vehicles Factsheet.

What signals show whether an AV market is actually ready for commercial deployment?

Look for geofenced operations, repeatable routes, local permits, insurer participation, remote-support processes, and paying customers rather than PR demos. Real readiness means operational discipline and bounded environments. See practical startup scaling frameworks in the European Startup Playbook and track current autonomous vehicle industry news.

How should startups think about autonomous vehicle insurance and liability risk?

Treat liability as a product design issue from day one. Log software versions, sensor state, route conditions, and handoff events so incidents can be reconstructed fast. That reduces disputes and improves insurability. Explore AI operations strategy for startups alongside this review of public acceptance, regulation, and legal concerns in AVs.

Why does public trust matter so much for self-driving vehicle adoption?

Public trust directly affects permits, ridership, partnerships, and city expansion. Even technically strong systems can stall if riders feel confused, unsafe, or excluded. Clear in-vehicle communication and transparent incident handling matter. Build stronger trust positioning with Vibe Marketing for Startups and read this comprehensive review on autonomous vehicle public acceptance.

What role does sustainability play in autonomous vehicle business decisions?

Sustainability is not just emissions messaging. It includes congestion effects, parking demand, energy use, accessibility, and whether shared fleets outperform private car expansion. Founders should quantify system-level impact, not just vehicle efficiency. Use SEO for Startups to communicate complex value clearly and reference this systematic review of AV sustainability impacts.

Which autonomous vehicle use cases are easiest for small startups to enter in 2026?

The best entry points are AV-adjacent: mapping validation, incident review, depot operations, accessibility UX, compliance reporting, and sensor maintenance. These niches need less capital than full autonomy stacks and solve immediate buyer pain. Find scrappy execution tactics in Vibe Coding for Startups and study how AVs are used across delivery, freight, and industrial operations.

How can founders distinguish between ADAS, Level 4 services, and true full autonomy?

Ask specific questions: what SAE level, what operating design domain, what weather limits, what fallback model, and whether a human must supervise. Many companies blur these distinctions in marketing. Sharpen technical communication with Prompting For Startups and use this autonomous vehicle levels and facts reference.

What does autonomous mobility mean for cities and infrastructure startups?

Cities need software for permits, curb management, pickup zones, accessibility oversight, safety reporting, and fleet coordination. That creates demand for municipal tooling, not just vehicles. Infrastructure founders can win by reducing deployment friction. Position B2G and ecosystem offers via LinkedIn For Startups and explore this review of AV impacts on transportation systems and infrastructure.

Are robotaxis the best autonomous vehicle opportunity for new startups?

Usually not. Robotaxis are visible but capital-intensive and operationally complex. Smaller startups often have better odds in support layers around fleets, trust, compliance, or logistics coordination. The glamour sits in vehicles; the margin may sit elsewhere. Apply the Female Entrepreneur Playbook to focused market entry and follow consumer-facing self-driving car trends and sentiment.

What should investors and founders watch next in autonomous vehicles after September 2026?

Watch city-by-city expansion, economics per route, remote operations, safety documentation, and software-led differentiation. Also track industrial autonomy, where revenue may scale faster than consumer autonomy. The strongest companies will prove disciplined operations, not just technical ambition. Track opportunity framing with AI SEO for Startups and monitor state-of-the-art autonomous driving technology trends.


MEAN CEO - Autonomous Vehicles News | September, 2026 (STARTUP EDITION) | Autonomous Vehicles News September 2026

Violetta Bonenkamp, also known as Mean CEO, is a female entrepreneur and an experienced startup founder, bootstrapping her startups. She has an impressive educational background including an MBA and four other higher education degrees. She has over 20 years of work experience across multiple countries, including 10 years as a solopreneur and serial entrepreneur. Throughout her startup experience she has applied for multiple startup grants at the EU level, in the Netherlands and Malta, and her startups received quite a few of those. She’s been living, studying and working in many countries around the globe and her extensive multicultural experience has influenced her immensely. Constantly learning new things, like AI, SEO, zero code, code, etc. and scaling her businesses through smart systems.