Skip to main content
Product management

Organise what you build for every client
without losing control

Run multiple client projects with sprints, epics, stories and tasks. A prioritised backlog, story points, acceptance criteria and both Kanban and list views. All in one place, with no per-user licences.

Each client is a project. Each project has its own backlog, sprints and KPIs. Switch context in one click without losing sight of everything you have in flight.

Project management with sprints, epics and stories — sprint planning view
Sprint planning

From backlog to sprint with drag & drop and story points

Planning a sprint shouldn't take an hour of unproductive meeting. Drag stories from the backlog into the active sprint, adjust story points as you go and see in real time whether you're overloading the team or still have capacity.

Each sprint shows planned vs actual velocity, an automatic burndown chart and the percentage of stories completed. When you close the sprint, unfinished stories go back to the backlog in one click.

  • Drag & drop to plan: move stories and tasks between backlog and sprint by dragging them. Reorder priority inside the sprint with the same gesture.
  • Story points and capacity: assign points to each story and set the sprint's capacity. The system warns you if you go over the limit before you even start.
  • Automatic burndown chart: a daily progress chart that updates itself as the team completes tasks. Nothing to configure.
  • Sprint close with a summary: when you close a sprint you see actual vs estimated velocity, completed and incomplete stories, and you can move what's left to the next sprint or back to the backlog.
  • Sprint history: review any past sprint, its velocity, what was delivered and what was left out. Data to improve sprint after sprint.
Sprint planning with drag & drop, story points and a burndown chart
Kanban board with epics, stories, tasks and bugs colour-coded
Work hierarchy

Epic, story, task, bug: each type with its own purpose and colour

Not everything is "a ticket". An epic groups a big chunk of functionality. A story describes value for the user. A task is concrete work. A bug is something that doesn't work. Each type has its icon, its colour and its flow.

Stories nest inside epics. Tasks and bugs link to stories. An epic's progress is calculated automatically from its stories. You see at a glance which big feature is at 80% and which hasn't started.

Epic
A large piece of functionality spanning several stories. Example: "Invoicing module".
Story
Value for the user, with acceptance criteria. Example: "As an admin, I want to export invoices to PDF".
Task
Concrete technical work linked to a story. Example: "Create an API endpoint to generate the PDF".
Bug
Something that doesn't work as it should. Priority, severity and steps to reproduce. Example: "The PDF comes out without the logo".
  • Automatic epic progress: the epic's progress bar is derived from the stories completed inside it.
  • Colour coding on the Kanban board: each item type has its own colour on the board. You see at a glance whether bugs are piling up or an epic is moving.
Backlog view

All outstanding work in one ordered, filterable, exportable list

The backlog is the single source of truth for everything left to do. A list view with filters by type (epic, story, task, bug), assignee, sprint, status and priority. Each item shows a progress bar if it has children.

Import work from a CSV if you're coming from another tool. Export the backlog to CSV to share with the client or for planning meetings. No copy-pasting between tools.

  • Combinable filters: filter by type + assignee + sprint + priority at once. Find exactly what you're after in the backlog in seconds.
  • Progress bar per item: every epic and story visually shows the percentage of children completed.
  • CSV import: bring your backlog over from Jira, Trello, Asana or any spreadsheet. Columns are mapped automatically, with a review step before importing.
  • CSV export: export the whole backlog or a filtered slice to share with clients, build reports or keep an external backup.
  • Ordering by priority: drag to reorder priority. The item at the top is the most important. No confusing numeric fields.
Backlog view with filters by type, assignee and progress — CSV import/export
Story: Export invoices to PDF
3 SP
Acceptance criteria
The PDF includes the logo, tax details and a VAT breakdown
It can be downloaded from the invoice list and from the detail view
Sending by email attaches the PDF automatically
Support for invoices in English with automatic translation
2/4 completed
Tasks linked to this story
Build the PDF template with Puppeteer Done
API endpoint GET /invoices/:id/pdf Done
Download button in the UI + email attachment In progress
i18n for the PDF template (ES/EN) To do
Acceptance criteria

