Many project teams already run critical registers, progress tracking, cost-code forecasts and look-ahead planning in Excel. The challenge is whether the project information is structured enough to support repeatable forecasting, reporting and review.
Pi Labs can help teams assess their current Excel-based project information, prepare a controlled PI workflow, run a managed forecasting pilot and move into retained support where a project or organisation is ready.
Project teams often have the information they need, but it is spread across registers, trackers, cost reports, progress sheets, quantity schedules and look-ahead files. Different people own different parts of the picture.
Field progress, resource expenditure, cost-code structure, register completeness and forecasting assumptions may not line up cleanly.
Managed implementation support is for teams that want to test PI against real project information under a controlled boundary, rather than treating a free evaluation tool as a live production deployment.
Paid services require a written scope, order form, statement of work, approved pilot, commercial-use licence or other written agreement with Pi Labs.
Start with the smallest useful step, then expand only after the workflow has been tested and reviewed.
The diagnostic reviews whether current project information is ready for a PI-compatible forecasting and reporting workflow.
A managed pilot tests PI against an agreed real project workflow under an approved pilot or written commercial arrangement.
A support retainer is for teams that have moved beyond self-guided evaluation and want a structured support rhythm around their PI-compatible project-controls workflow.
Support for organisations that want PI-compatible information requirements reflected in tender, contract, project controls or data-readiness documents.
Support to build or rationalise type libraries, cost-code mappings, progress gates and template structures before PI is trialled or specified.
Assess the current state, prepare a controlled boundary, pilot the workflow, report the findings and support only after validation.
Review the workbook, register, cost-code, progress and reporting environment.
Agree the workbook boundary, target registers, reporting cycle, assumptions and backup controls.
Run PI against the agreed project workflow under an approved pilot or written commercial arrangement.
Summarise what the pilot proved, what it did not prove and where data quality needs improvement.
Move to retained support, specifications or licensing only when the responsible team has validated the workflow.
Pi Labs can provide a mutual NDA before detailed confidential project, tender, workbook or commercial information is exchanged.
Paid services are governed by a written scope, order form or statement of work and applicable service terms issued for the engagement. The NDA, service terms, retainer T&Cs and SOW templates are not published as unrestricted downloads in this website update.
Pi Labs can support the agreed PI deliverables, but does not automatically take responsibility for client project approvals, source-data truth, payment certification, legal or commercial decisions, contract administration, safety, design assurance, claims, variation entitlement or production decisions.
Commercial support is designed to help structure the workflow, not to remove the team’s responsibility to review and approve project information and downstream decisions.
The Free Community Edition is intended for learning, education, demonstrations, evaluation, self-guided non-commercial use, self-guided workbook setup, template experimentation, student or trainee use and sample workbooks or pilots where PI is not used as a commercial production deployment.
Commercial production use, live project use by a company, company rollout, production deployment, implementation support and priority support will require a paid commercial-use licence, approved pilot or separate written agreement with Pi Labs.
PI can materially change workbook sheets, tables, ranges, formulas, formatting, comments, protection settings, reports and workbook structure. Users and project teams remain responsible for current backups, workbook version history, validation of outputs and downstream decisions.
Email Ryan McCall at Pi Labs with a short description of your project registers, reporting workflow, current Excel-based project controls process and the outcome you want to test.