Before the first call

What to bring to a first call (not much)

The first call is 20 minutes, and the only thing it really needs is you describing how the work gets done today. Everything below is helpful, but none of it is required. If you've got five minutes before the call, this page will help you use them well.

Not sure what to say? Most first calls start with "here's what's bugging us."

Helpful, but optional

What helps us understand the business quickly

Bring whatever's easy to grab. Rough is fine; the messier version is usually the more honest one.

  • ✓How the work gets done today. Walk us through one order, job, or request from start to finish: who touches it, where it's written down, and how it moves on.
  • ✓A few screenshots. The screen everyone lives in, the report nobody trusts, the system that's hard to change. Your phone's camera works fine.
  • ✓A sample spreadsheet or form. The one that holds things together. If it has customer, employee, or financial details in it, share your screen instead of sending the file, or send a copy with a few made-up rows.
  • ✓What's frustrating. The thing you'd fix first if you could. "We type everything twice" is a perfectly good starting point.
  • ✓Who's involved. Who does the work, who depends on it, and who makes the call. If the person who knows the process best can join, even better.

Want to organize your thoughts first? Take the two-minute self-check → It gives you a short starting plan you can send along with your call request.

Not needed

What you can leave off the list

These are the things people often think they need before calling. You don't.

Technical specs or documentation

Working out what the software should do is our job, and we do it with you. If you have an existing system with no documentation, that's normal; the code itself tells us a lot.

A budget figure

You don't need a number to talk. It helps to know what the problem costs you today, in time, missed billing, or mistakes, but even that can come later.

Knowing which service fits

Improve what you have, connect it, or build something new: sorting that out is what the call is for. Sometimes the answer is a small change, or nothing new at all.

On the call

What we'll ask about

We start with why, not with technology. Expect questions like these.

THE BUSINESS

What you do and how it runs

Who your customers are, what a typical day looks like, and which tools and people keep things moving.

WHY NOW

What changed

A key person retiring, growth the current setup can't keep up with, a mistake that cost real money, or an idea you're ready to act on.

A GOOD RESULT

What would make it worth it

What would be different if this were solved: hours back, billing that goes out on time, less riding on one person. That's how we decide what's worth building.

What happens after the call

We'll tell you honestly what we think. Sometimes that's a project: we'd suggest a first step, usually sitting down with the people who do the work to map how it really runs. Sometimes it's a smaller change than you expected, or connecting what you already have.

And sometimes it's not us. If the process isn't settled yet, or the real problem is between people rather than systems, we'll say so, and we'll try to point you to someone who can help.

Either way, there's no obligation, and you'll come away with a clearer picture than you started with. See how a project goes from there →

Start in your own words

You already know enough to call.

A 20-minute call, no deck and no pressure. Tell us how the work gets done today and what's getting in the way. Bring a screenshot if it's handy; if not, just bring the problem.