# How to answer a prospect who asks about your tech stack
> How to answer a prospect who asks what tools you use on LinkedIn, group your stack by outcome, and turn the question into a buying conversation.
- HTML: https://getkinlead.com/respond-to-prospect-asking-about-your-tech-stack
- Markdown: https://getkinlead.com/respond-to-prospect-asking-about-your-tech-stack.md

**Short answer:** A prospect asking about your tech stack is usually checking whether your process is repeatable and safe for their brand. Answer by naming the outcome each group of tools produces, then ask how their team handles the same step today. The tool names matter less than the workflow you describe around them.

## Understand why they are asking

A prospect who asks what tools you use is not shopping for software. They are looking for a proxy for risk. A team running everything out of a spreadsheet reads as a team that will drop the ball once volume picks up. A team using a tool nobody has heard of reads as a team that might not be around next quarter. Neither impression is fair, and both get made in about four seconds.

There is a practical reason too. If you are running outreach for them, they want to know their domain will not get burned, their brand will not appear next to spam, and their existing systems will not need a rebuild to accept your output. Those are fair questions and they deserve a real answer rather than a joke about having too many tabs open.

The question is also a buying signal. Someone who has already decided you are too expensive or too small does not ask about your process. They ask about price and disappear. The stack question usually comes from someone picturing the work happening, which means they are close.

So treat it as a request for confidence rather than a request for a list. Answer the confidence question and the list becomes a detail nobody argues about.

**A list of tools**

- We use Sales Navigator, Apollo, a couple of AI tools, HubSpot and Zapier.
- Honestly, whatever works. I have a lot of tabs open.
- I would rather not say, it is kind of our secret.

**A description of the system**

- We run three stages: sourcing, outreach and reply handling. Sourcing is a scoring tool that ranks people against your criteria, outreach runs from my own profile at a pace LinkedIn will not flag, and replies land in one inbox sorted by intent.
- The stack is small on purpose. Every tool we keep has to remove a manual step, otherwise it is one more thing to maintain.
- Happy to walk you through it on a call. The short version is that nothing sends without a limit I set and a send window.

## Group your stack by the job it does

Listing tools in whatever order you think of them makes you sound like a software directory. Group them by the job each one does. Four groups cover most service businesses: finding people, starting conversations, handling replies and delivering the work.

This does two things at once. It shows the prospect that every stage has a deliberate choice behind it, and it keeps the conversation away from a brand comparison. When you name the job first, the tool becomes supporting detail instead of the headline.

Keep each group to one or two tools. If a group needs five tools to explain, the process probably has a gap you should fix before you describe it to a buyer.

Write this out once, in a note you keep open during calls. Four lines, one per group. You will use it in DMs, on calls and in proposals, and having it ready stops you improvising a list that makes your process sound messier than it is.

| | Stage | The job it does | What to say about it |
| --- | --- | --- | --- |
| Finding people | Getting the right names in front of you | A scoring tool ranks people against the profile we agreed on, so the list starts narrow instead of long. |
| Starting conversations | Getting a reply without burning the account | Outreach runs from my own profile at a pace I set, with a note that says why I am writing to that person. |
| Handling replies | Not losing the interested ones | Everything lands in one inbox, sorted so the warm replies come first and nothing sits unread. |
| Delivering the work | Doing what you were hired to do | Project tool and shared doc, usually whatever the client already uses. This one is their call. |

## Write the answer in three sentences and end with a question

The answer should take about three sentences and finish with a question. Acknowledge what they asked, describe the system in stages, then hand the conversation back to them.

Do not send links to tool pricing pages and do not send a screenshot of your dashboard. Both invite an audit of your business when you want a discussion about theirs.

In LinkedIn chat, keep it to one message. Three short messages in a row reads as a pitch even when each one is useful. If you need more room, offer a call instead of typing a wall.

