Know how every project is going without asking anyone

Portfolio with the health of every project, kanban board with work-in-progress limits, a draggable timeline, team load against capacity and a conversation inbox. Your customer follows their project from their own area, the plan is born from the quoting tool and Bastino does the keyboard work. This is the Projects module of Fisher Platform.

See the workspace See the team orbit Request a demo

Portfolio
Board
Timeline
Team
Inbox
Hours and plan
From the quoting tool
Customer area
Bastino

Portfolio

The health of every project, with the reason for each point it loses

A bare number does not help you decide. Here every project has a health score from 0 to 100 and, below it, what is pulling it down: overdue deadline, progress behind schedule, overdue tasks, cost above budget or days without activity.

tuempresa.fishernetworks.net/admin/projects/workspace

Portfolio. Five sample projects of a construction company: two at risk, one to watch and two doing well.

Health with visible reasonsThresholds for «to watch» and «at risk» are yours to set in Settings. A closed project is not scored.
Pace and upcoming milestonesTasks created and finished per week, and the milestones ahead, including payment milestones still to invoice.
Team load and recent activityWho is short of hours and what happened today, without opening project after project.
It can be exportedThe portfolio goes out through Exports, to take it to the board meeting.

Screenshots of the system with fictitious sample data, with no data from any customer.

Board

A kanban over the same tasks you already have

It is not a copy: the cards are the tasks of the Tasks module. What you move here changes there, with the same rules, notices and timers.

tuempresa.fishernetworks.net/admin/projects/workspace/board/58

Board. Columns by status, a «5/5» in-progress limit, cards blocked by dependencies and the finished ones stacked.

Work-in-progress limitPer column. When it is exceeded, the board warns you or stops the move, as you decide in Settings.
Dependencies without cycles«Waits for #429». A task that waits for another one is flagged, and a cycle is rejected.
Shared viewsSave a filter and share it with the project team or with everyone.
Mouse, finger or keyboardYou can drag with any of the three, undo, and also move from the card menu.

tuempresa.fishernetworks.net/admin/projects/workspace/board/58

Plan. It proposes an assignment; only what you leave ticked is applied.

Assigns by real free timeTasks without an owner or a date, by priority, to whoever can finish them first, counting their load across all their projects.
You decideUntick what you do not want. On applying, it is recalculated on the server and each person gets their assignment notice.
With the rules of TasksAssigning and changing dates follows the same path as doing it by hand, with the same permissions.

Timeline

Plan, milestones and tasks on a single timeline

A window of 2 or 4 weeks, a quarter or the whole project. Bars move and stretch by dragging, and whatever clashes turns red.

tuempresa.fishernetworks.net/admin/projects/workspace/timeline/58

Timeline. Tasks hang from their plan activity; the red line marks a conflicting dependency.

Drag to rescheduleMoving a bar changes the dates; stretching it changes the duration. Also with the keyboard.
Conflicts in plain sightA task that starts before the one it depends on has finished is drawn in red.
Also in the CalendarProject and plan deadlines show up in the unified calendar; a plan one can be dragged and keeps its duration.

Team

Who is overloaded, before they burn out

Each person orbits the project: the more loaded this week, the closer to the centre, and in red if they pass the overload threshold. It is the ERP's own component, with sample data.

Load against capacityPer person and per week: planned, logged and free hours. It subtracts approved absences from Attendance.
Four-week heat mapYou see where work piles up before it arrives.
Burndown per milestonePending, ideal and scope, calculated from the status history of the tasks.

See hours and plan Request a demo

Team orbit

Hospital Los Pinos · Phase 1

This week's load · sample data

Rodrigo Salinas 128 %
Ernesto Villalobos 112 %
Fernanda Beltrán 96 %
Lucía Cabrera 82 %
Camila Arredondo 64 %
Andrés Montoya 58 %
Valeria Núñez 35 %
Mariana Ibarra 20 %

Hover over a person to see their load · it pauses when off screen

tuempresa.fishernetworks.net/admin/projects/workspace/team?project=58

Team. Rodrigo goes over 100 %; Fernanda has a day off and her capacity drops.

You set the thresholdFrom what percentage a person is overloaded, and the hours of an unestimated task, in Settings.
With AttendanceApproved absences reduce capacity, and the working day logged in Attendance is shown next to what was recorded.
Week by weekMove by week and by project, or look at all the open ones together.

Inbox

The conversations of all your projects, in one place

With read status per person, replies, attachments and a summary of what is still open. Each conversation decides whether the customer sees it.

tuempresa.fishernetworks.net/admin/projects/workspace/inbox?project=58

Inbox. Customer messages carry their label; the summary flags what nobody answered.

AttachmentsUp to 10 per message, no executables, stored by Storage with its limit and encryption. They download from the panel and, if the conversation is visible, from the customer area.
«Visible to the customer»Ticked when creating the conversation or in its header. Internal ones never go out.
#123 links the taskType the number and the message opens its sheet.
Summary and BastinoPeople, who wrote last and unanswered questions; «Summarise with Bastino» opens the chat with the request already written.

Hours and plan

Estimated against logged, and the plan tied to the tasks

The plan says how much work was promised; the tasks, how it is going. Here they stop being two lists that drift apart.

Estimated hours on every task

In the form, the sheet, the board card and the API. They are compared with those logged by the timer and turn red if exceeded: on the board, «12.0/6 h».

Status history

From which status to which, who and from where (panel, API, Bastino, portal). The burndown and the weekly pace come from it; a reopened task counts as pending again.

