Skip to content
BuilderSoft
Team Task Management SoftwareLive product

Run every project, sprint, and conversation from one system.

Projects, sprints, a Kanban board, a sortable task table, comments with @mentions, file attachments, team chat, and notifications to Discord, Slack, and Teams — one workspace per organization, built for how teams actually plan and ship work.

Sign in to TaskFlowBook a demoRead the docs

The problem

Work was never actually in one place.

Most teams run sprints in one tool, chat in another, and file imports and notifications as brittle afterthoughts. The result: tasks nobody owns, status that's always a Slack message behind, and a sprint board that doesn't agree with the spreadsheet someone is still keeping on the side.

  • Two tools disagree about what's actually in this sprint
  • An assignee changes and the team finds out a day later, if at all
  • Importing from Jira or Azure Boards means starting from zero, or starting over
  • Comments, decisions, and attachments live in whichever app someone remembered to open
  • A chat notification fires per task during a big import and floods the channel
active sprint per project, enforced by the system
1
rows importable per run, mapped before commit
1,000
chat platforms notified: Discord, Slack, Teams
3
per-task pings before a big import just sends one summary
25

9 modules, all included

Every module a team actually needs.

Not a toolkit you assemble — a complete operating system. Each module is included on every plan and connected to all the others.

Module 1 of 9

Organizations & Access

Every project, task, member, and integration belongs to exactly one organization — requested, approved, and run on its own, with roles that actually mean something.

  • Workspace requests reviewed by the platform owner before first sign-in
  • Four roles — Developer, Manager, Admin, and platform-wide Master — each with a distinct permission set
  • Invite links scoped to an email and a role, valid once for 7 days
  • Deactivate or reactivate members without deleting their history
  • Explicit sign-in messaging for pending, suspended, or rejected workspaces

Module 2 of 9

Projects & Backlog

Projects get a short key and unlimited sprints; anything not yet scheduled sits in a backlog you can actually plan from.

  • Projects with a short, permanent key (e.g. WEB) that numbers every task
  • Drag-and-drop backlog planning across the backlog and every open sprint
  • One active sprint per project, with planned sprints queued behind it
  • Sprint completion routes unfinished tasks to the backlog or a chosen sprint
  • Completed sprints collapse into a history of done/total and points tally
  • Archive a project without losing its history; restore it later

Module 3 of 9

Kanban Board

To Do → In Progress → Code Review → Done, scoped to the active sprint by default so the board stays usable even with thousands of tasks.

  • Scope switcher: active sprint, a specific planned sprint, backlog only, or all tasks
  • Drag a card to change status; double-click to edit, single-click to open
  • Developers move only their own cards; Managers and above move anything
  • Live filtering by search text, assignee, and type
  • Each card shows type, ticket number, import source, priority, points, and due-date status

Module 4 of 9

Task Detail, Comments & Attachments

Every task is a real record — type, assignee, priority, points, deadline — with a comment thread and file attachments underneath it.

  • Six task types (Task, Story, Bug, Epic, Improvement, Spike) with their own icon
  • @mention autocomplete in comments that notifies the mentioned teammate
  • Drag-and-drop or paste attachments directly into a comment, up to 10 files
  • Images, PDFs, Office docs, text/CSV/JSON, zips, and audio/video up to 10MB each
  • Deep links to a specific comment that scroll to and highlight it
  • Owners edit their own comments/attachments; Managers+ moderate anyone's

Module 5 of 9

My Tasks & Organization-wide Table

A focused queue of what's yours, and a sortable, filterable, shareable table of everything, for everyone.

  • My Tasks split into Open (by priority) and Completed, with inline status changes
  • Organization-wide table filterable by project, type, status, priority, assignee, sprint, and deadline
  • Every filter and sort lives in the URL, so a view is bookmarkable and shareable
  • Sort by updated, created, due date, priority, status, title, or manual rank
  • CSV and Excel export of exactly what's filtered, capped at 5,000 rows

Module 6 of 9

Bulk Import

