Giving context and talking to your data

Dictate — say everything you are doing and why

The best context you can give me is the whole picture, out loud.

Tell me what you are trying to do and why, in as many words as come naturally.

Not a tidy one-line request — the messy full version: the goal, who it is for, what is riding on it, the bit of history that matters.

Speaking hands over the nuance and the why; typing makes you stop at the sentence that felt good enough.

I would rather have too much than too little, so let it run.

Say it like this:

*"I have a renewal coming up with this client and I want to keep them.

They went quiet after the last price conversation, the relationship matters to us, and I need a note that makes the case without sounding like a nudge — here is what I am weighing."*

Point me at what would help, and I go get it

You do not have to gather the material first — point me at it.

Tell me what to read and where it lives, and I fetch it before I start.

• "Read this document first."
• "Fetch that thread from my email."
• "Look for every document that would help ground you, and pull them in."

Then I go get it all, so I am grounded in your truth instead of guessing from the open web.

The work inherits the quality of what I read first — so the more you aim me at, the sharper it comes back.

Name the record, and I pull it

Most of the context is already loaded — you do not re-supply it.

When you signed in I loaded your profile, your mail, and your domain’s own knowledge — how the work is done at the company, the standards, the past work.

Your domain also keeps a record per client, and the company directory holds who’s who.

So name the thing and I read the record instead of starting from a blank page.

• Name the client and I pull their threads, what was committed, where the relationship stands.
• Name the deal and I pull the record and its history.
• Name the invoice and I pull the record behind it.
• Name a person and the directory resolves them — you never spell out an email address.

Say it like this:

*"I have a call with this client in an hour.

Pull their record and tell me where we left off and what’s still open."*

That is the whole gap between a generic answer and a sharp one: the prep names the open commitment, the thing they asked for, the price conversation you are mid-way through.

What I need from you is only what is in your head

Everything on file, I can reach.

The one kind of context I cannot reach is what lives only in your head — a side conversation, a constraint someone told you out loud, a piece of history that never made it into a file.

So when it bears on the work, say it before I start.

Treat me like a sharp colleague who has read everything on file but was not in the room with you.

Say it like this:

"Before you draft this — they pushed back hard on price last quarter, so lead with the value and keep the number near the end."

Talk to your data the same way — it is a conversation

Reaching the company’s own data works exactly like this: you ask in plain words.

There is no query language to learn and nothing to export — I turn your sentence into whatever the system underneath needs, read the live data, and answer in plain terms.

The answer is current because I read the source the moment you ask.

"How many clients are past their renewal date?"

The first answer is rarely the end of it, so keep going — ask the follow-up the way you would of a person still holding the numbers.

*"Of those, which three are the biggest?

Now show me what each one bought last year."*

Then ask for the shape you want — a number, a short list, a table, or a draft built straight off the data.

"Put the top ten by amount in a table."

Each turn builds on the last, so the analysis deepens as you push instead of you re-asking from scratch.

Orient-2 named what I am wired into — your mail and documents, plus the records your domain keeps in its own artifacts; this is how you use it.

The one thing to remember

Dictate the whole picture, point me at everything that would help, and name the client, the deal, or the invoice so I pull the record — then add the one thing only you could know.

Do that and the work comes back right far more often the first time, because I am reasoning from your real situation instead of an average guess.

Next: what running a domain asks of you.