No report builder. No query syntax. Just ask.

Bridge doesn’t give you another dashboard to learn. You ask your own AI assistant a question in the words you’d use with a person, and it picks the right way to answer from your live Lightspeed data.

Below is the shape of what it reaches — the kinds of questions shops actually ask us. It isn’t a menu you pick from. It’s a map of what’s in range.

your assistant · Bridge● connected

you  ▸  which brands are sitting on stock we haven't sold in 90 days?

        Four, and one of them is most of the problem.

        Vermilion      $18,400   142 units   last sold Jun 12
        Halden          $6,200    38 units   last sold May 30
        Ottway          $3,950    61 units   last sold Jul 02
        Pike & Rowe     $1,100     9 units   last sold Jun 28

        Vermilion is 64% of your idle stock value. Twelve of those
        units are last-season colourways in size L.

you  ▸  what did we pay for the vermilion?

        $11,960 landed. At full retail you're looking at a $6,440
        margin, but nothing in that group has sold in over 80 days.

That’s two questions. No report was run, no export opened, no filter configured.

Bridge also knows the lists your business is organised by — your brands, categories, shops, payment types, staff, work-order statuses — so “by brand,” “by shop,” “by tech” mean something specific to you rather than a generic grouping.

Sales and revenue

What came in, when, through which till, and how it compares.

“How did we do Saturday compared to the same Saturday last year?”
“What’s our attach rate on tune-ups this quarter, and is it different by service writer?”
“Which two things sell together most often that I’m not bundling?”

Inventory and catalogue

What you’re holding, what it’s worth, and what isn’t moving.

“Which brands are sitting on stock we haven’t sold in 90 days?”
“What’s the dollar value of everything that hasn’t moved since spring?”
“A customer wants this part — do we already have one at another shop instead of ordering it?”

Customers

Who they are, what they’ve bought, and who’s drifted away.

“Who spent over $500 with us last year and hasn’t been in since?”
“Which house accounts are past due, and by how much?”
“Do we have the same person in here three times under different spellings?”

Service and work orders

What’s on the bench, how long it’s taking, and what’s holding it up.

“What’s still open past its promise date?”
“How long is a tune-up actually taking us, start to finish?”
“Which jobs are waiting on a part we’ve already got on the shelf?”

Purchasing and vendors

What you ordered, what actually arrived, and who’s reliable.

“What did we order that never fully arrived?”
“How long does this vendor really take, versus what they tell me?”
“Am I buying anything from one vendor that I could get cheaper from another I already use?”

Team

Who’s selling what, and when the shop was actually staffed.

“Who’s selling the most — and is that volume or ticket size?”
“How many hours did we actually run last week?”

Ask for anything

Every section above describes questions we anticipated. The useful part is what happens when you ask one we didn’t.

Bridge mirrors your complete Lightspeed record — not a curated subset chosen when we built it. So when you ask something oddly specific about your own shop, the answer is usually yes, even if no report anywhere was designed for it.

“We don’t have that data” is a bug here, not an answer.

If your assistant can’t reach something in your Lightspeed account, we want to hear about it — that’s a gap to close, not a boundary to explain.

Making changes

Pro · granted per person

Everything above reads. On Pro, your assistant can also do the work:

“The vendor sent a new price list — update the items it covers.”
“Build me a purchase order for everything below its reorder point from this vendor.”
“These two customer records are the same person. Merge them.”

You see it before it happens.

Every change is previewed first — what will be touched, and what it will become — before anything is applied.

Changes can be put back. New records can’t.

A price, a cost, a reorder point, a tag, a customer, a work order can be returned exactly as it was. Creating something new — a purchase order, a vendor, a customer — is one-way, and Bridge tells you so before you confirm.

You decide who.

Write access is granted person by person, across sixteen separate permissions. Your service writer can manage work orders and nothing else; your buyer can build purchase orders but never touch a price.

Your staff can see what happened, inside Lightspeed.

Every change leaves a dated note on the record itself, in the field your team already reads.

Why there’s no list of tools here

Bridge answers these questions through a large set of purpose-built tools, each one shaped around a specific question a shop asks. We don’t publish the catalogue — it’s a build specification, and we’d rather not hand it to someone assembling a copy.

Customers get all of it. The moment you connect, your assistant receives the full reference automatically, and you can read the same thing in your portal. Nothing about the surface is hidden from the people using it.

The fastest way to know is to ask it something.

Connect Bridge to the assistant you already use, and start with the question you’d normally run a report for.

Start Bridge — $39.99/mo See how it connects