The Vendor Coordination System Your EA Should Own (But Probably Doesn't)

I spent six hours in a single week emailing one vendor.

Not negotiating. Not reviewing deliverables. Six hours of: "Did the shipment go out?" "When can we expect the invoice?" "Can you resend the W-9?" Six hours of back-and-forth that required no specialized knowledge, no strategic judgment, and nothing specific to me at all.

I did it because no one else was doing it.

That is the real problem with vendor coordination. It looks like relationship management, so founders keep it. It is not relationship management. It is administration. The difference matters because it determines who should be doing it.

What vendor coordination actually is

Most founders think of vendor relationships as something personal. You negotiated the deal. You know the contact. You want to stay close.

That instinct is right for some things. Renegotiating terms? You should be in that conversation. A vendor relationship that is deteriorating? Your call to make. Deciding whether to renew or replace a supplier? Your judgment.

Those conversations happen two or three times a year per vendor.

Everything else is coordination. Status checks. Document requests. Invoice approvals. Deadline confirmations. Scheduling review calls. Sending reminders when something is late. None of that requires you.

A founder running a company with ten active vendors is spending roughly 4 to 8 hours per week on coordination tasks that any competent person could handle. At a founder rate of $150 to $300 per hour, that is $31,000 to $125,000 of your time per year going to status checks and follow-up emails.

Here is why it stays with the founder anyway: it lives in the inbox.

Vendor emails look like other important emails. They show up in the same thread as client conversations, partnership discussions, and team requests. When you are processing email yourself, you just handle them. A few minutes here, a few minutes there. You move on without realizing you have done it again.

Because each interaction feels small, you never stop to think of vendor coordination as a category of work you could remove from your life entirely. And even founders who hand off email triage often stay in vendor threads without thinking about it. The EA flags them and brings them back to you because no one told her she could own them.

The three-piece system

Getting vendor coordination off your plate requires three things: a vendor list, a communication standard, and explicit permission. No new software. No complex workflow tool. Three documents and a conversation.

The vendor list

Start with a document that captures every active vendor and the details your EA needs to interact with them. This is not a database. It is a reference doc she can open whenever something comes up.

For each vendor, include the contact name and email, what they do for your company, payment terms, where invoices go and who approves them, current open items or ongoing deliverables, and relationship notes.

The relationship notes column is the one founders skip. It is the most important one.

Your EA does not know that one vendor has been late on three consecutive deliverables and you are watching them closely. She does not know that another has been with you since 2019 and you would go out of your way to protect that relationship. She will treat all vendors identically unless you tell her otherwise.

Twenty minutes of notes per vendor changes that completely. You write it once. She uses it every time.

The communication standard

Once your EA has the vendor list, she needs to know what "good" looks like when she interacts with vendors on your behalf.

Write this out in one page or less. Example:

"For status check emails, keep them short and direct. One question per email when possible. Do not escalate tone unless something is 48 hours overdue. If a vendor misses a deadline, send one friendly reminder. If they miss it again, flag it to me before taking any further action."

That covers 90% of vendor interactions. Your EA knows when to handle something herself and when to bring it to you.

The second part: whose name goes on the emails. If she sends from your address, this is automatic. If she sends from her own address on your behalf, decide upfront whether vendor emails should be signed in your name or hers. Most founders prefer their name for continuity. Either works as long as you decide before she starts.

Explicit permission

This is the piece most founders forget.

Your EA will not take over vendor coordination unless you tell her to. She has been flagging vendor threads and routing them back to you because that is the behavior you modeled. Changing it requires a direct instruction: "From this point forward, you own all vendor coordination. I should not appear in these threads unless you escalate something to me."

That sentence sounds obvious. Founders routinely skip it and then wonder why vendor emails keep landing in their lap.

The same pattern applies to every category you try to hand off. An EA defaults to the behavior the founder has demonstrated, not the behavior the founder says they want. Explicit instruction changes the default.

Staying visible without being in the threads

Some founders hesitate to hand off vendor coordination because they are afraid of losing visibility. They want to know when something goes wrong. They want to stay close enough to catch problems before they become expensive.

This is a legitimate concern. The solution is not to stay in the threads. It is a weekly summary.

Ask your EA to send you a brief vendor update every Friday. Open items. Anything she handled that week. Anything she escalated. Nothing more than a bullet list. Five minutes of reading for you.

That gives you full visibility without any involvement. You know the state of your vendor relationships without being the person managing them moment to moment.

Set up one escalation rule clearly: if a vendor misses a deadline or if an invoice comes in more than 10% over what was agreed, she flags it immediately rather than waiting for the weekly summary. Everything else goes in the Friday update.

Most founders find that once they trust the weekly summary format, the anxiety about losing control disappears. The anxiety is almost always about information loss, not about the coordination itself. Solve the information problem and the control concern takes care of itself.

What to build this week

If you have an EA and you are still handling vendor coordination yourself, build the system over five days.

Day one: List every active vendor. Spend 15 to 20 minutes per entry. Do not skip the relationship notes.

Day two: Write the communication standard. One page. What good looks like, when to escalate, whose name goes on the emails, and how to handle the most common situations (late deliverables, wrong invoices, rescheduling requests).

Day three: Share the vendor list with your EA. Walk through three or four vendors together so she understands the format. Answer her questions. Explicitly tell her she now owns all vendor coordination.

Day four: Forward her the last three active vendor threads. Review her responses before they go out. Give specific feedback on what worked and what to adjust.

Day five: Stop touching vendor threads. Let the system run.

By the end of week two, you should have recovered 4 to 8 hours per week. Depending on your effective hourly rate, that is $600 to $2,400 per week in founder time returned to work only you can do.

The system takes about four to five hours to build. It pays for itself in the first week.

The contrarian take

Most productivity advice treats delegation as a skill. You get better at it over time. You learn to trust. You build the muscle.

That framing is wrong.

Delegation is not a skill problem. It is a systems problem. Founders who cannot hand off vendor coordination do not need to get better at letting go. They need a vendor list, a communication standard, and explicit instructions. That is the entire gap.

When the system exists, delegation happens automatically. When it does not, the founder stays in the threads because there is no real alternative. The EA cannot own what she has no instructions to own.

I have seen this play out clearly. Before I had a vendor system, I held onto vendor coordination because it felt "too complicated to hand off." After I spent three hours building the system, my EA owned 100% of it within one week. My direct involvement dropped to zero except for the Friday summary and the occasional escalation.

The complication was never the vendors. It was the absence of a system.

This applies to every category of work you are still doing yourself. The reason founders stay in work they should not be doing is almost never about trust or capability. It is about the absence of a system that makes delegation safe. When the system does not exist, the founder fills the gap. When it does, the EA fills it.

Your job is to build the systems. The EA runs them.

That division is what an EA relationship looks like when it is working correctly. And it starts with the unglamorous work of writing down what you already know: who your vendors are, how you communicate with them, and what good looks like. Three documents, one conversation. Done.

If you are ready to build this kind of operational foundation with an EA who has set up these systems before, apply for access and we will match you with someone who can run it from day one.