- Step 3 — Removed the premature close question ("Does it make sense to get you on a call with Erik?"). It came before we'd explained what the call was, which felt out of order.
- Step 3 — Added a clear "Not a Fit" path. If scope or location isn't right, handle it here. Only move to Step 4 if it's a fit.
- Step 4 — Rewrote the Viability Call introduction. Now leads with the purpose of the call ("make sure what you want can happen in the space you have for an affordable price") before asking if it makes sense. Closed question now comes after the explanation, not before it.
For New Hires: Read this script word for word on day one. That is completely fine. The goal over time is to know it well enough that you no longer need it — so your full attention can be on the caller, not the page. Once you know the flow, make the language your own. The words below are a starting point, not a cage.
v2 change: The closing question ("Does it make sense to get you on a call with Erik?") has been removed from this step. It was premature — you haven't explained what the call is yet. Instead, this step now ends with a clear fit / not-a-fit decision. If it's a fit, flow naturally into Step 4. If it's not, handle it here.
Then refer them out graciously. How you treat a non-fit caller reflects on Bosi. They have friends.
v2 change: Rewritten to lead with the PURPOSE of the call before asking if it makes sense. The old version asked for their buy-in before explaining what they were buying into. Now: explain it first, close second.
Why this order works: They just told you what they want. Asking "does it make sense to talk to our owner?" before explaining the call feels like a runaround. Explaining the call first — and leading with what they'll get out of it — makes the yes feel natural. People agree to things they understand, not to vague asks.
Text or call Erik immediately — don't just tag him in JobTread. He needs to know right now.
Log everything in JobTread: full name, phone number, email, neighborhood, project description in their words, lead source, and the booked Viability Call date and time.
Tag Erik in JobTread: "New lead — Viability Call booked for [day/time]. All details in notes."
- Never quote a number. Not a range. Not a ballpark. If they ask about cost: "That's exactly what the Viability Call with Erik is for."
- Never describe our process in detail. If they ask how we work: "Erik will walk you through all of that on the Viability Call."
- Never promise a start date or timeline. You don't know the current schedule. Any number you give will be held against us.
- Never live-transfer the call. The goal is a booked Viability Call. Book the time.
- Never collect contact info before you've engaged them. Name, phone, and email come at the end — after the call is booked. Leading with a form kills the energy.
| "You made an incredible decision reaching out today." | Decision reassurance. Say it right after they say hello. |
| "We've been doing this for almost 50 years." | Credibility anchor. Use it early. |
| "You called the right place." | Use it twice: once after they describe their project, once at the end. |
| "That's exactly what the Viability Call with Erik is for." | Use any time they ask something you can't or shouldn't answer. |
| "It's just a quick Zoom call — you can join from wherever you are." | Reduce friction when introducing the Viability Call. |
| Instead of "what are you trying to get done": | "What's driving this project for you?" or "What does this look like when it's finished?" |
| Instead of "would morning, afternoon, or evening work": | "What part of the day tends to work best for both of you?" |
| If they ask what the Viability Call is: | "It's a 15 to 20 minute Zoom call with Erik — he's one of our owners. He'll hear about your project firsthand and give you a real sense of whether Bosi is the right fit and what working with us looks like." |
| If they're in a hurry: | "Totally understand — it's genuinely just 15 minutes. Can I send you a couple of times to pick from?" |