Skip to content

What to bring to the first call.

30-45 min · No SDR layer · Engineer-led

You've booked or you're about to. Most agency first calls are sales pitches with discovery questions tacked on. Ours are the opposite. The conversation is with the engineer who would lead your build, the goal is to find out whether we are the right fit, and by the end we will say so plainly. Here's how to make the time worth it.

The five things that make the call efficient

  1. The problem in one sentence. Force yourself to write the operational problem in a single sentence before the call. "Our salespeople spend two hours a day pulling account history out of three systems before each meeting." If you cannot reduce it to one sentence, the call will surface it together — but that takes 15 minutes that could go elsewhere.
  2. The three to five systems in scope. CRM, ERP, ticketing, document store, project management, custom app. List the systems we'll likely integrate against. The architecture conversation depends on this answer more than anything else.
  3. Who decides. Name the person who can approve a six-figure engagement. If they cannot join the first call, plan to brief them within two business days. Two-step approval through someone who wasn't on the call is the single biggest delay between brief and signature.
  4. Constraints, not just goals. Compliance posture (Privacy Act, APRA CPS 234, IRAP), data residency (AU-only, region-flexible), identity provider (Entra ID, Okta, Google Workspace), budget cap, deadline, vendor restrictions. Constraints shape the answer far more than the goals do.
  5. What we should not do. Past attempts that failed. Internal politics we should not walk into. Vendors that are no-go. Tell us up front and we will design around it. Most agencies discover this in week three.

What we will cover

  • Your situation in plain language. We listen more than we talk for the first 10 minutes.
  • The operational map. Which systems, which workflows, which people. Where the data lives. Where the decisions get made.
  • The likely shape. We tell you what we think the build looks like and roughly what it costs. Not a quote — a frame.
  • Whether we are right for it. If we are, we say so and propose next steps. If we are not, we say so and point you elsewhere.
  • Next-step options. Discovery sprint, fixed-price proposal, or "let's talk again in a month when the project is unblocked".

What good prep looks like in practice

If you have 30 minutes before the call, use it like this:

  • 5 minutes. Read the pricing page. It tells you what real builds cost so we don't waste call time on bands.
  • 10 minutes. Open the relevant service page (or Bedstone OS if you're after an internal AI workspace) and check that what we describe matches what you need.
  • 10 minutes. Write the one-sentence problem statement and the three-to-five system list.
  • 5 minutes. Note the constraints and the no-gos.

You will arrive better prepared than 90% of the prospects we talk to. The call ends with a clear next step.

What we don't need on the first call

  • An RFP document. They almost always over-specify the wrong things and under-specify the right ones. If you have one, share it as background; we won't read it during the call.
  • A specific tool stack already chosen. Tool choice is a downstream decision. Bring the problem; we will help with the tooling.
  • Approval from procurement. That happens after we agree there's a fit.
  • A polished pitch deck about your company. We've probably already looked. If we haven't, we ask.
  • A signed NDA. We will sign yours if you need one, but the first call usually does not produce information that needs one. Save the paperwork friction for the proposal stage.

What happens after the call

  • Within 24 hours: a written follow-up. What we heard, what we think the shape is, what we'd recommend as next steps.
  • Within 3 business days: either a fixed-price proposal (where the scope is clear enough from the call) or a discovery sprint proposal (where it isn't).
  • Within 2 weeks of signature: kickoff. First-week work begins.

What if you're not ready yet

That's fine. Most operators are still working out the problem when they first reach out. Useful options:

  • Read the how to pick an AI agency piece. It is written to help you decide what to look for, not to sell you on us specifically.
  • Read the in-house team vs agency piece if you're undecided about whether to outsource at all.
  • Look at common patterns to see whether your situation matches something we've built before.
  • Email contact@bedstone.ai with a single paragraph about what you're working on. We will reply within 24 hours, normally same-day, with what we think the right path is — including pointing you to a different provider if that's the honest answer.

Related reading

Start a brief