← Resources

Pain Point → Implementation: How to Think Like a Builder

•15 min read•Team Onboarding Series #5

"Clients don't hire you to write code. They hire you to solve problems."

But here's the catch: Clients often don't know what they actually need.

They say "I need a login system" but mean "I need to reduce support tickets from password resets." If you build what they ask for instead of what they need, they reject the delivery and you don't get paid.

This guide teaches the 7-step framework ScopeLock uses to go from vague client pain → precise implementation plan → AC Green delivery.

The 7-Step Framework

Step 1: Pain Point

What hurts?

Extract the real problem, not the solution client asks for

The Question

"What problem is the client actually experiencing?"

How to Extract This

Most clients describe solutions (what they think they need), not problems (what actually hurts).

❌ Bad client brief
"I need a chatbot on my website."
✅ Good pain extraction
You: "What problem are you trying to solve with a chatbot?"
Client: "I get 50+ emails per day asking the same 5 questions. I spend 2 hours daily copying the same answers."
See the difference?
  • Solution thinking: "chatbot"
  • Problem thinking: "Wasting 2hrs/day on repetitive emails"

Real Example: TherapyKin

Client said: "I need voice AI for my therapy app."

We extracted:

Pain: Therapists spend 15 min/session taking notes instead of listening to clients. Notes are inconsistent and hard to search.

Impact: Lower session quality, harder to track patient progress, can't scale practice.

Why this matters: Now we know success = "reduce note-taking time to <2 min AND make notes searchable."

Step 1 of 7

7-Step Checklist (Interactive)

Use this checklist before you write ANY code. Progress is saved automatically.

✅ Step 1: Pain Point

✅ Step 2: Objective

✅ Step 3: Architecture

✅ Step 4: Flow

✅ Step 5: Test Plan

✅ Step 6: Implementation

✅ Step 7: Verification

Progress: 0 / 21 items completed

Common Mistakes & How to Avoid Them

❌ Mistake 1: Building What Client Says, Not What They Need

Example:

Client: "I need a mobile app."

You: *Builds mobile app*

Client: "This doesn't solve my problem. I just wanted customers to book appointments easily."

Fix:

Extract the pain first: "What problem does a mobile app solve?"

Real need: "Easy appointment booking" → Could be solved with:

  • Mobile app (expensive, 3 weeks)
  • Web app (cheaper, 1 week)
  • Calendly integration (cheapest, 2 hours)

Ask: "What's the simplest solution to the pain?"

❌ Mistake 2: Skipping the Test Plan

Example:

You build a "fast dashboard" but never define "fast."

Client: "This is too slow."

You: "It loads in 4 seconds, that's fast!"

Client: "I expected <1 second."

Fix:

Define "fast" in Step 2 (Objective):

  • Dashboard loads in <1s (p95)
  • Queries return in <500ms
  • Lighthouse performance >90

Now it's objective pass/fail, not subjective opinion.

❌ Mistake 3: Building Everything at Once (Big Bang Integration)

Example:

Week 1-2: Build database

Week 3: Build API

Week 4: Build UI

Week 5: Try to connect everything → Nothing works together

Fix:

Build thin vertical slices:

  • Slice 1: One feature, end-to-end, working
  • Slice 2: Next feature, end-to-end, working
  • Test integration at each slice

Related Resources

🔄
The Complete Mission Flow
See how this framework fits into the full delivery process
💬
How to Talk to AI Citizens
Ask Rafael to generate code from your implementation plan
💰
Compensation Structure
Understand how you get paid for delivering quality work

Questions About This Framework?

This is how every ScopeLock mission starts. If you're unclear on any step, ask:

Remember: Spending 2 hours on Steps 1-5 saves you 20 hours of rework later.