Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Weaveworks is shutting down

linkedin.com

Post reply on HN
Print view View original

61–70 of 266 posts

Re: Weaveworks is shutting down

#61

Post by catherinecodes »

gangstead wrote: post #56
mad_vill wrote: post #13

I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main revenue driver is consultancy. Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s.

> smaller consultancies that have awesome developers that build customer tooling on the side I've worked at a couple consultancies and they were always chasing after that recurring product revenue. I grew to believe that it isn't possible under that business model. When you are running a consultancy you are in the business of marking up developer hours: find a client to sign a contract for $150 / hour and hire a cons…

Right. I wonder what their cost structure was like. $10 million in revenue is enough to support a decent-sized team.

Re: Weaveworks is shutting down

#62

Post by sytringy05 »

xenophonf wrote: post #34
marcinzm wrote: post #21

Earlier quoted context omitted.

> Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s. Not really, the space has simply grown faster than these companies could keep up with and were left behind. I can code up a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions in well under a week. With docker compose for local…

> a CICD pipeline that does per-PR namespace isolated deploys of an app stack on EKS using Github actions... [with] docker compose for local testing Please teach me, oh wise prince!

“it’s that easy!”

Re: Weaveworks is shutting down

#64

Post by ralph84 »

ushakov wrote: post #4
tnolet wrote: post #3

I was following them on and off as they started around the same time I started a company in similar space and we shared an investor. Similarly, Armory.io also got sold in what seems a fire sale ($7M after raising $200M). Goes to show how hard this space is.

There’s no money in DevTools. Businesses will see you as cost, not asset

Atlassian’s market cap is $55 billion. GitLab’s market cap is $11 billion. GitHub sold for $7.5 billion in 2018. There’s money, you just have to be more than a point solution.

Re: Weaveworks is shutting down

#65

Post by master_crab »

FourierEnvy wrote: post #40
swozey wrote: post #36

Earlier quoted context omitted.

Hell, we do it once in terraform/pulumi/cdk and then it takes 10 minutes to tweak some variables and switch aws accounts and bam Our devs/SRE put up apps and clusters in minutes (aside from the terrible alb/ecs/eks/etc deployment times).

Yeah this is nice if you have large teams and repeatable projects. Smaller companies have much more ad-hoc requests. I stood up an entirely new type of project end-to-end from a docker compose into our cluster. Re-used alot of code base but it was still a bit of work. Much less than it used to be though.

This.

We looked at weaveworks and its competitor both as a product and an investment (mid 6 figure usage). Our big issue was that we had a lot of smaller teams doing different things and not one or two featured items raking in the majority of our revenue.

These solutions work if you have a bunch of snowflake workloads by design (or bad design).

Re: Weaveworks is shutting down

#66

Post by nixgeek »

catherinecodes wrote: post #61
gangstead wrote: post #56

Earlier quoted context omitted.

> smaller consultancies that have awesome developers that build customer tooling on the side I've worked at a couple consultancies and they were always chasing after that recurring product revenue. I grew to believe that it isn't possible under that business model. When you are running a consultancy you are in the business of marking up developer hours: find a client to sign a contract for $150 / hour and hire a cons…

Right. I wonder what their cost structure was like. $10 million in revenue is enough to support a decent-sized team.

According to LinkedIn they were 50-200 employees which after excluding all the other costs for running a company, is definitely not enough to cover the fully-burdened payroll of even a 50 person organization that’s probably predominantly Engineering types, that assumption being if most people are US-based (or if they don’t do “location based” pay, and indexed off a more expensive location).

Re: Weaveworks is shutting down

#67

Post by danjrslp »

gangstead wrote: post #56
mad_vill wrote: post #13

I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main revenue driver is consultancy. Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s.

> smaller consultancies that have awesome developers that build customer tooling on the side I've worked at a couple consultancies and they were always chasing after that recurring product revenue. I grew to believe that it isn't possible under that business model. When you are running a consultancy you are in the business of marking up developer hours: find a client to sign a contract for $150 / hour and hire a cons…

I agree. Being good at running a consulting company does not translate to being good at running a product/SaaS/devtools company.

Re: Weaveworks is shutting down

#68

Post by [deleted] »

gangstead wrote: post #56
mad_vill wrote: post #13

I feel like the next generation of this type of company is smaller consultancies that have awesome developers that build customer tooling on the side. But the main revenue driver is consultancy. Also it really feels like all the air has been let out of the docker/kubernetes/cloud-native balloon that was so popular in the late 2010s.

> smaller consultancies that have awesome developers that build customer tooling on the side I've worked at a couple consultancies and they were always chasing after that recurring product revenue. I grew to believe that it isn't possible under that business model. When you are running a consultancy you are in the business of marking up developer hours: find a client to sign a contract for $150 / hour and hire a cons…

[deleted]

Re: Weaveworks is shutting down

#69

Post by pyb »

javierluraschi wrote: post #18
mihaitodor wrote: post #9

Sometime last year, they had someone cold call me from the US to sell me stuff. I’m not sure where they got my number from, but I don’t think that’s a good strategy for trying to sell B2B solutions.

What's your ideal B2B sales strategy that would work for you?

Look up "permission marketing"

Re: Weaveworks is shutting down

#70

Post by dilyevsky »

gtirloni wrote: post #53
dilyevsky wrote: post #30

Earlier quoted context omitted.

They’re cheap until the management realizes they just spent a year (so like $300k) educating their devops how cni works and they bounced to faang or some other startup so the project needs to be scrapped or restaffed again and started over. That’s where the services come in. Also yeah it’s well known ICs view saas as direct threat so everyone tries to skip them and go directly to KDM. That’s the reason nearly all ent…

I think the comment you're replying to meant to say developers are cheap in the sense they allergic to spending money, not that their time/salary is cheap. Example: "John is a cheap bastard. He never spends any money or buys the cheapest options".

Oh right, yes i misread that. Not like they have any budget anyway
Post reply on HN