Capture
Start the day from what’s true
Home lists what’s overdue, what’s due today and what’s coming, and marks what you’ve planned for today. Jot a note that doesn’t have to become a task, and answer “what did I finish?” at the end of the day.
Private beta · used every day by the team that builds it
Plan like a product team. Move like a small one.
ScopeKite is work management for product and engineering teams: a fast daily loop, real planning structure, and your team’s own words for all of it.
- A web app, plus a companion phone app in development
- Keyboard-first: Command K (Ctrl K elsewhere) to jump and search
- Assistants connect as you, with scoped access
One calm place for the work that moves your product.
Many work tools make you choose: pleasant but shapeless as you grow, or structured but heavy to live in. ScopeKite is built for the space between.
A daily loop built to be fast
Home shows today: what’s overdue, what’s due, what you’ve planned. Capture a line in seconds, work through it as a list or a board, and press Command K (Ctrl K on Windows and Linux) to jump to a project, its board or cycles, or the Pages area; search tasks and comments; or start a new task — without leaving the keyboard.
Structure that stays out of the way
Projects, states, priorities, sub-tasks and relations. Cycles for timeboxes, a roadmap for the bigger picture, and knowledge pages beside the work they explain. Enough structure to plan a team’s work, with sensible defaults.
Your words, not ours
Call them stories and sprints, or tasks and cycles. Pick a vocabulary once — Default, Agile or Product — and screens, filters and buttons follow.
The daily loop, end to end.
Each stage of the loop has a screen built for it.
- CaptureWrite it down before it’s gone.
- Triage & assignDecide who owns it, and how urgent.
- PlanCommit it to a timebox.
- ExecuteMove it across the board.
- UpdateTalk about it where it lives.
- LearnSee where things stand.
Plan
Timeboxes that show their own progress
Commit work to a cycle and see how much is done and started, and what has no owner or no date — the things that quietly derail a plan.
Execute
Open anything without losing your place
Click an item and it opens beside the list. Set state, assignee, priority and dates inline, break it into sub-tasks, attach files, and talk about it with @mentions — then move on to the next one.
Learn
Numbers you can click through
Project dashboards count exactly what’s behind them: every tile and breakdown row opens the list it counted, so you can check any number against the work behind it.
On your phone
Capture the thought before it evaporates
The web app reshapes itself for a small screen, as shown here. There is also a companion phone app built for the daily loop: it opens on Today, keeps a capture button over its main tabs, and lets you swipe a row on Today to complete it or push it to later.
Planning and administration stay on the web for now, and the phone app isn’t publicly available yet — we’d rather say so than blur it.
Say it your way.
Same product, same data. Switch the workspace vocabulary and buttons, filters, placeholders and tabs follow. Choose Default, Agile or Product; custom wording is possible through the API today.
| Concept | Default | Agile | Product |
|---|---|---|---|
| A piece of work | Task | Story | Work item |
| A timebox | Cycle | Sprint | Cycle |
| A larger effort | Initiative | Epic | Module |
How it’s different.
We’re comparing kinds of tools, not products. Many work-management tools fall into one of two camps, and ScopeKite is built for the space between them.
| Topic | Light trackers, typically | Heavy suites, typically | ScopeKite |
|---|---|---|---|
| Daily speed | Quick to start, thinner on planning. | Powerful, with more to set up. | Dense, keyboard-first rows. The command palette jumps and searches from any screen. |
| Structure | Lists and boards, with planning added later. | Highly configurable, and often heavily configured. | Projects, cycles, roadmap and knowledge pages built in, with sensible defaults. |
| Language | Usually fixed nouns. | Often adjustable in a configuration screen. | Your nouns: Default, Agile or Product presets, applied across the app at once. Custom wording through the API. |
| Assistants | Not compared here. | Not compared here. | Assistants that support remote MCP connect as you: read-only unless you allow more, never deleting, with calls recorded under your name. |
| Access | Roles are often coarse. | Rich roles and heavy administration. | Four workspace roles — owner, admin, member, guest (guests can’t see project content yet); per-project permissions aren’t built yet. Every request is authorized on the server, and cross-workspace tests check that one workspace can’t reach another. |
These are generalizations about categories, and every product inside them is different. If we’ve described one unfairly, tell us.
Bring your own assistant.
Connect an assistant that supports remote MCP servers — the open standard for giving an assistant access to your tools. We developed it against Claude and ChatGPT.
- It works as you. It sees only what you can see, each call it runs is recorded under your name, and its edits appear in activity as yours.
- Read-only until you approve more. With an access token you choose: adding and editing is one checkbox, creating projects another. With browser sign-in you allow or deny what the assistant asks for.
- It can never delete or archive anything. No such tool exists to be misused.
- “What’s on my plate this week?”
- “Summarize the launch checklist page.”
- “Add a task to Website: rewrite the pricing page.” (needs write access)
Built to be trusted with your work.
- Workspaces are kept apart by the server
- Access is decided on the server, on every request. Cross-workspace tests probe the API’s workspace endpoints and expect each to answer as if the other workspace doesn’t exist.
- Assistants get no back door
- An assistant is held to the same permission checks as the person using it, so it can never see or do more than they can.
- Built with accessibility in mind
- WCAG 2.2 AA is the design target, and the app is meant to work from the keyboard. Automated scans cover the core screens; there hasn’t been an independent audit yet.
- This site keeps to itself
- No cookies, no analytics, and nothing loaded from anyone else; every page tells your browser to refuse anything else, and tests check the source and the built site. What you send in the request form is emailed to us, through our email provider Resend, and isn’t kept on the site. Like any website, the server that hosts it may keep ordinary access logs — the privacy note has the details.
Private beta
Where we are.
ScopeKite is used every day by the team that builds it — the project that builds ScopeKite is planned in ScopeKite. There’s a web app, and a companion phone app for the core loop that isn’t public yet.
We aren’t offering accounts to the public yet, and there’s no pricing and no service-level agreement — we’d rather say so than imply otherwise. What we build next is shaped by the teams who join early.
Questions, answered plainly.
Is ScopeKite available now?
Not publicly. It’s in private beta while we use it ourselves every day. Ask for early access below and tell us about your team.
What does it cost?
We haven’t set pricing yet, and we’ll be upfront when we do.
Who is it for?
Product and engineering teams: the people deciding what matters, the people sequencing the work, and the people doing it. Other teams can use it, but that’s who we design for.
Is there a mobile app?
There’s a companion app for the daily loop: Today, capture, and updating work. It isn’t available outside the team yet, and planning and administration are web-only for now.
What is MCP?
The Model Context Protocol is an open standard for connecting an AI assistant to the tools you use. ScopeKite supports it, so an assistant that supports remote MCP servers can work with your data under the same permissions you have.
Where can I read more?
The documentation covers the core daily screens and includes a roadmap of what has shipped and what hasn’t. Some pages lag the product. Read the documentation.
Want in early?
Tell us a little about your team. We’ll read your message and get back to you when there’s a fit.
Your message is emailed to us through our email provider, Resend, and isn’t kept on this site. See the privacy note.