Most of how a company runs is written down nowhere. myvue understands how work actually gets done, writes it down, and keeps it current. When someone asks a hard question about the business, you can answer it and show your working.
Four pieces of work stop. Invoice matching, premium finance follow-ups, carrier statement downloads and reconciling direct-bill commissions have only ever been done by Marcus in the last 90 days. Together they take about 19 hours a month.
Two of the four have a written procedure, drawn from the way he actually does them, so a colleague could step in. Invoice matching is the one to cover first.
Issuing a certificate of insurance. Across 19 recent runs it was done three ways: from the carrier portal in about 12 minutes, from the agency system in 19, and by email template in 26. The most common way is not the fastest.
Pick the way everyone should use and myvue writes it up as the standard, then tells you when a run strays from it.
Not quite. The procedure written in 2023 has four steps. The work has five. The step people actually do, flagging any refund over $200 before approving it, is not in the document.
myvue has written the procedure as it is really done. Set it as the official one and it stays current on its own.
Commission reconciliation. It ran nine times this month at about 48 minutes each, 12 minutes slower than in August. The slow part is re-typing carrier lines by hand before matching them, roughly 10 minutes a run. One person does all of it.
That one step is the first thing worth handing to software. The rest of the job is fine as it is.
Harbor Point Insurance, a demonstration company. Every sentence above was written from real runs of the work, and every claim traces back to one. If the work holds no evidence for a question, myvue says so.
The departments and processes below are the kind myvue finds. Each one was written down from the work itself, not from an org chart.
Certificates issued three ways, commission reconciliation on one person, a workaround nobody wrote down.
Dispatch scheduling slowing week by week, and the step where the minutes go.
Month-end close as it is really run, the same way by everyone, written down for the next hire.
Two loan processes resting on a person who gave notice, and the documents ready to hand over.
Owner reporting that used to take a day, found at the step level and handed to a workflow.
Insurance claims and recalls, written down from real days, in the form the auditor asks for.
Lightweight software runs on the computers where work happens and understands how people use their tools: which ones, in which order, for how long. Work that repeats the same way, found at least three times, is proposed as a process. A person confirms it. Screen video is never stored.
Found on 11 mornings in the last 30 days, by Priya, Beth and Tom, about 26 minutes each time.
The record suggests, you confirm. Nothing counts until a person who does the work says yes.
myvue keeps one honest figure: how many of your processes are written down, confirmed by someone who does the work, and current. A process nobody has confirmed in 28 days is aging. At 42 it drops out of the figure. Confirm it again and it comes back, at no penalty. Drag the days.
70 to 80% of how a company runs is written down nowhere. Ask three people how the same job gets done and you get three answers. Every confirmed process gets a document drawn from the steps people really take, with the systems used at each step, and it refreshes as the work changes. Drag across to compare.
Drag across. Left is what people remember; right is what the record holds.
The last confirmation is 63 days old. Carrier statements keep arriving, and a workaround is being worn around the blockage.
Every claim traced to a moment of real work · rests on 2 processes · print, save as PDF, publish
Ask a question once and myvue keeps answering it on the cadence you set, and tells you when the answer changes. When it matters, write it up as an Extract: a short briefing where every line can be shown. It is the page you hand to a partner, a board or an auditor.
Point Claude, ChatGPT, Microsoft Copilot, Gemini or Grok at your record. Before an assistant does a piece of work, it asks how the work is actually done here. When it finishes, it files what it did. Assistants get summaries and totals only. The work behind them never leaves myvue.
This is the whole idea, with nothing to learn. Three people do a piece of work. myvue notices it is the same piece of work. One of them says yes. From then on it is written down, and it stays current.
The same three steps, in the same order, 11 times in 30 days, by 3 people, about 26 minutes each.
Work that repeats the same way, found at least three times, is proposed. A person who does it confirms it.
The document a new hire, a board or an auditor asks for, written from real work. Nobody interviewed anyone.
myvue never reports on individuals. It draws the organization as one object: people, departments, tools and time.
It will not read your documents or your email. Which tools, in which order, for how long.
Each screen is understood in the moment, turned into notes about the work, and thrown away.
The record suggests, you confirm. Nothing counts and no process moves a stage until someone says so.
Run every engagement from one book. Each client has its own record; you read across all of them. Clients never see each other’s numbers, and you never put more people on the engagement to know more.
Work with clear steps that repeats the same way each time, found at least three times. One-off tasks never count. You confirm every process before it enters the count.
Blocked apps, paused time, personal activity. Screen video is never stored.
Discovery starts the first day. Most teams confirm their first processes inside two weeks. The record deepens on its own from there.
It stops counting. A process unconfirmed for 28 days is aging. At 42 days it is stale and out of the count. Confirm it again and it comes back, at no penalty.
Every process gets a grade, P1 through P5, on five public measures: drift from the document, how many people can run it, how much versions differ, how fresh the record is, and how much it matters. The full criteria.
No. It understands the shape of work: which tools, in which order, for how long. It never reports on individuals, and nothing changes without a person confirming it.
A walkthrough of a live record, on a demonstration company, in thirty minutes.