The Questions We Ask Before We Touch Anything

Scope creep does not usually happen because a project was too complex. It happens because the right questions never got asked at the start. At Heiwa, our first conversation with a nonprofit is less about Salesforce and more about understanding what is actually going on.

Here are the questions we always ask — and why they matter.

• What is the one problem this project is solving?

  • Not five problems. One. If the answer takes several minutes and touches three departments, that tells us something important about what we are actually walking into. Clarity here sets the tone for everything that follows.

• What made this the right time to act?

  • The timing of a project reveals a lot. A grant deadline, a leadership change, a system that finally broke — the reason something is happening now shapes how we approach it and what realistic success looks like.

• What does success look like six months after launch?

  • We push for specifics here. "Everyone is happy" is not a success metric. "Our program team can pull a donor report in under five minutes" is. Vague outcomes lead to undefined scope, which leads to frustration on both sides.

• Walk us through your current process, step by step.

  • This one is where the real picture emerges. Documentation often describes how a process was designed, not how it actually runs. We want to hear it from the people doing the work because that is where the workarounds, the gaps, and the real requirements live.

• Who needs to approve this project?

  • We ask this early because discovering a key decision maker halfway through a build is one of the most common reasons projects stall. Knowing who holds authority — and who needs to be kept in the loop — saves everyone time.

• What is your budget range?

  • We know this can feel like an uncomfortable question. We ask it anyway because a proposal built without budget context helps nobody. We would rather have an honest conversation upfront than deliver something that was never going to work financially.

• Have you tried to solve this before? What happened?

  • Past attempts tell us more than almost anything else. Not to assign blame, but to understand what the organization has already been through and what realistic expectations look like going in.

These conversations happen before we write a single line of a proposal. For nonprofits especially, where budgets are tight and capacity is limited, getting this right from the start is not optional. It is the whole foundation.

If you are planning a project and want to think through it together, we are here.