FAQ
Common questions from firms evaluating Bucky — how it is used across the development, who gets added, and how to roll it out.
These answers use the language people bring to a first conversation. Deeper how-to lives in People on a project and First week with your team.
How do we actually use this?
The same project carries the site from first look through entitlement and team formation.
Week one: one address you already know. Bucky pulls the parcel, zoning, and overlays. You read feasibility and share the read if someone else needs to see it.
After that: screening, go/no-go, definition, entitlement, and who you hire all stay on that file. Parties join when the stage needs them — not as a day-one roster. See people on a project.
Bucky is the pre-development record, not the construction job site. The quickstart is the firm starting path.
Who gets added to a project?
You first. Then only the people who need a seat or a view:
- Team — colleagues who will work in Bucky.
- Viewer or share link — a client or principal who should see the workspace.
- Stakeholder — a planner, lender, or neighbour you track (no login).
- Partner company — a firm you may hire (no login until they need a workspace).
Do not add the whole office on day one. They join by stage — a viewer at go/no-go, a stakeholder at entitlement, a partner when you hire. See people on a project.
What's the best way to roll this out?
One champion, one live project, then one invite. Week two is when you decide whether anyone else needs a seat. After that, deploy means the same project through the development — not a firm-wide IT rollout, and not MCP or the API.
Walk the first week in First week with your team. The stage map is on people on a project.
Last updated on