Process design documents as a fit signal: how automation consultants can introduce clients

Why are process design documents a fit signal for automation consultants?

If you write process design documents (PDDs), exception catalogs and as-is maps for clients, you already know which of them have years of documented, step-by-step workflows. That is the kind of record AI buyers describe wanting for agent training, and it makes automation consultants well placed to introduce a client to SourceX. Documents you wrote under a client statement of work are generally the client's to license, not yours, depending on the contract.

An automation engagement leaves a trail: discovery workshops, as-is process maps, PDDs, exception handling rules, test evidence, runbooks and bot logs. A client that keeps that trail organized has something more useful than a client with only raw system exports.

This page is for consultants at automation and intelligent-process firms, including partners in RPA vendor ecosystems. It does not suggest any vendor endorses the arrangement.

Which clients look strongest?

Insurers, business process outsourcers (BPOs), shared-service centers, finance operations teams and healthcare administration groups (non-PHI) often run documented, repetitive work.

Process mining outputs and orchestration logs can add value if the client owns them and personal data is removed, but that is a rights and privacy question for the client.

Who owns the documents you wrote?

Ownership depends on your contract. Under the Copyright Act, a work made for hire can be one prepared by an employee within the scope of employment, or a specially commissioned work in a listed category where the parties agree in a signed writing; see the Copyright Office's Circular 30 on works made for hire. Copyright otherwise vests in the author, and ownership can be transferred or licensed in part, as set out in 17 U.S.C. 201. Many SOWs assign deliverables to the client, but your own templates and know-how may be retained by your firm.

In practice, check three layers:

• Deliverables written for the client: typically the client's to license, if your SOW assigns them.
• Your reusable templates and methods: yours, but they are not part of an introduction.
• Client records you touched: the client's data, often containing personal information.

This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

The 4-document screen

Before you suggest a conversation, ask yourself whether the client can point to all four.

• As-is map or workflow inventory covering at least one department
• PDD or SOP with enough step detail for a new analyst to run the process
• Exception log with outcomes
• Owner inside the client who maintains these documents today

If all four exist, the client likely clears the Records and Readiness parts of a standard screen. Rights and reach still need confirming.

When to raise it

How does the introduction work?

1. Confirm your SOW and any partner agreement allow referrals, and tell the client about the reward.
2. Register as a partner and share your referral link, or submit basic fit information with the referral form.
3. SourceX qualifies size, history, breadth and rights.
4. The client completes its own data inventory. You do not export or describe documents.
5. Price and terms are agreed before buyers review.
6. After an executed agreement and the client's authorization, delivery follows under agreed redaction rules.

What to say to a client sponsor

Common mistakes

Illustrative: a fictional regional insurer's claims-intake team has a three-year-old PDD set, an exception log and a named process owner. The consultant raises the idea at handover and offers an introduction, nothing more.

How rewards work for a consultant

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 cumulative per referred company. The reward is payable only after the buyer pays and SourceX receives its fee; a lead, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. The reward is never deducted from what the client receives. Check your firm's conflict and disclosure rules. Details are on the rewards page.

When it is not worth raising

A short rule helps: if the client could not hand a new analyst the document and have them run the process, the documentation is not yet a signal. Revisit after the next engagement phase.

Skip clients with fewer than 50 full-time employees at peak, with documents that sit mostly under another party's SOW, with records dominated by consumer data or PHI, or with no one who can export. Also skip a client whose process documentation is thin or recent. Network design consultants face a similar discipline with shipment data; see supply chain network design consultants. A quick preliminary check is available with the company fit checker; read who qualifies for the full baseline.

Next step

Pick one client with a clean documentation set, check your SOW, and register as a partner. The client can also apply directly at sourcex.si/apply using your referral link.