Projects

Milestones, time logs and budget — per project.

#What Projects does

Plan client work with milestones, log time per team member, and watch budget burn in real time.

  • Milestones & deadlines. Break work into milestones with dates and owners. Progress reflects what is actually done, not what is hoped.
  • Time logs per member. Every team member logs time against tasks. Hours roll up per project and per person — and feed straight into Billing.
  • Budget tracking. Set a budget per project and watch burn against it live. No more surprise overruns at invoice time.
  • Client-linked. Each project belongs to a CRM client, so context — quotes, documents, conversations — is always one click away.

#Create and run a project

  1. Click New project, pick the client company, a stage (Brief → Design → Development → Delivery → Follow-up) and a service type (Website, SaaS, App, SEO, Branding…).
  2. The project header shows stage, status (Planning / Active / Paused / Done), milestones progress, logged hours and budget burn — with Stage and Status selectable right in the header.
  3. Work through the tabs: Overview, Workspace (canvases and documents), Process (ordered milestone plan), Time, Tech (stack, repos, environments) and Connections (the automatic relationship hub).

#Time, budget and the client portal

  • Log time per team member on the Time tab — hours roll up per project and per person, and can be pulled into invoices.
  • Set a budget and an hourly rate (the project’s own, or the org default from Billing settings) to watch burn live in the header.
  • Share with client (toggle in the header) publishes the project to the client portal.

#On the MCP surface

Hand your AI a brief over MCP and it can create the project, set its tech stack, register repos and environments, and link it to the client and related records — inside your structure, with real org-scoped tools.

Tools (write):

  • sstm_project_create
  • sstm_project_tech_set
  • sstm_project_repo_add
  • sstm_project_env_set
  • sstm_project_link
  • sstm_project_review_record
  • sstm_project_review_resolve

Resources (read):

  • sstm://projects
  • sstm://projects/links
  • sstm://project/{id}/context
  • sstm://project/{id}/review

Full definitions live in the MCP reference.

#On the Cloudflare side

  • Project records live in the platform database — but every client reference on a project resolves against your own BYOC D1: the company on a project is the row in YOUR database.
  • Your AI reads the full project graph over MCP (sstm://project/{id}/context).