Comparison
Memtro vs the model alone
The same questions to the same model, with and without memory and tools in front of it.
The examples on this page are illustrative: realistic exchanges with the names changed, showing the shape of the difference rather than quoting a customer's data. Run the same questions on your own workspace to see the real thing.
The model is the same in both columns. The difference is what sits in front of it: with Memtro, retrieved memory, read-only tools over your systems, and an agent loop that cross-references before it answers.
"What do I need to know for my 3pm with BigCo?"
| With Memtro | Model only |
|---|---|
| BigCo renewed for £40k on 2 October (owner Priya Sharma). There is an open Help Scout ticket, #2450, about a duplicate charge on order 4411: the warehouse shows two payment captures and Xero a duplicate paid invoice, INV-2202, not yet refunded. Sam Lee emailed on Tuesday asking for a timeline. Lead with the refund. Sources: help scout #2450, hubspot, warehouse.payments, xero INV-2202, gmail. | I don't have access to your CRM or ticketing system, but here is a general checklist for a customer meeting: review the account history, check for open support issues, confirm the renewal date, and prepare questions about their goals for the coming quarter. |
"Have a look at Help Scout ticket #2450"
| With Memtro | Model only |
|---|---|
| Sam was charged twice for order 4411: two payment captures a minute apart, one shipment, and Xero shows a duplicate paid invoice (INV-2202). Refund INV-2202 and reply on the ticket. BigCo is a £40k account owned by Priya, so flag it to her. Systems consulted: Help Scout (ticket), HubSpot (account, owner), warehouse (orders, payments, shipments), Xero (invoices), Gmail (nothing new). | I can't open Help Scout tickets. If you paste the conversation I can help you draft a reply. |
"Who owns the billing migration?"
| With Memtro | Model only |
|---|---|
| Priya Sharma owns the billing migration. It launches on 14 November; Linear shows 14 of 19 issues closed and nothing blocked. Sources: memory (decision, 2 Oct), slack #payments, linear BIL. | I don't have information about your organisation's projects. Typically a billing migration would be owned by a payments or platform team lead. |
What makes the difference
- Retrieval before the model sees the question. Relevant memories and the graph neighbourhood are injected, so names, decisions and dates are already there.
- Tools, not pasted context. The model calls Help Scout, HubSpot, the warehouse and Xero itself, and the results are cached briefly so agent loops stay cheap.
- Cross-referencing by default. A question about one record is treated as a request for the full picture.
- It gets better. Everything the agent looked up is anchored into memory with provenance, so the next person asking about BigCo starts further along.