Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Asks HN: Solo founders-How to respond when customers ask how big is your company
59 points by brycelarkin on Oct 9, 2023 | hide | past | favorite | 62 comments
I've built an MVP and am talking to a prospective customer. They would be my first customer. They're asking how many people are in the company and I don't know how to respond to that in a reassuring way. It's just me.

Some background is I've built a pretty niche / domain specific product, so there's actually no one else doing what I'm doing. The MVP works. I don't have any customers yet (some trialing).



Don’t dissemble. You should ask about what their concern is (you getting hit by a bus, you losing interest, etc.) so that you can find a solution that will work for them and other similar customers.

One of our licensees had a lawyer who asked us to put our source code in escrow, in case we got acquired or went under. It was a little embarrassing for her when I explained that they already had our source code, which was integrated into their platform during our pilot. Sometimes the concern is like this, just a box-checking exercise not based in reality.


Side note on escrow - we get asked this from time to time. We respond, we're happy to provide it on certain plans and quote them for it. No one has ever taken us on it.

In b2b you never say no, always have an option for what they're asking and charge more for it.


This is the right way. Never say No but also don't just say Yes. A lot of times B2B customers are just doing a checklist and once they hear that it will cost more, they would drop it. I have been asked for escrow by customers paying $299/mo and I laugh internally first and then tell them "For escrow, you will need to be on our enterprise plan starting at $xx,000 per year with a minimum 3 year contract. let me know if this is something you would be open to". Usually crickets after that.


Out of curiosity, what reason would you give if they asked why escrow requires a more expensive plan?


Never try to justify your pricing. The moment you go down that rabbit hole, there is no coming back. You will give 1 reason and they will continue to challenge it.

Best way is to just say "It is company policy and I am afraid we cannot work around that. I am happy to discuss alternatives" and go from there.


I find that being a solopreneur (or just as CEO of a small startup), it's hard to invoke "company policy". You can say your board won't go for XYZ, but if your customer knows you own most of the company, that wouldn't fly either.

Tips?


Good point. You could replace company policy with "I do offer Escrow option with a customized/enterprise plan at $x/Year with a minimum contract to compensate for the additional overhead, cost and risks that comes with setting it all up"

Then, stick to it and don't try to justify it too much.


"Experience for previous clients shows that this is the best solution for everyone involved."


Risk, administrative burden.


Yep, even just having a process for offering escrow makes you seem like a more mature/reliable company, as opposed to one guy who had never encountered the question before.


same thing for any long 'security' checklist. Just send them whatever standard $X report you use for $Current Year. If they don't like your ASFSRADA Complaince Report Level 3, you can offer to bill hourly to complete theirs. 99% will then accept yours, and it shows you care, you have already done it!


> In b2b you never say no, always have an option for what they're asking and charge more for it.

This was a somewhat recent revelation for me, and it totally works.

"Well, we don't really want to work on this or agree with the approach, but pay us double our normal rate, and we'll do whatever you want."

Typically that will end the conversation, and in the rare case they do move forward, being paid handsomely is really nice


"Right now, it is just me as I recently started this startup. Do you have any questions or concerns ? "

Then listen. Sometimes it is just a casual question. Sometimes it is a checklist. Also depends on how large the customer itself is.

You can also make this a plus by adding "You get direct support from the founder and will never have to talk to a robot" if they have any further concerns/objections.

I have lost like 2 deals out of 1000s where the company size was a potential issue and that too I am guessing because they never told me specifically but I guessed based on their questions/concerns.


No need for the "Right now" qualifier. It implies a particular future and a desire to grow, which may not be the case. It is perfectly fine to be a solo entrepreneur and adding that prefix implicitly implies otherwise.


Hire a few freelancers for some small tasks here and there and say you’re a team of 5 with most of them located in India or Eastern Europe. Never say you’re a team of 1 even if you are. Some people here are too honest for their own good


I would do this, but not just to deceive. Having a small team you work with will address some of your potential customers concerns about your ability to scale.

It’s how I’ve been working lately. It’s mainly me the customer is buying, but I have a team of 3-5 trusted freelancers I work with. Customers don’t seem to bat an eyelid at that proposal.


