richiebonilla

Thanks! It's a subscription: $8.25/m billed annually, $12.99/m billed monthly

Sure sounds like it. Are you doing this for a team or yourself? You can use Clarity in either case, but I’m curious.

Not silly at all, it's an important consideration. The following is based on what we've seen work well.

The first place I'd start is by outlining your team's week in the Weekly. I'd finish any ongoing projects in their current tools and link to those other tools from the Weekly. This way those projects aren't disrupted, but you've now gained a central hub for your team.

As you start new projects, you can create a project doc in Clarity for each of them. Eventually the existing projects will be finished, or you can migrate what's left.

Next, I would start to conduct meeting notes in Clarity because any action items that come out of those meetings can be delegated and managed alongside your projects and their tasks.

Finally, you can start posting articles, ideas, research, and customer feedback in the shared notes feed in Clarity (rather than posting them in Slack/chat). This way chat is less distracting, and you can resurface those notes later by using tags. The notes feed gives everyone a chronological feed of notes shared by the team, without the distraction of chat.

Rather than conducting a huge migration from your current tools to Clarity, I find it's less overwhelming if you bring information over as it's relevant to your work. Not only is this less up front work, it also starts your knowledge graph off with a useful foundation.

Happy to elaborate further and answer any scenario-specific questions.

As for pricing, we are rolling that out this week. All Clarity bases are free to use for an unlimited period of time and with unlimited members. Each base has 1,000 free blocks per month [1], and can have up to 100 active tasks [2].

When you exceed either of these usage limits, you'll have the option to upgrade your base to a Pro subscription that is billed per member per month.

This is our only business model. We do not sell your data or any metrics derived from user activity. Privacy is our top priority.

[1] - A block is a unit of content (e.g. a paragraph of text, an image, a video embed, a checklist item). All documents in Clarity are composed of blocks. The 1,000 block limit resets at the start of each calendar month.

[2] - Tasks created, but not marked done, are considered active.

Sweet, we should connect. My email is in my bio. Feel free to ping.

Funny enough, our early prototypes were done using Google Docs. There are features in Clarity that were impossible to simulate there, which is what drove us to build custom software in the first place.

The two most obvious are: 1) declaring tasks across documents and visualizing them in a single task database to create filtered views of work 2) interconnecting docs by topics and keywords so that you can navigate your knowledge base more effectively

There's also a shared notes feed for async information sharing, nested projects, in-app notifications, and other features that fill in the whole picture. The outline block structure also makes your information queryable beyond basic string search, which enables new types of exploration through your knowledge base, notes, and conversations.

I also wouldn't underestimate the power of a default home screen. There's a lot of power in having an enforced front page vs a doc the team must remember to check.

It's a cohesive set of functionality built to support teamwork vs a generic collection of documents.

Thanks for the heads up. Our app only uses Intercom and Mixpanel. Are there any best practices for how to handle this so that Brave users can use the app and keep their privacy preferences intact?

Totally agree with you about templates.

Definitely see what you're saying about the Superhuman-like interface. We're still iterating there. We need to enable pro-level usage without hindering accessibility to casual users. We're continuing to simplify simplify simplify :)

We are currently testing an integration using the Loom SDK.

Will definitely take you up on the user interview. Thanks!

Yep, you can make any document public & readonly. We plan to add more options for public pages too.

Third thought's the charm!

Have a look at our demo video, those workflows are not possible in Notion :)

Great question. If you're looking at a single weekly doc, then you could write it anywhere. However, if you're working across multiple weeks, and you have a few projects in various stages of development, then Clarity saves you a lot of time & effort. Widgets summarize the work happening across your base, and backlinks help you look back across Weeklys, projects, notes, and conversations to resurface information according to keywords.

The issue with tools like Notion is that you need to do everything manually. The more powerful your system, the more work you have to do. This leads to what the Notion community refers to as “breakdowns”—where a workspace is overwhelming and must be redesigned & refactored to be useful again.

Hey HN! We're Richie and Eni, the founders of Clarity (https://clarity.so/).

Clarity is a SaaS product for distributed teams to track tasks, plan projects, and build long-term knowledge in one place. Instead of consulting multiple tools or maintaining a bespoke system, teams have a single weekly doc that pulls together their projects, tasks, and notes.

In order to function well, teams must maintain a shared mental model of their work. This is especially difficult for distributed teams because we don't have a physical space to reinforce context. To solve this, the Weekly is your team's front page throughout the week.

We've both been working remotely since 2014 and we met on a mutual client project in 2018. Clarity started as a side project to help us run our client work. Our clients were happy, but we were running it all manually behind the scenes. Last year we dropped everything to turn that system into a self-serve SaaS product.

What's unique about our approach is the combination of real-time collaboration, a knowledge graph, and a formal project management feature set. With a knowledge graph, teams can capture & retrieve information quickly without the friction & fragility of folder organization. Clarity's project management functionality can leverage the graph to centralize tasks and surface what's important to your work. This creates a high-context workspace without the maintenance overhead.

Distributed work is only becoming more popular. We believe the next decade of the Internet will be more collaborative than the last. As a result, we'll need tools built specifically for collaborative Internet squads to assemble around a project or a cause. We're building the spaces on the Internet where that happens.

Check out our demo video: https://youtu.be/PDKgvD5BEgE.

I agree that following browser default behavior is more intuitive in general. I'm not a fan of scroll jacking.

I'd say apps skew towards mouse-heavy because controls are on-screen and therefore discoverable. It takes a good deal of product-market fit before you can count on your users knowing/caring enough about your app to remember keyboard shortcuts.

Most apps are grown by adding users, so optimizing for the new user is more important to the business until a certain level of maturity and market saturation is reached.

Applications with a dedicated professional user base can go deeper into power-user territory sooner since they can charge more per user, and new users expect there to be a learning curve.