Bring your backlog with you — from a spreadsheet, a Jira/Azure CSV export, or a live connection — without duplicating what's already there.

  • Excel/CSV import with auto-detected column mapping
  • Jira and Azure Boards CSV import that updates existing tasks by key, instead of duplicating them
  • Live Jira Cloud and Azure DevOps import via API token or PAT; nothing is stored after import
  • Four-step wizard: source, load, preview & map, import — with per-row override and exclusion
  • Imports capped at 1,000 rows per run, with a single batch notification instead of a per-task flood

Module 7 of 9

Team Chat

Real-time direct messages and groups scoped to your organization's members — separate from task comments, for everything else.

  • Direct messages and named groups of up to 50 members
  • Add people to an existing group later without starting over
  • Images (up to 5 per message) and text up to 4,000 characters
  • Automatic resend of messages sent while the connection was reconnecting
  • Scoped entirely to organization members — the platform owner has no access

Module 8 of 9

Notifications & Webhooks

Outgoing webhooks to Discord, Slack, or Teams turn task activity into a live channel feed, with delivery you can actually see.

  • Per-project or org-wide webhooks, scoped to the events you pick
  • Ten event types: created, reassigned, status change, deleted, attached, imported, commented, @mentioned, deadline approaching, deadline missed
  • Test send before relying on a webhook; pause without deleting
  • Recent deliveries log with status and error detail for diagnosing a bad channel
  • Encrypted-at-rest webhook URLs; daily automated deadline reminders need no manual trigger

Module 9 of 9

Platform Admin Console

The platform owner (Master) approves, suspends, and steps into any organization — without ever being a member of one.

  • Platform-wide stats: pending requests, organizations, users, projects, tasks
  • Approve or reject pending workspace requests
  • Suspend an active organization (locks out every member) or restore it
  • Organization switcher to step into any workspace and look around
  • No visibility into chat — the Master role is deliberately scoped out of it

How it works

From a registered workspace to a shipped sprint

Every screen reads and writes the same task record. Nothing is re-typed between the backlog, the board, the table, and the chat someone gets pinged in.

  1. 1

    Request or join a workspace

    Register a new organization (reviewed by the platform owner) or accept a teammate's invite link, and land in your own private workspace.

  2. 2

    Set up the project and import

    Create a project with its key, then bring existing work in from Excel, a Jira/Azure export, or a live connection — mapped and previewed before anything commits.

  3. 3

    Plan the sprint

    Drag tasks between the backlog and an open sprint, start the sprint, and the board scopes itself to exactly what's in flight.

  4. 4

    Work the board

    Cards move across To Do → In Progress → Code Review → Done as the team works, with comments, @mentions, and attachments collecting on each task.

  5. 5

    Stay notified without watching

    Discord, Slack, or Teams gets pinged on the events you chose — a reassignment, a mention, a deadline — instead of someone checking the board all day.

  6. 6

    Close the sprint and report

    Complete the sprint, route what's left to the backlog or the next sprint, and export exactly the filtered view a stakeholder actually asked for.

Built for every seat

One platform, every role covered.

  • Admin

    Before
    Manages members, roles, and integrations by asking around who has access to what.
    After
    One Settings area for members, roles, invitations, and webhooks — with a join link generated, not emailed through a separate system.

  • Manager

    Before
    Plans sprints in one tool and reports status in another, by hand.
    After
    Sprint planning, assignment, and the board all live in the same record — nothing to reconcile before standup.

  • Developer

    Before
    Loses track of what's actually assigned to them across projects.
    After
    My Tasks shows everything open and completed, sorted by priority, with status changes made inline.

  • Platform owner

    Before
    Supporting multiple customer workspaces means separate logins and no shared view.
    After
    One admin console to approve, suspend, and step into any organization on the platform.

Connected stack

Plays well with the systems you already run.

