The future staff experience
Sign in, see the functions assigned to your role, provide the requested information and review the result. No prompts to write, AI accounts to manage or systems to connect.
THE INAMA NEXUS AZEO · IMPLEMENTATION
One Inama back office.
Built around your work.
Nexus Azeo maps the work, designs each process and builds the platform. Inama staff will use clear, approved functions through one familiar interface.
14department field cards
30 daysproposed discovery
4pilot hypotheses
Day 100evidence-based decision
For Arnaud and department owners
Prepare the interviews, observe workflows, record sources and baselines, then play the findings back to each person before selecting a pilot.
What is ready here
Audit & evidence
Department questions and seven workbook formats for interviews, systems, scoring, pilots and markets.
Training & trials
Role-specific induction, reviewer checks and four proposed functions with measurable acceptance targets.
Decisions & sources
Nexus Azeo’s phased build programme, Day-100 criteria and documented approval before each release.
A message for the team
We want to understand how work really happens: what information you need, where time is lost, which steps depend on experience and which controls must remain human. The audit is about improving workflows, not evaluating people.
Italian opening for staff discussions
Non stiamo valutando le persone e non vogliamo automatizzare il mestiere. Vogliamo capire come avviene davvero il lavoro: quali informazioni servono, dove si perde tempo, quali passaggi dipendono dall’esperienza e quali controlli devono rimanere umani. L’AI potrà aiutarci a cercare, riassumere, confrontare, preparare e verificare. Non prenderà decisioni operative senza l’approvazione del responsabile.
This edition is Nexus Azeo’s implementation console. It saves audit records; it does not yet run operational AI functions. Staff permissions, review queues and connections will be built after the relevant workflows are agreed.
INAMA / DETAILED IMPLEMENTATION
The first 100 days.
Nexus Azeo conducts the audit, designs the workflows and builds the Inama back office. Staff receive only the functions approved for their role. Start the clock at the agreed kickoff.
Nexus Azeo implementation plan · based on the supplied documents dated 2 September 2026, adapted to Arnaud’s direction: one managed Inama platform. Owners, schedules and pilot targets remain to be agreed.
The first month, week by week
Week 1 · Set the conditions
90-minute leadership kickoff. Confirm scope, roster, Nexus Azeo-managed platform, source owners, excluded data, interview language and the staff message.
Output: audit brief, calendar and temporary data policy.
Week 2 · Follow information and decisions
Interview leadership, commercial, export, market, marketing and finance roles. Observe how one real task reaches its recipient.
Output: verified steps, handoffs, time and error evidence.
Week 3 · Follow the wine
Visit vineyard, intake, cellar, vessels, lab, bottling, stock and quality workflows. Include seasonal and offline work. Use a past example if current work is unavailable; mark the limitation.
Output: identity chain, source map, exception cases and human decisions.
Week 4 · Play back and choose
Check findings with every agreed department, including people/IT and sustainability. Correct the maps before scoring. Select the hypotheses whose evidence merits a pilot.
Output: confirmed audit summary, backlog and four draft charters.
From discovery to controlled use
Mobilise
Confirm sponsor, programme owner, staff roster, language, seasonal constraints and temporary data policy.
Exit gateNamed owners and agreed boundaries.
Discover
Interview people, observe real work, inventory systems and establish time, error and rework baselines.
Exit gateDepartment playback confirms the workflow.
Design
Score evidenced use cases, agree source owners and complete four pilot charters.
Exit gateScope, test cases, human gate and measures approved.
Prototype
Start with synthetic or redacted examples, then approved snapshots. Test normal and difficult cases.
Exit gateIdentity, units, sources and exceptions checked.
Run beside the current process
Record preparation, checking and correction time. Review failures and usefulness every week.
Exit gateDay-100 decision: stop, improve, scale or connect.
Roll out what passed
Nexus Azeo releases each approved function to named users with a task guide, trained reviewer and support route.
Exit gateRepeatable use by the team.
Consider connections
Assess read-only access first, then proposed changes in a review queue.
Exit gateSeparate integration decision and tested recovery.
Who carries the programme
| Role | Responsibility | Discovery effort in the guide |
|---|---|---|
| Executive sponsor | Resolve priorities, access and cross-department decisions. | Kickoff, 30 minutes weekly and gate reviews. |
| Programme owner | Calendar, evidence, backlog, decisions and follow-through. Nexus Azeo / Arnaud leads the implementation. | About one day/week; pilot effort scoped separately. |
| Department owner | Confirm workflow, samples, baseline and acceptance. | Interviews, observation and weekly pilot review. |
| Staff participant | Show real work, correct findings and try the workflow. | Approximately 2–3 hours in discovery. |
| Data / system owner | Authoritative sources, definitions, exports and access. | Depends on the selected systems. |
| Builder / analyst | Approved prototypes, tests, documentation and training. | Nexus Azeo builds after the pilot charter is agreed. |
| Privacy / compliance reviewer | Review data boundaries and procedure changes. | Gate reviews and exceptions. |
Keep the identity chain intact
Parcel + harvest pass → intake lot → wine lot → vessel history → bottling run → finished lot → pallet / shipment → business customer.
Record the identifier, date, quantity and explicit unit at each handoff. Show a missing or conflicting link; ask the source owner to resolve it. The winery’s existing records remain authoritative.
Day-100 decision criteria
Evidence & accuracy
100% of material statements sourced; at least 95% factual accuracy on agreed cases; 100% correct identity and units where relevant.
Control
Zero unapproved consequential action or automatic production, statutory, finance or HR write.
Value
At least 20% measured time saving, including review and correction, or an agreed equivalent quality gain.
Usefulness & continuity
Average usefulness at least 4/5. A named owner and another trained user can reproduce the workflow.
These are acceptance targets from the supplied guide, not achieved results. A failed control pauses the pilot; a persuasive demonstration is not evidence to scale.
INAMA / DETAILED IMPLEMENTATION
Every part of the winery.
For Nexus Azeo facilitators: prepare each department’s interview, collect a small evidence sample and observe real work. These cards guide the implementation team.
Nexus Azeo implementation plan · based on the supplied documents dated 2 September 2026, adapted to Arnaud’s direction: one managed Inama platform. Owners, schedules and pilot targets remain to be agreed.
Leadership and day-to-day management
Card 1 / 14Purpose
Create one reliable rhythm for decisions, exceptions and follow-through without turning AI into the manager.
People to include
Executive sponsor; family/leadership representatives; operations, commercial, finance and technical owners.
Evidence to collect before the session
- Weekly/monthly meeting packs, KPI reports and action logs
- Budgets, forecasts, production plans, stock reports and commercial reviews
- Management calendars, seasonal deadlines and recurring requests
- Examples of decisions delayed by missing, late or conflicting information
Questions to ask
- Which decisions recur daily, weekly, monthly and by season?
- What five questions should leadership be able to answer immediately?
- Which numbers or narratives arrive late, conflict or require manual reconciliation?
- Where does a decision depend on tasting, field observation, experience or relationship context?
- How are actions assigned, followed and closed today?
- Which information is too confidential for a shared AI project?
- What would make a weekly brief genuinely useful rather than another report?
What to observe live
- Preparation and conduct of one real leadership meeting
- How a decision moves from question to evidence to owner and deadline
- How exceptions are escalated and how past decisions are retrieved
First safe pilot hypothesis
A weekly sourced management brief: performance, changes, exceptions, decisions required and actions with owners/dates.
MUST REMAIN HUMAN No budget commitment, strategic decision, contract, price, payment, hiring or staff-performance decision.
Measures and Day-30 output
MeasureAcceptance signal
Preparation timeAt least 30% reduction from measured baseline
Action qualityAt least 95% of actions have owner and due date
EvidenceEvery material claim cites an approved source/date
UsefulnessLeadership average at least 4/5 after four cycles
Day-30 output: Decision calendar, KPI dictionary, source map, current baseline and one manually reviewed brief prototype.
INAMA / DETAILED IMPLEMENTATION
The working audit book.
Nexus Azeo’s implementation records: interviews, observed workflows, systems, use cases, pilot charters and market requirements. Staff are not asked to configure AI or invent their own tools.
Nexus Azeo implementation plan · based on the supplied documents dated 2 September 2026, adapted to Arnaud’s direction: one managed Inama platform. Owners, schedules and pilot targets remain to be agreed.
For your account’s audit discussions. Saved records are visible to the signed-in account that created them. This edition has no shared staff review queue. Status is a recorded declaration by the author; it does not grant access or activate an integration.
Your saved audit records
Load your records or create the first one above.
01 / LISTEN FIRST
Where could AI
help your day?
Bring one real task. Nexus Azeo will use it to map the process and agree what to build with the department owner.
Your saved contributions
Save a task above, or load your previous contributions.
STAFF INDUCTION / PROPOSED
Learn the task.
The platform handles the technology.
Nexus Azeo trains each team on the functions built for its work. This is the proposed induction structure; operational practice starts once a function is tested and released.
Find your assigned work
Your Inama account will show the functions released for your role. Nexus Azeo configures each workflow before it becomes available.
- Open the assigned function in the Inama back office.
- Read its purpose, required information and named reviewer.
- If the task is outside its scope, send a request to the programme owner.
The working rule
Staff do not choose AI software, write prompts or connect systems. The function must be approved and released first.
03 / BUILD WHAT PROVES USEFUL
Start small.
Make it work.
Four hypotheses from the supplied decision guide. Confirm the problem, source quality, owner and baseline during the audit. Targets below are proposed acceptance measures, not results.
01 / P1 · LeadershipProposed
Weekly management brief
- Use what we have
- Audit the current meeting pack and time one complete preparation and review cycle.
- Inputs
- Approved KPI, production, stock, commercial reports and action logs, each with owner and date.
- Output
- Performance, changes, exceptions, decisions required and actions with owners and dates.
- Human review
- Executive sponsor. Source owners resolve conflicting figures.
- Pilot test
- Target: preparation time −30%; 95% of actions have an owner and due date; material claims sourced.
02 / P2 · Start with the UKProposed
Export & market cockpit
- Use what we have
- The UK market work and CRM are starting material to reconcile and approve, not a verified live database.
- Inputs
- Market, importer, SKU/vintage, stock, sell-in, depletion, price, listings, pipeline, samples and actions.
- Output
- A weekly market review and proposed CRM changes, with gaps and conflicting account ownership visible.
- Human review
- Export/commercial owner. Reconcile Hallgarten, heritage accounts and Arnaud’s relevant relationships before activity allocation.
- Pilot test
- Target: 95% of opportunities have owner, next action and date; review preparation time −40%.
03 / P3 · ViticultureProposed
Vineyard observation digest
- Use what we have
- Map the observation vocabulary, seasonal calendar and field-to-record process before designing the pilot.
- Inputs
- Approved parcel observations, photos, phenology, weather records and follow-up, with IDs and units.
- Output
- Structured observations and a weekly exception digest. Missing context remains visible.
- Human review
- Viticulture manager. No diagnosis, treatment, dose, harvest decision or work instruction.
- Pilot test
- Target: 90% complete records; digest in under 10 minutes; correct parcel identity and explicit units.
04 / P4 · Winery and cellarProposed
Lot & vessel memory
- Use what we have
- First establish the lot/vessel dictionary, source precedence and representative histories.
- Inputs
- Approved lot, operation, analysis, tasting and vessel/barrel history exports.
- Output
- A read-only lot passport and meeting pack with source dates and visible lineage conflicts.
- Human review
- Winemaker / cellar master. No addition, transfer, blend, vessel instruction, release or official write.
- Pilot test
- Target: reconciled lineage; lookup under 60 seconds; meeting preparation time −30%.
Test before expanding
20–30 evaluation cases per pilot
Include normal work, incomplete records, stale sources, conflicts, duplicate identities, wrong units or dates, unauthorised requests, instructions hidden in documents, unavailable systems and recovery.
Define expected facts, permitted sources, required flags, prohibited actions and the reviewer before running the test.
Keep a weekly review
Record current-process time, assisted preparation, reviewer time, factual accuracy, missing information, identity errors and usefulness.
Stop on an unapproved consequential action, wrong operational identity or hidden unit conversion.
No pilot has been activated through this portal. Approved snapshots come before live connections. Knowledge and communication tasks may become additional platform functions after the same audit and approval process.
PLATFORM DESIGN / NEXUS AZEO
Simple on the surface.
Methodical underneath.
Inama staff work in an Inama back office. Nexus Azeo designs, builds and maintains the processes behind it, with AI available only inside the functions approved for each role.
What staff will see
- My work
Only the functions and records assigned to their role.
- A clear task form
Familiar fields, approved sources, required information and visible gaps.
- A prepared result
Source references, draft status, checks and the next permitted step.
- Review and support
A named reviewer, correction route and a history of the task.
What Nexus Azeo manages
Workflow design, instructions, approved knowledge, field validation, access rules, AI configuration, tests, versions, monitoring and support.
ChatGPT, Codex or a suitable AI service will support this layer behind the interface. Staff will not be sent to a general chat tool.
Operational AI functions not connected
One release process for every function
Nexus Azeo observes the real workflow, sources, decisions, handoffs and current baseline.
Arnaud and the Inama department owner agree the problem, output, limits, reviewer and success measures.
Nexus Azeo builds the task form, source handling, processing and review steps on approved test material.
Run normal, missing, conflicting and unauthorised cases. Resolve failures before staff access.
Enable the specific function for named roles after sign-off and task-based training.
Review usage, failures and value. Nexus Azeo controls changes, retests them and can pause a function.
Responsibilities to encode in the platform
| Role | Allowed work | Release / approval |
|---|---|---|
| Staff member | Run assigned functions, provide evidence, review their draft and report problems. | Cannot create integrations, expand access or change workflow instructions. |
| Department reviewer | Review outputs in their scope, return corrections and confirm operational accuracy. | Technical and business decisions remain with the designated Inama owner. |
| Nexus Azeo | Design, build, test, configure, release and maintain approved functions. | Releases follow agreement with the accountable Inama owner. |
| Inama sponsor | Set priorities, resources, data access boundaries and acceptance criteria. | Approve scope, phase progression and consequential integration decisions. |
Current status. This site presents the implementation programme. The role matrix above is the build specification, not an active staff permission system. Audit forms save records; the operational modules, shared review queues and AI processing are the next build stages after workflow approval.