Project managementCAN I VIBECODE
Teamwork?
BUILD FIRST
- One specific customer type and one primary use case
- A vertical slice that completes the main job without manual workarounds
- Visible limits, review steps, and a fallback when an external dependency fails
LEAVE FOR LATER
- Broad third-party integrations
- High-scale collaboration, syncing, and permissions
- Automation that can cause harm without human review
RESEARCH NOTES
What this tool actually does.
Teamwork.com is a SaaS project management platform aimed at agencies and client-services teams. Core workflow: plan projects via templates or an AI Project Wizard; structure work with tasks, milestones, and dependencies; view work in List, Board, Table, Timeline, and Gantt views; standardize process with reusable Workflows (custom stages applied across projects) and trigger-based automations; collect client requests via Forms that convert to tasks, plus a help-desk module (Teamwork Desk) that turns tickets into tasks. It includes resource management (forecasting, workload/capacity, utilization targets, skills/roles, scenario planning, availability with holidays), native time tracking with billable/non-billable flags, budgets, quoting, invoicing synced to Xero/QuickBooks, and reporting (Project Health, planned vs actual, profitability, utilization, custom reports). Permissions are user- a
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a focused replacement for Teamwork.com's core client-work project management workflow, called something original (not 'Teamwork'). The workflow: a client-services team takes in requests, plans projects, assigns and tracks tasks, manages capacity, logs billable time, and reports on project health. User-facing requirements: (1) projects with templates, milestones, task dependencies, custom fields, and status; (2) task views: List, Board (drag-and-drop), Table, and a Timeline/Gantt with drag-to-reschedule; (3) reusable Workflows: named stage sets applied to projects, with simple trigger-based automations (e.g., on stage change, notify assignee); (4) intake Forms that create tasks; (5) time tracking with timers, manual entry, and billable/non-billable flags; (6) per-project budgets with spend alerts; (7) dashboards: project health, planned vs actual, utilization, profitability; (8) roles: admin, project manager, member, and client (client sees only their projects). Technical requirements: web app with React/Next.js frontend, Node or Python backend, Postgres, auth (e.g., Auth.js), REST API, WebSockets for live updates, CSV export, and seeded demo data. Implementation approaches: use a Gantt library (e.g., Frappe Gantt) for timeline, a DnD library for board/kanban, and a simple dependency graph for scheduling; persist timers server-side. Do not copy Teamwork's brand, logo, colors, copy, or UI; design an original interface. Deliberately out of scope: AI wizard/comment summarization, help-desk/ticketing, Xero/QuickBooks integrations, SSO/enterprise security, mobile apps, multi-tenant billing. Include a README with setup steps and important limitations (e.g., no real-time conflict resolution, single-tenant, no invoicing).