Responding to Project Opportunities

13.1 How to Read an Expert Network Project Description

An expert network project description is usually brief. It may include a title, a few bullets about the topic, the client’s desired expert profile, screening questions, call length, proposed rate, and requested timing. Sometimes it is clear. Sometimes it is vague. Sometimes it is written by an associate who understands the topic well. Sometimes it is written by someone translating a complex client request into a short message as quickly as possible.

Project description: the summary of a client’s research needs that the expert network shares with potential experts to determine fit, relevance, availability, and compliance.

Read the description carefully before replying. Do not react only to the industry label. A project titled “healthcare technology” could be about electronic health records, revenue cycle management, clinical workflow, payer data exchange, cybersecurity, or enterprise software buying. A project titled “industrial distribution” could be about branch operations, private equity diligence, pricing, e-commerce, supplier rebates, inventory productivity, or customer switching behavior. The screening questions usually reveal the real room.

Start by identifying the client’s likely use case. Are they doing commercial due diligence, market mapping, public-company research, product discovery, vendor evaluation, pricing work, or implementation planning? A description that asks about customer retention, market growth, competitor positioning, and pricing power may suggest private equity diligence. A description asking about recent demand, quarterly trends, or industry sentiment may suggest a public-market investor. A description asking for benchmarks, best practices, operating model examples, or implementation risks may suggest a consulting firm or corporate client.

Next, identify the expert perspective requested. The client may want a former executive, customer, competitor, supplier, channel partner, buyer, operator, regulator, clinician, or technical specialist. This matters because you should not answer from a perspective you do not have. If the client needs a buyer and you were a seller, you may still have useful insight, but you should frame it clearly. If the client needs current customer behavior and your experience ended five years ago, you may be a partial fit for historical context but not a strong fit for current market signals.

Then look for time period, geography, and segment. Many projects are specific even when the description looks broad. The client may need U.S. enterprise buyers, European distributors, Asia-Pacific manufacturers, mid-market software customers, hospital procurement leaders, outpatient clinic operators, public-sector technology buyers, or former employees from a certain period. If your experience is close but not exact, say so. Precision helps the associate decide whether to present you.

Finally, read for compliance risk. Be cautious when the project asks about a current employer, a public company’s current performance, confidential customers, private pricing, pending contracts, unreleased product plans, regulatory decisions, or anything that sounds like material nonpublic information. A project can be legitimate and still be inappropriate for you. Your response should define the safe lane before the call is scheduled.

Project reading checklist:

• What is the topic really about beyond the title?
• What client use case does the wording suggest?
• Which expert perspective is the client seeking?
• What industry, segment, geography, and time period are relevant?
• Which questions are factual fit questions versus unpaid research questions?
• What compliance boundaries should be stated before accepting?
  
  

13.2 Deciding Whether You Are a Fit

The most important decision is not how to win every project. It is whether you should try to win this project. Expert network work rewards relevance. If you accept calls outside your lane, you may waste the client’s time, disappoint the associate, receive weak ratings, and damage your future opportunity flow. If you decline professionally when you are not a fit, you build trust.

Strong fit: you have direct, recent, nonconfidential experience with the topic, perspective, market, customer type, role, or decision the client wants to understand.

Partial fit: you have relevant but limited, adjacent, historical, or narrower experience that may be useful if the client understands the boundary.

Poor fit: you do not have enough direct experience to answer the client’s likely questions, or the topic would require you to discuss information you cannot properly share.

Strong fit is easy to recognize. The project asks for someone who has done exactly what you did. The client wants a former procurement leader who selected warehouse automation vendors, and you led several warehouse automation evaluations in recent years. Or the client wants a former regional operator of urgent care clinics, and you ran a region of urgent care sites until last year. In these cases, respond quickly and specifically.

Partial fit requires more judgment. Suppose the client wants current enterprise buyers of a software category, but you last evaluated the category three years ago and now advise companies on implementation. You may still be valuable, but you should not present yourself as a current buyer. A good response might say, “I am a partial fit. I can discuss enterprise evaluation criteria and implementation risks based on buying experience through 2022 and advisory work since then, but I cannot speak to current quarter demand or confidential vendor negotiations.”

Poor fit should be declined. There is no shame in declining. Associates want experts who are honest about fit. If you are not qualified, say so briefly. If you know the kind of expert who would be better, you may offer a referral if appropriate. Do not force yourself into a project because you want the fee. One weak call can cost more than one missed opportunity.

Fit also includes compliance. You may be technically knowledgeable but unable to discuss the topic because of current employment, board duties, consulting obligations, confidentiality agreements, customer relationships, regulatory restrictions, or material nonpublic information. In those situations, the right question is, “Can I discuss this safely, at a general and nonconfidential level?” If not, decline.

