One task list. Everybody's work on it.
A follow-up call, a support ticket, a project milestone, emptying the dust extractor and a production stage are all tasks. Gydon keeps them in one place, because filing everybody's work under somebody else's module is how a system starts feeling like it is not for you.
Recorded once, reportable everywhere
Shop floor time and office time use the same model. That sounds like an implementation detail until you try to answer a question that crosses the line, like what a job really cost including the drawing work, or how much of last month went on a customer who is not profitable.
Elsewhere this is sold as an add-on that bridges two separate systems. Here it is simply how it works.
- A running clock, or time entered afterwards, whichever suits the work
- Cost rate and billable rate per person
- Workload across a week, so overcommitment is visible before it bites
For the work that is a job of work
Where a piece of work is bigger than an order, projects give it a portfolio view, a planner, team capacity and templates so the same shape of job does not have to be set up from scratch each time. Applying a template creates its tasks the same way raising a work order creates its production steps.
Tickets against the customer, not in a separate inbox
Support tickets sit on the account they belong to, next to the orders and deliveries that probably caused them. Service levels, canned responses and a knowledge base keep the answers consistent, and the person who picks up the phone can see the whole relationship rather than one complaint.
The people side, without another subscription
A people directory, an org chart, leave requests and approvals, an absence register, a team calendar and a payroll export. It is the practical half of HR rather than the whole discipline, and it is there because a small manufacturer should not need a fourth system to book a week off.
