FAQ
Common questions from firms evaluating Bucky — how it is used across the development, who gets added, coverage, liability, 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.
Don't I already have an analyst, broker, planner, or consultant who does this?
Yes, and Bucky doesn't replace their judgment. It gives that expert a reusable, sourced starting point instead of a blank spreadsheet — so their time goes to the calls that need a human, not to re-deriving parcel and zoning facts on every site. See feasibility.
Will your data be right for my market? We work in one city and we know it.
Coverage expands jurisdiction by jurisdiction, and Bucky shows what's cited, cached, or missing for an address rather than promising universal coverage. Check a site you already know before trusting one you don't. See Coverage.
Who is liable if the data is wrong?
Bucky is decision support, not a permit, appraisal, or legal opinion. Every zoning and feasibility value carries a status so you can see what's sourced from the bylaw and what still needs verification before you rely on it. See Citations and confidence.
We already use GIS, spreadsheets, or a data provider — why add this?
Those tools stay useful. Bucky connects the work that starts at the address and carries it through zoning and feasibility to a deliverable, instead of living as one more disconnected lookup.
Won't this cut into billable hours or proprietary process?
Bucky increases that expert's capacity. Killing a weak site in week one is cheaper than discovering it is weak in week six — the hours that frees up go to judgment, design, and client service, not to re-running diligence you've already paid for once.
Site lookups are metered. Personal hard-stops at 200 a month. Professional continues past 1,000 at $0.10 each. Exports and concurrent projects hard-stop on both plans. See Plans and site lookups.
Is the subscription worth it for my volume?
Run it on one address you already know before judging it against your volume — the quickstart is built for exactly that, not a feature tour. Personal is for an individual in covered cities. Professional continues past 1,000 lookups at $0.10. Developer PAYG is the same $0.10 with no seat extras. See Plans and site lookups.
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