When deciding fit, ask whether you can provide at least three useful, nonconfidential examples or decision criteria during the call. If you cannot think of any, you may be less qualified than the project requires. Also ask whether you can answer follow-up questions without guessing. Clients rarely stick only to the first question. They probe. If your knowledge is thin, the call will expose it.

13.3 Writing a Strong Screening Response

A screening response is not a mini-consulting report. It is a concise argument for why you are relevant. The associate may paste your response into a client-facing note or summarize it in a profile. Write it so the client can quickly see your fit.

Screening response: your written or verbal answer to project-specific questions that helps the expert network and client determine whether to select you for a paid call.

Good screening responses are specific and bounded. They answer the question directly, provide the basis of your experience, include time period and context, and state any limits. A weak response says, “Yes, I have experience in this industry.” A strong response says, “Yes. From 2019 to 2024, I led procurement for packaging, disposables, and cold-chain logistics suppliers for a national restaurant group. I can discuss supplier selection, RFP criteria, distributor relationships, service-level issues, pricing negotiations, and switching triggers from the buyer perspective.”

Do not give away the full answer before the paid call. Some screening questions are legitimately designed to determine fit: “Have you evaluated vendors in this category?” “Which customer segment did you serve?” “When was your last direct involvement?” “Can you discuss pricing negotiations generally?” Other questions may drift into substantive research: “Which competitor is best positioned and why?” “What is the market growth rate?” “What will customers do next year?” You can answer enough to show relevance without doing unpaid analysis.

A useful screening response often has four parts. First, state your fit. Second, explain the source of your knowledge. Third, list the topics you can discuss. Fourth, state boundaries. For example: “I am a strong fit for the buyer perspective. I evaluated and selected vendors in this category as CIO of a U.S. manufacturing group from 2018 to 2024. I can discuss buying committee structure, security review, procurement process, implementation risk, renewal behavior, and vendor differentiation. I cannot discuss current confidential negotiations or internal security findings.”

Use plain language. Associates may not be experts in your field, and clients may compare several expert summaries quickly. Avoid unexplained acronyms, internal project names, and vague executive wording. Use the same terms a client would use when searching for an expert: customer segment, product category, vendor type, geography, role, time period, and decision process.

When answering multiple screening questions, use short, complete bullets. The response should be easy to scan. If the associate needs more detail, they will ask. If the client selects you, you can go deeper on the call.

Strong screening response checklist:

• Respond quickly, preferably the same day when the project is relevant.
• Answer each screening question directly.
• State your role, time period, geography, and perspective.
• Name specific topics you can discuss without giving away the whole call.
• Use client-searchable language rather than broad executive adjectives.
• State confidentiality or compliance boundaries clearly.
• Provide availability windows and confirm your rate if requested.

If you are a partial fit, say so. A partial-fit response can still get selected when the client values your lens. For example: “I have not bought this product directly, but I advised three companies implementing similar tools and can speak to integration risk, workflow adoption, and implementation cost. I would not be the best expert for procurement pricing.” That honesty helps the client use you correctly.

13.4 Setting Your Hourly Rate

Your hourly rate is both a compensation number and a market signal. Set it too low, and you may undervalue your time or attract marginal requests. Set it too high, and you may price yourself out of projects where you would have been selected. There is no universal correct rate. The right number depends on seniority, scarcity, recency, client demand, opportunity cost, and the type of expertise being requested.

Hourly rate: the amount you charge for expert network consultation time, usually stated per hour even when calls are scheduled for shorter or longer periods.

Start with your opportunity cost. What is an hour of your focused professional time worth? Consider not only the call itself but also the time spent screening, scheduling, preparing, completing compliance steps, and handling payment administration. Expert calls are efficient, but they are not zero-effort.

Then consider scarcity. A former CEO of a niche company, a specialist physician, a former senior regulator, a current buyer of a hot enterprise software category, or an operator with rare technical knowledge may command more than someone with a common or outdated perspective. Scarcity is not only title-based. A mid-level buyer with recent experience selecting a specific vendor category may be more valuable for one project than a retired executive with broad but dated knowledge.

Recency matters. Current or very recent experience often supports a higher rate, especially for fast-moving markets, but it can also create restrictions. Do not accept a high rate for a call you cannot conduct safely. Historical expertise can still be valuable, particularly for strategy, regulation, market structure, and operating models, but the rate should reflect the actual value to the client.

Some networks ask for your rate during registration. Others ask project by project. Some may suggest a rate or indicate a client budget. You can negotiate politely, but avoid turning every interaction into a prolonged rate discussion. Associates are often moving quickly. A clear rate helps them present you. If you are flexible for certain project types, say so. If you have a firm minimum, say so.

