Straight answers.

Trucking companies that run their own trucks, at any size: owner-operators, small and growing fleets, regional carriers and multi-terminal operations. If your week runs on dispatch, drivers, invoices, papers and a Friday close, it is built for you. Brokers are not the audience.

No. The same records and workflow serve one truck or many terminals; the menu stays short for a small team and opens up as the fleet grows. Honestly stated: the pilot fleets today are owner-operators and small and growing carriers. A larger fleet starts with a scoped pilot on one terminal or one lane, and enterprise single sign-on and API access are planned, not built. We do not claim verified performance at enterprise scale yet.

No. BAI is not an electronic logging device (ELD) and does not replace one. Keep your ELD. Connections to Motive, Samsara and Geotab are built but not switched on yet, so ELD positions and hours of service are integration-dependent.

Today BAI makes export files your bookkeeper can bring into QuickBooks Online or any other accounting tool. A direct connection to QuickBooks Online is integration-dependent: the BAI side is built, and it needs activation before it carries anything.

No. BAI prepares the worksheets for IFTA, state road taxes, IRP miles, Form 2290 and UCR from your own records. You or your preparer review every figure and file. BAI never files or pays anything.

Pricing is not published. During the pilot program, terms are set by agreement with each fleet. Nothing on this site is a price.

Week 0: we set up your records with you from what you already keep. Weeks 1 to 4: you run one week at a time on BAI, next to what you do today. Then we review together with a pilot scorecard, measured on your records, against thresholds we agree with you up front.

No. Drivers who do not use the driver app get their load by text or email. The app adds stops, positions, proof-of-delivery photos and messages for drivers who want it.

Your records are yours. You can export them as files at any time. Each fleet’s records are kept apart from every other fleet’s, and our own staff can only see them through recorded support sessions.

No. BAI takes on routine admin: status calls, data entry, chasing paperwork, getting invoices out. That way your people spend their time on the work that needs judgement, and the next hire can wait until you are ready. People keep oversight, and anything involving money or outside messages waits for a person to approve.

Pilot: built and tested, and offered to pilot fleets under a controlled pilot program, but not yet a finished, generally available product. Integration-dependent: the BAI side exists, but a vendor agreement, credentials or activation has not happened yet, so the file-based or manual path is what works today. Planned: designed, not yet built or switched on, with no date promised.

You set up one step at a time. Import trucks, drivers, papers and open invoices from a spreadsheet, invite your people, and run your first week next to what you do today. There is no long project before you see your own records in BAI.

Yes. A dry run shows every row from your spreadsheet before anything is created, so you can fix problems first. Anything BAI does not know stays marked as unknown; it never fills a gap with a guess or a zero.