The consulting contract
A mission the provider steers: workshops, committees, recommendations, often an intangible deliverable. What matters is the record of what the mission made possible, and the staffing of the consultants.
A contract is not decided when it is signed. It is decided every week, in the gap between what was promised and what is being produced. In pylotik, each project has its contract, where the billing mode is chosen, and maintenance contracts are part of the core. This page is the entry point: the type of contract, the billing mode, the governance around it, and the interventions counted against it.
What changes from one contract to another is what is owed. What does not change is the client's question: where are you with what you promised me?
A mission the provider steers: workshops, committees, recommendations, often an intangible deliverable. What matters is the record of what the mission made possible, and the staffing of the consultants.
Milestones, deliverables, payment terms and client obligations. What matters is seeing the margin take shape and holding the dates, before the gap is discovered at billing time.
A period, a volume in days, a catalog of authorized interventions, a committee. What matters is a consumed volume the client reads exactly as you do, and a history nobody has to rebuild the day before renewal.
The billing mode says how the work is paid for. It does not say who steers it, a distinction explained on the commitment levels page.
A schedule tied to the milestones. The gap between consumed and sold is computed when time is entered, and the margin at completion is visible from the first month, not at closing. See fixed-price project tracking and profitability and margin.
A monthly schedule computed on the days produced and the rate of each profile. The need is no longer to defend a margin against a fixed price, but to reconcile the days produced with what was announced. See project time tracking.
In both modes, pylotik tracks ordered, invoiced, paid and outstanding amounts, then sends billing orders to your ERP's financial management, which issues the invoice. Details on project financial tracking.
A well-executed contract is one whose decisions are dated. Governance is not an extra layer on top of the contract: it is what turns an announced date into a commitment kept, or into a gap that gets decided on.
Project committee, steering committee, maintenance committee: each has its rhythm and its agenda. See project governance, the steering committee and the project committee.
Who does the work, who approves, who is consulted, on both sides of the contract, with a single approver per decision. See the RACI matrix.
Each committee produces minutes submitted to the client, approved or rejected with a reason, then frozen. See client approval of minutes.
The Interventions module, from the Business tier, schedules the intervention by half-day against real workload, then has its completion signed off by the client. It stays attached to its contract: on a maintenance contract, it is deducted from the volume; on time and materials, it is valued at the rate of its intervention type; on fixed-price, the contract keeps its own schedule.
That link is what makes the difference with a shared calendar: the consumed volume you read is the one the client reads. Details on intervention management.
pylotik covers part of an ERP's functions, but covers neither financial management nor accounting: it prepares billing orders, and your ERP's financial management issues the invoice. See the ERP functions covered.
When the client manages the people itself and buys days with no trajectory carried by the provider, there is no execution to steer on the provider's side. It is not time and materials that rules it out, it is the absence of steering.
Yes. A project has its contract, fixed-price or time and materials, and a maintenance contract can take over after go-live. The client record brings them together: production and billing progress of each project, and the financial overview.
They see what concerns them: milestones, minutes to approve, interventions to sign off, the indicators of their maintenance contract. They see neither your costs nor your teams' workload. Their access is free.
The same mechanisms apply, without purchase order or penalty: dates announced in committee that become due. See internal projects.
No, maintenance contracts are part of the core. Only intervention scheduling and signed sign-off form a module, from the Business tier.
The demo runs on a data set that is already filled in: a fixed-price project, a maintenance contract, their committees and their interventions.