100%. Not only this, but it forces you to document things for other people (one of which is future you), and it forces you to have a plan for if you get hit by a bus. People do actually get hit by busses sometimes, and if you actually care about your customers you should have a plan for that.


This is the worst advice you could ever take. Always be true to yourself. Always be honest. Your potential client should be honored to have the founder and CEO of their new vendor and your undivided attention.


Just be honest, it will save you lots of pain down the road. I know getting the first customer(s) is hard, but don't lie to do it. They may not even care, and just want to know what they are getting into.

Good luck on your project. Getting this kind of interest is a good signal!


You can also turn it into a positive -- you're small and new, but it means that you will be incredibly responsive to any feedback/changes/issues/support they face. You can build out the product with them.


To add to this - one more concern might be that you will change your mind in 2 months and they want to protect their investment. To address that, you can cover the issue in contract - especially if it's business critical. So open discussion is probably most important as it will help you with future clients.


At a guess - I suspect they are assessing risk of investing time/money in installing your product into their company and how they would deal with issues if you are off ill one day or want a holiday.

You need to be honest about your company size, but turn it into a positive, such as sole developer, backed by a third-party support package (assuming you have one), or that the company is expected to grow fast, so they wont be relying on just one person to fix things etc.

Pitch it really well, and depending on the type of customer, they may even end up wanting to invest in your company to help you scale up faster than you could expect (yes, I have seen that happen with start-ups).

Don't be afraid of awkward questions like these, as they will crop up, and each time you gain experience in handling the RFP style enquiries, and with experience comes improved skills to close those sales deals.


Be upfront. Also, the fact that they will have the founder as their “customer success manager” instead of a hire that won’t really know what’s going on is a HUGE benefit.


