01
Intake
Brief, scope, contract.
A client record, a contract and a scope — what every later stage refers back to, and what every other tool makes you enter again.
Sign in
Menu
Project management, simplified
Every stage of delivery, on one path.
The client brief, the sprint, the board, the test run, the release, and the portal your client signs off in. One set of records and one permission model — instead of four tools that disagree about what shipped.
Already a customer? Your organization administrator provisions accounts. New here? Request access.
99.9%
Availability
monthly target
< 5s
Dashboard
at the 95th percentile
1,000
Concurrency
authenticated users
4h RTO
Recovery
24h RPO, daily backups
The problem
Delivery breaks in the gaps.
The sprint lives in one tool, the test run in another, the release note in a doc, and the client hears about the slip a week later on a call. Every handoff is a place where the record stops agreeing with reality.
02
Plan
Backlog, capacity, dates.
03
Build
Board, list, timeline.
04
Verify
Test runs, defects.
05
Release
Notes, deploy, history.
06
Client
Status, milestones, sign-off.
What is in it
Sixteen modules.
Every capability listed is in the specification, not on a roadmap. Where something is out of scope for v1, it is not listed at all.
- 16
- modules
- 10
- built-in roles
- 6
- board views
- 11
- reports
Workspace
Departments, teams and people, with invitations that expire.
- Departments and nested teams
- Single-use activation invitations — admins never set passwords
- Custom roles composed from the permission catalog
Module · screen · action permissions
Clients & invoicing
Client records, portal accounts, and the money that follows them.
- Client profiles, archived rather than deleted
- Invoices with non-reusable numbering and finalization
- Satisfaction ratings from verified portal users only
Invoiced · Paid · Outstanding
Projects & milestones
Agile, Waterfall or Hybrid — with the billing model attached.
- Project Manager and Delivery Manager on every project
- Fixed Cost or Time & Material billing
- Milestones spanning sprints, with client approval gates
7 milestone states
Sprints
Plan, run and close iterations without dropping work.
- 1–4 week sprints that cannot overlap in a project
- Burndown snapshots daily and on every completion change
- Carry-forward is explicit and recorded in sprint history
Velocity over 3 trailing sprints
Work items
Epics down to subtasks, with the detail work actually needs.
- Epic, Story, Task, Bug and Subtask
- Checklists, watchers, comments and attachments
- Bugs carry their own lifecycle and severity scale
5 types · 7 statuses
Agile boards
Six views over one set of records — change one, change all.
- Kanban and Scrum with drag-and-drop
- List view with inline editing
- Calendar, Timeline and Gantt with dependencies
6 board views
Resource planning
See who is overloaded before the sprint tells you.
- Allocation by percentage, with start and end dates
- Available, allocated, partially allocated and bench
- Capacity excludes approved leave and non-working days
Utilization heatmap
Time & productivity
Timers, timesheets and the approval chain behind them.
- Start/pause/stop timer, or enter time manually
- Approval from reporting manager through to project manager
- Planned against actual hours
Billable vs non-billable
QA & release
Test runs that trace back to the work item that caused them.
- Test cases, test runs and regression suites
- Release → test run → test case → work item traceability
- A release cannot pass QA approval until validation completes
10 release states
DevOps visibility
Repos, builds, pull requests and deployments, in project context.
- Commit visibility and pull request tracking
- Build and deployment status with history
- Jenkins, Azure DevOps, Docker and Kubernetes
GitHub · GitLab · Bitbucket
AI assistant
Advice with its reasoning shown — never an automatic edit.
- Predicts delivery delays and sprint completion
- Recommends scope adjustments and reassignments
- Drafts release notes, retrospectives and status reports
Advisory by design
Meetings & communication
Turn a recording into tasks, decisions and risks you can track.
- Timestamped transcripts with speaker separation
- Extracted action items become real tasks, with their source kept
- Teams, Slack and email as scoped sources — no blanket ingestion
12 meeting types
Knowledge base
Documents with versions, permissions and semantic search.
- SOPs, architecture, retrospectives and lessons learned
- Version history you can restore from
- Per-document permissions, separate from the module grant
View · Edit · Download
Client portal
What the client sees is a decision, not an accident.
- Clients reach only the projects assigned to them
- Status, approved milestones, releases, documents and invoices
- Internal notes, test cases and defect detail never cross over
Approved content only
People operations
Skills, leave and growth — the inputs capacity planning needs.
- Skills and certifications with expiry
- Leave requests, balances and policy
- Appraisals, goals and review history
Skill matrix
Reports & audit
Eleven reports, and an activity trail nobody can edit.
- PDF, CSV and XLSX, with export as its own permission
- Large reports run as background jobs
- Audit log is append-only — no edit or delete exists
11 reports · 24-month audit
Intelligence
It tells you what it thinks.
It does not touch the record.
The assistant predicts delays, forecasts capacity, drafts the release note and turns a meeting into action items. Every one of those is a suggestion with its inputs shown, waiting on a person to accept it. Nothing is written by the model alone.
- Predicts delivery delays and sprint completion
- Flags resource overload before the sprint does
- Drafts release notes, retrospectives and status reports
- Extracts decisions and action items from a meeting
- Answers in plain language across your own knowledge
Assistant
Delivery risk. Sprint 14 is tracking 3 items behind its trailing velocity. At the current rate it closes on 18 Oct, four days past the milestone the client approved.
Move 3 items outExtend the milestoneShow the burndown
Based on 3 completed sprints, current assignments and approved leave. Applying any of these is your call — and it is logged.
Trust
Multi-tenant means nothing without the enforcement.
Tenant isolation, enforced server-side
Every organization-scoped request, job, report, export and AI retrieval resolves the caller's organization before it reads. Changing an id in a URL does not change what you can see.
Argon2id, MFA, and sessions that end
Passwords are salted one-way hashes. MFA is mandatory for platform and organization administrators. Sessions idle out at 30 minutes and cannot outlive 12 hours.
Isolation holds through AI
Only the minimum necessary data reaches an LLM, zero-retention controls are preferred where the provider supports them, and one organization's data is never reachable by another through AI.
Uploads are treated as hostile
Extension and MIME validation, malware scanning, filename sanitization, a 25 MB ceiling per file, and nothing executable is ever stored.
Ten built-in roles, plus any custom role you compose
Project ManagerDelivery ManagerTeam LeadTeam MemberQA EngineerDevOps EngineerHR ExecutiveOrg AdministratorPlatform OwnerClient
Stop reconciling four tools.
One platform from the client brief to the signed-off release — with the audit trail to prove what happened.
Request access
Tell us who you are and we’ll set up your organization. You invite your own team once it’s ready.