By profession Steering software for integrators

Steering software for integrators has to follow the same client from the deployment project to the maintenance contract that extends it, with the suppliers who deliver a part of the system and the teams who move from one site to the next. IT integrator, industrial integrator or business software integrator: the profession differs, the question stays the same, keeping what was promised to the client. pylotik manages these commitments, their milestones, staffing and team workload on a single set of data, which your client follows and validates.

The problem

When the task board is no longer enough.

Trello, a spreadsheet and email threads hold up as long as projects are few and everyone talks to each other. Then the portfolio grows, and the same symptoms come back.

Projects running late with nobody seeing it coming

Cards move, columns empty, and the go-live milestone slips anyway. The board says what is done, not what was promised or by what date.

Clients who discover the delay at the committee

The client learns of the drift the day it is presented to them. They dispute the minutes, ask what had been decided, and the discussion restarts from memory.

Experts who carry everything, then leave

The same project manager or the same technician is on three sites and an on-call rota. Without a workload plan, overload is not visible before they leave, and knowledge of the project leaves with them.

This is not a matter of filling in a task tool better. What is missing is what links the contract, the schedule, the teams and the client: steering, in the sense of what was promised and the means to keep it.

Three professions, one relationship

IT, industrial or business software integrator.

The system delivered changes from one profession to the next. The relationship with the client always follows the same thread.

IT integration

Infrastructure, networks, workstations, cybersecurity: a fixed-price deployment project, work packages by site, then a maintenance contract with a volume of days and a regular committee.

Industrial integration

Automation, robotics, industrial IT: design, factory acceptance and commissioning milestones, technicians on site, and a client who accepts the work.

Business software integration

ERP, MES, PLM, CRM or management software: a vendor you depend on, functional work packages, acceptance tests validated by the client, then maintenance by volume. To place these families, see the enterprise software landscape and MES or ERP.

In practice

What pylotik brings to an integrator.

It replaces the task tool and the tracking spreadsheet. Your technical tools, your project ticketing and your ERP stay in place.

From the deployment fixed price to the maintenance contract

A project carries its contract, fixed-price with a milestone-based payment schedule or time and materials: ordered, invoiced, paid, balance due and margin at completion in the same place. The maintenance contract that follows carries its period, its volume in days, its catalog and its committee. See maintenance contract management.

Staffing and team workload

Who works on which project, week after week: the forecast workload plan is checked against milestones, time entry is done weekly, and overload or underload alerts go up to the manager. See team steering.

Suppliers linked to the project

The vendor, the manufacturer or the subcontractor runs its own project, linked to yours. Dependencies between projects and milestones are watched: a milestone that slips at a supplier shows up on your side. See multi-project and multi-party steering.

A client who follows and validates

Your client gets free access to their own space. They follow their projects and contracts, validate or refuse committee minutes and amendments, without ever seeing your margins or your workload. See the client portal.

Committees held on the working screen

Decisions, actions and risks are kept up to date from week to week and frozen at every committee. The minutes are no longer rewritten the night before: they are submitted to the client, who validates them.

On-site interventions, as a second step

With the Interventions module, from the Business tier, an intervention is scheduled by the half-day against real workload and accepted by the client's signature. See intervention management.

Nobody is rated, nothing is scored: feedback from teams goes to the recipient its author chooses. This is what we call operational commitment management: reference data, time-stamped, that the client and the supplier each read according to their rights. The full tour is on the product page.

The tools in place

Your ERP stays your ERP.

An integrator almost always has an ERP for sales management, invoicing and accounting, and an incident ticketing tool for support. pylotik does not replace them: it steers what happens before the invoice, and sends billing orders to the ERP through a connector built to your needs. Project ticketing, such as Jira, connects in the same way. What it replaces is the project task tool, such as Trello, Asana or Monday, and the tracking sheets rebuilt before every committee. The difference between the two families is detailed in ERP or steering software, and the comparison with Trello in the alternative to Trello.

The limits

What pylotik does not do for an integrator.

Out of scope pylotik is not an ERP, does not keep the books and does not issue invoices. It is neither a CMMS nor an asset management tool: no equipment inventory, no spare parts, no stock. It is not an IT service management (ITSM) tool: no incident queue, no SLA calculation, no automatic contract renewal or expiry alert. No routes, no geolocation, no offline mode for interventions. A project has a single client, and a subcontractor does not have an account in another's project: it runs its own, linked to yours.

Seat and module prices are public on the pricing page, and the comparisons place pylotik against the other families of software.

Frequently asked questions

What integrators ask us.

Does pylotik replace Trello?

Yes, for client projects: work packages, tasks, milestones and schedule live in pylotik, with the contract, staffing and the client. It replaces the project task tool, not the project ticketing tool or the ERP.

Can we keep our ERP?

Yes. The ERP keeps invoicing and accounting. pylotik sends it billing orders, through a connector built to your needs.

Can our clients log in?

Yes, for free, on every tier. The client follows their projects and maintenance contracts, validates or refuses minutes, interventions and amendments, and sees neither your margins, nor your workload, nor your HR data.

Do you manage our maintenance SLAs?

No. pylotik steers the maintenance contract, its volume in days, its catalog, its committees and its indicators shared with the client. Calculating incident response and resolution times belongs to an ITSM tool.

Where is the data hosted?

In France, with a host under French law and no American parent company, with backups at a second French provider. pylotik is published by orgatypik SAS, in Toulouse. The detail is on the sovereignty page.

Project management in IT services: fixed prices, staffing and continuous margin.
Project management in industry: capital works, maintenance and subcontractors.
Maintenance contracts: period, volume, catalog and committee.
French project steering software: what each one documents.