It keeps coming back
Someone repeats it every day, every week or whenever the same kind of request arrives.
Recorded product run
PDF DDI Sheet Email
This is a recorded Memric run using demo data in our own environment modeled on DDI. Repetitive data entry was sped up; no actions were removed.
See the run step by step
The recording is silent. These steps describe what Memric does on screen.
- 1A user attaches a two-product PDF and asks Memric to add the first product to DDI, create a catalog sheet and email the product details to Riccardo.
- 2Memric opens DDI on its Windows desktop and signs in.
- 3It opens Product Inquiry, starts a new product record and enters the product details from the PDF.
- 4It creates the CHM-FLR-1G record in DDI.
- 5Before creating a Google Sheet called “new catalog,” Memric asks for approval.
- 6After approval, it creates the sheet and asks again before adding the product details.
- 7After the second approval, it fills the sheet, shows the result and prepares an email to Riccardo.
- 8Memric asks one final time before sending. After approval, it sends the email and reports that the task is complete.
Where Memric fits
Choose a task your team knows by heart.
A good first task is frequent, predictable and easy for a person to review.
The path is familiar
The same kind of input moves through the same screens, with exceptions your team can name.
Easy to check
Your team can tell whether the result is right before it is accepted or sent.
How a pilot works
We start with the person who does the work.
We agree on the scope and timeline once we understand how the task works today.
Watch the task
The person who handles the task shows us the normal steps and the cases that need judgment.
Agree on the limits
Together, we decide which accounts Memric can use, what it can do and where it must stop for approval.
Review every run
Your team checks the result and the record of each run before we expand the pilot.
A few questions before we start.
Does Memric replace our current software?
No. Memric uses its own Windows computer to work through the interface your team already uses. A first pilot is built around one task inside that system.
Why not use an API instead?
Sometimes that is the better answer. If a reliable API covers the whole task, we’ll say so. Memric is for work that still requires someone to use the interface.
Where does Memric run, and what can it access?
Memric runs on its own remote Windows computer. Before a pilot, we agree on the accounts, applications and data it may use.
What happens when Memric needs a person?
We set the approval points before the pilot. At those points, Memric stops and waits. For every run, it keeps an action record and screenshots so your team can review what happened.