Corsa Media House

Notes

How we built Jarvis, a command center for every business we run.

A dashboard is easy to build and hard to keep believing. These are the rules that decide whether an owner still opens it in a month.

Published September 23, 2026

Our founder runs a collision repair shop, an estimating software product, an online store and this studio at the same time. Each one has its own system: Shopmonkey for the shop, Stripe for payments, a database behind the store, Search Console for traffic, and the servers everything runs on. Knowing whether anything needed him meant a tour of all of them, every morning.

Jarvis replaced the tour. It is a private screen with every business on it, it lights up only what needs attention, and it answers questions out loud. It went from first question to live in one day. The build was the easy part. The rules below are what make it worth opening.

Rule one: show what needs you, not everything you have

Most dashboards fail the same way. They show forty numbers at the same volume, so a number that is fine and a number that is costing money look identical, and within a week nobody reads either. We started from the other end: a list of things that have actually gone wrong in these businesses, turned into checks.

  • A finished car sitting in delivery, still unpaid, three days later.
  • A paid online order nobody marked as shipped.
  • Stock at or under its reorder point.
  • A website not answering, or a security certificate about to expire.
  • A scheduled job on the server that failed its last run.
  • A data feed that stopped answering.

Each check is a warning light, the way a car dashboard works. Dark means checked and fine. Amber or red comes with one plain sentence saying what is wrong. The count of lit lights sits in the middle of the screen. When it says zero, there is nothing to do, and that is the point.

Rule two: a broken feed must never look like a quiet day

The most dangerous number on any dashboard is a zero that means "I could not read the source". It looks exactly like a slow day. So every figure in Jarvis is stored with where it came from and when it was read. If a feed fails, its panel says "no feed" and the light for that feed turns amber. A panel we have not connected yet says so in words instead of showing a zero, which also keeps us honest about what it can see.

Rule three: look, never touch

A command center reads from the systems that take real money, so it must be incapable of changing them. Jarvis reads through database accounts that can only read, and only the specific columns it needs. It cannot see password hashes, customer phone numbers or email addresses at all, and every attempt to write is refused twice over. We tested each of those refusals before building anything on top.

Rule four: private by default

An owner’s full financial picture does not belong on the public internet behind a password. Jarvis runs on the owner’s own server and is reachable only over a private network from his own devices. There is no login page to attack because there is no public page at all. On the desktop it is a small Mac app that opens at login and reconnects by itself if the network drops.

How it is built

  1. A collector runs every ten minutes. It reads each system, turns what it finds into figures and warning lights, and writes one snapshot file.
  2. A small web server shows the latest snapshot. It never talks to a database itself, so a slow system cannot make the screen hang.
  3. The screen draws the snapshot: the ring of businesses, the lights, a panel per business, and a question box.
  4. The question box answers from the same snapshot the panels show, so it cannot say something the screen does not. The briefing is read aloud by the device’s own voice.

The look is deliberately a HUD, because the brief was "Jarvis". But the structure underneath is plain: collect, store with provenance, show only what needs you. That structure is what we would carry into a command center for any owner.

What we would do for another business

Start with the morning tour: every system you check and what you are looking for in each. Turn the things that have actually hurt you into lights. Connect read-only, prove the access is read-only, and only then design the screen. Run it on accounts you own. The demo on our command center page runs the real interface on invented businesses, so you can click through it before deciding anything.

Questions

How long does it take to build a business command center?

Jarvis went from first question to live in one day, because every system it reads was already reachable. Most of the time in any build goes into connecting systems, so the number and accessibility of your systems sets the timeline.

What is the difference between a dashboard and a command center?

A dashboard shows numbers. A command center decides which numbers are problems, stays quiet while they are fine, and tells you in a sentence when one is not. It is built around the decisions an owner makes, not around the data that happens to be available.

Can a command center read Shopmonkey data?

Yes. Jarvis reads a collision shop’s Shopmonkey data, including repair orders by workflow stage, balances owed and when orders were paid in full.

What this relates to

Read next

Taking new work

Want it set up this way from the start?

Every account opened in your name on day one, and a written assignment before the first invoice. Tell us what needs building.