10 templates. A template is a whole page, like a landing page or a dashboard, built from website components, blocks, and components.
A small company that makes one product for the people who run teams.
We ran teams for years with a spreadsheet, a shared calendar, and a chat that never stopped. Every week someone missed the change of time.
So we built one place for who is coming, what is planned, and how each goal is going. Our own teams used it first.
We still answer every message ourselves.
12
People on the team
Across 6 countries
3
Offices
In three time zones
2019
The year we started
Every screen says what it does in words a new member understands.
Anyone can download what we hold about them, or ask us to delete it.
Each page loads quickly on a slow network and an old phone.
Free for one team. No card needed.
A whole about page, built from our website components: a floating navbar, a page title, the story beside its headline, a few figures, what you hold to, the people, a closing band, and a footer.
Product news, guides, and notes from the team.
Product, 4 min read
Put files in one folder that the whole team can open, and choose who can change them.
Design, 6 min read
One meeting, a short list, and notes that stay on the design.
Product, 3 min read
Find a document by a word in it, not only by its name.
Engineering, 9 min read
What we changed so a team of a thousand sees edits in under a second.
Company, 2 min read
More room for the team, and a place to meet the people we work with.
Design, 7 min read
How we check every pair of colors before it ships.
Engineering, 6 min read
The steps a team can follow from the first list of changes to the day it ships.
Free for one team. No card needed.
A whole blog index, built from our website components: a floating navbar, a page title, every post with the newest drawn wide and a row of tags to narrow them, a closing band, and a footer.
Every release, newest first.
Save a filtered view of any list and share it with your team. Everyone sees the same columns and order.
Search now answers as you type, across every workspace you belong to.
Make a key that only reaches one project, and see when each key was last used.
Leave a comment on any file, and mention a teammate to ask them to look.
Free for one team. No card needed.
A whole changelog page, built from our website components: a floating navbar, a page title, every release newest first with tabs to narrow them to one type of change, a closing band, and a footer.
Ask about plans, get help with your account, or tell us what to build next.
A whole contact page, built from our website components: a floating navbar, a page title over the ways to reach you, a form in one soft card, a FAQ, and a footer.
One app the whole team is in. Leads and members each get their own dashboard: who's coming, the plan, the calendar, and how each goal is going.
Used by teams at
Set the team up
Leads plan events and check who is coming. Everyone answers for themselves.
Everyone answers
Every meeting and event has an answer-by date, so nobody chases replies in a chat.
Watch the count
The number going sits on the event, and the list fills in as people answer.
Pick the event, and the email takes people straight back to it.
When an event changes, calendar apps pick up the new time.
Track goals by team and quarter. Everyone finds their own progress.
Availability, reminders, calendar feeds, and roles sit together around the week.
Talk about the work and keep in touch in the channels you belong to.
Attach a saved agenda to another event, or copy it for the next one.
The person who texts their lead still gets counted. The lead sets the answer.
Review someone's past check-ins before deciding what to discuss next.
Add the team calendar to any calendar app once, and it stays up to date.
Any member can download what we hold about them, without asking first.
Members can ask for their account to be deleted, across every record.
When an event changes, every phone shows the new time on its next refresh.
| Team task | Workspace | Shared table | Group chat |
|---|---|---|---|
| Who's coming, with an answer-by date | Included | Manual work | Manual work |
| Reminder email to whoever hasn't answered | Included | Not included | Not included |
| A calendar on everyone's phone | Included | Not included | Not included |
| Team and admin roles | Included | Manual work | Manual work |
Monday mornings used to start with forty messages. Now everyone answers in one place, and I know who is coming before I book the room.
Setup took an afternoon.
People stopped asking me what time the all-hands is. That alone was worth it.
We had three spreadsheets, a group chat, and a whiteboard in the office. Now we have one list that everyone trusts.
I can see who is out before the shift starts, so I plan the queue around them.
The reminders go out on their own. I have not chased a late reply all quarter.
Tell me how the week runs, and we'll set it up together.
A whole landing page, built from our website components: a floating navbar, a split hero, a logo row, bento grids, a comparison, a testimonial wall, pricing, a FAQ, and a footer.
The steps a team can follow from the first list of changes to the day it ships.
A release goes better when everyone knows what is in it, who owns each part, and when it ships. These are the steps a team can follow, from the first list to the day it goes out.
Start with a short list of what the release changes. Keep each line to one change, and give it one owner.
Pick the day it ships first, then work back from it. Leave a few days between the last change and the release, for testing.
Move the release, not the testing.
Run the checks on the release branch with npm run check. Every check must pass before the build goes out.
Post the notes where people already look, like the changelog and the team channel, and name who to ask about each line.
Product, 4 min read
Put files in one folder that the whole team can open, and choose who can change them.
Design, 6 min read
One meeting, a short list, and notes that stay on the design.
Engineering, 9 min read
What we changed so a team of a thousand sees edits in under a second.
Free for one team. No card needed.
A whole blog post page, built from our website components: a floating navbar, the post with its author and a list of its sections, other posts to read next, a closing band, and a footer.
A whole pricing page, built from our website components: a floating navbar, a two-tone page title, the plans side by side, a comparison, a testimonial wall, a FAQ, and a footer.
A projects page with board, list, and timeline layouts that share one shell per project.
A whole projects page for an app: the left rail beside one set of projects shown as a board, a list, or a timeline. On narrow screens the rail moves into a menu.
A whole product website in page files: home, pricing, a blog with a page per post, a changelog, about, and contact, with one navbar and footer, ready to run in a Next.js app.