The estimating vendor has no users API, so the roster is derived: every cached estimate carries its author's email, and the distinct set is the roster. Each author can be mapped to one of your employees. 'Built by' is the immutable original author and is never edited; the mapping decides ownership.
Also called: estimator roster · built by · map the estimator to an employee · commission attribution
- 1Distinct author emails across cached estimates form the roster, with a count per author.
- 2Mapping an author to an employee is one row and resolves every job, past and future.
- 3Confirming a map also sets that employee as the owner of all the author's estimates by default; owner stays independently reassignable per estimate.
- 4Auto-detect surfaces a one-click confirmation whenever an author's email matches an existing employee.
- 5The cross-walk is by email only, never by name.
Nobody could answer who built a given estimate, which makes commission, coaching and 'who do I ask about this one' guesswork across a book of hundreds. Every author is now resolved to an employee and mapped across every job they ever built, past and future. The cross-walk is by email only and never by name, because name-matching corrupts attribution the first time two people share a surname or somebody's account says Mike while their estimates say Michael.
- No employee attribution on estimates authored in an external tool
- Attribution corrupted by name matching
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →