Every workflow in your company, mapped from recorded work
From what the desktop client records, Subliminal maps your company’s workflows and keeps the evidence behind each one. No interviews and no timesheets.
Subliminal maps how your company runs: its teams, the systems they work in, what they hand each other, and every workflow with the hours it takes and how ready it is to automate.
A company map of teams, systems and hand-offs
Workflows ranked by hours a week and criteria met
Each workflow step by step, with where the time goes
NNorthwind BillingSearch⌘K
Company map
How Northwind Billing works: its teams, the systems they work in and what they hand each other.
Customer support3 workflows · 25% of timeZendeskNetSuiteStripe
Billing4 workflows · 32% of timeNetSuiteBank portalExcel
Accounts payable2 workflows · 21% of timeBill.comNetSuiteGmail
Collections2 workflows · 22% of timeNetSuiteHubSpotGmail
Workflows
Every kind of work Northwind Billing does, found from recorded work. Open one to see how it is done.
11 workflows 232 h a week
WorkflowTeamsPeopleHours a weekCan it be automated?
Match incoming paymentsBilling441.56 of 7
Answer billing questionsCustomer support336.86 of 7
Chase overdue invoicesCollections333.16 of 7
Approve vendor billsAccounts payable329.45 of 7
Send the month’s invoicesBilling222.66 of 7
Resolve invoice disputesBillingCustomer support418.23 of 7
Close the monthBillingAccounts payable414.33 of 7
Set up payment plansCollections211.74 of 7
Issue a refundCustomer support29.65 of 7
Update billing detailsCustomer support37.96 of 7
Pay vendorsAccounts payable26.45 of 7
Company map / Billing / Match incoming payments
Match incoming payments
Build automation
When a payment lands in the bank account, Billing finds the invoice it pays and applies it in NetSuite. Four people, most mornings.
Hours a week
41.5
People
4
Finished examples
1,180
Per payment
2.1 min
Steps 5 steps, as people actually do themShare of time
1Download the day’s bank statementBank portal8%
2Find the invoice each payment is forNetSuiteExcel46%
3Apply the paymentNetSuite24%
4Flag payments with no matchExcel14%
5Post the day’s summarySlack8%
Hours a week last 6 weeks
Can it be automated? 6 of 7
Rule-based decisions
Digital inputs
Enough volume
Stable process
Clear finished state
Systems can be reached
Low risk if wrongA wrong match changes a customer’s balance
Exceptions seen in recorded work
Partial payment14%
No remittance details9%
Combined payment6%
What each workflow page holds
01
How it works
The steps as your team really takes them, each with who does it, the systems used, what comes in and what goes out.
02
Where the time goes
Hours a week, the teams involved, the time one case takes, and the share of time each step takes.
03
Exceptions
The cases that leave the usual path, how often they happen and how your team handles them.
04
Examples
Real past cases of the workflow, each linked to the recording it came from.
05
Can it be automated?
Seven criteria, each with its verdict and the reason, such as whether its decisions follow rules and whether the finished state is clear.
06
Open questions
Where the recordings leave something unclear, the page asks. Your team answers on the page.
02 / 02 Understand
Read it, ask about it, check the recording
The wiki says how each job is done. Ask answers questions about it in plain English. Both point to the recorded work they came from, so anyone can check.
A wiki written from recorded work
Answers with sources you can open
The recording behind any example
NNorthwind BillingSearch⌘K
Match incoming payments
Written from 1,180 recorded examples updated today
HistoryWhat changed
When a payment lands in the bank account, Billing finds the invoice it pays and applies it in NetSuite. Four people, most mornings.
How it is done 5 steps
1Download the day’s bank statementBank portal124 recordings
2Find the invoice each payment is forNetSuiteExcel1,180 recordings
3Apply the paymentNetSuite838 recordings
4Flag payments with no matchExcel342 recordings
5Post the day’s summarySlack119 recordings
Rules
Reference first, then amount and customer within $0.50. 838 recordings
A payment matching more than one invoice goes to the Billing lead. 37 recordings
Exceptions seen in recorded work
Partial payment14%165 recordings
No remittance details9%106 recordings
Combined payment6%71 recordings
Ask the wiki
Ask
Ask anything about how the team works. Answers come from the wiki and recorded work.
New chat
Why do some payments stay unmatched?
Read 1 wiki page Searched 342 recordings
A payment stays unmatched when it does not line up with exactly one open invoice. In recorded work, three cases come up:
Partial payment, 14%. The amount is less than the invoice it names. S1
No remittance details, 9%. The bank line carries no reference to search by. S2
Combined payment, 6%. One payment covers several of a customer’s invoices. S3
Each one is flagged in the Unmatched list instead of being applied.
Sources
Partial paymentS1Billing · Oct 14 · 6 minNo remittance detailsS2Billing · Oct 9 · 4 minCombined paymentS3Billing · Oct 21 · 8 min
Ask about work across your company…
Ask / Why do some payments stay unmatched? / S1
A partial payment from Halden Freight
Full screen
RecordedNetSuite · Customer paymentOct 1409:13:10
Customer payment
INV-20231
InvoiceDueAmount due
INV-2023110/09/20267,400.00
INV-2026410/23/20262,980.00
INV-2029011/06/20265,310.00
To apply 0.00Unapplied 0.00Save
Match incoming payments · Billing · Oct 141:10 / 6:00
Working hours by team and by kind of work, time by workflow, the top automation opportunities, open risks and what changed this week.
Workflows
Every recurring workflow, ranked by the hours it takes and how ready it is to automate, with its place on the company map.
Wiki
How each job is done, the systems, the rules and thresholds, written from recorded work and checked before it is published. Your team comments on any passage, and each page keeps its history.
Ask
Questions in plain English about how work is done, answered with numbered sources that open the wiki page or recording they cite.
Risks
Policy and security risks, knowledge gaps, errors and rework found in recorded work, each with a suggested fix.
Reports
Your own charts, built from a one-line request, over company, team, workflow and application data.
Applications
Every application your company uses, the time that goes into each and how many people use it.
Automations
Each automation’s progress from first build to live, with its tests, its runs and what is waiting for a person.
The same context, inside your AI tools
Connect Claude, ChatGPT or your own agents through Subliminal’s connector for AI tools (an MCP server), and they answer with the context of how your company works.
From recordings to a map of the company
01
Stretches of work
Each recording is cut into stretches of focused work, and each is written up: what was worked on, the steps taken and the outcome.
02
Hours
Stretches add up to working hours by team, by kind of work and by application. Personal time and breaks are left out.
03
Workflows
Work that recurs across people and teams is grouped into workflows and written up step by step, with its exceptions and examples.
04
Map and wiki
Workflows take their place on the company map and the wiki is written, then both are kept up to date as more work is recorded.
What the dashboard shows, and what it never shows
What the dashboard shows
Work, by workflow
Time, steps and exceptions are organized by workflow.
Recordings, opened on the record
Opening a recording asks the viewer to confirm it is to understand the work, and the view is logged before anything loads.
What it never shows
A ranking of employees
There is no score or ranking of people, and the assistant is instructed to decline requests for one.
Personal time and breaks
Stretches recognized as personal time or breaks are left out of the dashboard and scheduled for deletion.
Questions
Process mining and task mining map how work runs. Subliminal maps recurring workflows from real work across applications, without interviews. It then builds automations for those workflows and tests them against work employees already completed, so results can be checked against a known outcome before anyone depends on them.
Interviews describe how people remember a process. Subliminal adds evidence from how work is actually performed, including the steps, applications, and exceptions involved.
First results show within three days: working hours by team and the first workflows, mapped from real work. The picture fills in over the first two weeks.
Yes. Each workflow comes with recorded examples, so your team can open the recording behind a step and review the evidence for the process.
Only the people you make an admin or a dashboard viewer. Everyone else in the workspace only runs the client.
Yes. Claude, ChatGPT and your own agents connect to Subliminal with your sign-in. The same rules apply there: connected tools are instructed to refuse requests to monitor or rank employees, people are shown by short IDs unless you ask otherwise, and every query is logged with its stated purpose before it runs.
Process mining and task mining map how work runs. Subliminal maps recurring workflows from real work across applications, without interviews. It then builds automations for those workflows and tests them against work employees already completed, so results can be checked against a known outcome before anyone depends on them.
Interviews describe how people remember a process. Subliminal adds evidence from how work is actually performed, including the steps, applications, and exceptions involved.
First results show within three days: working hours by team and the first workflows, mapped from real work. The picture fills in over the first two weeks.
Yes. Each workflow comes with recorded examples, so your team can open the recording behind a step and review the evidence for the process.
Only the people you make an admin or a dashboard viewer. Everyone else in the workspace only runs the client.
Yes. Claude, ChatGPT and your own agents connect to Subliminal with your sign-in. The same rules apply there: connected tools are instructed to refuse requests to monitor or rank employees, people are shown by short IDs unless you ask otherwise, and every query is logged with its stated purpose before it runs.