What a person sees
The surface is three things and the rest stays underneath; why the simplest interface is the product.
Most software that runs agents shows you the agents. It shows the steps, the model, the tokens, the prompts, and a graph of what called what. That is the right view for the person who built it and the wrong view for the person who runs a business.
Three things
A person using an Igata deployment sees three things.
What needs them: a reminder to approve, a question to answer, two records that look like the same customer. What is running: the work in progress, as plain cards, each with its cost in credits. What it cost: the credits left on the plan and what each piece of work took.
Everything else exists and is never shown unless opened. The agents, the steps, the models and the prompts are there, doing the work, and a business owner has no reason to look at them. The only technical noun a customer ever meets is credits.
One name
Each brand has one named persona, the supervisor, and it is the only agent a customer meets by name. On the Noura deployment it is Noura. The specialists behind it, for marketing, sales, operations, research and engineering, are named in the code by their function and never on a screen.
A person approves what Noura drafted. A person answers what Noura asked. Nobody approves what marketing-agent drafted, because that is the system's word for the row and not the customer's word for the thing.
Simpler never means weaker
A page only hides what the function would refuse. A simpler surface never weakens who may approve what, because the gate lives in the runner and the outbox and not in the page. Nothing leaves a workspace in the customer's name without a person's yes or a standing rule the customer set, and every send records who or what authorised it.
The product never asks for a choice when only one is valid. Recovery belongs to the runtime: one automatic retry, then an incident for the market company's staff, so a person only ever sees questions that are real business decisions.
Why this is the product
The orchestration underneath is table stakes. What a business with no technical staff will pay for is the part they can see, understand and trust in the first minute. Every screen in every deployment is held to that: plain words, the customer's nouns, and nothing that needs a manual.
The next step is the walking skeleton: one workflow, end to end, that chases an overdue invoice, asks the owner before it sends, and shows what it cost.