Questions

No, and it never will. The model produces scope and quantities only. Your price book, day rate, markup and tax settings turn those quantities into money. If you change a rate, every future quote changes with it. Nothing is benchmarked against other contractors.

The assessment says so. Each line carries a confidence, and the job carries an overall verdict on whether a site visit is needed, with the reason stored alongside it. Low-confidence lines are sorted to the top of your editor so you can fix them, ask the customer one follow-up question, or book the visit.

Accurate enough to give a customer a number the same hour, and honest about where it is not. That is the design goal. It measures against reference objects in the photo and against what the customer told you, and it says which of the two it used on every line. You review every quote before it leaves.

Not at launch. The request flow runs in the phone browser, camera and all, from your link or QR code. A native app is on the roadmap once the quoting loop is proven with real contractors, and it will stay free for customers.

Yes, at the database level. Every company is isolated by row-level security in Postgres, not by a filter in the application code. A customer sees their own jobs and the quotes sent to them, never a draft, and never another customer's photos. If you need the detail for a security review, ask support@ubuildit.ai.

You start from a seeded starter book for each trade you select, then edit it. CSV import is on the phase one list, so the rates you have spent years refining come across rather than being retyped.