I don't know if this is the best way, but what I've done in this situation is to answer along the lines of "we're a small, highly-focused company of under 50 employees. Do you have any specific concerns I can address?" (I choose "under 50" because that's often the smallest bracket in forms wanting this data).

The idea being that this question is often asked instead of what the customer really wants to know: "can you do the job properly in the required time frame?" I want to cut to the real question as soon as possible and not waste time and effort on the superficial one.


FWIW, if it’s a Fortune 500 company, one of two things could be happening:

a. Minority Owned or SMB. Many Fortune 500 company’s have internal metrics where they try to do more business with Minority Owned or SMB businesses.

b. Bus Factor or Financial Risk. If you’re providing a service that will become core to them or poses financial risk to them if it stopped working (or you went out of business) - they are assessing how much risk you pose to their business.

As other have said, the better you can understand why they are asking the question the better you can respond.

And don’t lie.


I wonder if the first point is applicable under Title VII of the Civil Rights Act, given that as a solo founder, one is below the 15 employee threshold.

https://en.wikipedia.org/wiki/Civil_Rights_Act_of_1964#Title...


Aside from everyone else's input, I would also like to add that smaller companies usually come with the added benefit of adaptability, quick iterations/improvements, and clients' have direct access to the key decision maker which are all great points sought after by customers. It's classic interview 101: turn a seeming weakness into a strength.

As long as you have a long term vision of where you want to take the company (plan for the next quarter, next semester, one year plan, pipeline of possible improvements, potential pipeline of clients, hiring plan of who and when if necessary, etc.), and can communicate this in a reassuring way without puffery you can come across as trustworthy and even respectable to do business with. Customers just want to know you are the best value option within the category/niche. Part of being the best option is the reassurance that you: 1. have a product that meets their needs (product-market fit) 2. have long-term potential (so they don't have to worry about you shutting down and them wasting time looking for another alternative) <- depends on your niche 3. will be readily available to lend customer support

You can answer with the truth and then redirect that question back at them and ask things like: - what do you look for specifically in a company? - Does the number of employees affect the metrics you are trying to achieve or need help with? (the answers you get will give you a better idea of how to adapt your pitch based on their priorities, metrics, & expectations)

In the end, if they aren't happy with the truth, you get out of this all the wiser and still win. Good luck!


I'm guessing most of the people here who are saying "be truthful" have never started a company. Sometimes you just gotta fudge the numbers a bit and do what needs to be done to get your company off the ground. I've been in your shoes and I recommend saying something like "we are a team of 5".


Nah. Give the impression of scale if you can and need to, but I would draw the line at outright lying. If it doesn’t totally backfire then it’s dishonest. I would rather lose the deal.


> Sometimes you just gotta fudge the numbers a bit and do what needs to be done to get your company off the ground.

I disagree. I've never had to lie to get a company off the ground, and if that was a requirement, I'd rather let the company die and try again with something else.

Being vague, however, is OK.


"I'd love to meet the team!"


Right. There’s a practical justification for being honest, which is that if you’re dishonest, you can find yourself in a situation of having to continue the lie, or coming clean and damaging or losing that relationship, or even your reputation.

I have started two businesses that have generated positive cash flow (and sat on a board for one that didn’t), and honesty is the only right answer.

You gain trust in thimbles and lose it in buckets.


“We are a small company and don’t discuss employee counts as a matter of policy.”


That's a great answer


The question is predicated on the argument that 'small is bad'. As stakeholders in the industry, and active participants in the community, it is our job to try and change any negative perception of small enterprises. We have to show examples of 'small is good', and be truthful.


It's not predicated on that. It's predicated on risk. I've been a buyer of software and the last thing I want to worry about is a guy gets hit by a bus (figuratively) and then I am stuck.


The irony being that the number of employees a company has is a poor proxy for answering that concern.

I think that at most large companies I've worked for (including my current one), there have been projects that had a key employee that would cause the project to screech to a halt if they got hit by a bus.


A project or a running product that I'm paying for?

For the purposes of discussion, I'll agree regardless. For every product I have ever bought, I'll gladly stick my head in the sand and assume the existing employees can take over in the event a person disappears. I can't do that if it's one person.


> A project or a running product that I'm paying for?

My apologies for being unclear. I was using the terms as synonyms of each other. Every product is a project.

> I'll gladly stick my head in the sand and assume the existing employees can take over in the event a person disappears.

My point is that this even in large companies, it's is far from unheard of that the entire product relies on a single individual's knowledge. If that individual were to go away, the product cannot be changed until someone else is able to come up to speed enough to replace that person. It's probably more likely to happen in a very small company, of course, but big or small, if it happens the effect is the same.


Yep, agree with this last part. For whatever reason (including irrational ones) it just feels less "in your face risky" than choosing an outside vendor who is a single person.


Who is asking? Generally as a small software company founder, key man risk worries come from middle managers who are afraid of the worst case (you dying or something) then their boss asking, so they are just trying to cover all their bases. It should be a minor consideration for the overall business who is the ultimate customer (as there is risk in everything - getting acquired, going bankrupt etc.), ask their concerns and reassure, focus on the value and product since you have a niche


I've used: "We are tiny but mighty!"

People don't care how big you are but what problems you solve for them

Now we are four people working full time in our company, but still... tiny but mighty.


Gaining confidence is a huge part of any startup. Customers, investors and employees dislike insecurity. Every presentation, new customer, investment, and discussion helps increase your confidence. The confidence you build as part of these interactions will not only make your startup successful, it will help you become a better person.


Also a solo founder.

I didn't know I had this question. (Don't have an MVP yet.)

Thank you for everyone that has given good answers!


Whatever you do, don't convey your insecurity in your response (as many of these comments suggest).


I am in the same situation and I am being honest about that is currently only me. My plan is to hire people, business developers, project managers and engineers. But there has to be work for them before I hire.


You could join a freelancer programmer cooperative to share the risk and tell them that you cooperate with x others.


I'd say something like:

> I _am_ <company name>. This product is my baby.


update 1: Thanks everyone! I ended up being transparent and telling them it’s just me and we just released an mvp.

Will keep you all posted!


create a team of AIs with cute names


Tell them you are alone. No need to be afraid


Lie like hell --- and try to turn small into a positive.

But truthfully, you really do need at least 2 people as a bare minimum to sell a viable product.

Lots of customers will want some assurance that if you die in a car crash on the way home, there is someone left to continue on with.


> Lie like hell --- and try to turn small into a positive.

Don't do that. Unless you don't care about your reputation.

> But truthfully, you really do need at least 2 people as a bare minimum to sell a viable product.

When did this become an immutable law?

> Lots of customers will want some assurance that if you die in a car crash on the way home, there is someone left to continue on with.

One can also figure out a business continuity plan. Place code in escrow, subcontract some of the work, avoid writing software that only runs when a specific person is constantly tending to it.


Place code in escrow

Doesn't help most customers because they lack the expertise to use it. Most people looking to buy software are not in the software development business and don't want to be.

subcontract some of the work

What about the rest of the work?

avoid writing software that only runs when a specific person is constantly tending to it.

If it is a hosted solution, someone needs to tend to paying the bill. If it is not, someone needs to tend to support and make adjustments when needed.

The quick, simple, easy, all purpose answer to this line of questions for a small startup is, "My partner can take care of it".


The "bus factor" analogy is just that, an analogy. It shouldn't be solely taken literally, as in "what do we do if someone important becomes incapacitated".

The point of that analogy is to get people thinking about business continuity (https://en.wikipedia.org/wiki/Business_continuity_planning) and how to mitigate various types of risks. The keyword being mitigate. One cannot eliminate risk, and no sane customer expects their use of a client or software to carry 0 risk.

If a vendor tells a client that nothing can disrupt their ability to deliver their product, they are either lying, or have failed to understand the risks their company actually faces.

And the final point, "my partner can take of it". That addresses only one, frankly minor aspect of business continuity, which is "what happens if someone important becomes incapacitated". The number products that failed because someone important literally died (not just left the company) is probably extremely minute. There are way bigger risks a company should focus on mitigating first, including:

- software fails to meet regulatory compliance (if applicable)

- company fails to manage finances properly and has to close shop

- someone important leaving the company

Can some of these be mitigated by adding another partner? Depends on what they bring to the table.


"My partner can take care of it" is the easy, all purpose answer for a small startup.

If they want to dig any deeper, you're probably screwed and don't really have a chance at a sale anyway.

About the same result as with, "I can not tell a lie. I run this business from my basement. I know nothing about business or sales or marketing cause I'm just a nerd and I've never done this before and I'm all you got". What the customer hears is, "I'm so fired if this doesn't work out".

I know because I've been there. First rule of business ---Survival is always job #1 and sometimes it involves some compromise; particularly early on. Those who don't understand this probably shouldn't quit their day job.


> If they want to dig any deeper, you're probably screwed and don't really have a chance at a sale anyway.

Once again, is this true across the board? How about questions around data security, authentication, data storage and backups, privacy...those should have solid technical answers, not "my partners and I know what we're doing". I'd run for the hills if I couldn't get a solid answer for any of those things for important enterprise software.

> About the same result as with, "I can not tell a lie. I run this business from my basement. I know nothing about business or sales or marketing cause I'm just a nerd and I've never done this before and I'm all you got". What the customer hears is, "I'm so fired if this doesn't work out".

Would you agree there's some middle ground between "I cannot tell a lie" and "I will do anything to make sure the company survives, including lying to customers"?


Would you agree there's some middle ground between "I cannot tell a lie" and "I will do anything to make sure the company survives, including lying to customers"?

Sure. But there isn't much middle ground between success and failure.

Until your small startup is succeeding, you're just a failure in progress. And statistically, failure has the better odds --- probably due to a lot of half hearted attempts aimed at the middle ground.


If the most substantive thing you can say involves fixating on the definitions of “success” and “failure”, then I overestimated how productive of a conversation this would be. Have a good day.


> But truthfully, you really do need at least 2 people as a bare minimum to sell a viable product.

Not true. Fine to be a solo entrepreneur, especially for more senior founders. YC may want multiple founders, but they cater to first-time founders.

> Lots of customers will want some assurance that if you die in a car crash on the way home, there is someone left to continue on with.

Another person involved does not improve the chances that the company will survive if you get hit by a bus. Releasing all the code as Open Source, or providing the source to existing customers is a much better way to mitigate risk.


You’re arguing against a straw man. Nobody is claiming another person will improve chances of survival. It will improve chances of a sale


How do multiple people increase the chance of a sale?

I was responding to "if you die in a car crash on the way home, there is someone left to continue on with." Which seems pretty clearly attached to survival.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: