Viictor as an Assistant · VaaA
Describe how you trade. It builds the control tower.
The Assistant is the setup role inside the Orchestrator. It turns the way you already talk about your operation into a working configuration — your organisation, your supply chain, the checkpoints that watch each trade lane and the data sources that feed them — staged for your approval before a single thing goes live.
Built by the team whose software runs live customs operations every working day.
Watch a sentence become a live setup.
A trade manager describes a new lane in the words they'd use to a colleague. The Assistant turns it into a configuration you can read — the data it will draw on, the services it will call, the checks it will run — and then stops and waits. Nothing is live until it is reviewed and activated. What you're watching is one lane; the same conversation stands up as many as you trade. Illustrative, with sample data.
Viictor as an Assistant
We’re adding a lane — wiring harnesses from Morocco into Genk. Can you set it up?
Gladly. Let me see what I already hold for that lane.
Reading your organisation and supply chain… Most of it is already here, John — the plant, the product and the regime.
Two things only you can tell me: who the supplier is, and whether they hold approved-exporter status.
Atlas Wiring Systems, Casablanca. Yes — approved exporter.
That settles the origin route. I need one new data source for their certificates, then I’ll draft the lane around it. Nothing touches your live systems until you activate it.
Add the data source → The lane is live. The Operator has it from here — and if what actually happens starts to differ from this plan, I’ll come back to you with what needs tightening.
Viictor as an Operator · now watching MA → BE →You describe the lane, it drafts the whole thing — and nothing goes live until you say so.
Compliance platforms don’t fail at go-live. They fail at configuration.
Not because the software is weak — because setting it up asks you to translate what you know into someone else’s data model, and almost nobody can do both halves.
What you know
- We make car parts in Genk and import trim from Türkiye.
- The A.TR covers most of it; the rest is normal third-country.
- Our supplier data lives in SAP, our shipments in the TMS.
- Nothing ships until Anne has signed off the classification.
What the software asks for
- Define an entity type and its cardinality.
- Map source field 47 to the target schema.
- Select a rule template and bind its parameters.
- Raise a change request with IT for the interface.
The gap between those two columns is what consultants get paid to cross, and it is where budgets and timelines go. The Assistant crosses it for you — you stay on the left-hand side, in your own language, and it does the translating.
Four things it stands up for you.
A control tower isn’t one setting — it’s a model of how your business trades. The Assistant builds all four parts of it, and keeps them consistent with each other as you grow.
Your organisation
Who you are in customs terms — legal entities, sites, authorisations, the regimes you operate under and the jurisdictions you answer to. The frame everything else hangs on.
Your supply chain
The parties you trade with and the goods you move — suppliers, carriers, forwarders, customs authorities, products and their classifications. Not a generic model: yours.
The checkpoints that watch it
Where in each trade lane compliance has to be proven, what has to be true at that moment, and what should happen when it isn’t. This is the part a consultant usually charges for.
The data that feeds it
Acquisition points onto the systems you already run — ERP, TMS, CRM, SRM, government portals — pulling master data on a schedule so your compliance picture stays current without anyone rekeying it.
It proposes. You decide. Always.
An assistant that could quietly reconfigure your compliance would be a liability, however clever it was. So it can’t. Every change the Assistant makes is staged against your live setup, checked against your own rules while it is still a draft, and shown to you in full — what it will read, what it will call, what it will enforce — before anything is switched on.
You review it, you activate it, and it is recorded that you did. Which is also what makes it auditable: the setup has an author and a moment, not a mystery.
- 1 Drafted The Assistant works out what your description implies, and writes it down.
- 2 Checked The draft is tested against your own rules — before it is real, not after.
- 3 Shown You see the whole thing in plain language, not a diff of a config file.
- 4 Activated Only on your word. And the Operator starts running it from that moment.
What changes about setting it up.
Six moments in the life of a configuration, and what each one costs depending on who is doing the translating.
| The moment | Forms, tickets and projects | With the Assistant |
|---|---|---|
| A new trade lane opens | A change request, a specification, a slot in someone’s sprint. Weeks before the first shipment is covered. | You describe the lane. Viictor drafts it from what it already knows about your operation, and you review it the same afternoon. |
| Connecting your ERP | An integration project: field mapping workshops, a spec document, a developer at each end, a test cycle. | An acquisition point onto the system you already run, scheduled, with the master data flowing in and visible. |
| A rule needs tightening | Raise a ticket. Wait. Explain the customs reasoning to someone who doesn’t have it. | Say what should change. It is staged against your live setup and shown to you before it applies. |
| You don’t know the answer yet | The form demands a value anyway, so someone guesses — and the guess is load-bearing for years. | Start deliberately loose and tighten as reality teaches you. The setup is meant to move. |
| Something would be wrong | You find out in production, on a real shipment, with the goods already moving. | It is checked against your own rules while it is still a draft — before anything is switched on. |
| The setup drifts from reality | Nobody notices until an audit, because nothing is comparing the two. | The Operator reports what actually keeps happening, and the Assistant turns that into a refinement. |
Who feels the difference.
Setup stops being the part of the project everyone dreads.
Customs & trade managers
The people who know how the business really trades. For the first time, the setup is theirs to shape directly — no translating their expertise into a specification for someone else to misread.
Teams without an IT queue
Mid-sized operations that could never justify a six-month configuration project. The thing that used to require consultants becomes a conversation.
Whoever signs it off
Nothing reaches production unreviewed. Every change is staged, checked and shown in full before it applies — so approving it is a decision, not a leap of faith.
One of two roles inside the Orchestrator.
The Assistant sets your control tower up; the Operator runs it live — and feeds what it learns back into the setup, so it keeps getting sharper. Advise with the Consultant, configure with the Assistant, run with the Operator: one colleague, three modes.
The Assistant · VaaA
Sets it up — you’re here.
Turns how you actually trade into a working control tower — organisation, supply chain, checkpoints, data sources — staged for your review before anything goes live.
The Operator · VaaO
Runs it.
Watches every transaction against that setup, acts on what it can, escalates what it can’t, and tells the Assistant what needs refining.
See the OperatorSee it build your control tower.
Describe one lane out loud. That’s the whole demo — and it’s the fastest way to see whether this is real.