What it's like to work with us.

Senior data engineers build your Switchboard and run it week after week. Inside week one you have live sources, a first dashboard, and the built-in AI, Operator, on your data. Your part takes a few hours.

"It feels like we hired a full data team overnight, without the cost or complexity."

Alyse Borkan, Co-Founder  Rocco

A first dashboard in week one.

Built on your live sources, so the first thing you see is your own numbers.

A few hours of your time.

You sit for a working session, log in to connect your tools, and react to what we ship. We do the rest.

Senior engineers, on your account.

The people who build your Switchboard stay on it. You'll know them by name.

The job, in four parts.

01 · Define

Agree on the numbers.

Working sessions turn how the business runs into written definitions. Every metric gets one: what counts as an order, a customer, CAC.

02 · Build

Lay the foundation.

We connect your sources, join the data across tools, and build the dashboards on top. It all lives in the platform, not on someone's laptop.

03 · Enable

Make the AI fluent in your business.

Every definition we write becomes context Operator reads: your metrics, your rules, your team's language. Agents run on the same foundation.

04 · Run

Run it and keep it current.

We monitor the syncs, fix the breaks, and update the model as the business changes, for as long as you're a customer.


What the first weeks look like.

The build takes weeks. Almost none of them are yours.

  1. A working session on how the business runs.

    You bring the people who know the rules and the spreadsheets only your team has. We ask what you need answered and where the numbers live.

    Your part~2 hours
  2. Your tools come online.

    Mostly sign-ins: you log in and click approve. Our engineers handle everything after, including connectors built to order.

    Your partMinutes per tool
  3. The first dashboard ships.

    We build the report you named in the working session first. Tell us what's wrong with it; that list is the plan for week two.

    Your partReact to v1
  4. Weekly sprints from there.

    You get a shared Slack channel from day one, working sessions while we build, and a weekly recap of what shipped and what's next.

    Your partSlack us

Do we keep the same engineers?

Yes. The engineers who build your Switchboard stay on your account, and you talk to them directly in the shared channel. There's no support layer between you and the person who did the work. Meet the engineers.

How do requests work after launch?

Message the channel. Requests go into the weekly sprint, and the recap at the end of the week shows what shipped. Bigger asks get scoped in the channel before we build, so you see what you're getting.

What happens when something breaks?

Monitoring catches a lot before it reaches your dashboards. When something slips through, or a number looks off to you, an engineer digs in and comes back the same way every time: what happened and what changed, in plain language. You don't file a ticket.

Is this consulting?

No. Switchboard is the product; the engineering is part of it and part of the price. There's no statement of work and no hourly bill.

See what your first weeks would look like.

Book a demo. We'll walk through a sample Switchboard and map what week one would cover.