PayMe Guide

PM Guide

Manage projects, allocate budgets, track team capacity, and let the intelligence layer catch problems before they escalate.

PM Guide

As a PM or admin you control the full project lifecycle — from importing a FiC quote to archiving a completed project. This guide covers every step.

Core concepts

PayMe organises work around three nested levels:

Project (budget envelope)
  └── Period  (monthly / quarterly / custom slice)
        └── Allocation  (member + discipline + hours)
              └── Task  (work item with estimate)
                    └── Time entry  (logged hours)

Allocated hours is the planned budget. Logged hours is actual time recorded. They live in separate columns throughout the UI — never conflate them.

SectionWhat you do here
ProjectsCreate, configure, and manage the full project lifecycle
TeamMonitor workload, resolve overload, manage schedules
IntelligenceBudget health, deadline nudges, slack detection, scope creep
ReportsBudgets, utilisation, time history, client profitability
Telegram PM ToolsBot tools for PMs: workload, who-can-help, simulate, forecast

Key flows

Starting a new project from a quote

  1. FiC sync runs hourly — accepted quotes appear in Projects → New from quote.
  2. Review the imported budget and client name, confirm.
  3. Apply a template (optional) to auto-create allocations by discipline.
  4. Assign members to each allocation.
  5. Set the project deadline and billing type.
  6. Activate — members can now create tasks.

Monitoring a running project

  • Budget page shows burn % vs completion % per member and period.
  • The intelligence layer sends Telegram nudges when burn outpaces completion.
  • The Slack detection badge appears on project cards when a member's actual hours lag well behind their allocation.

Closing out

  1. Mark allocations as completed when a member finishes their work (or let members do it themselves).
  2. Move the project to completed — triggers billing status tracking.
  3. Archive when invoiced and no further activity expected.

On this page