For contractors

Project Software for Contractors

One project file from request to close-out. The estimate that was offered, the planning that was agreed, the progress and what has actually been booked, kept together and linked.

WHAT IT IS

A contractor's project usually lives in four places.

A request list in Excel. A calculation in another Excel. A planning in a third. The costs in the ERP. Nobody sees them side by side, so deviations are found late, often when the invoice is already wrong. GUSTY keeps these together in one project file: the request, the estimate with its versions and offers, the planning with its baseline, the progress, and what has actually been booked in the ERP. On top of that sits a copilot that does not add another overview. It tells each project leader what is waiting on them: a gate that is overdue, a date that moved, hours nobody accounted for, a forecast running over budget.

HOW IT WORKS

From request to close-out, on one route.

  1. Every project follows the same route

    Five phases: initiation, definition, preparation, execution and close-out, each with its own milestones. You decide what the phases are called, which ones you use and which milestones every project passes.

  2. The offered estimate stays as it went out

    The project leader builds the estimate from labour hours, materials, external services and subcontracted work, using your own units and rates. Offering freezes that version with the quote attached. A change after that is a new version.

  3. One baseline, every date move logged

    When the order comes in, the planning is laid down once as the baseline. After that, dates can still move, but every move is logged with what carried it and, if given, a reason. The baseline also releases the project to the resource scheduler.

  4. Bookings come from the ERP

    Project numbers, purchase invoices and booked hours are read from your ERP every night and shown against the order value and the estimate. They are never typed over in GUSTY. What the ERP does not hold, such as the estimate, the planning and progress, is kept in GUSTY.

WHAT YOU SEE

Six views across the project flow.

  • My projects

    Each project leader's own projects, shown in the phase they are standing in. The project file opens from here.

  • The project file

    One project in six tabs: request, planning, estimate, progress, financial and summary.

  • Estimate and offers

    The calculation with its versions, the offer that went out, and after the order a post-calculation view beside the frozen offer.

  • Project copilot

    A queue per project leader, not a dashboard. Running projects first, and against each one the lines waiting on them. Every line is answered in place.

  • Resource scheduling

    The scheduler's grid: people per day, with the projects that still need people. A project appears here once its baseline is set.

  • Insights across all projects

    What is missing on projects, what they have cost, the request list and the subprojects, read across the whole portfolio.

HOW YOU START

How implementation begins.

  1. We talk to a project leader, the scheduler and whoever controls the finances. How do you calculate today, which phases do you recognise, and where do your documents live?
  2. We connect your ERP for projects, bookings and subprojects, and configure your phases, milestones, units and rates.
  3. Running projects are brought in one by one from the original quotes, calculations and plannings, starting with a handful from one project leader and checked together.

PRACTICAL

Pricing model, data, and setup time.

  • Pricing

    Scoped during initial conversation

  • Data source

    ERP integration for projects, bookings and subprojects, refreshed nightly

  • Setup time

    Scoped during initial conversation

  • Audience

    Project leaders, resource schedulers, managers at industrial contractors