Rate floor: the minimum hourly rate at which you are willing to accept an expert network call, considering your expertise, time, preparation, and opportunity cost.

Premium rate: a higher rate reserved for rare, senior, technical, urgent, or highly specialized topics where your expertise is especially valuable.

One practical approach is to set three numbers for yourself. The first is your standard rate for good-fit calls. The second is your premium rate for rare or highly specialized calls. The third is your decline threshold, below which the work is not worth your time unless there is a strategic reason to accept. Having these numbers in advance prevents you from making rushed decisions when an invitation arrives.

Be professional when discussing rate. “My rate for this type of consultation is $___ per hour” is enough. If the associate says the client budget is lower, you can decide whether to accept, counter, or decline. A reasonable response is, “For this topic, given the specificity of my experience, my rate is $___. If that is outside the client’s budget, I understand.”

Do not change your rate after the call is scheduled unless there was a genuine misunderstanding. That creates friction and makes you look unreliable. Also clarify billing increments where needed. Some networks pay by the minute, some in fixed increments, and some have minimums. Know the platform’s process before assuming how a 45-minute or 75-minute call will be paid.

13.5 Template: Response to an Expert Network Invitation

A good response template saves time, but it should never sound robotic. Customize it to the project. The associate needs enough detail to evaluate and present you, but not a full unpaid consulting answer. The template below is designed for a strong-fit project.

Strong-fit response template:

“Thank you for reaching out. This project appears to be a strong fit for my background. I can speak to [topic one], [topic two], and [topic three] based on my experience as [role] at [company type or industry] from [time period], with responsibility for [relevant decisions, customers, suppliers, operations, or market exposure].

For the screening questions:

• Relevant experience: [Briefly describe direct experience, including role, time period, geography, and perspective.]
• Topics I can discuss: [List the specific nonconfidential topics you can cover.]
• Boundaries: [State anything you cannot discuss, such as confidential pricing, current employer activity, client information, material nonpublic information, or restricted topics.]
• Availability: [Provide two or three clear time windows with time zone.]
• Rate: My rate for this consultation is [$___] per hour.”

Here is what that looks like in practice:

“Thank you for reaching out. This project appears to be a strong fit for my background. I can speak to enterprise software selection, procurement review, cybersecurity requirements, systems integrator evaluation, and implementation risk based on my experience as CIO of a mid-market manufacturing group from 2018 to 2024.

For the screening questions:

• Relevant experience: I led or sponsored evaluations of ERP, endpoint security, identity access management, cloud infrastructure, and data analytics vendors across U.S. and Mexico manufacturing operations.
• Topics I can discuss: I can discuss buying committee structure, vendor shortlisting, security and procurement review, implementation timelines, integration challenges, renewal considerations, and common reasons vendors win or lose.
• Boundaries: I cannot discuss current confidential vendor negotiations, internal security findings, nonpublic pricing, or any current employer confidential information.
• Availability: I am available Tuesday 10:00 a.m.–12:00 p.m. ET, Wednesday 2:00–4:00 p.m. ET, or Thursday after 3:00 p.m. ET.
• Rate: My rate for this consultation is $___ per hour.”

For a partial-fit project, use a modified version that is candid about the boundary:

Partial-fit response template:

“Thank you for reaching out. I may be a partial fit. My direct experience is in [specific adjacent area], not [exact requested area]. I can speak to [useful topics] based on [role/time period], but I would not be the best expert for [topic outside your experience]. If that perspective is useful to the client, I would be happy to participate. My rate is [$___] per hour, and I am available [availability].”

For a decline, keep it brief and professional:

Decline template:

“Thank you for thinking of me. I do not think I am the right expert for this project because [brief reason]. I have not had direct enough experience with [topic], and I would not want to overstate my fit. Please keep me in mind for projects involving [your actual expertise].”

When responding, remember that speed and clarity matter. The associate may be trying to fill the project quickly, and the client may be choosing between several experts. A long, hesitant, vague response creates work for the associate. A concise, specific response makes you easier to present.

Before sending, review your response from the client’s perspective. Does it clearly show why you are relevant? Does it state the source of your knowledge? Does it define the time period and perspective? Does it avoid confidential detail? Does it provide availability and rate? If yes, send it. Be thoughtful, but be fast.

Responding well is one of the highest-leverage skills in expert network work. You can have excellent experience and still lose opportunities if your screening responses are slow, vague, inflated, or risky. You can also build a strong reputation by being the expert who replies quickly, states fit honestly, protects boundaries, and makes the associate’s job easier. Over time, that reputation becomes part of why networks come back to you.