LupinusBuildContact
← All guides
Guide 01 · Getting Started

Understanding LupinusBuild

LupinusBuild is designed to keep operational information connected as construction work moves from the earliest customer interaction through quoting, project execution, field activity, and completion.

What LupinusBuild does

LupinusBuild brings operational information into one connected system so customers, proposals, projects, tasks, materials, documentation, and project activity do not have to live in disconnected tools.

The platform is being developed around real construction and specialty-contractor workflows, with an emphasis on maintaining continuity as information moves from one stage of work to the next.

The core workflow

A construction operation rarely begins with a project record. Work typically starts earlier, with a customer, an opportunity, requirements, pricing, and a proposal.

Customer→
Quote→
Proposal→
Approval→
Project→
Operational Work→
Completion

LupinusBuild is designed so relevant information can continue forward rather than being recreated every time the work enters a new operational stage.

One connected operational record

Customer information can support quoting. Approved commercial information can support project setup. Project information can support tasks, documentation, materials, coordination, and field activity.

This continuity is a central product principle: information should remain associated with the work it describes.

Office and field

LupinusBuild is intended to support both the people coordinating work from the office and the people responsible for execution in operational and field environments.

Access and available actions can differ according to a user's role and operational responsibilities.

Current pilot status

LupinusBuild is currently in pilot. Product workflows, access patterns, documentation, and operational details may continue to evolve as the platform is tested and refined.

Documentation principle

These guides document confirmed product behavior. Features that are still being designed or validated will not be presented as completed functionality.