Funnalized
DEENTell me when it starts
Module 06 · Projects

Won deals become delivered projects

Tasks, sprints, kanban and time tracking in one record — an automation turns the won deal into the project.

0Capabilities
0Paths through
0Handovers
0Entries in the catalogue

Screens from a demo workspace. Companies, people and figures are fictitious.

What it does

Projects at work

Four capabilities people actually open Projects for. Everything else it can do is listed in full in section 04 — this is only what stands on its own.

The load-bearing capability

Four views, one set of data

List, kanban board, calendar and timeline all reach into the same tasks. In the timeline you drag a bar to new days or stretch it at its start or end, with the mouse or the arrow keys. It draws the dependencies and flags a task that starts before its predecessor ends — if you want, the successors move along. Which card fields and columns are visible is yours to set per view, and your setting is remembered.

Four views

one set of data — list, kanban, calendar, timeline

Sprints and velocity

Plan in iterations with a goal and a timeframe. Pull tasks from the backlog into the sprint, start it and close it — progress, completed against planned points and velocity are live in front of you. Closed sprints move into the archive automatically if you want them to.

Live

points done against points planned, and velocity, visible straight away

Time tracked at the task

Book hours exactly where the work happens — on the task. The timer keeps running even if you close the page, sits at the top of the Projects module and, when stopped, books the time on the day it was started. Anything you forgot you add afterwards with a date — with a note, as billable or internal. The “Time” tab shows all time logs of a project with totals per person, filtered by person, period and type, and exports them as CSV.

Timer or added later

billable or internal — the total sits on the task, the project and the budget

Tasks with a system behind them

5 templates

bug, feature, spike, refactor and design — title, priority and labels prefilled

Subtasks, checklists, dependencies, priorities, several assignees and custom fields — and every task carries its own reference like OPS-14, which you call by name in the meeting, in the chat and in every follow-up question. Five templates — bug, feature, spike, refactor and design — pre-fill title, priority and labels for you.

Interplay

Paths that run through here

Project, task, time and person hang off ONE record — and off the customer whose deal the project came from. There is nothing to transfer.

Handovers

What Projects receives and passes on

Comes in to Projects
Projects
Goes out of Projects

Projects carries the work after the deal — tasks, sprints, hours. Everything before that, from lead to signed quote, belongs to Sales & CRM.

Complete

Everything that is in it

0Entries in the catalogue

30 capabilities in 5 groups — complete, not curated.

Honestly

What it does not do

Every limit names the place where it happens instead.

  • Hours do not become invoices.

    Hours are logged, marked billable or internal, totalled and exported as CSV. You write the invoice in Sales & CRM; there is no automatic bridge.

  • Capacity is one weekly figure per person.

    Workload counts the working days Monday to Friday and the weekly capacity you enter per person. It does not know about holidays or leave.

  • The client does not work inside the project.

    They see the status in the customer portal. Tasks, sprints and hours stay internal — that is a decision, not a gap.

Follow-up

What teams want to know beforehand

Can I create a project from a template?

Yes. “From template” creates it from one of your saved templates or a starter template — with the task tree, dependencies and milestones, every date calculated from the start day. Whatever deviates afterwards does not change the template.

Do colleagues see the hours I log?

Yes — anyone who sees the project and may read tasks sees the entries of everyone involved in the “Time” tab; for a private project that means only its members. Everyone can change or delete their own entries; other people’s only those allowed to edit tasks across the whole workspace.

What if we do not work in sprints at all?

Then leave them out. Tasks, board and time tracking work without them; sprints and velocity are an addition, not a prerequisite.

Can we add our own fields?

Yes — your own fields and labels, plus one estimation unit for the whole workspace. They are then available in filters and reports, not just in the form.

All 30 entries as a list

Tasks, views and the board 9

  • Tasks with a system behind them Subtasks, checklists, dependencies, priorities, several assignees and custom fields — and every task carries its own reference like OPS-14, which you call by name in the meeting, in the chat and in every follow-up question. Five templates — bug, feature, spike, refactor and design — pre-fill title, priority and labels for you.
  • Four views, one set of data List, kanban board, calendar and timeline all reach into the same tasks. In the timeline you drag a bar to new days or stretch it at its start or end, with the mouse or the arrow keys. It draws the dependencies and flags a task that starts before its predecessor ends — if you want, the successors move along. Which card fields and columns are visible is yours to set per view, and your setting is remembered.
  • A board with your own statuses Name the columns freely — the name becomes a valid status, with no rigid to-do/doing/done corset. A WIP limit per column — only so many cards may sit there at once — keeps nobody overloaded, and drag and drop puts cards in exactly the order you want, which is exactly the order that survives.
  • My work One view across all projects gathers precisely the tasks assigned to you — grouped into overdue, due today, this week and later. One click opens the task inside its project. In the morning you know straight away what is on.
  • Milestones A key date instead of a time span — sign-off, go-live, trade fair — shows as a diamond in the timeline, the list and the board. The project overview shows the next milestones and counts the overdue ones.
  • Files on project and task Briefings, drafts and sign-offs sit right on the project or on the individual task — upload them or drop them in, stored in the central file storage. Anyone who may not see a private project does not see its files either.
  • Custom fields as text, number, choice or date
  • Coloured labels for tasks and tags for the project
  • Story points or hours as the estimation unit — set workspace-wide

