These are very generous consultant pitch #s not reality. We doubled running 1-$200k/guy … 2x full stack devs (me) 2x data guys 1x MSP for IT.
That team was awesome and did serious buzz saw damage because we shipped solutions that made the company better every day.
Didn’t have to be huge. Just help someone do something better.
That adopted mentality pays off tech debt fast.
At least that's how I feel about team sizes.
I don't think the numbers OP chose really matter. The point is to do the exercise. Try and work out some numbers on how much the current software is costing, how much room there is for improvement and how much investment it will take to get there. Add a big margin to account for all the uncertainty with building something out.
If the numbers still work out significantly in favour of writing your own software then it may be a project worth considering.
Not saying that this is astroturfing, just that this format has been around forever.
$5m is a solid number to ballpark any new initiative from scratch.
Do people just pull random numbers out of their ass with no actual experience? 99% of developers do not live in Silicon Valley on 1m salaries.
And to be honest, I'm not convinced a moderately complex in-house crud app would really require 5 senior developers but impossible to have a strong opinion on that based on the details that OP provided. It might be a one man job, it might take a team of 10..
If you have a four person team you drastically reduce the bus factor. It also means you can have people routinely pairing on things which can be hugely impactful when working on new software in a new domain like this.
But let’s say they have a 5 man team for in-house development. 1.5m/yr would be a stretch to spend.
That’s a weird question to ask someone who stated their relevant experience in the first sentence of their comment. I just looked him up on LinkedIn and it checks out, you can do the same.
If you have substantive objections to what he wrote, perhaps it’s better to state them explicitly? You seem to say that the figure he suggested is based on developers being based in a very expensive location, and therefore not generalizable.
What numbers have you come up with that contradict his?
Avg salary in the U.S. is 105k. Better to go on average as you’re not going to high 10 seniors. That would be dumb. Hell getting 10 for an in house app is just as dumb. Hosting? On an in house app. If they spend more than 100k in the first year that’s dumb too. Support for an in house app? That’s part of the dev team. Tooling? For what? Some IDEs and few dev tools like slack etc. Let’s bundle it with their equipment. 100k for some computers and software.
I don’t understand how HN has to always look at the extreme pessimistic side to everything. The type of people here are the ones who go into a business and spend insane amounts of money building junk software wanting to pull in 5 different databases, 3 caches, elastic search and host their 10 years on 25 “microservices” hosted in docker that falls over multiple times a day when 95% of the software people on HN build could be hosted on a couple of load balancer servers with a single db instance. Spend way too much money trying to solve non existent problems.
A team of 5 senior freelancers in Europe will cost about 150-200k per person.
Median compensation for senior engineers in Europe is nowhere near 150k. Even in Switzerland.
Office space
Hardware and software, SaaS licensing, cloud costs, etc.
Hiring costs (recruitment, recruiters, time lost in selection and hiring)
Secondary cost to rest of the business to change processes, retrain, integrate, help the dev team understand requirements, effectively build and iterate, etc.
Quite possibly a bunch of compliance, security, audit, pen testing, and other regulatory costs depending on the demands their clients have, etc.
Running a team != hiring a bunch of freelancers as a one-off.
You don’t make tax contributions for them. They bring their own hardware and usually software unless otherwise agreed.
The rest of the stuff is just a laundry list you made up to try and blow costs way past what they actually could be if you’re prudent. Come on
Funding (and related longevity) are key drivers of technical debt. If a team has to constantly pivot projects to politically justify their existence, bad technical things happen.
So figure out a budget model that works, is sustainable, is justified on ROI (as logistics dev will be compared to capex alternative investments).
As a "halfway" solution, you could find 1-2 senior inhouse architect type people (ideally, who have reasons to stick around like quality of life) and pair them with project-based freelance/outsourced development teams. (Hard to find good small dev firms, but they exist)
That way, if dev screws up the project because they're incompetent, you have more options. But you retain the core institutional knowledge and some dev ability inhouse.
And it maximizes budget flexibility and gives you time to find the right people for the inhouse team.
I would caution... the goal of this arrangement should always be to grow the inhouse team until it's big enough to ship projects on its own.
But it's easier to slowly grow a good team than to hire one all at once.
My first question is to check the basic economics:
$2-300M in annual revenue, ~15% margins, you’re probably looking at earnings/profits around $30-45M. Building and running your own software team is probably around $5M/year, which feels like it could be a substantial hit to your margins. Is there a clear story for how this software will allow you grow to $300-500M in revenue or more? I like to have a credible story for 5-10x ROI on software development because the costs end up being so variable and uncertain.
Then the trick is figuring out how to hire, train, and establish a productive environment for the team. My customers approach was to hire a vendor [Pivotal Labs] to ship a first release and help hire in-house staff to replace vendor roles until the team was fully in-house. The customer got rapid feedback that the team and concept worked; we shipped working software. The new hire landed into a productive context, and could see that the company had an effective approach to software development (because it was already shipping working software).