Define what "done" means before you start building

Every story has its acceptance-criteria checklist: the conditions that must be met for the story to count as complete. No ambiguity, no "I thought that…". Everything is written down before work starts.

Criteria link to the technical tasks. When every task behind a criterion is complete, the criterion is ticked automatically. The story's progress bar reflects how many criteria are validated versus outstanding.

  • Checklist per story: add as many criteria as you need. Each one is a concrete, verifiable condition.
  • Criterion-to-task linking: attach technical tasks to each criterion. As the task is completed, the criterion advances.
  • Visual progress: a progress bar and a counter of criteria completed versus total. The client sees exactly how their story is progressing.
  • Validation before closing: a story can't move to "Done" until all its acceptance criteria are validated.
Multi-proyecto

Each client is a project. Switch context without losing the big picture.

If you run development for several clients, each one gets its own independent project with its backlog, sprints, epics and KPIs. Switch project in one click from the selector at the top.

But you also need the big picture. The consolidated dashboard shows velocity across all projects, how many stories are in flight in total, which sprints close this week and where the bottlenecks are. Portfolio management without extra tools.

  • Project selector: switch between client projects from the top bar. Each project keeps its full context isolated.
  • Consolidated dashboard: a global view with aggregated metrics for every active project. Velocity, stories in progress, open sprints.
  • KPIs per project: average velocity, lead time, cycle time, bug-to-story ratio, story points delivered per sprint.
  • No project limit: create as many projects as you have clients. No extra cost per project or per user.
Multi-project view with a client selector and consolidated KPIs
Ready to get started?

Stop running sprints in spreadsheets and disconnected boards

We'll show you what your project management would look like with epics, sprints and acceptance criteria all in one place. No commitment, no cost, no per-user licences.

We reply within 24 working hours. No commitment.

Frequently asked questions about project management

Can I use Kanban and list at the same time, or do I have to choose?
You can switch between the two views at any time. The Kanban view shows the status columns (To do, In progress, In review, Done) with draggable cards. The list view shows every item in a filterable, sortable table. The data is the same, only the way you look at it changes.
How do story points work? Are they mandatory?
Story points are a relative estimate of effort you assign to each story. They're optional: if your team doesn't use them, you can ignore them entirely. If you do use them, the system automatically works out sprint velocity (points completed), available capacity and the burndown chart. Use whichever scale you prefer: Fibonacci, t-shirt sizes or plain numbers.
Can I import my backlog from Jira, Trello or Asana?
Yes. Export your backlog from any tool to CSV and upload it. The importer maps the columns automatically (title, description, type, priority, assignee, status) and shows you a preview before you confirm. You can also import from a free-form spreadsheet.
Is there a limit on users or projects?
No. We don't charge per user or per project. Create as many projects as you have clients and invite your whole team at no extra cost. Pricing is based on the platform as a whole, not on seat count.
Can I share the project's progress with my client?
Yes. You can generate a read-only view of the project behind a private link. The client sees epic progress, the current sprint's status and the acceptance criteria without needing an account or a licence. You can also export sprint reports as PDF or CSV.
Do acceptance criteria link to the technical tasks?
Yes. Each acceptance criterion can be linked to one or several tasks. When every task attached to a criterion is complete, the criterion is marked as validated automatically. The story can't move to "Done" until all its criteria are validated.
Can I customise the Kanban board's statuses?
Yes. The defaults are To do, In progress, In review and Done, but you can add, rename or remove columns to match your workflow. You could add "QA", "Deploy" or "Awaiting feedback" as intermediate statuses, for example.
How are bugs handled? Are they different from tasks?
Bugs are a specific type with extra fields: severity (critical, high, medium, low), steps to reproduce, expected vs actual result and environment. They link to stories and show up in red on the Kanban board so you spot them fast. You can filter the backlog to see only open bugs and prioritise them.
Project management with sprints and epics

Tell us your challenge. We'll propose a solution.

No commitment. Within 24 hours, you'll receive a proposal with scope, timeline and budget. No fine print.

Book a free call →