Ask HN: My CEO wants to go hard on AI. What do I do?
I'm the lead software engineer at a company building a B2B hardware/software product in the US. Great team, great technology, great PMF and good progress on revenue targets. There are lots of opportunities for how to develop the product further. It's been an extremely hard scale-up but we are finally starting to see it pay off.I'm struggling with the CEO being increasingly focussed on investing heavily in AI. I'm not opposed to using this tech at all – it's amazing, and we incorporate a variety of different ML models across our stack where they are useful. But this strategy has evolved to the point where we are limiting resource on key teams aligned with core business to invest in an AI team.The argument seems to be that they've realized the only way to achieve the next round of funding is to be "AI-first". There is no product roadmap for what this looks like, or what features might be involved, or why we'd want to do it from a product point of view. Instead the reason is that this is the only way to attract a big series C round.I'm not well-informed enough to know if this is the correct approach to scaling. Instead of working on useful, in-demand product features, it feels like we're spending a lot of time looking at a distant future that we'll struggle to reach if we take our eye off of the ball. Is this normal? Are other organizations going through the same struggle? For the first time in five years I feel completely out of my depth.
33 points by throwaway778 - 37 comments
The question is whether the key value of your product can benefit from the strengths of AI? If not, don't go there. If so, you then need to determine if your team can actually deliver an AI-driven vision that enhances the existing value prop. Again, if not, don't go there. If so, do it.
But from your description, your CEO is not asking those questions - they are asking, "How do we get more funding?" Which tells me that your CEO doesn't give a crap about building a product, they are just trying to make money and get some nice bullet points on their resume about the size of a company they led.
That puts you in the position of choosing whether you want to go on a VC-driven startup ride just to have the experience, or whether you want a product-driven role. People have their reasons for both directions, but if you want a product-driven role, you are out of alignment with your CEO and probably shouldn't work for them.
Include as much non-AI work as you can in the AI teams' projects, pitch an "AI efficiency initiative" that minimizes new spend on AI with the justification of other teams picking up the slack, talk up whatever ML you're already doing, etc.
(Also, huh - I wonder if that’s actually directly doable; “assembled by AI out of programmed outputs”?)
E.g. If you don't work on AI now, and AI models keep improving, how likely is it that a competitor who integrates AI well will eat your lunch? If it's >50%, it seems worth it to shift some focus to AI regardless of the series C round.
This post from a few days ago has some great tips on how to integrate AI _well_: https://koomen.dev/essays/horseless-carriages/
If investors only want AI, then you will either be forced to do that (whatever it means), do something else but make it look to them like AI, convince them they're wrong, or quit.
Things are a little more nuanced if your existing investors side with you but all new investors are AI-driven. Then you don't have to quit, but you do have to run the business without new outside capital. This may or may not be possible. If not, you still have to quit.
Note that starting a business with your own capital is not a way to escape it either, since you still have to answer to customers.
Sounds like the CEO is more interested in selling the company than building the product. IMHO that's a bad sign. It's also notable that you're aware of AI and use it to some extent. That means you have understanding of what it can and can't do. So why then is the CEO telling you how to do your job?
I've seen folks wanting big changes and we sit down and draw things up and surprisingly it looks like the old roadmap. Everyone is happy and I don't say anything about the similarities, and most importantly we're on the same page ;)
Sometimes when leadership asks for big changes, even when they say big changes, you might find if you get into the details it's not THAT big a change.
In the meantime don't let your mind run too wild assuming and worrying about what they might be asking for. I do that too, it's a developer thing I think, we start considering possibilities or even misused terminology and we get into a loop ;)
I once was in a company during the "everyone is going to replace their laptops with tablets next year era." The CEO pushed heavily for mobile, and underinvested in the actual product.
A year later, all of our customers were still using their laptops. We were sold to a private equity firm, the CEO was pushed out, and (almost) everyone who worked on the failed mobile product was out of a job.
In your case, I'd try to decide if your CEO is just following a fad. If so, next year they will follow a different fad. Are you critical to your business? If so, you'll be critical to your business with or without AI. If not, figure out how to make yourself critical to your business without being vulnerable to this year's fad...
(...And perhaps ask ChatGPT for advice. If you can't beat it, join it.)
So many companies invested vast engineering resources in building out iOS/Android apps only to later find that their users only interact with their tool once every few weeks, which wasn't often enough for them to earn a place in that relatively tiny list of a few dozen apps that any one individual actually uses.
For many users with cheaper phones asking them to install your app is asking them to pick which of their photos they're going to delete to make space for it!
Turns out someone already made a version with AI as the desirable technology du jour.
https://www.reddit.com/r/ProgrammerHumor/comments/1dckq74/so...
Most AI "deployments" I have seen, are glorified knowledge search engines, or query engines. There are some content/code assistants as well. It is also the least intrusive way to be "AI - First". There is too much noise, too little value , but yet a significant pressure to be an "AI company". Most startups are feeling this (including the one I work at).
Unfortunately, VCs are always blinded by the next cool thing to invest in. So I think of it as a marketing feature that you have to build, rather than any real roadmap thing.
Think about it like a research project. The company or its culture may not be prepared for that, but that's what it is.
Your product is not really the product. So the only thing that really matters is how your company is perceived to those who could potentially buy it and give your C-suite an exit.
This is the argument for virtually every company going AI-first: it's just a way to scam VCs.
It seems crazy but it really works.
You've two outcomes from this, either you do find a disruptive AI angle and move a sufficiently-large part of your team to it, or you don't, but figure out a minimal effort that would satisfy the "investor positioning angle". The third option, to do nothing or aggressively push back against AI and the CEO's desire, would potentially yield to no Series C or a down-round, which is something that you, your CEO, and your customers would not like.
As the engineer you need to support all three, while being the voice of realism (internally). But don't get confused when they conflict -- they always conflict to some degree.
If it's not an AI story for your business you need exceptional metrics. Like growing from 8M to 24M in a year for a C round.
If not, I'd say make a data-backed case for another course of action, or find another job.
Most CEOs I've worked with would be open to hearing a well-reasoned argument for another course of action.
Also presenting a good case can be a nice career move even if it's not adopted.
"useful, in-demand product features" have to generate revenue greater than cost. If its too low or execs think there are better ways to grow the firm then these decision happen all the time.
imho, I would like to think tough times are ahead of us - that in my mind, neutralizes my 'tech optimism'.
"If the the average CIO is committing 10 or 15% of their budget to AI. If you're not in that you're getting shrunk."
You want to start with at least an AI Roadmap that outlines whatever you want to do, and sprinkle in some AI love.