The module system

One platform, composed per project.

A small core is always on. Turn on the rest — bugs, a roadmap, client messages, billing, a knowledge base — per project. What you skip never shows up.

Get started See the modules

Module by module

Everything each module gives you.

A small core is always on. The rest switch on per project — enable only what each one needs.

TasksCore

The engine every other module links to.

One backlog, four ways to see it — and everything links back to it.

Four views, one backlog

List, Board, Table, and a dependency Graph — one keystroke apart. Right-click any task for stage, assignees, priority, and more.

WEB-142Fix nav overflow on tabletIn Progress

WEB-139Copy pass on pricing pageIn Review

WEB-137Add OG images to blogTodo

WEB-131Ship dark-mode tokensDone

Reference anything, inline

Type @ to mention a person — or any task, doc, or bug. It drops in as a live chip and leaves a backlink on the target.

Blocked until @da

See the dependency chain

The graph lays out blocks and blocked-by, so what's holding up the release is obvious at a glance.

Subtasks nested any depth, priorities, estimates, and saved views
Comment threads, reactions, attachments, and stage-change automations
My Tasks aggregates everything assigned to you across projects

DocsCore

A native doc hub, versioned and linked to the work.

Write and collaborate in one place, with every source alongside.

Write together, comment in place

A WYSIWYG editor with real-time collaboration and comments anchored to the exact selection they are about.

Launch runbook

DOC-24 · edited 2h ago · v7

Cut over at 02:00 UTC. Freeze deploys the day before and page the on-call lead.

Roll back automatically if the error rate stays over 2%Marco for five minutes.

Freeze deploys the day before

Dana Reyesnow

Can we add the Q3 cutover dates here?

One hub, every source

Native docs, PDFs, and external links — Google Docs, Drive, Figma, Notion — searchable side by side.

Search docs…

Launch runbookDOC · v7

Q3 contract.pdfPDF

Pricing modelGoogle Docs

Brand kitFigma

Every save is a version

Full version history you can view or restore, so a doc is never lost or overwritten.

v7Dana Reyes2h agoCurrent

v6Marco VidalYesterdayRestore

v5Dana ReyesJul 14Restore

v4Priya NairJul 12Restore

Nested folders and tags, org- or project-scoped
Doc-level comments and universal @-references
Mark docs or whole folders internal-only, and export to .md / PDF

BugtrackerOpt-in

Defects with their own board, linked to the fix.

Track, triage, and let clients report — without touching your task board.

Triage on a status board

A kanban by bug-specific status — New, Triaged, In Progress, Fixed — with severity on every card. Its own board, separate from tasks.

Open2

BUG-58Critical

Checkout 500 on expired coupon

BUG-61Medium

Search returns stale results

Triaged1

BUG-55High

Avatar upload fails over 4MB

Fixed1

BUG-51Low

Dark-mode contrast on badges

A bug is more than a title

A structured report — severity, environment, steps to reproduce, expected vs actual — plus a link to the one task that fixes it, with a nudge to close it when that ships.

BUG-58Open

Checkout 500 on expired coupon

CriticalProduction · v2.4.1Checkout

Steps to reproduce

Apply an expired coupon to the cart
Proceed to checkout

Expected

Coupon rejected with a message

Actual

500 error, cart cleared

Linked to WEB-142 — marks Fixed when it ships

Clients can file their own

A focused form clients use to report bugs — gated per project. Reporters see only their own and what you choose to share.

Report a bug

Summary

Checkout fails with an expired coupon

Severity

LowMediumHigh

Steps to reproduce

1. Apply an expired coupon
2. Click checkout

Send report

