What she carries
- 01
Starts with your company
Who she works for, the business and industry context you provide, the systems you approve and the responsibilities she starts with.
- 02
Learns through work
Authorized communications, what your team teaches her, the corrections it makes, and the outcomes of the work she is part of.
- 03
Carries understanding forward
Relevant company knowledge helps with later calls, handoffs, questions and analysis, instead of starting over each time.
- 04
Knowing is not permission
Sabina’s understanding of the company can grow. Her authority continues to come from the permissions the company grants. What she learns never widens what she may do; you decide when that changes.
The memory, in full
The context travels with the work.
A customer’s scheduling requirement learned during one job can inform the next booking. When another authorized teammate takes over, the relevant context can travel with the work.
This company context is separate from model weights: teaching, company memory and model training are different mechanisms, and nothing here is a claim that a model is retrained on your business or that every detail is recalled correctly.
Shaped around your company, not one person’s account.
Sabina starts with the company and industry context you provide. As she works with the sources you authorize and the people on your team, useful knowledge stays connected to the work. An instruction, a correction, or a decision can help with the next responsibility.
Start with one responsibility: tell her how you handle it, correct mistakes and review the result. She needs your company’s sources and instructions. The record can retain context when team members change, subject to access and retention terms. It is not perfect memory or a guarantee of improvement on a calendar.
Company context
Give her a record worth reading.
Who your customers are, what you’ve quoted, what you committed to and what came back. The available sources and corrections provide context; completeness, recall and usefulness still need to be checked.
What she is not yet able to do
She will need clarification and correction. A stored record is not proof that she has understood every detail or can act on it.
Questions from the record · Scope-dependent
She raises the thing that was never anyone’s job.
When the relevant record and capability are available, these can become questions with supporting evidence for your team to review.
Useful discovery depends on source coverage, record quality and the work enabled for your company. There is no month-two deadline or promised performance advantage.
What she is not yet able to do
She surfaces; she does not decide. What she raises comes to you as a question with the evidence attached.
- A quote sitting untouched.
- A recurring handoff that stalls.
- A customer waiting for an answer.
Curve three · Decisions, and whether they were right
Keep the reasoning with the decision.
An outcome is more useful when you also record the decision: what was known, what constrained it and what you expected to happen.
Recording expectations before the outcome is known gives your team something to compare later. It can support a review of decisions and results; it does not establish which decision caused a result.
What she is not yet able to do
Attribution is not causation, and this site will never claim otherwise. Linking decisions to outcomes tells you what accompanied what. Establishing cause requires deliberate testing, and that is a later capability, described plainly when it exists.
The outcome
Job closed. Invoice $8,400.
Context to keep with the same job
- What was true
- Quoted at $9,600 on 14 May. Two other bids in play, the nearer one at $8,900. The crew had an open week on the 27th.
- What constrained it
- Materials were already on order against the original scope, and the open week would otherwise have gone unbilled.
- What else was possible
- Hold at $9,600 and risk the bid. Move to $8,400 and fill the week. Offer the 27th at full price with a longer warranty.
- What was expected to happen
- That the lower price would take the job and still leave margin above twenty-two percent.
The illustration shows the context worth recording. Sabina can only work from the sources available to her; an alternative, constraint or expectation needs to be provided or supported by evidence.
Broader use · Separate agreement · Not offered today
Your company’s value does not depend on a broader program.
Any future use of eligible derived information beyond providing your company’s service requires separate, specific agreement, with identifying information removed before anything ascends. The value of Sabina’s work for your company does not depend on joining a broader intelligence program.
Three commitments govern it, and they are commitments, not aspirations:
- Your record is yours. Nothing ascends without your specific, revocable consent. Declining costs you nothing — no capability is withheld and nothing about your terms changes.
- Identity is removed before ascent, not after. Nothing that ascends carries your customers, your counterparties, or you.
- We will never tell your competitor what to charge. No price recommendations, no coordinated pricing signals, no bid intelligence. Not as policy — as design. If that is what you want from a data product, we are the wrong vendor.
No broader program is offered today. Nothing about it is part of what you are asking Sabina for, and declining it later changes nothing about your company’s service.
What you are putting into operation.
Your company’s own AI starts with a defined responsibility and the authority you agree. Teach her how you want the work handled, keep useful context and review the evidence. Additional responsibilities are agreed as their fit and support are established.
Start with the seven-step operational assessment. If you enter a public website, its address is sent to begin research. Other answers are sent with your contact details when you choose Meet Sabina or ask for the meeting with Mark.