Most repeatable processes in Google Docs are still:
copy the old doc → rename it → manually update everything
Alpine templates let you use lightweight {{variables}} throughout a document.
Enter values once and every reference updates automatically
Long Slack threads fall apart fast.
Someone replies to point 2.
Someone else replies to point 7.
Now everyone’s copy-pasting quotes trying to preserve context.
In our app you highlight text and reply directly. Every response stays anchored to the exact phrase it references.
In Google Docs when you share a doc it goes into the black hole of email
In our integrated chat + docs + tasks work app when you share anything it goes into your chat!
Right in your chat inbox along with the rest of your conversation history. I love this feature.
Linking to a Linear project in Notion/Slack could be so much better
We built an app where tasks/docs/chat are bundled together so you get:
- Live preview of task status
- Click to open a full task viewer you can read/edit
- Simply @ mention the task to reference it
Slack, Linear, and Notion have a bunch of confusing dropdowns/syntax if you want to search for "stuff by person"
We built an app that just reads english
You know where I'm still handwriting artisanal code?
Not in an IDE…in docs/chat, surprisingly
Since I write specs for my agents in docs or send code snippets over chat to engineers
So we added common IDE keyboard shortcuts to our editor (auto indent, balanced parens, etc)
How many times have you opened a chat then forgot to respond because it disappeared from your life forever?
(I've done this way too much…)
Marking messages as read when you open them was a mistake
We built an app where notifications only go away once you reply or react
This is a sign that you need an agent command center
You're using 5 agents but how do they share context? How do you get work done without constantly switching between 5 different apps??
We're building the best API/CLI/MCP for agents so you can direct them all in one place
I'm a little lurker. I love lurking. Slack makes it impossible
I just want to see what cool things my coworkers are doin so I can learn from them
We built an app for the lurkers where all the docs/projects/channels from your company go in one algorithmic "for you" feed
You ever just... give up and leave an image in the middle of the page because you’re trying to hard to make it look nice? Not anymore
We made it so creating beautiful documents is easy. Drag, drop, float and your content automatically flows around it
Notion/Google Docs comments are the worst…they cram all your conversations in the margin
1. You can't read the doc without getting distracted
2. You can't have proper, in-depth, conversations about the doc
We built an app where comments don't leave your doc a cluttered mess
@InsiderPresider it depends on the quality of code that you write :)
it's way better at collecting context than me that's for sure
also better than me at solving bugs in an area of code i haven't touched in a while
Adding Cursor agents to Alpine is a gamechanger
Customer bug comes in, I drop a comment and Cursor starts digging, all inside the same task. Bugs get fixed, it finds the context it needs, and all I had to do was type @
Stop losing your docs in the Google Drive/Notion blackhole
We built an app that has both your chat/docs/tasks in one place. Your teammate asks for the spec. @ it. Preview drops in chat. Done
Stop clicking through a calendar every time you schedule a task
In Alpine you just drag it into the right section of your week and the due date sets itself
Our task tracker supports MILLIONS of tasks in a single project without blinking an eye
This is leagues above what Linear/Asana/Airtable/Notion can do on their best day
Let me tell you how we did it: the database we use is OpenSearch!
At my former employer (Airtable) I had this realization. At the same time as Airtable was struggling to filter/sort/display 50k records in a project we were using OpenSearch to filter/sort production logs (a massively larger dataset) and OpenSearch didn’t even blink an eye when aggregating 200k results.
But OpenSearch alone isn’t enough. It has loose durability guarantees and it takes 5-10 seconds for data you write to show up in the index. So here’s how we architected our task system:
1. CRDT event log in DynamoDB. This is our canonical source of data for the task system. OpenSearch is a materialized view on top of the CRDT event log. CRDT means we don’t need a centralized server to make commits.
2. Realtime service with WebSocket connections to clients. When a client makes a task query with filters/sorts we run the query on OpenSearch (fast but up to 15 seconds stale) then we replay the last minute of CRDT events (which we keep in memory in each realtime service) to get the latest data.
We haven’t found an upper limit yet that this system can’t handle. Tested against a million tasks in a project and our task tracker was as fast as ever.