# How to answer questions about your tech stack on LinkedIn
> How to answer when a prospect asks about your tech stack on LinkedIn, what to say, what to skip, and how to turn a spec question into a sales conversation.
- HTML: https://getkinlead.com/handle-prospect-asking-about-your-tech-stack
- Markdown: https://getkinlead.com/handle-prospect-asking-about-your-tech-stack.md

**Short answer:** When a prospect asks about your tech stack, they are usually checking risk: whether it fits their tools, whether security will approve it, and whether it will keep working. Name the one or two main pieces, say what that choice does for the buyer, then ask what they run today. Skip the full inventory of libraries.

## Work out why they are asking

A question about your tech stack is rarely about the code. Most buyers use it to check risk. They want to know whether your product plugs into the tools they already run, whether their security team will approve it, and whether it will still be standing in two years.

The answer changes with who is typing. A CTO is checking for modern standards and how you handle scale. A procurement lead is checking for paperwork they can file. An operations manager wants to know it won't fall over during their busiest week. Same question, three different answers.

A list of libraries answers none of them. It also hands the thread to whoever knows the most about infrastructure, which is usually not the person selling.

**Inventory reply**

- We use PostgreSQL, Redis and Python.
- Our frontend is React with Tailwind.
- Everything runs on AWS.

**Reply tied to a consequence**

- Postgres and Redis, so the dashboard stays quick even with a few million rows in it. What are you running today?
- React on the front end. We picked it so the interface stays usable on the older laptops field teams actually carry.
- AWS in the EU region, because most of our buyers need their data to stay in the EU before security will sign off.

## The four-part shape of a good reply

Keep it to about four lines. Acknowledge the question, name the main piece, say what that choice does for the buyer, then ask what they run today. That last question is the one that turns a spec check into a sales conversation.

Write it once for the stack questions you get most often, then reuse it. Most teams hear the same three or four technical questions from every buyer, and improvising each time is how you end up writing an essay about your queue.

1. **Acknowledge the question.** A short 'fair question' or 'happy to answer that' costs nothing and stops you sounding evasive.
2. **Name the main piece only.** One or two technologies. Postgres, not Postgres plus the queue plus the cache plus the CDN.
3. **Attach a consequence.** Say what that choice does for them: stays up through their peak week, passes their security review, works on the devices their team carries.
4. **Ask what they run today.** This moves the thread from your architecture to their problem, which is where you can actually help.

## What it looks like in a real thread

The last sentence decides whether the conversation continues. A list ends it. A reason plus a question keeps it alive.

Here is a narrow technical question getting a short answer tied to the buyer's problem, with the thread handed back to them.

- **them:** Quick one, what's your backend running on?
- **you:** Node and Mongo. We picked that pair so reporting views stay quick when a customer pushes a few million rows through them. What are you on today?
- **them:** Postgres. Reports crawl and people complain about it every week.
- **you:** That's the exact thing we tuned for. Worth 20 minutes tomorrow to show you how the reporting layer handles it?
- **them:** Yeah, send me a time.

## When they push back on your choice

Sometimes the prospect argues. They ask why you aren't on Go, or why you don't use a particular database, or they mention that their last vendor used something else and it felt faster. This is where most sellers start defending a technical decision they didn't make.

You don't win that argument by defending the library. You make the library irrelevant to the decision. Agree that the alternative works for some cases, say what your setup delivers, and ask what specific bottleneck they are worried about. If they have a real one, you now know what to solve. If they don't, the thread moves on.

Keep your tone flat. A defensive reply reads as doubt about your own product, even when the stack is perfectly fine.

> Never defend a library choice. Ask what specific performance or security concern made them question the stack.

```
Fair point, [Alternative Tech] is good for some cases. For our users, this setup is what lets us deliver [specific result] consistently. Is there a particular performance or security worry driving the question?
```

## When you shouldn't answer it yourself

Not every stack question deserves a full answer from you. Some belong with your engineer, some belong in a security questionnaire, and some are a competitor fishing for detail. Knowing which is which keeps you from guessing in writing, which is the one thing you can't take back on LinkedIn.

When you hand something off, say who will answer and when. 'I'll get our head of platform to reply by Thursday' is a stronger answer than a half-remembered detail about your caching layer.

| | Situation | What to say | What to avoid |
| --- | --- | --- | --- |
| They want architecture detail before a contract | Offer a call with your engineer under a mutual NDA, and say who would join and what they would cover. | Sketching a diagram from memory in a DM. |
| They ask about a tool you dropped last year | Say what you moved to and why. If it was cost or reliability, say that plainly. | Pretending you never used it. |
| Their security team sends a questionnaire | Forward it to whoever owns it and give a date for the reply. | Answering compliance questions off the top of your head. |
| They compare you to a competitor's stack | Ask what problem that competitor's setup solves for them, then answer that problem. | Arguing that their favourite tool was the wrong pick. |

## Doing this with Kinlead

Kinlead finds people on LinkedIn who match the customer you describe and scores each lead from 0 to 100 against that profile. Leads below the fit line aren't kept. You can sort them into lead groups and point any campaign at any group.

For stack questions, set the campaign to hand-off mode. The conversation comes to you at the first reply, so you answer the technical question yourself instead of letting a template take it. Replies from every campaign land in one inbox, sorted by intent, so the technical ones don't sit behind a wall of 'thanks, not now'.

## Related

- [Unified reply inbox](https://getkinlead.com/features/unified-inbox.md)
- [Reply hand-off workflow](https://getkinlead.com/ai-reply-handoff-workflow.md)
- [Sales playbook for LinkedIn](https://getkinlead.com/ai-sales-playbook-for-linkedin-outreach.md)

## Common questions

**Should I give a full list of every tool I use?**

No. A full inventory creates noise and invites a debate about choices you can't change mid-deal. Give the one or two main pieces and tie them to something the buyer cares about.

**What if my stack is genuinely old?**

Talk about what it has done. Say how long it has run your customers' workloads without a serious incident, and what you have added around it. Age is only a problem if you dodge the question.

**Is it bad to say I don't know?**

Only if you leave it there. 'I don't know, our platform lead does, I'll get you an answer by Thursday' reads as honest. Guessing and being wrong later is what damages the deal.

**How technical should I get in a first message?**

Barely at all. Name the stack in one clause and spend the rest of the message on the buyer's situation. Depth belongs in a call with their engineer present.

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