How iyuda works.
iyuda sits inside your actual tools, reads what is happening, and produces the next action: an order update, a reorder follow-up, a campaign, an order correction. Every one of those actions moves through the same mechanism: draft, review, approve, learn.
Four states, one trust model
Every drafted action sits in exactly one of four states. Nothing moves to the next one without a person deciding.
Prepared and ready. Nothing has moved yet.
Waiting on your approval.
Sent, and logged where your team can see it.
Something needs a person before it can continue.
A person decides, every time
iyuda does the work directly, in the systems you already run. But it never sends, posts, or updates anything on its own. Here is what happens between a draft existing and it reaching someone outside your team.
Drafted
iyuda prepares the order update, reorder, campaign, or correction inside the system it already lives in.
Reviewed
It lands in your queue as pending approval, with the full context attached.
Approved & sent
A person approves or edits it. Only then does it reach a customer or a system of record.
Campaign production is manual work that scales with send volume.
For a retail brand with a busy email calendar, each campaign means assembling copy in a design tool, choosing images and products by hand, and checking inventory timing. The work repeats every week and takes hours per email. Reviewer feedback is applied once and forgotten, and testing is rare because there is no time to set it up, so each send starts from the same baseline.
A brief goes in. A reviewed, on-brand draft comes out.
Your plan is the input. iyuda assembles the email, your team reviews it, and nothing goes out without approval.
Calendar and briefs
Your plan is the input.
Draft and product picking
Copy, layout and products assembled for you.
Review
Your team edits and comments on the draft.
Feedback becomes rules
Comments are saved and applied to future drafts.
Pushed to your email platform
As a template draft, unscheduled.
Your team sends
Nothing goes out without approval.
Reviewed drafts
Open a draft, comment in place, and approve it or send it back.
Drafts in your email platform
Approved drafts land in your email platform as unscheduled template drafts.
A/B analytics
Test variants and see what works, so each send stops starting from the same baseline.
Closed-loop learning
This applies to the words themselves, not just the workflow. When your team rewrites a line in an order confirmation or a campaign subject, that edit becomes part of how the next draft gets written.
Draft written
iyuda writes a first version based on what it knows about your business today.
You edit or reject it
Every change you make is a correction, not just an approval.
Next draft reflects it
The correction carries forward, so future drafts read closer to what your team would have written.
One operator, run across the whole business
The queue above does not distinguish between a wholesale reorder, a campaign, or an order fix. They all move through the same draft-review-approve mechanism, across whatever systems they touch.
Wholesale account management
Takes the manual work out of wholesale relationship management: tracks each account's order cadence, surfaces reorders that are due or stalled, and flags anything that needs a person before it reaches a buyer.
Campaign production
Writes and stages campaign copy in the tools you already send from, ready for review before anything goes out.
Order management
Creates orders and accounts, catches mismatches between systems of record, and drafts the correction instead of leaving it for someone to find later.
Quality comes first. Every action is for your team to approve.
Human approval
Every action is drafted first and approved by a person before it is sent.
Audit record
Who approved what, and when. History is reversible.
Scoped access
Reads templates, campaign metrics and catalogue. Writes template drafts and unscheduled campaigns. Never touches user profiles, per-user exports, proof sends or triggers. The limit is enforced in code and the key can be revoked at any time.