Orbit: where it stands, and 6 calls to make
31 Oct 2026
Where it stands
- Live at https://orbit.singlebit.xyz.
- Everything in the PRD is built: projects and tasks, Home, My Work, Daily Brief, Inbox, docs and approvals, the credentials vault, proposals, invoices with GST, share links, PDFs and MCP.
- Accounts are set up: SingleBit and Guiding Elephant, with the admins we agreed.
- Sign-in is the blocker. Orbit signs people in with an emailed link, and Amazon hasn't finished verifying our email domain yet, so those emails don't go out. We're switching on "Continue with Google" so people can sign in today.
- In progress: importing our existing Linear work into Orbit, so nobody starts from an empty screen.
The 6 calls
Each one is already built the way the PRD suggested. If you agree, say yes and nothing changes.
1. Sign-in: is Google plus email link enough, or does anyone use Microsoft accounts? Now: Google, or a sign-in link sent to any email address. Someone on Outlook can already sign in with the email link. Suggest: yes, enough. Adding a "Continue with Microsoft" button is about a day's work if we ever need it.
2. Guests (people from outside, like a client): are these limits right? Now: a guest sees only what's shared with them by name. They can comment and be @mentioned. They can't create tasks, can't see who else is on the project, and don't show up when others search for people. Suggest: yes.
3. Custom fields: set up per project or per company, and never required? Now: a project manager can add fields like "Client" or "Region" to their project, and a company admin can add them for every project in their company. Nobody is forced to fill them in, and they stay out of the quick-create box. Suggest: yes. Required fields stay limited to assignee and due date.
4. Trash: keep deleted things for 100 days? Now: 100 days, then deleted for good. Most tools keep 30 days. This is a server setting, so changing it takes a minute. Suggest: keep 100.
5. Subtasks: is one level enough? Now: a task can have subtasks, but a subtask can't have its own. Anything bigger becomes a project or a milestone. Suggest: yes. Deeper nesting is real work to build and makes tasks harder to find.
6. Shared projects: when one company's team joins a shared project, should the other company see the whole team or only the people on the project? Now: only the people on the project. Example: SingleBit Engineering joins a shared project with Guiding Elephant. Guiding Elephant sees the team's name and the three engineers on that project, not the rest of the team. Suggest: yes. Each company's team list stays private.
What I need back
Reply with the numbers you disagree with. Silence means yes to all six.