TaskFlow is the operational core — and it connects outward to the tools around it, so nothing gets typed twice.

  • Notifications

    • Discord webhooks
    • Slack webhooks
    • Microsoft Teams webhooks

  • Import sources

    • Excel / CSV
    • Jira (CSV export)
    • Jira Cloud (live)
    • Azure Boards (CSV export)
    • Azure DevOps (live)

  • Data

    • CSV export
    • Excel export
    • Shareable, URL-encoded filtered views

Security, control & compliance

Enterprise controls, whatever your size.

  • Organization-scoped data

    Every project, task, member, and integration belongs to exactly one organization — there's no cross-workspace visibility outside the platform owner's admin console.

  • Role-based permissions

    Developer, Manager, Admin, and Master each unlock a distinct, enforced set of actions — see the full reference in the manual.

  • Encrypted webhook URLs

    Webhook destinations are encrypted at rest, with a recent-deliveries log so a misconfigured channel is diagnosable, not a mystery.

  • Rate-limited sign-in

    Repeated failed sign-in attempts are rate-limited per account and per network address before a retry is allowed.

  • Scoped, time-boxed invites

    Join links are tied to a specific email and role, expire after 7 days, and can only be used once.

  • Data ownership & export

    CSV and Excel export are available on demand from the organization-wide task table, filtered to exactly what you're looking at.

Getting started

Live in weeks, not quarters.

  1. Day 1

    Register & get approved

    Request a workspace with your organization's details. The platform owner reviews it before anyone can sign in.

  2. Week 1

    Invite your team

    As the first Admin, invite teammates by email and role from Settings — each gets a one-time join link valid for 7 days.

  3. Week 2

    Import your backlog

    Bring existing work in from Excel, a Jira/Azure export, or a live connection, previewing and mapping every row before it commits.

  4. Week 2 onward

    Plan the first sprint

    Drag tasks from the backlog into a sprint, start it, and wire up a webhook so your team's chat channel sees activity as it happens.

We stopped losing the first week of every migration to CSV cleanup. Re-importing the same Jira export just updates what's already there instead of duplicating it.
BuilderSoft Product TeamFrom the TaskFlow design notes
The batch notification on large imports wasn't a nice-to-have — a 400-row import pinging the channel 400 times would have gotten the webhook muted by lunch.
BuilderSoft EngineeringOn designing TaskFlow's notification system

Questions

TaskFlow FAQ

Something not covered here? Email info@buildersoft.ca — a human answers within one business day.

What is TaskFlow?

TaskFlow is BuilderSoft's team task-management platform: projects, sprints, a Kanban board, a filterable task table, comments with @mentions and attachments, built-in team chat, bulk import, and outgoing notifications to Discord, Slack, and Teams — all scoped to your organization's own private workspace.

Who is TaskFlow built for?

Teams who want sprint planning, a task board, and status reporting in one system instead of split across a separate tracker, a spreadsheet, and a chat app. Every role — Developer, Manager, and Admin — gets a view scoped to what they need.

Can I import my existing tasks from Jira or Azure DevOps?

Yes. Upload a Jira or Azure Boards CSV export, or connect live with an API token/PAT. Issue keys and work item IDs are preserved, so re-importing the same file updates existing tasks instead of duplicating them.

Will a big import flood our Discord/Slack/Teams channel?

No. Imports send a single batch summary to your notification channels; per-task pings stop after the first 25, so a 1,000-row import can't spam the channel.

Can more than one sprint run at a time?

Only one sprint per project can be active at once — you complete the running sprint before starting the next. Any number of sprints can be planned ahead of it.

Who can see and change what?

Developers can view everything in their organization but only edit tasks assigned to them. Managers and Admins can edit, assign, and delete any task, manage sprints, and import in bulk. Only Admins manage members, roles, and webhooks. The full breakdown is in the manual's roles & permissions reference.

Is my organization's data isolated from other TaskFlow customers?

Yes. Every project, task, member, and integration belongs to exactly one organization. The platform owner can approve, suspend, or step into a workspace to help, but is not a member of any organization and has no access to its chat.

See your work running in TaskFlow this week.

A 30-minute demo with your own project structure — no slideware.

Book a demo