Projects
Templates, hierarchies, and dependencies that hold. Built to run one project or two hundred.
Everything you can do with project management
Run one project or two hundred on records the rest of the workspace can read.
Inside project management
Every piece that makes this work, and what each one is actually for.
Workstreams
A lane that spans projects, for the teams whose work never fits neatly inside one of them.
Sprints & cycles
Fixed windows and repeating cadences, with carry-over, archive, and velocity handled rather than remembered.
Roadmaps & initiatives
Initiatives and objectives above the projects, with portfolio-level progress rolled up from the work itself rather than from a status meeting.
Requests become scheduled work
Tickets have their own typed stages and SLA clocks that pause while you are waiting on the requester, so the clock reflects your obligation rather than the calendar. Promoting a ticket to a task carries the attachments across, and the ticket resolves when its linked tasks are done. Client facing commitments and internal work are one graph, so SLA state and delivery state cannot tell different stories.
What this removesRe-typing a client conversation into a second tool, and the silent gap between what support promised and what delivery scheduled.
See how everything connectsThe questions this actually answers.
The long version, because this is where the category has real objections.
How do you run projects when every team works differently?
Pick a methodology per project instead of per company. Engineering runs sprints with backlogs and estimates, ops runs a board, delivery runs a gantt, and all of it happens on the same task records with the same custom fields. Templates carry your phases, tasks, and dependencies into every new project, so the second hundred projects start as sharp as the first.
How does the next thing to do find you?
Most tools show you a project and make you dig for your part of it. Scrambl starts from the other end: My Tasks gathers everything with your name on it across every project, Today pulls forward what is due, and Focus clears the rest out of view. Priorities stop being a morning ritual of opening six boards.
My Tasks, across everything
One list, every project, no digging.
Today
What is due now, pulled to the front.
Recurring work
The repeating stuff schedules itself.
What happens to a request from outside the team?
It becomes a ticket with its own stages and an SLA clock that pauses while you wait on the requester. Route it, work it, and if it turns out to be bigger than a reply, promote it to a task, a project, or a deal in one move with the whole conversation attached. Nothing gets re-typed into a second tool.
Where do the decisions end up?
Discussions are threaded by topic and pinned to the record they concern, so the reason behind a call lives next to the work it shaped. Notes sit alongside the project or the meeting they came from, and action items extract into tasks with the link back to the sentence that produced them.
Every module has its own page.
The short version lives here. Each module below has a page of its own with the views, fields, and edge cases spelled out.
Questions people actually ask
Can each project use a different methodology?
Yes. Methodology is chosen per project, so a sprint-based build and a milestone-based retainer run side by side on the same records and roll up to the same reporting.
Do tasks support subtasks and dependencies?
Yes. Subtasks, dependencies, milestones, priorities, due dates, custom fields, and per-type statuses, with list, board, calendar, and gantt views on the same data.
Can work repeat on a schedule?
Yes. Recurring tasks arrive on schedule with their checklist attached, so the monthly close and the weekly report stop depending on memory.
Is there one view of everything assigned to me?
My Tasks collects your work across every project, and Today pulls forward what is due. Focus clears everything else out of view when you need to ship.
How do requests from clients enter the queue?
Through the client portal, a branded form, live chat, or inbound email. Each becomes a ticket with routing and an SLA clock, and can be promoted to project work in one move.
Can we bring projects over from another tool?
Yes. Bulk import with validation, a full run history, and a recovery path if a file was wrong. See the migrate page for the supported sources.
It does not stop at one capability.
Scrambl is one workspace, so the records here are the same records the rest of the platform reads. These pair with it most often.
.svg)
Ready to crack the chaos?
One workspace for projects, clients, finance, and everything in between. Try for free.