Clarity before complexity.
A workspace should help you answer a few useful questions: what needs doing, who owns it, and what is getting in the way. More information only helps when it makes those answers easier to find.
Meet the people behind Cursis.
A small team with a shared belief: keeping work moving should leave you more time to do the work.
01 / Our story
A task on a list.
Then what?
We built Cursis around a simple frustration: a task can be written down and still go nowhere. The owner is unclear. The important context is buried in a conversation. A deadline gets closer while everyone waits for an update.
Adding another list doesn’t always fix that. Teams need to understand how the work connects: what matters now, who is taking it forward, and where a little help could make a difference.
That’s the idea behind Cursis. We’re bringing tasks, projects, conversations, and planning into a shared workspace, with Ordis AI to help teams see what needs attention. Less time piecing the day together. More time making progress.
What we’re working toward
Less chasing.
More doing.
Our mission is to make the next step clear, so small teams can spend their energy on the work they care about. A calmer workday starts with a shared understanding of what needs to happen next.
02 / Our approach
What matters to us.
These are the ideas we want to show up in the product, from the first task to the end of a busy week.
Keep the context close.
A task makes more sense beside the conversation, project, and plan it belongs to. We want fewer gaps between deciding what to do and having what you need to do it.
Make AI useful.
Our aim for Ordis is practical help: understanding the state of work, spotting what needs attention, and helping with the next action. The team’s judgment stays at the centre of the work.
03 / The people
Three perspectives.
One shared direction.
Product, engineering, and community come together around the same question: how can Cursis make the workday easier to navigate?
Saransh Vashistha
CEO · Product direction
Saransh focuses on what Cursis should solve and why it matters. His work connects the bigger product vision with the everyday details that help a team understand what to do next.
Mukul Kumar
CTO · Engineering
Mukul turns the product direction into the tools people use. His focus is on how the parts of Cursis fit together, from the workspace experience to the systems behind it.
Lakhan
CGO · Growth & community
Lakhan focuses on the conversation around Cursis: listening to teams, understanding where work gets stuck, and sharing what we build with the people it could help.
04 / Build with us
Your workday is part
of the conversation.
We have a direction for Cursis, and we want to understand how it fits into real teams’ days. The handoff that always gets missed. The update you have to ask for twice. The small change that would save you a little effort every week.
If you’ve tried Cursis, tell us what felt useful and what felt difficult. If you’re still exploring, tell us what your team needs. Those are the conversations we want to have as we keep building.