- **them:** Out of curiosity, what are you using to find these people and run the outreach?
- **you:** Three pieces. A scoring tool ranks people against the profile we agreed on, so we are not guessing. Outreach runs from my own profile at a fixed daily limit with a send window, which keeps the account healthy. Replies land in one inbox sorted by intent so nothing warm sits unread.
- **you:** The tools are the boring part. What matters is that we only contact people who match your criteria and we stop the moment someone says no.
- **them:** Makes sense. We are doing most of this manually right now.
- **you:** Most teams are at this stage. How are you deciding who to contact first?

## When they ask for the specific product

Some prospects will name a tool and ask if you use it. Usually that means they have used it themselves, or they are considering running the same play in-house. Neither is a threat.

Name the tool if it is a commodity. Hold back the configuration: the scoring criteria, the message sequence, the follow-up timing and the rules for who gets dropped. That is the part you built, and it is the part they are paying for.

If you would rather not name anything, say that plainly and offer a walkthrough instead. Vagueness dressed up as mystique reads worse than a straight answer, and it makes the prospect wonder what else you are keeping back.

> Name the tools if it helps the conversation. Keep the scoring rules and the message sequence to yourself, because that is the part the client is buying.

```
Fair question. We use [tool] for [stage], and the tool itself is not where the results come from. What we tuned is the scoring criteria and the follow-up sequence around it, and that is built for your market. I can screen-share the workflow on Thursday if that would help.
```

## Ask a question back before you finish

The answer is half the exchange. The other half is finding out what they are comparing you against. A prospect asking about your stack is often midway through deciding whether to build this in-house, hire someone or buy a tool.

One question does most of the work: how does your team handle this step today? The answer tells you whether you are replacing a person, a process or nothing at all, and those are three different sales conversations.

1. **Ask how they do it now.** One sentence, no pitch attached. 'How are you handling sourcing today?' tells you whether there is a process to replace or a blank page.
2. **Ask what went wrong last time.** If they tried a tool or an agency before, the reason it stopped is the objection you will hit in two weeks. Get it on the table now.
3. **Ask who else is involved.** Stack questions often come from the person who will have to integrate with you. Find out early whether that is the buyer or a gatekeeper.
4. **Write the answer down.** If three prospects ask the same stack question, put your answer in your saved replies and on your profile. It has become part of your pitch.

## Doing this with Kinlead

If sourcing and outreach are two of the stages you are describing, Kinlead covers both. It finds people on LinkedIn who match the customer you describe or your website, scores each lead from 0 to 100 against that profile and drops anything below your fit line. Lead search uses LinkedIn's standard search, so a Sales Navigator seat is not required.

Leads sit in lead groups, and any campaign can point at any group. The Steal Customers agent watches competitor company pages and optional founder or employee profiles, reads the comments on their recent posts, and turns commenters who look like buyers into leads with the post URL, the topic and their comment kept alongside.

Outreach runs from your own LinkedIn account through Unipile, at most one action every five minutes, inside daily limits and a send window you set in the lead's time zone. Replies from every campaign land in one inbox classified by intent, and you get an email when someone replies. Pro is $49 a month after a 7-day free trial, and the [minimum booking guarantee](/minimum-booking-guarantee) is worth reading before you start.

## Related

- [AI LinkedIn outreach](https://getkinlead.com/features/ai-linkedin-outreach.md)
- [Steal Customers agent](https://getkinlead.com/features/steal-customers.md)
- [Lead scoring and groups](https://getkinlead.com/features/lead-groups-and-scoring.md)

## Common questions

**Should I mention every tool I use?**

No. Mention the ones that prove you have a repeatable process. A long list of small utilities makes the process sound fragmented, and the prospect stops listening halfway through.

**What if they use a competing tool they prefer?**

Say it is a good tool and explain that your choice comes from the outcome you need for their project. Keep the conversation on the result rather than the brand.

**Is it a red flag if I do not have a complex stack?**

Not if you can show the results. A short stack that runs reliably beats a complicated one that breaks, and most buyers have seen both.

**Should I answer stack questions in the first message?**

Only if they ask. Volunteering your tools before anyone asks reads as a pitch about you rather than a conversation about them.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
