Ruth has run the close for twenty-two years. She tells you at ten past nine on a Monday, kindly, with six weeks left. This is what those six weeks look like with Kept. Every name and every line of it is example material.
Prototype with synthetic material. No live workspace, customer content or input collection.
01 / The Monday
Six weeks.
You thank her. You mean it. Then you close the door and think about the close. Not the checklist, which is fine, but the part of it that lives in Ruth: the step everyone skips until April, the vendor she calls before anyone else, the one exception at quarter-end that nobody has ever written down.
Synthetic transcript · Controller (fictional) · The Monday
“I've been meaning to write it all down. There's a lot of it. I'm not sure where I'd start.”
This story is available entirely as text.
02 / What walks out
The list nobody wrote.
A procedure says what to do. Twenty-two years of judgment says when the procedure is wrong. Here is a fraction of what would leave with Ruth, and the reason each item never made it into the binder.
Illustrative list · What only Ruth knows
The close, as it is actually run
Why step four matters even though the close balances without it.
Which vendor to call first when a charge is disputed, and why it is never the one on the contract.
The quarter-end exception for the euro account, and who agreed to it.
The bank sweep that posts a day late on the last day of the month.
Who covers the sweep when she is out, and how to reach them.
Why it was never written down: every item felt too obvious to Ruth to be worth a page.
03 / What now
A conversation, not a binder.
The old answer was a documentation sprint in the last week: forty pages nobody reads, missing everything that felt obvious. The new answer is that Ruth talks and Kept keeps. She turns capture on herself, on the Tuesday, and June asks her about a close that went wrong.
June
Walk me through a close that went wrong. What did you catch, and how?
Ruth, Controller
The one where the bank sweep posted a day late. I always check the sweep before I trust the cash line, because the feed lags on the last day of the month. If you don't, the line reads low and you chase a shortfall that isn't there.
Capture is on, by Ruth's own choice, and she can turn it off at any time.
Twenty minutes, between real work. Not an exit interview.
04 / Weeks two to five
Kept, in her words.
Half an hour here, twenty minutes there. Each conversation becomes pieces of knowledge with the trigger, the response and the reason, shown to Ruth before they count. By week five the list from chapter two is no longer only in her head.
Synthetic knowledge item · FinanceReviewed by the partner
Cash line on the last day of the month
Trigger
Closing on the last business day of the month.
Response
Check that the bank sweep has posted before trusting the cash line.
Reason
The bank feed lags a day at month-end, so the line reads low until the sweep lands.
Example review: checked against the source. Ruth added who covers the sweep when she is out.
Nothing is kept that Ruth has not read. She fixes a date, deletes a guess June made, and adds the name of the person who covers the sweep. Work captured for a business workspace stays with the workspace when she goes, with every source intact.
“Step four is the one that matters. Skip it and the close still balances. You find out in April.”
About source availability
Keeping a knowledge item does not promise permanent access to its original transcript. Sources can become unavailable after retention or removal. Check what evidence is available before relying on an answer.
06 / Three months later
“Why do we check the sweep before the cash line?”
Ruth's replacement, six weeks in, asks the workspace. The answer comes from what Ruth said, and it cites the day she said it. And when the question is one Ruth never answered, Kept says so instead of guessing.
The new controller
Why do we check the sweep before the cash line?
Kept
Check that the bank sweep has posted before trusting the cash line. Ruth's reason: the feed lags a day at month-end, so the line reads low until the sweep lands. Dana covers the sweep when the controller is out.
No cutoff for the euro account is in what Ruth kept. I can't establish the answer.
Ask the treasury lead, and keep the answer once it is known.
Every answer cites the conversation it came from. AI can make mistakes: open the source and decide.
Two questions people ask at this point.
Is the information safe?
Capture is opt-in, and each partner reads what was kept before it counts. What a workspace keeps follows that workspace's permissions, enforced in the database on every row, never by an AI model. It is encrypted in transit and at rest, never used to train a model, and a session transcript cannot be edited or deleted once recorded. Single sign-on, two-factor and an exportable audit ledger are part of the business plan. What is live, in progress and planned.
Does it bolt on to what we already run?
Kept runs beside your systems, not inside them. There is nothing to install in your stack and nothing it needs from your ledger, CRM or ticketing tool to work: your people talk to June in the browser or the companion window, sign in through your identity provider, and add the documents that matter. What it keeps stays yours: every answer cites its source, the workspace audit ledger exports as JSON or CSV, and each person can download a complete copy of their own record. How the systems you already use fit in.