Tony Sampano · Founder & Ecosystem Designer
Running a business is hard enough. The software should make it easier.
I’m Tony Sampano, founder of Speedway. I have spent more than 35 years across telecommunications, IT infrastructure, management and operating businesses. Eventually I became the customer of the kind of technology I had spent a career around—and I saw first-hand how much work disconnected systems push back onto the owner.
Speedway grew from one simple idea: the business should not have to become the integration layer. Sales, customers, stock, staff, bookings, payments, communications and AI should be able to work from the same governed business context, while people stay focused on customers and the work that actually matters.
The short version?
I got tired of seeing good businesses spend their time making software agree with other software. Speedway is my attempt to make the technology behave more like one capable operating team.
35+ yearsTechnology, management and entrepreneurship
Telecoms → hospitalityInfrastructure experience translated into operations
AI since 2022Sheila Innova through to governed Atlas AI
Founder-operatorSoftware shaped by businesses that have to work every day
What shaped Speedway
I learned early that good technology disappears into the job.
Telecommunications teaches you quickly that reliability is not a presentation feature. When systems are doing their job well, people can get on with theirs.
My professional background covers telecommunications and IT/ICT across Australia and Southeast Asia. The work included satellite communications, transmission towers, international voice, private circuits, broadband, Carrier and Metro Ethernet, BTS and mobile backhaul, fibre-optic networks, internet connectivity, network operations, billing, management and monitoring.
Infrastructure work gives you a particular way of looking at problems. You think about links between systems, points of failure, capacity, coverage, recovery, interoperability and what happens when conditions are less than perfect. You learn that the architecture behind the interface matters, because the person using the system should not have to care how complicated the plumbing is.
Those lessons never left me. A business platform should not assume perfect connectivity, depend unnecessarily on one expensive device or let one failed integration bring the operation to a halt. It should know what the authoritative record is, move information reliably, recover cleanly and let people keep doing the job they are there to do.
That is one reason Speedway is designed from edge to core rather than as a collection of unrelated web applications. Connectivity, devices, real-time events, offline continuity, integrations, identity, permissions and evidence are part of the operating design rather than afterthoughts.
The experience behind the idea
Technology, infrastructure, management—and then the reality of running businesses.
I include the career detail because Speedway did not begin as a software exercise. It grew out of decades spent seeing systems from the technical, commercial and operator sides.
Built around complete telecommunications and engineering services, including transmission towers, wholesale international voice, private leased circuits, satellite networks and commercial bandwidth, broadband over power lines, and network operations, billing, management and monitoring.
Board-level technical advisory experience in satellite communications, adding to the practical understanding of large-scale network planning, service continuity and telecommunications operations.
Management experience with a licensed Australian telecommunications carrier and satellite-broadband provider serving large and remote geographic markets.
Worked with carriers, utilities, internet service providers, enterprises, equipment vendors and financiers on communications infrastructure and managed services, including Carrier Ethernet, Metro Ethernet, fibre and mobile/BTS backhaul.
Moved deeper into hands-on consumer and service operations through an asset-based Bali business, dealing directly with customers, vehicles, maintenance, bookings, staff, logistics and day-to-day service delivery.
Operating restaurants made the fragmented-software problem impossible to ignore: POS, stock, online ordering, membership, promotions, delivery, staff, customer communications, reviews and reporting all needed to work as one business.
RaffsSync became the practical technology response: connect sales, inventory, staffing, work, fulfilment and automation around a shared operational record instead of asking a business to continually reconcile separate applications.
I began coding and developing applied AI systems for real business workflows in 2022. Sheila Innova became an early RaffsSync AI assistant for sales, customer enquiries, support-oriented workflows and guided hand-offs. That work grew into a wider approach to business AI: assistants should understand the company's live operating context, respect permissions and guardrails, and know when to answer, act, escalate or ask for human approval. Those principles are now carried forward in Atlas.
Speedway extends the RaffsSync operating model into a modular ecosystem spanning commerce, payments, hospitality, workforce, communications, customer services, integrations and governed Atlas AI.
I was born in Sydney, Australia, in 1968. Across my career I have also worked in senior management, advisory and commercial roles involving company formation, strategy, capital investment, partnerships, joint ventures and complex technology rollouts. My experience has taken me across Australia and Southeast Asia, including Indonesia, Malaysia, Singapore, Hong Kong, Thailand and Vietnam.
My public professional profile lists Computer Science study at Curtin University and an MBA focused on Information Technology at the University of Sydney. The combination of technical education, commercial responsibility and real operating businesses has shaped the way I approach Speedway: technology only matters when it makes the business itself work better.
The turning point
Owning businesses changed the question from “Can we build it?” to “Why is this so hard to run?”
The view changes quickly when you are paying for the systems, responsible for the team and still have to keep the business moving when those systems do not agree.
Running restaurants and service businesses gave me first-hand experience of the pressure entrepreneurs and business owners carry every day. There is always something demanding attention: a customer waiting for an answer, an order that needs to move, stock that does not match, a supplier issue, staff scheduling, a booking, a payment, a delivery, a review, a promotion, an equipment problem or a report that has to be reconciled.
The common software answer has often been to add another application. One system for sales. Another for inventory. Another for online ordering. Another for bookings. Another for staff. Another for marketing. Another for accounting. Another for customer messages. Another for reviews. Each one may solve a narrow problem, but the owner becomes the integration layer between them.
That creates duplicated customer records, duplicated products, different prices in different places, manual reconciliation, repeated logins, multiple subscriptions, expensive hardware changes and staff training on systems that each understand only one small part of the business.
A business owner should not have to spend the day making software agree with other software. The systems should agree because they are working from the same governed operating record.Tony Sampano, founder of Speedway
From RaffsSync to Speedway
I did not start with a product catalogue. I started with a problem.
RaffsSync began as a practical response to the friction inside our own operations. Speedway grew that idea into reusable infrastructure that can serve many businesses, industries and workflows.
Customers, products, orders, bookings, stock, work, payments, people and operational evidence should resolve against one governed business record instead of drifting between disconnected databases.
Cashiers, managers, kitchen teams, field crews, customers and AI assistants need different interfaces, but they should not be working from different versions of the business.
A business should be able to start with the capability it needs and add more later. New modules should join the same operating fabric rather than become another isolated system.
External systems and providers still have a place. The Integration Hub exists so businesses can connect what they need without turning every integration into a bespoke technical project.
The Speedway principles
Practical, connected and built to earn its place.
These principles are not abstract software preferences. They come from what matters when you are responsible for the business outcome.
Modern business software should not force owners to buy the most expensive specialist hardware simply to participate. Requirements differ by workflow, but ordinary compatible devices should do as much of the work as practical.
Supported workflows should account for intermittent connections and real-world edge conditions, with controlled recovery and reconciliation when connectivity returns.
Native Speedway modules, SDKs and external integrations should be discoverable and activatable through the Integration Hub with clear pricing, capacity, prerequisites and permissions.
The platform should remove repetitive coordination, duplicated data and unnecessary worry instead of turning the business owner into a full-time systems administrator.
Automation should help without quietly taking control away from the business. Permissions, approvals, evidence, auditability and the authoritative operating record matter.
A small operator and a larger multi-site organisation should be able to use the same underlying principles, adding capability without rebuilding the whole stack.
Why Atlas exists
AI should feel like a capable team member—not another thing to manage.
Atlas is the continuation of applied AI work I have been coding and developing since 2022, including earlier RaffsSync assistants such as Sheila Innova. The goal has remained consistent: use AI to reduce repetitive owner workload while keeping the business in control.
Working on Sheila and other AI-assisted workflows taught me that a useful business assistant needs more than a conversational model. It needs current business knowledge, clear responsibilities, controlled hand-offs, permissions, evidence and a reliable connection to the systems where the work actually happens.
As a business owner, you should not need to personally handle every routine marketing task, answer the same customer questions over and over, chase every review, manually assemble every operational summary or constantly search through separate systems to understand what is happening.
Atlas is Speedway's AI assistance layer for that reason. It is designed to work with governed business context: the products you actually sell, the services you actually provide, current promotions and events, customer-facing information, operational records, permissions and the rules that define what the business has authorised.
The important part is the guardrails. AI is useful when it can assist confidently inside the boundaries of the business. It should know when it can answer, when it can propose an action, when approval is required and when protected Speedway services remain the authority. That is a very different idea from giving an unconstrained chatbot control of the company.
Help answer routine enquiries using current merchant information, catalogue, events, promotions, reservations and approved business knowledge.
Assist with monitoring and responding to customer reviews in the business's voice while keeping evidence, moderation and owner controls where required.
Support promotions, offers, customer communication and campaign work using the same products, membership rules and business context already used operationally.
Summarise what changed, surface exceptions, help staff find the right workflow and reduce the time owners spend hunting across multiple tools.
Why Speedway is modular
One business. Different jobs. Shared context.
Speedway separates the interface for the job while keeping the underlying business authority connected.
The merchant and business command workspace for catalogue, inventory, webstore, customers, promotions, staff, reporting, configuration and connected modules.
Sales, counter, mobile, table and QR ordering workflows that stay connected to fulfilment, customer context, pricing, payments and the shared catalogue.
Customer-facing sales, reservations, events, promotions, membership benefits and service access projected from the same business data instead of rebuilt separately.
Production and service teams receive the information they need from the live order rather than from another manually re-entered ticket.
Assignments, workforce coordination, field work, routes, proof and staff operations stay connected to the same people, jobs and business authority.
Property management, communications and other vertical capabilities can use the same platform principles rather than becoming separate technology islands.
Native modules, SDKs and external providers can be added through one governed integration surface instead of hidden one-off configuration.
The customer experience and AI assistance layer connect back to the same merchant and operating context, preserving continuity from discovery through service and support.
What success looks like
The result should be calmer operations, not more software.
I do not measure success by how many modules a business uses. I care whether the technology makes the business easier to understand, easier to operate and easier to grow.
Enter important business information once and let authorised workflows use it consistently.
See what is happening without chasing staff, spreadsheets, inboxes and disconnected dashboards for the same answer.
Adopt modules progressively, connect external services where appropriate and avoid unnecessary all-at-once technology changes.
Let software and governed AI handle repetitive coordination while people remain responsible for the decisions that actually need human judgement.
Founder questions
What people usually ask me.
The founder story explains the design motivation; current product pages remain the authority for specific Speedway capabilities and availability.
Why was Speedway created?
Speedway was created from first-hand experience of fragmented business systems, duplicated records, expensive hardware expectations and the day-to-day pressure placed on owners and operators. Its design centres on modular workflows sharing one governed operating record.
Is Speedway only for restaurants?
No. Restaurant and hospitality operations are an important part of my practical operating experience, but the platform is designed as modular operating infrastructure for many kinds of businesses and service organisations.
Does Speedway require expensive specialist hardware?
The design principle is to avoid unnecessary dependence on expensive proprietary hardware. Exact requirements depend on the workflow, peripherals and integrations a business chooses, but Speedway is intended to work with practical compatible devices wherever possible.
Is Atlas allowed to run the business by itself?
No. Atlas is designed to assist inside governed context, permissions and guardrails. Protected services and authorised business rules remain authoritative, and workflows can require human approval where appropriate.
From experience to infrastructure
If you are spending too much time running the systems instead of running the business, Speedway was built for that.
Start with the problem that costs you the most time or attention. Keep your business authority, add the modules you need and expand without rebuilding the same business in another disconnected stack.