Launch HN: Livedocs (YC W22) – Live data in your documents, without code (livedocs.com)
Working on early stage teams in the past, I got tired of tracking and reporting even simple metrics. My team would resort to either esoteric hacks, VBA scripts, or simply nagging data guys for metrics—even simple ones. Tracking metrics from multiple tools is a pain in the neck.
That’s when I realized most teams rely heavily on software that already offer some sort of embedded analytics on their dashboards. All they needed was a way to compose data from these dashboards into a single place.
Livedocs lets non-technical users track common metrics like retention, MRR, etc by connecting directly to tools via OAuth. IMO, until teams or projects hit a certain size or success, writing SQL queries or hopping between different dashboards to track simple metrics is overkill. So we let these users build live reports and documents using pre-built blocks that connect to their tools directly.
For example, solopreneurs, super-early stage startups, and small businesses use us to keep track of metrics like MRR, churn, web traffic, and product analytics like retention, activation, etc., from Stripe, Google Analytics, and Segment. See here for what that looks like: https://livedocs.com/doc/1e2e4001-ed5a-44ad-8d13-806deafdde9....
To pick another example: side projects! I have so many side projects, each with their own Google Analytics, Stripe, and sometimes Twitter account that I lose track of how each is performing. Now I just set up a quick report on Livedocs for each—like this: https://livedocs.com/doc/46a38473-e525-4482-aa46-4da4a77cf18....
We call these “live documents” because they are like a document with live variables, graphs, etc. The closest comparison would be a dashboard, but way more flexible—e.g. as editable as a document.
I also wanted these documents to be easy to replicate for other projects and quick sharing, so I built a templates feature into Livedocs. Commonly used templates are listed here: https://livedocs.com/templates. You can easily clone one and connect it to your own data sources to get started, so please feel free to try it out.
We charge $30/month and offer a free 14 day trial (without a card).
I’m keen to hear your feedback!
49 comments
[ 3.3 ms ] story [ 116 ms ] threadQuick question: how do you plan to compete with existing platforms like Notion and Coda? For them, this could be just another block element type that they could ship with minimal effort?
Segment doesn't have a built in visualizing layer, and relies on destinations to handle that (like Mixpanel, etc)— but even there, non-technical operators are lost because they have no mental model of how to transform a stream of events into something like, say, "Activation rate" or "Retention curve". We connect to Segment and have pre-written the SQL required to generate these commonly used metrics.
I applied to YC almost a decade ago with a company called LiveDocs. Didn't get in at the time (I applied again w/ a different name), but glad there's finally a LiveDocs in YC :)
I'll tell ya, at the moment, this isn't quite where I need it to be, because every team I work in/with is entirely Drive / GDocs-centric, and so what I'll need in the long-run to roll it out is a native integration within that interface. I'd love for GOOG to just buy y'all and integrate that capability into their rapidly-growing Workspace capabilities. Until then, watching with great interest, may play around with it a bit.
We're trying to work with Google Docs currently. We're aware of the huge switching cost that comes with adopting a new editor, and we're trying to integrate with Drive/Gdocs. Will keep you in the loop!
- https://coda.io/
- https://patera.io/
- https://grid.is/
I've tried Coda a couple times, but have always ended up at the same roadblock encountered with Airtable / Smartsheet / etc. - any "power user" type integrations require learning entirely new workflows that don't translate to any other system. Put another way, these systems should obviate the need for dedicated "Rev Ops" headcount, but the narrow scope of applicability of Coda knowledge (traditional stack knowledge translates poorly into Coda; Coda knowledge translates poorly into any other system) has always meant it's felt like more work than upside, at least in my use cases.
The other two are new. Patera is gorgeous, and the very definition of elegant, based on what I can see. I could easily see myself running proposal documents through something like this to make them much more scalable.
Grid is even more interesting, though I'll have to dig in. A huge crop of dynamic forecasting tools (effectively masks over spreadsheet backends) seem to have sprung up in the past 18mo - I'm most familiar with Causal, but this goes a meaningful step further. Will be digging into it this week.
Appreciate the reccs.
Our documentation and discoverability is currently zero, and the rich text feature is in development, but another space to watch if you’re into this kind of thing.
I also added a bibliography page, so you can see other apps in this space: https://inflex.io/blog/bibliography (“Vaguely similar market products”)
Agreed.
The default output of a spreadsheet these days should be an embedded web component. Live graphs, linked to data source, edit and customize.
At another startup, over the weekend, we connected tableau to our DB (which was also pulling in mixpanel via API) and scheduled reports to be sent to every employee.
I like the idea of live data which can be a dashboard of sorts, as to how I can see myself using it. Connect your data source (eg segment) -> Use prebuilt queries -> it gives an overview dashboard which can be sent to everyone as a report in email every morning -> If people are reading it, makes your job easier. (of course, use it as a live source for wherever and whenever people open it.) makes all the meetings and discussions easier.
BTW, you can also setup Livedocs documents to automatically send to a slack channel and/or by email daily.
We're focused on allowing non-technical folks to track metrics and data from third party tools (although we do also support pulling live data on tickets/PRs from Github too, as that is something that most operators, particularly founders at early stage co's are interested in tracking to see dev team activity, open bugs, etc)
I’ve spent quite a few hours on it and am nowhere near done. Looks like this will save people some serious time. 1-click live data entry is a really powerful selling point.
The end goal is to combine all 3 into one place that I have complete control of. (And make a bunch of cool looking graphs to look at)
Thiro [https://apps.apple.com/us/app/thiro/id1555982483] a basic time tracker that does grouping and reports right. The only thing it lacks is billable hours.
Emerald [https://apps.apple.com/us/app/emerald-money-journal/id143705...] A super simple expense tracker that does most things right, but unfortunately has a few bugs. It’s the only one I could find available that is privacy friendly and doesn’t have bloat.
Both of those apps are made by indie devs and have no subscriptions.
In addition, I am trying out timeator[https://apps.apple.com/us/app/timemator-time-tracking/id1458...] which has the right idea for how I want revenue and time tracking to be integrated.
Notebook styled tools were the inspiration for Livedocs, for sure.
You could integrate directly into Drive so customers can create LiveDocs from Drive, and get marketing exposure in the marketplace.
Beyond that, integrations with CRMs like Salesforce could also be really powerful for a too like this.
Also, have you considered integrating with a tool like Zapier rather than integrating directly with each app to accelerate the number of apps you’re integrated with?
Re: CRMs, we currently work with smaller teams who use CRMs like Hubspot (we have a Hubspot integration), but salesforce could be interesting too.
Zapier I believe doesn’t give you data in a structured format, rather a series of “events” as and when they happen. This is workable, Ofcourse, and I will look into it today.
Thanks for the feedback!
Prebuilt reports vs interactive custom data exploration
Does that make sense?
let me know if you need help!
Check out this template which has an example – https://livedocs.com/templates/4cc353b1-f771-4e07-ae68-2f3d8...