Samuel Mfinanga · Named engineer · 20+ years infrastructure
Shape the first conversation
Start with the decision in front of you.
Answer what you know; every question is optional. Your choices prepare an editable brief, not a price or a delivery promise. Only these fixed choices travel to Contact; do not enter private records here.
Where it enters, who checks it, and where it has to land
A private model when the data requires one
A named person stays on it after the demo
AI Ops & Automation: the practical distinction
What changes when this work is done here.
A chatbot on the website.
The repetitive path, automated, with a person still responsible.
The workflow
How automation is put in
01The volumeThe repetitive work, counted with you. When the volume is there, we build it and stay on it.
02The pathWhere the work enters, who checks it, and where it has to land.
03The buildAutomation on that path. A private model when the data requires one.
04The ownerA named person stays on the automation. A demo that expires is not a delivery.
Start with the job
Four workflows. Four different first tests.
A document queue, a broken handoff, and a decision awaiting approval do not need the same solution. Choose the work that matters; the first scope should test its actual failure cases before promising scale.
01
Document intake
Which facts must be captured from incoming documents, and who checks an uncertain result?
Bring to the conversation
Describe document types, monthly volume, required fields, current review steps, and exceptions. Use counts and redacted examples in the first conversation.
Ask to see in the scope
Ask for a field-level test set, accuracy and correction measures, an exception queue, and an approved route for sensitive source files.
02
Cross-system handoffs
Where is the same information re-entered, and which system owns the correct record?
Bring to the conversation
Name source and destination systems, data owners, access boundaries, reconciliation rules, and what happens when either system is unavailable.
Ask to see in the scope
Ask for a data-flow map, duplicate and failure handling, a non-sensitive integration test, and an owner for mismatched records.
03
Approval routing
What can move automatically, and what requires a named person's decision before it changes a record?
Bring to the conversation
Identify the decision maker, delegation and expiry rules, material actions, notification channels, and how a request is withdrawn or corrected.
Ask to see in the scope
Ask for an approval-state map, authorization and audit requirements, timeout behavior, and a test of denied or unanswered requests.
04
Exception triage
Which repeated cases need a faster route to the right person without hiding unusual work?
Bring to the conversation
Bring category counts, current queue age, escalation owners, examples of misrouting, and the consequences of a wrong recommendation.
Ask to see in the scope
Ask for a baseline, a reviewed test set, routing and override rules, escalation timing, and a measurement plan for misses and rework.
Start with a job your team already performs: intake, handoffs, approvals, or exception triage. Map its volume and exceptions first; then choose whether a rule, integration, model-assisted step, or no automation is the right investment.
01
The task and its volume
Show representative cases, exceptions, time spent, and the current error path. If the work is rare or unstable, automation may not be the first investment.
02
Data and permission
Identify what information the system may read, what it may write, and what cannot leave the approved environment. Do not send confidential records through a website inquiry.
03
Human control
Name the decisions that need review, who can override an action, and how an uncertain or failed case reaches a person without being hidden as success.
04
Proof of value
Agree on a baseline and representative test set. Measure cycle time, quality, correction rate, exception volume, and operating cost before expanding the workflow.
05
The operating owner
Name who sees failures, maintains rules and integrations, reviews quality drift, and can pause the workflow. A build is not an operating plan.
What gets scoped
The proposal separates discovery, the first workflow, data boundary, integrations, evaluation, human review, monitoring, and support. Delivery and ongoing operations are separate scopes; NEXUS product access and autonomy are separate release decisions.
These sources help frame the questions. They are not a LUCA certification or a promise that every control is included in a service quote.
Before you choose
Questions worth settling before you switch.
Do we need AI for this workflow?
Not necessarily. Stable rules, a system integration, or a better handoff may solve it with less cost and risk. Compare options against the same case volume, exceptions, quality target, and operating owner before selecting a model-assisted step.
What can we share in the first inquiry?
Send the workflow goal, approximate volume, systems involved, and decision owner. Do not attach confidential records or patient information to the public contact form. If samples are needed later, agree on a protected channel and the minimum necessary data first.
Can a workflow approve or post a consequential change on its own?
That is a separate authorization decision, not an implied feature. The scope should name allowed actions, approval thresholds, the human decision maker, audit evidence, and how an action is paused or reversed where possible.
What happens when an input is missing or a system is down?
Define a visible exception path before release: stop or queue the case, notify its owner, preserve the source and reason, and test retry or manual completion. An uncertain case must not be recorded as a successful one.
How would we know the work is worth automating?
Measure today's volume, handling time, error and rework rate, and the cost of operating the proposed path. Run a bounded test with representative exceptions, then compare results against the agreed baseline rather than assuming a return.
Is this the same as buying NEXUS Workflows?
No. This page describes a scoped Technology service. NEXUS Workflows is a separate product, currently coming soon and not customer-ready. A service inquiry does not grant access; the product has its own customer-use gate.
Service here · product under NEXUS
That's AIRCITE, an available NEXUS product with its own plans and publishing authorization, not this service.
