Where this goes
Memry stops waiting to be asked.
Today it acts when you ask it to, like every other tool your company owns. The next release changes that: it wakes up, reads the record, works out what actually needs to happen today, and does the boring ninety per cent of it.
None of this page is built. Everything described here is designed and staged; the first section is a ruled decision, the rest is where the architecture points. Every other page on this site describes only what ships today. This one does the opposite, and says so here rather than in small print at the bottom.
The change
Right now it sits there until somebody looks.
That is the honest description of every tool a company owns, this one included. What is designed is a heartbeat: it wakes, reads the record, works out what needs to happen, drafts what it can, and hands you the last ten per cent.
The reason nobody else does this is not that drafting a letter is hard. It is that nothing else has the record to draft it from.
Designed, not built
The chase writes itself — and it knows who to chase.
A promise is held as one party owing another a specific thing by a date. So the system already knows who owes it, who is waiting, what was promised, when, everything said about it since, and what the contract says happens if it is late. Which means it can write the actual email.
Gary — checking in on the floor-three snagging sign-off. You committed to the thirteenth when we spoke on the second of June, and Rachel needs it to release the retention. Are we still on?
Every clause in that sentence comes out of the record, and every one of them is checkable.
It knows when, not just what
The timing is calibrated against your company's own track record. A supplier who historically runs eight days late is chased ten days early. A client who takes a fortnight to approve anything gets the request a fortnight ahead, without anybody doing the arithmetic. And it stops the moment the answer arrives — it will never chase a question that has already been answered.
Escalation follows the same logic
A polite nudge four days out, a firmer one on the day, and when the delay crosses the point where the contract gives you an actual right, it drafts the formal notice, quotes the clause, computes the dates from the notice period, and flags when the window shuts.
It drafts the paperwork, not just the message
A variation agreed in a meeting — the variation order drafts itself, priced from the contract's rates, citing the decision that authorised it. A contract nearing auto-renewal — the notice letter is ready six weeks before the window closes, clause quoted. A supplier's delivery record crossing a threshold — the performance letter is drafted with the real history behind it. Somebody resigns holding eleven open promises — eleven handover emails, drafted to eleven counterparties, naming the new owner. The board meets on Thursday — the pack assembles itself: decided, at risk, unresolved, changed since last time.
None of that is clever. All of it is derivable — as long as something remembers the decision, the clause, the date and the history.
What it does to the working day
The inbox becomes an outbox that gets approved.
Today the inbox is a to-do list maintained in somebody's head, badly, at eleven at night. Open the product in the morning and twelve things are drafted, sequenced and addressed correctly, each quoting the thing that makes it true. Read them. Change two. Send.
A junior issues the same quality of contractual notice as a partner, because the draft came out of the contract rather than out of memory.
And no, it does not get to send things on its own
It arrives in three deliberate steps. First it can only read and digest — it notices, and is not permitted to file anything at all. Then it can draft, and drafting is proposing: it writes, a human approves, nothing leaves the building unsent. Only then, and only switched on deliberately, does it file overnight — and even then it owes you a morning summary: what it did, why, and the undo.
Does this need an expensive AI subscription?
Less than you would expect, because the design splits in two. The noticing is deterministic — an overdue promise, an expiring certificate, a missed threshold, a decision short a signature. That is the record and a rule, and no model is involved. Only writing the prose needs one. An account with no key still gets a product that notices everything; what it loses is the drafted paragraph, replaced by an explicit “draft this” button.
A year from now
Four ordinary days.
Nothing below needs anything beyond what is described above. Same company you can open in the demo today, and the same people.
Tuesday, 07:50 — the site manager
Gary is the man the system chases. It matters that he does not experience it that way.
He opens Memry in the site cabin before the gates open. Two things want him. The first is the snagging sign-off he owes the finance director — and it is not a red badge and a guilt trip. It is a drafted reply, already written, quoting what he committed to and why she needs it, with a one-line note that the retention release depends on it. He did not know that. Nobody had told him. He amends one sentence and sends it in nine seconds.
The second is yesterday's site report, which he dictated walking back to his van. Memry has read it and pulled out four things: a delivery slipped, a variation was discussed with the client's engineer, one subcontractor finished early, and a temporary works certificate expires in five weeks. It has made no changes. It has proposed four, each quoting the sentence he actually said.
He approves three and declines one — the variation was floated, not agreed, and he says so. That decline is now part of the record too.
Eleven minutes, and the entire administrative residue of his previous day is filed, accurate, and attached to the right project. He has not opened a spreadsheet, written a status update, or remembered anything. He goes and builds a building.
Thursday, month-end — the finance director
Month-end used to take Rachel four days, and two of them were spent asking people questions they had already answered somewhere.
This month she opens one screen. The payment applications have assembled themselves out of the commitments that were actually delivered — not out of what anybody claimed. Where a claim and a delivery disagree, the disagreement is on the screen with both sources, rather than discovered in six weeks by a quantity surveyor with a highlighter.
One invoice is flagged. Not as “over budget” — as twenty-four thousand pounds over the decision that authorised the spend, with that decision open beside it, its reasoning intact, and the name of the person who approved it. She does not need to reconstruct the story. The story is the record.
The penalty notice is drafted and waiting: the clause quoted, the dates computed from the delivery history, and a line telling her the contractual window closes on the fourteenth. Legal will approve it in a morning instead of researching it for a week.
She finishes month-end before lunch on the second day. The two days she gets back are the two she used to spend chasing.
Wednesday — operations and people
Nadia's week contains the thing every operations manager dreads: a good project engineer resigned on Monday.
In the old world this is three weeks of quiet damage — the things he was carrying that nobody knew about, surfacing one crisis at a time for a year. Here it is a screen. Eleven open promises, each with a counterparty, a date and the conversation that created it. She assigns them in an afternoon, and eleven handover emails go out that evening, drafted, each naming the new owner and quoting the original commitment so nobody on the other end has to ask what this is about.
The same morning she onboards his replacement. There is no forty-page induction pack, because the induction is a conversation with the company's memory. Why do we use this supplier rather than the cheaper one? — answered by the decision that settled it two years ago, reasoning attached, with the tender comparison behind it. The new engineer is asking the company questions and getting the company's actual answers, on day one, without occupying a single senior person's afternoon.
And in the background, quietly: three certificates renewed before they lapsed, two contracts flagged before their notice windows closed, and a supplier insurance document chased and filed without her touching any of it.
Nothing dropped, on the worst week of her quarter.
Friday, 16:00 — the managing director
There is no status meeting any more. There has not been one for months, and nobody has asked for it back.
The board pack for Tuesday assembled itself this morning: what was decided since the last meeting, what is at risk, what is unresolved, what changed and why. She reads it, changes the emphasis in two places, and files it. It took twenty minutes. It used to take four people two days, and it was always slightly wrong by the time it was read.
Then she does the thing she could never do before. She asks a question — are we exposed on this supplier? — and gets an answer with receipts: the decision to retain them, the delivery record that argued against it, the penalty invoked, the variation currently in dispute, and the exact sentence in the contract each of those rests on. Not a summary. Not somebody's recollection. The record, with its sources, in four seconds.
She is not managing by asking people how things are going. She is managing by knowing.
The test that actually matters
Imagine the week it gets switched off.
Monday, nobody knows what was agreed with the client's engineer on site. Tuesday, an invoice is paid that nobody notices is over the decision that authorised it. Wednesday, a notice window closes and the right to recover twenty-four thousand pounds quietly expires. Thursday, the leaver's fourth forgotten promise surfaces as somebody else's emergency. Friday, four people spend two days assembling a board pack that will be out of date before it is read.
None of that is dramatic. That is exactly the point — it is the ordinary, invisible, expensive friction that every company treats as the cost of existing.
A tool you would notice losing is a good product. A tool whose absence you would feel in every department by Wednesday is infrastructure.
And then there is what comes after that
Soon, most of the work in your company will be done by something that isn't a person.
That is not a prediction anybody seriously argues with any more. Here is the part nobody has an answer for: those things will be agreeing to things on your behalf. Ordering materials. Accepting a delivery date. Confirming a price. Saying yes to a variation.
And right now, nothing checks any of it. An AI assistant works off a key that either lets it act or doesn't. There is no record of what it changed, no way to prove what it was stopped from doing, and no answer at all to the question a director will eventually have to answer out loud: who agreed to this, and were they allowed to?
Memry already knows what your company has promised — every commitment, every date, every price, every clause, and who signed it off. So it can do the one thing nothing else can: refuse.
Give an assistant a limit — this much, on these things, with these suppliers, until this date — and it works inside it. Ask it to agree something that contradicts what you have already agreed, and it does not get to. The attempt is written down, the reason is written down, and it goes to the person entitled to decide. That is not a setting. It is how the product already works, for people, today.
Anyone can say yes on your behalf. Almost nothing can say no.
And when the company on the other side of the deal is running the same thing, the two sides stop having different versions of what was agreed. Both signed it. Both have a copy. Neither can quietly change it. Which is roughly what happened to money once banks agreed how to settle it — and has still never happened to promises.
Underneath all of it
Companies forget. They forget why. They forget who promised. They forget what the contract said. They forget the expensive lesson from the last project — usually about eight months after the person who learned it walks out of the door. And everybody who works there spends a real part of their life doing archaeology, or re-supplying a status they already gave, or carrying the blame for a decision somebody else made and nobody wrote down.
A company that remembers properly is faster, cheaper and better governed. It is also a much better place to work.
And that is not the soft argument. It is the whole one.
Meanwhile
The part that exists is worth an afternoon.
Everything above is where this is going. What ships today is a whole company tool on a record that will not quietly change underneath you — and you can be inside it, on a real company, without an account.
Explore the demo → No account needed. About ninety seconds to see the point.