Projects, budgets and teams

Companies buy for many sites at once, with several people involved. Three ideas organise that: projects, teams and plans. Homeowners don't need any of them.

Projects

A project is one job: a site, a scope and a budget. Requests, RFQs, BOQs and purchase orders belong to a project, so the company can see at a glance:

• Committed: what has been ordered from suppliers.
• Received: what has been signed off on site.
• Budget left, and whether the project is heading over it.

A project that would go over budget triggers the owner's approval. A project can be archived once its orders are finished.

Teams and roles

Everyone in a company has one or more roles:

Role	Can
Owner	Everything: team, approval rules, billing. There is always at least one.
Buyer	Build requests and RFQs, issue them, pay, follow orders
Approver	Approve requests and awards up to a personal limit
Site receiver	Check deliveries and sign goods receipts on site
Viewer	See everything, change nothing

The owner invites people by phone or email, sets their roles and approval limits, and can limit them to certain projects.

Lists, spend and the assistant

• Saved lists hold the materials a company buys again and again. One click turns a list into a new request, scaled for the job.
• Spend shows what was bought, by month, project and supplier, and exports for accounting.
• The assistant answers questions about the company's own records, such as "how much have we spent on cable for Hazmieh?", and shows where each answer came from. It never places or changes orders.

Plans

Companies are on a subscription plan (Free, Pro or Enterprise) that sets the number of seats and features. Homeowners and suppliers don't pay a subscription. Suppliers pay commission instead; see commission.

A homeowner who starts working professionally can upgrade to a company account and keep their orders and history.