Statuses customizable per project (plus Won't Fix / Duplicate)
Mark a bug as a duplicate of a canonical one
A triage list with filters by severity, status, area, and environment

RoadmapOpt-in

A client-facing view of what's shipped, in progress, and next.

Milestones and progress, rolled up from the work underneath.

A timeline that fills itself in

Milestones on a timeline, each with a progress bar and its items ticking from planned to shipped — rolled up automatically from the work underneath.

Launch

5 of 8 done

✓Billing checkout
●Client roles

Q3 · Billing

1 of 5 done

◐Invoice PDF export

Q4 · Mobile

Planned

Or the same roadmap as a graph

The connected node view — milestones and their dependencies laid out as a graph, the second of two ways to read the plan.

A changelog clients can follow

Shipped work becomes a month-grouped changelog — a public log clients can watch, read-only and safe.

July 2026

Billing & invoices

Rates, uninvoiced pool, and PDF export

Jul 14

Client messaging

Forum threads with email in and out

Jul 6

June 2026

Bugtracker

Statuses, repro template, client reports

Jun 28

Milestones and one level of sub-milestones
Read-only and client-safe — they see the story, never your internals
Progress derived from item status — no manual percentage upkeep

MessagesOpt-in

Client conversations, forum-style, on the record.

Wall-style threads beside the work — with email in and out.

A wall of threads, not a chat

Client conversations live as forum threads — title, category, opener, participants, and reply count — organized, not a firehose.

Q3 pricing copy — live by Friday?Request

Can we get the new pricing copy live before Friday? The client wants a final review first.

DRMV4 replies · 2h ago

Logo files — final handoffGeneral

Uploaded the final SVGs and the favicon set to the shared drive.

PN2 replies · 1d ago

Email in and out

Clients reply straight from their inbox and it lands in the thread — no login required. Replies you send go back out as email too.

Q3 pricing copy — live by Friday?Request

You· 09:41

The new pricing copy is in review on WEB-139 — live today.

Dana at Acme· 10:02via email

Perfect, ship it. Drop the annual-discount line though.

You· 10:10

Done — live now.

Internal when you need it

Flag a thread team-only and it never appears in the client's view — private discussion beside the client-facing ones.

New thread

Pricing questions from Acme

Who can see this

Client & teamInternal only

Internal threads never appear in the client's view.

Organized by category and tags, with unread markers and mutable threads
Every thread sits beside the work it is about, with @-references

BillingOpt-in

Turn billable time into invoices, from the same hours.

Time tracking is core; Billing adds the rates and the invoice.

Rates, per project or member

Set a project rate, then override it per member where it differs — the layer Billing adds on top of the time tracking every project already has.

Rates · Acme Website

Project default$120 / h

DRDana Reyesoverride$140 / h

MVMarco Vidal$120 / h

PNPriya Nair$95 / h

A pool of billable hours

Every billable log lands in an uninvoiced pool. Pick what to bill and generate an invoice from real logged time.

Uninvoiced time · Acme$880

Design · pricing page2.7h$324

Frontend · nav fix1.2h$144

QA · regression pass3.1h$412

Generate invoice

One line per log — and no silent gaps

The invoice is a line per time log. A draft reflows as you edit rates, and unpriced time is flagged before you can issue — never a silent $0 line.

Invoice · Acme WebsiteDraft

Date	Description	Hours	Rate	Amount
Jul 14	Design · pricing page	2.7	$120	$324
Jul 15	Frontend · nav fix	1.2	$120	$144
Jul 16	QA · regression pass	3.1	No rate	—
Total				$468USD

Issued invoices freeze so a sent invoice never changes underneath you
Currency and tax handled per org

Knowledge baseOpt-in

A structured home for reference material.

Reference docs, guides, and FAQs — in the order someone should read them.

Reference, organized

Docs, guides, and FAQs — searchable and linkable from anywhere via the same @-reference system.

Getting started Onboarding a new clientPublished

Running it Deployment runbookReview due

Conventions Brand & voice guidelinesDraft

Written articles only — files, PDFs and links stay in Docs
Every article has an owner and a review date, so nothing silently rots
Share individual articles with clients as a help centre

Your agents can compose it too.

Every module here is drivable over the MCP server. An AI-first team can enable modules, open tasks, write docs, and move roadmap items without ever opening the app.

See what agents can drive

agent · zeypm-mcp

▸turn on the bug tracker for acme and triage the checkout bug

enable_module { project: "acme-website", module: "bugs" }✓ bugs enabled · tab + routes now live create_bug { title: "Checkout 500 on expired coupon", severity: "critical" }✓ BUG-58 filed · Open

Compose your project in two minutes.

Start with the core. Switch on bugs, a roadmap, messages, billing, or a knowledge base the moment a project needs them.

Get started Book a walkthrough

No credit card · Core modules on by default