26-014
Turbo Tasks · PORT edition · marine production
Task management you can't get away from.
Projects, orders, resources and time in one place, from the first enquiry to the last warranty visit. Every hour lands on a project. Every order sits on a task. Nothing changes silently.
Turbo Tasks Corporation builds one platform and one edition per industry. PORT — Projects, Orders, Resources, Time — is the edition for marine production and project management.
Waiting 3
In progress 2
In review 1
The problem
Four tools, four versions of the truth.
Tasks in one app, hours in a spreadsheet, purchase orders in e-mail, the offer in somebody's Excel. By Friday nobody knows where the project stands. Turbo Tasks puts all four on one project number.
The modules
Fourteen modules. One project number holding them together.
This is the navigation of the product, not a diagram of it — every entry below is a module you click in the left-hand rail, with the access it is gated on. PORT stands for Projects, Orders, Resources and Time, and those four words are what the fourteen modules are made of.
Two more sit inside Projects rather than in the rail: Offer and margin, the offer with its live margin, and Change log, the record of every edit to the project and its tasks.
The platform and its editions
One engine. One edition per industry.
Turbo Tasks Corporation is the platform: the task engine, the time engine, the permissions, the search, the log. An edition is that engine with the vocabulary, the fields and the workflow of one industry already in place — so nobody spends the first six months configuring what their sector has always needed.
PORT
Marine production and project management Available nowTANK
Defence and security In designGRID
Energy and utilities In designSITE
Construction and installation In designSame engine underneath, so an edition is a vocabulary and a workflow, not a rewrite. If your industry is not on the list, it is a conversation, not a wish.
How it works
One passage, from enquiry to warranty.
A project moves through stages like a vessel through waypoints. The number stays. The history stays. Only the stage changes.
Every screen, with real work in it
This is what a Tuesday looks like.
Nine screens from a project running right now — a hull under automation, its orders, its hours and its margin. The numbers below are a demo dataset, but the screens are the product.
01 · Dashboard
Open it and the day is already sorted.
Your assigned work, overdue first, with hours logged against hours planned. The inbox beside it carries only what concerns you. Switch the whole thing to a board when you would rather drag than read.
My week
WeekMonthListBoardLog time · t26-014Hull 512 · automation4 tasks · 62% done
26-009Ferry retrofit · monitoring2 tasks
26-003R&D · configuration tool1 task
This week
Inbox
02 · Project
One project, one number, four views.
Progress is computed from closed tasks and hours consumed — never typed by anyone. Milestones show how much of their work is done and whether the rest still fits before the date. Epics carry their own hour budget, and finished work folds away.
Hull 512 · automation and monitoring
ListBoardTimelineWeeklyNew task · cMilestones
Automation cabinetepic · 240 h planned · 212 h used · 28 h left
Control softwareepic · 320 h planned · 214 h used · 106 h left
Generalno epic · 4 tasks
6 completed tasks hidden · show
03 · Timeline
The same tasks, on a date axis.
The third rendering of one task set — a Gantt with a real date axis, today's line, milestones as diamonds and the share done inside each bar. Drag a bar and the deadline moves, which is logged like any other change. Nothing here is a second plan kept beside the list; it is the list.
Hull 512 · automation and monitoring
ListBoardTimelineWeeklySep 2026 – Feb 2027Green inside a bar is the share of its hours already logged · dashed is not started · orange is overdue
04 · Time calendar
Drag it onto the day. Stretch it to the hours.
The week as an hour grid with the week's planned tasks beside it. Drop a task at eight, pull it to two, six hours logged. Hold Alt while dragging and it copies to another day, for work that carried on. The eight-second keyboard entry on t has not gone anywhere.
Time calendar
WeekMonth‹Today›Quick entry · t26-014
26-014
26-014
26-014
26-009
26-014
26-014
26-014
26-014
26-014
Planned this week · 6
Other open tasks · 11
05 · Orders
The order sits on the task it serves.
Every purchase carries its lines, its promised date, the task it belongs to and the milestone it can block. Payment stages, transport and customs, and documents live on the order. A delivery promised after the date that needs it turns red where the milestone is, not in somebody's inbox.
Orders
ListTimelineStage: allNew orderORD-0142 · PLC and I/O cards · expanded
Lines
Payment stages
Documents
Serves these tasks
Category
Needed by
06 · Offer and margin
The margin you will actually make.
Hours per expertise at separate engineering and management rates, equipment, services, recurring fees over the contract, a warranty reserve and annual price growth. Sisterships are estimated once and multiplied. The price is the rows grossed up; the margin is read from the numbers and never typed.
Series of 3 · monitoring and remote management
Engineering 60 €/hManagement 90 €/hWon → production| Row | Hours | Cost | Margin | Price |
|---|---|---|---|---|
| Monitoring | 400 | 24 000 € | 30% | 34 286 € |
| Monitoring · 2 sisterships × 16 h | 32 | 1 920 € | 30% | 2 743 € |
| Remote management | 120 | 7 200 € | 30% | 10 286 € |
| Project management | 40 | 3 600 € | 25% | 4 800 € |
| Commissioning · hours row | 96 | 5 760 € | 20% | 7 200 € |
| Equipment estimate | — | 15 000 € | 12% | 17 045 € |
| Equipment · 2 sisterships | — | 4 000 € | 12% | 4 545 € |
| Connectivity and hosting · 36 months | — | 3 600 € | 20% | 4 500 € |
| Price-growth reserve · 5% / a × 3 y | — | −3 273 € | ||
| Warranty reserve · 3% / a × 24 months | — | −5 072 € | ||
| Own cost · one-time, all in | 688 | 65 080 € | ||
| Computed price · one-time | 85 405 € | |||
| Monthly fee · 36 months | 2 500 € | |||
| Contract value · 36 months | +24 920 € | 90 000 € · 28% |
Comments on the offer · 3
07 · Resource plan
Who is loaded, who is free, eight weeks out.
Load per person and per competence, with holidays and sickness already taken out of the week. Utilisation over one hundred per cent is shown rather than hidden, because it is a thing to plan around. Free capacity is the row managers read first.
Resource plan
MineMy projectsEveryoneCompetence: all| Person | W38 | W39 | W40 | W41 | W42 | W43 | W44 | W45 |
|---|---|---|---|---|---|---|---|---|
| Thomas Neumann · Monitoring | 118% | 104% | 88% | 92% | 60% | 55% | 20% | — |
| Claire Dubois · Monitoring | 95% | 90% | 106% | 80% | holiday | holiday | 75% | 50% |
| Marco Rossi · Hybrid | 80% | 92% | 96% | 112% | 88% | 70% | 45% | 15% |
| Sofia Lindqvist · Remote | 62% | 74% | 78% | 90% | 94% | 72% | 40% | — |
| Daniel Berg · Management | 70% | 72% | 68% | 75% | 70% | 66% | 64% | 50% |
| Lucas Meyer · Hybrid | 88% | 102% | 84% | 78% | 80% | 55% | 35% | 10% |
| Free capacity · h | −18 | −4 | 26 | 31 | 88 | 142 | 214 | 268 |
Competence coverage · next 12 weeks
08 · Portfolio timeline
Every project on one axis, with the capacity underneath.
The register's own Gantt: what is running, what is being offered, what is in warranty, and the load each month against what the company actually has. The bar that matters is the one at the bottom — a project starting in January is only good news if January has the hours for it.
Project register
ProgressTimelineSep 2026 – Feb 2027Capacity · committed hours against the month
| Product line | SEP | OCT | NOV | DEC | JAN | FEB |
|---|---|---|---|---|---|---|
| Monitoring | 112% | 94% | 88% | 70% | 48% | 22% |
| Hybrid | 78% | 90% | 104% | 72% | 40% | 15% |
| Remote | 55% | 68% | 74% | 86% | 64% | 35% |
| Free capacity · h | −22 | 36 | 54 | 180 | 312 | 408 |
09 · Log book
The weekly meeting, on the same data.
Recurring meetings keep their roster, their agenda and their protocol. The participants' board is the week's work, not a slide someone prepared. Tasks born in the meeting are listed on its page, priorities are recorded as mentions, and the hour everyone spent is logged to the right project.
Production weekly · W38
Series: weeklyLog 1 h for allParticipants' board · this week
Thomas Neumann · 31.5 h
Claire Dubois · 36 h
Marco Rossi · 30 h
Priorities and mentions
Tasks created in this meeting · 2
Milestones that know
Linked tasks, remaining hours against the capacity left before the date. A milestone with open work cannot be marked reached.
Warehouse and stock
Project stock built from what arrived, quantities and places, issued to the object when it leaves the shelf.
Search that understands
AND, OR, minus a word, quoted phrases and kind prefixes. Find a project, task, order, ticket or wiki page from anywhere.
Visibility by project type
Decide once which teams see sales, production, warranty and admin projects. Anyone with a task in a project sees it.
Wiki and files
Company knowledge and project documents next to the project number, with internal links and AI-drafted first pages.
Seven languages
English, French, German, Italian, Swedish, Danish and Estonian. Every label, button and message translated, switched in one click.
API and agents
Open at both ends.
An operations tool that cannot be reached by your other systems becomes another island, and one that cannot act on its own leaves the chasing to people. So the data has a door, and the work has help standing inside it.
The API
One REST endpoint per object the screens already use — projects, tasks, hours, orders, offers, people, tickets. JSON in, JSON out. A token belongs to a person, so it sees exactly what that person sees; no token can quietly read the whole company.
- Read and write
- Webhooks on change
- Visibility rules apply
- Every call logged
- Typical uses
POST /api/v1/tasks
Authorization: Bearer <company token>
{
"project": "26-014",
"title": "Replace gateway after yard comments",
"assignee": "t.neumann@yard.example",
"allocated_h": 12,
"deadline": "2026-09-26",
"milestone": "FAT"
}
→ 201 { "id": "t-8841", "number": "26-014", "status": "waiting" }
→ webhook task.created → https://your-erp.example/hooks/portAgents inside the app
An agent is a standing instruction that watches your data and does a part of the work nobody enjoys. It is three things: a prompt, a trigger, and a place to put the result.
You can create any kind you like.
It runs on your instance, against your own database. It proposes rather than decides — the draft lands in front of a person, who sends it, edits it or throws it away. Nothing leaves the company on an agent's own authority, and every edit an agent makes is in the change log under its own name.
If the thing you repeat every Friday can be written down, it can usually be handed over.
Pricing
One price. Every feature. Every user.
No tiers to decode, no module locked behind a plan, no per-feature pricing to negotiate. Add people as the team grows, and the whole edition comes with each of them.
- Every feature on this page — Projects, Orders, Resources, Time
- Unlimited projects, tasks, orders, hours and documents
- List, board, timeline, weekly plans and the time calendar
- Offers with live margin, warranty, recurring fees and series pricing
- Change log on everything, in-app notifications per person
- Wiki, files, command palette, seven interface languages
Onboarding and data import
Bringing over projects, people and open orders from Odoo, spreadsheets or e-mail is quoted per company, once we have seen the data.
Your own instance
Each company runs on its own database. Your project numbers, your teams, your visibility rules, your language.
Another industry?
TANK, GRID and SITE are the same engine with another vocabulary. If yours is not on the list, tell us what the work is actually called.
Ready when you are
Stop managing tasks.
Start being unable to lose them.
A demo takes thirty minutes on your own kind of project. Bring the messiest one you have. We will run it in the PORT edition, or talk about the edition your industry needs.
Book a demo