Questions
What people ask before they sign up
Including the two questions a pre-release product is usually asked last: what it costs, and what does not work.
Pre-release
- What is JobSite?
- Construction-management software for Canadian builders. One project record carries the estimate, the budget, the cost records, the tasks and milestones, the daily logs, the documents, the messages, the permits and inspections, the compliance items, the invoices and the holdbacks — so they are one record rather than separate files that have to agree.
- Who is it for?
- Custom home builders, renovators and general contractors working in Ontario who currently run projects, estimates, permits and client communication across spreadsheets and email threads. It is pre-release and is being built with its first customer.
- How is the estimating built?
- JobSite's estimating engine splits responsibility: the language model owns scope, quantities and line descriptions, while code owns every number — contingency, margin and Ontario HST at 13% are computed deterministically. Each line's confidence is derived from the estimate's own flags rather than from a model's opinion of itself. An AI run is enqueued as a governed job with a named purpose, required scopes and an output schema, and a person approves the result before it is acted on.
- Does JobSite handle permits and inspections?
- Permit applications, inspections and compliance items are tracked per project against Ontario and Ottawa references, including seeded zone rules that cite City of Ottawa Zoning By-law 2008-250. There is no automated zoning analysis and no code-compliance engine: obligations are tracked, and compliance outcomes are never promised.
- What does the client portal do?
- Each client can be invited to a portal scoped to their own project. One sign-in page serves the whole platform and routes by role, so client accounts land in their project portal while staff land in the builder workspace. No verified client-portal login has taken place yet, so that describes what the software provides rather than what anyone has done with it.
- How is one builder’s data kept separate from another’s?
- Every request is served over HTTPS with HSTS. Tenant rows carry an organization key and are enforced by Postgres row-level security under a dedicated runtime role that cannot bypass it, and every tenant query carries transaction-local tenant context. API routes resolve the caller’s active organization membership and assert the record’s organization before answering. JobSite’s tables live in a Postgres shared with other Baldwin products, so isolation is by schema and row-level security rather than by a separate database instance.
- What does it cost?
- Nothing is charged today, because there is no published price, no paid plan and no mechanism that could charge one. Creating an account does not collect a payment method. When pricing is decided it will be published before it applies to anyone.
- What does not work yet?
- Outbound and inbound email are not operating. There is no monitored public mailbox, so this site cannot receive a message. There is no zoning analysis and the AI bid drafter is retired. No AI provider key is present in this environment, so whether a model answers a run is unverified. Passkey sign-in is disabled at the identity provider. Each of those is stated on the page where the capability is described, not only here.
Still looking
There is no monitored public mailbox yet, so this site cannot answer a question sent to it. The most useful pages are the walkthrough, the security mechanisms and the two Ontario guides — all of which can be read without asking anyone.
What JobSite does · Security · Construction resources · Contact