Ask Your Own Data · half-day workshop · Santa Monica

Next date to be announced.

You own the data. You still can’t ask it a question.

Four hours on your own live systems. You arrive already connected, and you leave asking your data questions in plain English — in Claude or Codex, whichever you already use.

It sits in a database somewhere. Every order, every job, every location, every month going back years. And to ask it anything you need SQL, table names and relationships — a language built for the machine rather than for you. So either you file a request and wait, or you never ask. Both of those are the same problem wearing different clothes.

Half a day Setup call before the day No SQL In person · not a webinar
Kash Badami
The workshop
Half a day, in person · next date to be announced
  • A setup call before the day so you arrive connected to your own data rather than spending the morning on plumbing.
  • Ask questions in plain English — of your real systems, not a sample dataset someone prepared.
  • In the tool you already use. Claude or Codex, your choice. Nothing new to adopt.
  • Every answer shows its working so you can check the number before you act on it.
  • Read-only, always. Nothing you do in that room can change or damage your data.
  • You keep the setup. It still works on Friday, and the Monday after.
Leave able to ask your own data questions in plain English — or a full refund
The guarantee

If you leave without it, you pay nothing.

Most workshops guarantee your satisfaction, which is unfalsifiable and therefore worth nothing. This one guarantees a specific outcome you can check yourself before you walk out of the room.

You will leave able to ask your own data a question, in plain English, and get an answer back with its working shown. If that has not happened by one o’clock, tell me and I refund the whole fee. No form, no window, no argument.

The one condition is the setup call. It is where we find out whether your systems can be connected at all — and if they cannot, I tell you before the day and refund you then, so neither of us wastes a Thursday.

Why there is a setup call

Connecting to a live business system needs credentials and, often, someone in IT to approve read-only access. Nobody arranges that in the middle of the morning while the room waits.

So we do it first, on a 30-minute call before the day. Bring your IT person if you have one. If you are the IT person, bring the connection details.

It means the morning is about your questions rather than about configuration — which is the part worth paying for.

The problem

Computers forcing people to think like computers.

This shows up two ways, and they are the same problem underneath.

If nobody is coming to help

You are the analyst.

There is no reporting team. There is you, a system holding every transaction across every location, and a query language you never signed up to learn. So the question stays unasked and the decision gets made on a feeling.

If someone else runs the reports

You ask, then you wait.

You have the question on Tuesday. The answer arrives Friday, by which time you have moved on or guessed. The dashboard answers what somebody anticipated last quarter, not what you need right now.

Either way the data is sitting right there and you cannot get at it on your own terms. That is not a gap in your ability. It is a gap in the tooling — software was built to be operated by specialists, and nobody went back and fixed it when that stopped being necessary.

What you walk away with

Not notes. A thing that works on Friday.

01

A live connection to your own data

Read-only, scoped to what answers business questions, running inside the AI tool you already use.

Still working the next morning
02

Your own vocabulary, written down

What “a customer” means in your business, which date column is the real one, how you count a return. The machine gets this wrong until somebody tells it, and that somebody is you.

The part that makes answers correct
03

The ten questions you actually ask

We build against the real ones — the ones you currently email somebody about, or never get around to.

Answered before you leave
04

A way to check the answer

Every response shows the query it ran and the rows it read. You never have to take a number on faith, which matters the first time one looks wrong.

Trust, earned rather than assumed
The four hours

Hour by hour.

Setup call, 30 minutes

We connect you, read-only, and confirm it works. If it cannot be done, you find out here and get refunded.

The questions you never get to ask

Everyone writes down the questions they currently have to ask someone else. These become the morning’s work.

Asking, and being wrong

First real questions against your own data — including the ones that come back wrong, because understanding why is what stops you trusting a bad number later.

Teaching it your business

Your definitions, your rules, your exceptions. This is where a generic tool becomes yours, and it is the hour that does the most work.

Lunch, and the harder questions

The ones you would not have thought to ask on Monday. Patterns, comparisons, and what changed when something changed in the business.

You leave with it running

On your machine, against your data, in your own words.

Who this is for

People who run something and own their data.

This is for you if

  • Your business runs on a real system — orders, jobs, patients, properties, shipments, locations.
  • You have questions about it you either cannot answer or have to ask somebody else to answer.
  • You can get read-only access to it, or know who can.
  • You would rather ask in English than learn a query language.

This is not for you if

  • You write SQL comfortably already. You would be bored, and I would rather say so now.
  • Your data lives only in spreadsheets someone maintains by hand — that is a different problem and this will not fix it.
  • You cannot get any access to your own systems, even read-only. Sort that first.
  • You want a dashboard built for you. That is a different job and I am happy to talk about it, but it is not this room.
Next date

Next date to be announced.

Leave your email and I will tell you when the next date is set. Nothing else.

Common questions

Common questions.

What if my data cannot be connected?

We find that out on the setup call, before the day, and I refund you in full. That is exactly why the call happens first — so nobody discovers a blocker on the morning itself.

Most systems are reachable. The usual obstacle is permission rather than technology, which is why it helps to bring whoever controls access.

Is my data safe? Does it leave my systems?

Access is read-only, enforced at the database, so nothing you do can change or delete anything. You connect your own systems yourself and keep the credentials — I never hold them.

If your data is regulated or you have a security team with a view on this, bring them to the setup call. It is a fair question and it deserves a real answer rather than a reassuring one.

Do I need to know SQL?

No. If you already do, this room is not for you — you can do this yourself and would be bored.

Claude or Codex?

Whichever you already use. The setup works in both, and the point is to put this where you already work rather than ask you to move somewhere new.

What if my data is a mess?

Most are. Messy data is a reason to come, not a reason to stay away — a lot of the morning is teaching the tool what your particular mess means. What this cannot fix is data that does not exist, or that only lives in someone’s head.

Can you run this for my whole team instead?

Yes, and for most companies that is the better version — the room is a good place to find out whether this works for you before committing a team to it. Book a call.

One question, asked in your own words, answered by your own data.

Next date to be announced.

Tell me the next date