End to end

We collect the data. We put it in your systems. We build the reporting.

It starts with what you already have: documents, scans, positions off your vehicles. We work the analysis with you, and it comes back as native Excel, PowerPoint, or a map in Power BI.

Scope an engagement
Exhibit A

Live asset tracking

Trucks and rail cars moving on one map, each with its own trail and its stops. The same pings measure dwell at every stop and driving hours per driver: an overtime bill on city work, an hours exposure on the highway.

Click any vehicle on the map, or any row in the list, to isolate it and follow just that asset.

Map loading, feed already running

Demo feed · sample data

  • Main line
  • Yard, siding, industrial

© OpenStreetMap contributors

Driver hours Measured from the same position pings the map is drawing, not typed in by a dispatcher and not read off a separate device. Thresholds shown are demo values, like the rest of this feed.

    The map and the feed are a demonstration: a synthetic track baked into this page and replayed in your browser, identical on every load. It is not live customer data, and no vehicle, tenant, or account feed is connected to this page.

    Capability

    One map for every asset you move, measured from the position data you already collect.

    • Demurrage and detention

      How long each car or trailer actually sat, stop by stop. That clock is either an invoice line you can bill or the evidence that kills a disputed one.

    • Driving hours

      Time behind the wheel, derived from the same pings as the dwell. Moving and stopped are one classification, so there is no second system to reconcile.

    • Overtime

      City work crossing its threshold mid-week, while there is still a week left to move the schedule. A payroll run tells you the same thing after it is too late to act.

    • Runs that stopped

      A stop that happened every week for a year and has not for three. Nobody files a report when a route falls off. It just stops earning, and the cadence is already in the stop history.

    • Telematics and ELD

      We take positions from whatever you already run, so nothing gets ripped out. The map, the tiles, and the rendering are ours, so the data does not leave for a vendor to draw it.

    Exhibit B

    Ask your workbook

    Drop in a workbook and ask it questions in plain language: what it is, where the numbers come from, what feeds what, and what to check first in diligence. You get an answer in seconds, even on files too large to hand a model whole. This panel is a preview of the built app, not a live feature on this page.

    Preview of the databa-chat app: a workbook is read and its structure shown as sheets, formulas, manual inputs and external links, with a plain-language answer and an ask box below. A brass Coming Soon sign is laid over the design.

    databa-chat is built and launching soon. This is a static preview of its design, with representative values; nothing on this panel uploads or reads a file.

    Built in house, not resold. What we hand you runs in your own environment, on software you already have.

    Scope of work

    1. Office output

      Models and reports delivered as native Excel/PowerPoint that recalc on your own data. No add-ins, nothing phoning home.

    2. Fleet map

      Your fleet's map, on your own infrastructure. No per-view map tax, no telematics rip-and-replace.

    3. Document extraction

      Structured data out of PDFs and scans, sourced back to the page it came from, not an LLM guessing at a table.

    4. Data warehouse

      Governed write-back into your own data warehouse, not just another read-only dashboard.

    5. Cloud estate audit

      A deterministic map of your own MS/cloud estate, and what's broken in it, read-only against a tenant you already control.

    6. Quality of earnings

      Coming soon: drop in the financials, get a quality-of-earnings read on how the business actually makes money.

    7. Roadmap

      Coming soon: handwriting reading.

    The work runs inside your own environment, under your own admin's sign-in, with the access your admin already has. Where a deliverable calls our engine, that call runs on our side, because the engine is ours and it stays with us. Your data goes there to be worked on, and nothing readable stays behind. We either keep none of it or keep it encrypted under a key only you hold, so we cannot open it ourselves. What we hand you that stands alone, a model or a report in native Excel or PowerPoint, keeps working on your machines whether or not we are here. What calls our engine depends on our engine. When the work ends, the access you granted is removed, and you can confirm that yourself in your own admin console.

    What we build is yours to keep and run after the engagement ends.

    Scope an engagement