About
We think most project tools make the work harder.
Not because they lack features — because they have too many, spread across too many products, none of which know what the others hold. Projects.chat is an attempt at the opposite.
One place per project
If a piece of information belongs to a project, it should live in that project. Not in a drive, a wiki, a chat channel and a spreadsheet that each hold a quarter of it.
Writing beats meetings
Written things can be searched, quoted, corrected and read by someone who joins in six months. Meetings can't. We're biased towards the durable version.
AI should remove admin
Not add a chat window that knows nothing about you. If it can't draft the update you were dreading, it isn't earning its place in the sidebar.
What we're deliberately not doing
Every product decision is also a decision about what to leave out. Ours, so far:
- No per-seat charge for clients. Charging you to talk to the people paying you is backwards.
- No configuration weekend. If a project needs a setup consultant, we've failed.
- No engagement metrics. We don't want you in the app more; we want your project finished.
- No training on your data. Ever, under any plan, for any reason.
- No lock-in. Full export on every plan including Free, from day one.
Who's building it
A very small team, in the open, in Ruby on Rails. We're shipping the core before the extras, and we'd rather have a hundred teams who love it than ten thousand who forgot they signed up.
If you want to shape it, the waitlist isn't a mailing list — we email people, ask real questions, and change the plan based on the answers.
Come and be an early one.
The first teams in have disproportionate influence over what this becomes.
Free to join. One email when your invite is ready — nothing else, ever.
