How to respond when a prospect mentions a current project
Handle the internal build objection on LinkedIn. Move the conversation from feature lists to maintenance costs and the risk of missed opportunities.
Get startedShort answer
When a prospect is building a solution internally, don't tell them their project will fail. Shift the focus to the cost of long term maintenance and the risk of missing edge cases. Your goal is to determine if they have a prototype or a full system and if they've planned for the burden of owning the code.
Stop the better product argument
When a prospect says they're building a tool internally, your first instinct might be to list why your software is better. Don't. If you tell a prospect your features beat what their team is coding, it sounds like an attack on the people writing it.
If you're messaging the project manager, you're telling them they're wasting their time. If you're messaging an executive, you're implying they're wasting company money. Both paths make the prospect defensive and end the conversation.
Instead, acknowledge the effort. Act like someone who understands the build process. By validating their choice to solve the problem, you stop being a vendor and become a peer who knows the technical hurdles they're facing.
The first reply sets the tone. If you come back with a pitch, the prospect stops sharing details. If you come back with a question about the build, they keep talking. That conversation is where you learn whether the project has a real owner, a budget, and a date.
The goal is to keep the door open for the next conversation.
The feature push
- Our tool already has the automation and API integrations your team would spend months building.
- Why spend six months on a build when you can get a working version today?
The peer approach
- That makes sense. An internal build can keep the logic tight and specific to your workflow.
- That route usually gets a prototype running fast.
The three questions to ask
After you acknowledge the project, look for gaps in their plan. Your aim is to show where the plan might strain, so your tool looks like the safer bet. Internal builds tend to hit timeline slips, edge cases the demo never showed, and a maintenance plan that stops at launch.
Get the prospect to describe the build in concrete terms. Use open ended questions that make them think about delivery and what happens after launch.
- What date are you working toward?
- Which part of the build is taking the most time?
- Who owns the tool after launch?
Example
- Prospect
We appreciate the reach out, but we're actually building a version of this internally right now.
- You
That makes sense. Are you aiming to have this live by a specific date, or is it more of an ongoing internal experiment?
- Prospect
We're hoping to have a beta ready by Q3.
- You
Got it. The build usually starts with the core logic. Edge cases show up later. Which part is taking the most time for your devs?
Avoid yes or no questions. Instead of asking if they have a timeline, ask what the timeline is. This forces them to give a specific detail you can use later.
Handling the "we have developers" objection
Prospects often respond by saying they have the engineering capacity and budget to finish the work. The question becomes whether the build is the best use of their engineering time.
Introduce opportunity cost. Every hour a developer spends on a tool that already exists is an hour they aren't spending on the core product that makes the company money.
That argument works better than a feature comparison because it uses their own priorities.
Keep the math simple. You don't need to know their exact salaries. Ask how many weeks the build will take and what else that team could ship in the same window. The prospect will do the math in their head.
- 1
Agree on the talent
Confirm their developers are capable. Say, "I don't doubt your team can build this. They're clearly talented."
- 2
Pivot to opportunity cost
Ask what other high priority projects are being delayed. Ask, "If your team wasn't spending time on this build, what's the next biggest project they'd be tackling?"
- 3
Highlight the maintenance burden
Explain that building is the easy part. The hard part is updating the tool when the market changes or bugs appear a year from now. Ask who is responsible for the long term maintenance.
Choosing your response path
Your next move depends on where they are in the build. If you push for a demo too early, you'll seem tone deaf to their effort. If you wait too long, they'll be too invested in their own code to switch.
Use the project stage to decide how much pressure to apply. Stay a helpful resource so that when the internal build hits a snag, you're the first person they call.
The offer should match the stage. A checklist is low friction early. A sanity check call works during the build. A review after launch gives them a way to talk after the first version ships without losing face.
If they ask for a feature comparison, send one page. Keep it short and tie each feature to a problem they mentioned. A long comparison sheet makes the internal build look like the safer choice because it has no adoption cost.
Early discovery
- Project stage
- Stay top of mind
- Goal
- A checklist of common pitfalls in internal builds
During the build
- Project stage
- Identify gaps
- Goal
- A sanity check call to compare roadmaps
Nearly finished
- Project stage
- Position as backup
- Goal
- A review after launch to discuss scaling
What to do when the build slips
Internal builds slip. A beta date moves, a key developer leaves, or the edge cases take longer than the demo suggested. That is the moment your earlier patience pays off.
Don't open with "I told you so." Ask a plain question about the delay and offer one specific thing that helps. A short checklist, a call with an engineer, or a look at how another company handled the same workflow.
Keep the tone even. The prospect already knows the build is late. Your job is to be the easy next step. They already have enough people reminding them of the problem.
Set a follow-up date before you end the call. Ask, "Should I check in after the August beta?" A specific date gives you a reason to return without chasing.
Example
- Prospect
Hey, quick update. The beta is moving to August. We ran into some issues with permissions.
- You
Thanks for the update. Permissions are usually where the first version gets messy. Do you want the checklist we use for role and access edge cases? It might save your devs a week.
- Prospect
That would actually help. Send it over.
Doing this with Kinlead
Finding people who are considering an internal build often starts with competitor posts. The Steal Customers agent watches competitor company pages and optional founder or employee profiles, reads comments on recent posts, and turns commenters who look like buyers into leads. Each lead keeps the post URL, what the post was about, and what they commented.
Run a campaign with a sales playbook that includes these internal build responses. Kinlead sends from your own LinkedIn account at a human pace: one action every 5 minutes, inside the daily limits and send window you set. Use hand-off mode so the conversation moves to you at the first reply. Replies from every campaign land in one inbox, classified by intent, with interested replies first.
Frequently asked questions
Related
Get started with Kinlead
Prefer markdown? How to respond when a prospect mentions a current project.md