Plan linked to tasks

Each activity becomes a task or is linked to several existing ones. Its progress comes from them, by estimated hours or by finished tasks.

tuempresa.fishernetworks.net/admin/projects/view/58

Work plan. The progress of «Concrete structure» (33) comes from its 6 tasks, so it is not edited by hand.

Convert into a taskWith its name, dates, person, milestone and the pending hours as the estimate.
Link existing tasksOne activity with N tasks, one task in one activity. They can be moved from one to another.
No double countingOn the timeline tasks sit below their activity, and in team load they count, not the activity.

From the quoting tool to the project

What you sold is the plan you start with

When a quote in the quoting tool is accepted, one click generates the implementation plan as a project: no retyping what you already promised.

The quote carries the hoursEvery implementation item brings its hours and its phase, which become milestones and activities.
It schedules itselfActivities are chained over working days, skipping holidays, with the hours per day and the team size from Settings.
Payments are already setThe payment milestones, with their percentage and amount over the implementation, stay in the plan, and the project remembers which quote it comes from.

tuempresa.fishernetworks.net/admin/projects/view/58

A project that comes from a quote. Phases, activities and three payment milestones (30, 30 and 40 %), with «Comes from a quote» at the top.

Payment milestonesThe ones the proposal showed: those of the quote, those in Settings → Quoting tool or those in Settings → Projects. «Milestones to invoice» shows up in the portfolio.
Reschedule the planChange the start date and everything shifts, respecting weekends and holidays.
You set the rulesHours per day, team size, working days and default payment milestones are settings, not code.

Projects in the customer area

Your customer follows their project without calling you to ask

The company's contact signs in to their customer area and sees how things are going. You choose, project by project, what to show them.

tuempresa.fishernetworks.net/clients/projects/58

What the customer sees. Progress, team, visible conversations, milestones, plan and tasks marked for them.

Only their own companyThey see the projects of their company and none of anyone else's.
Chosen per projectMilestones, tasks, plan, team and activity, with defaults in Settings. Internal conversations never go out.
Replies, attaches and opens conversationsIf the project allows it. The team gets a notice for every message.

Conversation of a project seen from the customer area, with messages from the team and the customer, two attached files and the box to reply and choose files — **A conversation, with attachments**The customer downloads what the team attaches and replies from there, with their own files.

Email notices, with nothing to configure

When the team replies, the customer gets an email with the project, an excerpt and the link to their area.
When the customer writes, the project team receives it.
Status changes of tasks visible to the customer also reach them by email.
The texts come ready-made and are edited in Notifications.
Nothing is sent if the customer area or the projects portal is closed, if the contact is inactive or lacks the «Projects» permission, if they turned off «Project emails» or «Task emails», or if their address is on the unsubscribe list.

It comes off by default: you turn it on in Settings → Projects → Customer portal, and contacts need the "Projects" permission.

With Bastino

Ask Bastino for what you would do with the mouse

Bastino, the AI copilot of Fisher Platform, looks up what you see and, with a confirmation card that shows the before and the after, does what you would do, with your permissions. Meet Bastino.

Health of the projects Lookup«Which projects are going badly and why?» It reads the health and its reasons.
Conversations LookupIt reads a conversation, with the customer's side marked as such, and helps summarise it.
Create a project With cardWith its customer and its dates, and you can change its data afterwards.
Move a task on the board With cardIt respects the work-in-progress limit and the rules of Tasks.
Dependencies With cardMake one task wait for another, without cycles.
Plan With cardThe card shows the assignment; on confirming it is recalculated.
Move dates With cardOf a task or of a plan activity.
Estimate tasks and link the plan With cardSets estimated hours and links activities with tasks.
Write in the inbox With cardReplies in a conversation and marks it visible to the customer, if you want.

Bastino needs an AI provider configured, and nothing runs unless you confirm the card. Every action checks your permissions again on confirming.

Connected to the rest

Projects do not live apart

Tasks

The tasks of a project are those of the Tasks module: same status, same owners, same timer.

Quoting tool and Invoicing

The plan comes from the accepted quote and the payment milestones still to invoice show up in the portfolio.

Expenses

The cost of the project (expenses and hours at the hourly rate) goes into its health against the budget.

Calendar and Attendance

Deadlines in the unified calendar and approved absences reducing the team's capacity.

Notifications and Storage

Notices in the app and by email with editable templates; attachments with the destination's limit and encryption.

Everything is adjustable

Areas, columns, limits, health thresholds, hours per task, animations and what the customer sees, from Settings → Projects.

With the Tasks module off, the board and the planner disappear; the portfolio, the timeline, the team and the inbox carry on. It respects dark mode, works on the phone and turns animations off with «reduce motion».

Frequently asked questions

Before you try it

Are the tasks on the board different from those in Tasks?

No. They are the same rows: what you change on the board changes in Tasks and the other way round, with the same status, the same owners and the same notice.

What exactly does my customer see?

What you tick, project by project: progress, milestones, plan, team, activity, the tasks you declare visible and the conversations marked as visible. Internal things never go out. It comes off by default.

Can I use Projects without the quoting tool?

Yes. The quoting tool generates the implementation plan, but you can also create projects by hand, write the plan in the form or ask Bastino to do it.

Is there an email for every message?

Yes: each message sends its notice right away. There is not yet a digest that groups those of the same conversation; it would be a Notifications feature, for all notices.

Can I try it before paying?

Yes. We set up a demo with sample data so you can walk through it with your team. Write on WhatsApp or to proyectos@fishernetworks.net.