One PM Tool for Every Team: Software, Marketing & HR

The problem with one-size-fits-all PM tools

Most project management tools are designed by and for software engineers. That means HR managers stare at "Sprint" and "Story Points" when they just want to track a hiring cohort. Marketing leads scroll past "Change Management" and "AI Docs" every time they open a campaign project. The tool works, technically — but every non-software team is constantly translating its language into theirs.

Three templates, three worlds

When you create a project in Decuga, you now choose a template. Each template configures the workspace for a specific domain. You can change the template at any time from the project header — the change takes effect immediately.

1 — Vocabulary remapping

The most immediately visible change is labels. "Sprint Tasks" becomes "Campaign Waves" for marketing teams and "Hiring Cohorts" for HR teams. "Group Tasks" becomes "Content Groups" or "Action Items". "Story Points" becomes "Effort". The rename flows through the entire sidebar navigation and the list view — so every team member sees language that matches how their function actually works.

• ✓Sprint → Campaign Wave (Marketing) / Hiring Cohort (HR)
• ✓Backlog → Content Bank (Marketing) / Talent Pipeline (HR)
• ✓Group Tasks → Content Groups (Marketing) / Action Items (HR)
• ✓Story Points → Effort (Marketing & HR)
• ✓All vocabulary is defined in a single config — no magic strings scattered across the codebase

2 — Section masking

Not every team needs every feature. Marketing and HR projects automatically hide two sections that are irrelevant to their workflows: AI Documents (PRDs, architecture diagrams, decision memos) and Change Management. The sections are not deleted — they are simply not rendered in the sidebar. If a project's template is later changed back to Software, all sections reappear.

3 — Context-aware AI system prompts

When your team asks Decuga's AI assistant a question inside a Marketing project, the underlying LLM receives a custom system prompt that primes it as a senior marketing strategist. HR projects prime the LLM as an HR specialist. Software projects use the default prompt. This means the AI gives answers in the right professional register without you needing to repeat "we're a marketing team" in every question.

4 — Pre-seeded intake forms

When a Marketing or HR project is created, Decuga automatically creates a pre-configured service desk intake form. Marketing projects get a "Marketing Asset Request" form with fields for Asset Type, Campaign Name, Target Audience, Deadline, and a Creative Brief. HR projects get an "HR Request" form with Request Type, Employee Name, Department, Manager, and Description. These forms are immediately live on the project's helpdesk portal — no manual setup required.

Changing a project's template after creation

Templates are not locked at creation. To change a project's template, click the pencil icon next to the project name in the top header bar. A template dropdown appears alongside the name and description fields. Pick the new template and save — the sidebar immediately updates with the correct sections and labels. The underlying data (tasks, sprints, documents) is never touched; only the presentation layer changes.

A real-world example: marketing campaign project

A content marketing manager creates a new project and selects the Marketing Campaign template. They immediately see "Campaign Waves" instead of "Sprint Tasks" and "Content Bank" instead of "Backlog". They submit a creative brief through the auto-seeded Marketing Asset Request form on the portal. A designer receives the ticket, picks it up as a sprint task (Campaign Wave task), and completes it. The marketing manager tracks progress on the board — all without the mental overhead of translating PM jargon. The AI assistant, when asked "what should we focus on for Q3?", responds with campaign and audience recommendations rather than engineering roadmap advice.

Under the hood

The template system is designed to be zero-cost for existing projects. Projects created before templates were introduced are treated as Software template projects — no migration needed, all existing behaviour is preserved. The template value is stored on the project entity and round-trips through every API response, so the frontend always has accurate state without extra fetches.