It takes your instructions, write a versioned spec, then generates a hybrid workflow of code+LLM calls and protects it with tests/evals
The result is that the agents run much faster (90% of it is code), cheaper (LLM steps are scoped tightly and uses smaller models) and reliably (specs get turned into coded state-machine)
The only real way to see this if you have consistent evals for common usecases in your B2B SAAS product and see if the tricky usecases are being solved. You'd then go down to the cheapest model that can solve the evals.
Dropbox has deep integration ecosystems, runs your company's data, I think its a no-brainer for it to become the agentic memory for your company if done right with it syncing data across all company services.
It's a great product. They had the brand, the capital, and the user base to become what Slack, Zoom, or Notion became. Instead, they spent a decade fighting a losing battle over storage pricing with Google and Microsoft. Their lack of a second act is due to a failure of product vision and enterprise execution.
And they had Paper, which was an excellent product (I was at Dropbox a decade ago; we all used Paper constantly and it was great) very close to what Notion later became. They never got it over the hump to wider PMF — like you say, a failure of product and of enterprise execution.
(Given that it was so close to Notion, I think Paper is one area where the product vision was on to something good; but they didn't succeed at product execution, connecting customer feedback to iterating correctly on product improvements.)
Never worked at Dropbox, but I absolutely loved Paper.
The problem at Dropbox seems to have been that there was no cohesiveness to all the products. Paper, Passwords, Sign, all seem to have never been truly integrated into a single experience. Each one felt like it was trying to have its own identity.
Yeah, when signing into Paper it always felt pretty silly how the auth flow was all like "are you sure you want to share your Dropbox account info with this Paper thing?" as if it was some third-party service.
Ironically, just within the last year Paper has gotten much more integrated into Dropbox as a single UX. And… it's significantly worse: slower, clumsier, harder to navigate. (I don't think there's any inherent reason those had to be correlated; it's just that Paper has clearly been destaffed a lot in recent years, so naturally any new changes will tend to be less polished.)
Another issue: Paper was tied to your Dropbox account.
From Dropbox's perspective, this sounds great. Accounts become more useful and valuable. The addressable market of a Dropbox account grows! Plus, everyone has a Dropbox account already, right?
Unfortunately, it turns out that business customers generally don't deploy Dropbox wall-to-wall. It's expensive. Not all employees need file sync.
A Dropbox account ends up being an obstacle to adoption.
And a distraction: a common account creates an irresistible urge to spend a lot of time finding ways to tie this new product into the old one.
I'm not sure I ultimately buy that Dropbox is expensive - for one thing, Notion now charges basically the same as Dropbox, and you don't even get file sync in the deal.
I can definitely believe that that was an objection customers had, though. I just suspect that what it really meant was another way of expressing that there wasn't PMF - if the PMF were there, they'd have willingly paid, just like they do now for Notion or Slab or what have you.
And yeah, there was definitely some energy going into trying to tie the products together more (putting Paper docs in your Dropbox folders) - and when that finally shipped it sadly made the Paper experience worse, not better.
I don't see the need to become bloated like slack and a one size fits all application. They do a great job with the product they have. Is there anything wrong with just being what you are? Why does the lack of a second act need to be a bad thing if your first product is great and still extremely valuable?
I would also if anything put Zoom in with Dropbox, they have a product that is by far the most enjoyable to use in that space, but any other offshoot is not worth it.
Teams being free doesn't make teams good. Just like Google Drive and OneDrive being packaged in for cheap doesn't make them good. It is clear why they are lower value.
> They had the brand, the capital, and the user base to become what Slack, Zoom, or Notion became. Instead, they spent a decade fighting a losing battle over storage pricing with Google and Microsoft
Is the alternative not likely that they would have spent a decade fighting a losing battle over office software with Google and Microsoft? Paper was a great product but the big guys have vertical integration so companies prefer their end-to-end solutions (GSuite etc) and I don't see how Dropbox could have easily overcome that.
> Is the alternative not likely that they would have spent a decade fighting a losing battle over office software with Google and Microsoft? Paper was a great product but the big guys have vertical integration so companies prefer their end-to-end solutions (GSuite etc) and I don't see how Dropbox could have easily overcome that.
Slack, Zoom, and Notion all argue against that. Yes, they have to compete against Google and Microsoft's integrated solutions, but they're good enough that they have held their own. Of course they would be bigger if Google and Microsoft didn't have such products.
There are so many research papers; just finding a solution to, say, a bio problem in a deep math paper would be a gold mine of opportunity. Very exciting times!
I've been thinking about this and I believe the best place to be is a scientist who keeps looking at an AI's output, prods it in the right directions, verifies the proofs, fixes and fills gaps, takes the proof to production with safety, risks etc mitigated and then distribution with a company wrapped around the discovery. I think it wouldn't be black-boxed as much and will require a lot more understanding and reviewing to trust and productize it.
Also I'm a little bitter, prior to this I never had trouble getting my username on websites. No one used this combination of 4 letters for godamn anything.
It's going to be dramatic - it's unclear how much of their DAUs are organic and how much is through their PE usage deals. There's a large amount of organic usage certainly, it's a useful tool, but there are quite a few of the tell tale signs that they have an internal number they want their user acquisition to be at and they're failing to meet that through organic growth.
couldn't an llm be used for verification like we're seeing some OSS projects do? Some projects are moving so fast, its almost certain there's little human involvement.
It takes your instructions, write a versioned spec, then generates a hybrid workflow of code+LLM calls and protects it with tests/evals
The result is that the agents run much faster (90% of it is code), cheaper (LLM steps are scoped tightly and uses smaller models) and reliably (specs get turned into coded state-machine)
reply