Twitxy Saved

Routine

@routinehq

Experience the next-generation, all-in-one platform for professionals and teams to get more things done, faster! Download now for free.
Paris, France routine.co/get-started Joined December 2020
38 Following 3.3K Followers 2.1K Posts

Latest posts 5

Routine @routinehq
One of the most interesting things in SaaS over the past decade is how very different products slowly converged into the exact same category.

Consider these starting points:

- Asana started as a fast way to capture and manage tasks.
- Airtable began as “spreadsheets meet databases.”
- Coda tried to reinvent documents by embedding the power of spreadsheets.
- Notion focused first on notes and personal knowledge management.

Four completely different entry points.

Four completely different mental models.

Yet today, they all look surprisingly similar.

Projects.
Knowledge.
Databases.
Custom fields.
Views (table, board, timeline, calendar).
Automation.

Because they all realized the same thing: companies don’t want dozens of disconnected tools.

They want a work operating system.

A single place where teams can structure information, run projects, document knowledge, and adapt the system to how their organization works.

And we’re still early in figuring out what the true OS for work should look like, in particular with AI that is shifting everything.

What do you think?
Routine @routinehq
Want to thrill your community? Do this one thing and you will... 👇

Close the loop!

Most companies “collect feedback” for their benefit i.e to find frustration and detect opportunities.

But rare are the companies that do it for the benefit of the user/customer.

Here’s how we do it at Routine (with a bonus point you can apply):

1️⃣ Be everywhere: Slack. Discord. Reddit. X. Email.
2️⃣ Make it easy for the reporter. We never ask users to fill forms, we just collect feedback wherever they report it
3️⃣ We collect the feedback super quickly by applying an emoji, label or else depending on the platform.
4️⃣ The feedback flows to Routine where we categorize everything (bug, feature, integration etc.).
5️⃣ We use the popularity of requests to take decisions on future developments.
6️⃣ Once we start working on something that has been requested, we press a single button which triggers an automation that notifies all the users by email to tell them we've started working on what they reported. That's a bonus which is super appreciated by the community.
7️⃣ Once the development is done, we press another button which closes the loop and notifies the reporters by email once again, this time to tell them that it is done.

Not only will your community be amazed (because nobody does it), but this is a chance of re-activiting users you've lost.

People don’t just want features. They want to feel heard.

When users see their feedback shape the product, they stop being users. They become advocates.

And advocacy compounds...
Routine @routinehq
LLM still heavily rely on frameworks and online documentation to know how to structure code, even though they still poorly do, in particular when it comes to rearchitecturing & factorizing by itself.

But if we assume that AI will get better, why not ditch Javascript which is super slow and unreliable (even though that part we could assume it's a problem only for humans as AI will not make mistakes) in favor of low-level code that is faster e.g assembly (WASM) or even machine code?

Let me know what you think.