When should you use a workflow map instead of a system list?
Use a workflow map when you want to show where the records for a whole business process live, from first request to final outcome. A system-by-system inventory answers "what tools do you have"; a workflow map answers "where is the evidence of how quote-to-cash, ticket-to-resolution or hire-to-retire actually runs". AI buyers evaluating agents think in workflows, so this view shows breadth that a list of tools hides.
This template is one page, metadata only. It records names of systems, years of history and who can export. It never holds record contents, and partners never fill it in with confidential information. It complements the system-by-system inventory and feeds the data inventory builder, which helps list systems and records.
The template
Copy the block below into a document, one workflow per page. Fill the braces with metadata only.
Add as many step lines as the workflow has.
Which workflows should you map first?
Start with those that cross several systems and end with a clear outcome.
| Workflow | Typical systems along the path | Outcome record to note |
|---|---|---|
| Quote to cash | CRM, CPQ or proposal tool, ERP, billing, collections | Invoice paid, written off or disputed |
| Ticket to resolution | Help desk, chat, knowledge base, engineering tracker | Closed, escalated or reopened |
| Procure to pay | Purchasing, approvals, receiving, accounts payable | Matched and paid, or exception resolved |
| Hire to retire | Applicant tracking, HRIS, payroll, learning system | Hired, separated, reviewed |
| Month-end close | General ledger, reconciliations, workpapers, ticketed requests | Close signed off, adjustments posted |
| Change to release | Issue tracker, code review, CI, deployment tools | Shipped, rolled back or deferred |
The chargeback representment files page and the KYB review files page are examples of narrower workflows with a decision and an outcome, which is the pattern to look for.
How do you fill it in without touching the data?
- Interview the process owner, not the data. Ask what happens at each step and which tool it happens in.
- Write system names, not contents. "Help desk tool" is fine; the text of tickets is not.
- Note years for each step. Where history begins matters for buyers, and gaps matter more than totals.
- Mark the exceptions path. Where approvals, overrides and rework are recorded is often the most valuable part.
- Mark the outcome record. Without it a workflow is a pile of activity.
- Mark rights. Own, client, vendor or unsure. Anything "unsure" goes to the company's counsel, not to you.
- Hand the page to the company's sponsor to complete, review and share with SourceX in the inventory stage.
How do you personalize it for a client?
| Client situation | Adjustment |
|---|---|
| Recently migrated ERP | Add a line for the retired system and whether an export exists |
| Multi-entity group | One page per entity for the same workflow, so rights stay clear |
| Services firm with client work | Add a column marking which steps touch client-owned records |
| Heavy Slack or Teams use | Add a "side-channel" line per step where decisions were discussed |
| Thin documentation | Start with two workflows rather than six |
SlackFor kaizen-style improvement work, the Kaizen and A3 records page shows how a workflow's before-and-after can be captured as a record; the management letter and remediation records page does the same for finance controls.
What never goes on the map?
- Customer, employee or vendor names
- Excerpts from emails, tickets, contracts or code
- Prices, balances or any financial detail
- Passwords, keys or connection strings
- Promises about payment, or any typed reward amounts
If the map begins to contain content, stop and strip it back to metadata.
How does this connect to a referral?
An ERP or CRM consultant is already in the room when processes are mapped. A clear map can show whether the company has the breadth strong candidates tend to show: records across 10-15+ systems and several years of history. It also helps the sponsor answer inventory questions quickly. The referral opportunities for ERP consultants page covers when to raise it, and the company introduction record template is the place to log the introduction itself.
Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards are paid only after the buyer pays and SourceX receives its fee, and no reward is guaranteed. The reward is a share of SourceX's fee and is never deducted from what the company receives. Check your client contracts for disclosure duties and read the program terms.
Follow-up timing
- Day 0: finish the map with the process owner.
- Day 2: send the one-page map to the sponsor with your short note.
- Day 7: if no answer, one reminder; do not chase further.
- After a system change: offer to update the map, since archive status often changes.
Next step
Map one workflow for one client this week, then check it against who qualifies. If the company fits and the sponsor agrees, register as a partner and make the introduction. Also see how exceptions appear in the exception handling guide.