Sprints, time and what runs by itself 6

  • Sprints and velocity Plan in iterations with a goal and a timeframe. Pull tasks from the backlog into the sprint, start it and close it — progress, completed against planned points and velocity are live in front of you. Closed sprints move into the archive automatically if you want them to.
  • Time tracked at the task Book hours exactly where the work happens — on the task. The timer keeps running even if you close the page, sits at the top of the Projects module and, when stopped, books the time on the day it was started. Anything you forgot you add afterwards with a date — with a note, as billable or internal. The “Time” tab shows all time logs of a project with totals per person, filtered by person, period and type, and exports them as CSV.
  • Budget with plan and actuals Set a budget per project in hours and in euros, plus an hourly rate. The overview puts booked hours against the plan, forecasts from the open remaining estimate when you estimate in hours, and turns amber from 90 percent, red above 100 percent. Amounts are visible only to people allowed to edit projects.
  • Project reports A reports tab of its own per project shows the points completed in the last two weeks, the completion trend across twelve weeks, velocity per sprint (planned against completed), tasks per person, the cycle time from creation to done and the status distribution — plus a CSV export of the tasks. Calculated by fixed rules, plainly labelled, with no AI guesswork.
  • Project automations A status change, a due date reached, a new assignment or a starting sprint set follow-on actions off: assign, set status, apply a label, create a subtask, notify. Overdue work reports itself — the routine handles itself in the background, as a quick rule or a visual workflow.
  • Project templates with a task tree Save a project that worked as a template — with columns, tasks including subtasks, checklists, dependencies, milestones and custom fields. A new project from it calculates every date from the start day you choose. Assignees, sprints, hours and budget deliberately stay behind. Three starter templates are ready: website relaunch, client onboarding and campaign.

Dependencies, portfolio and workload 6

  • Portfolio across all projects The portfolio view puts every project side by side: progress, budget used, delay and next milestone. Next to your traffic light sits a suggestion with its reason, such as “3 of 12 open tasks overdue”. Taking it over is one click — the decision stays yours.
  • Workload per person Planned hours per person and week against their weekly capacity, across all projects: the estimate of an open task spreads over the working days between start and due date, with the booked hours beside it. Capacity is 40 hours until you change it per person. If you estimate in points, you see tasks per week instead of hours.
  • Blocking and blocked-by relations between tasks, visible in the timeline
  • Blocked work as a status of its own instead of a hidden note
  • Whoever completes a task with open predecessors sees those predecessors and decides deliberately: leave it open or complete it anyway
  • Tasks per person in the reports tab — completed, in progress and overdue side by side

Visibility and health 4

  • Mark visibility: private, internal or customer-visible
  • Health as green / amber / red, plus priority and owner
  • Header statistic “at risk”: active projects that are not green
  • Link to customer and deal: set in the deal record or by automation — and that is where the linked projects are listed

Roles and permissions per project 5

  • System roles such as project lead and scrum master, plus roles of your own
  • Permissions per project role, grouped by tasks, team and automations
  • Notify on assignment, mention, comment, status change and due date — each event on its own, with a lead time from zero to fourteen days
  • Which view opens by default — list, board or calendar — and whether the project overview starts as tiles or as a list
  • Add, remove and reshuffle members with their role
The neighbours

The module before, the module after

All 21 sit in a fixed order — from here it continues in both directions.

Projects is module 6 of 21 — the same order as in the menu and the footer.

One message at launch. After that you'll find me in the top right of the app.

Projects is one of 21. You get all of them.

Sign up and you'll hear from us the moment we go live. Not a newsletter — one message.

€50€150/ month · permanently

Waiting list

Only your email address. No spam, unsubscribe at any time.

See all modules

€50€150/ month · permanently

50 founder placesTell me when it starts