Find your next move
One question about where you are, one optional question about what’s in the way, and a straight answer about what to do next, including when the answer is that you don’t need to hire anyone yet.
Step 1 of 3
Where are you right now?
Pick whichever sentence sounds most like your situation. There is no wrong answer and nothing to fill in.
Step 2 of 3 (optional)
What’s actually in the way?
This adjusts the answer below. Skip it and the answer still stands.
Step 3 of 3
Your next move
Where you are
Usually one of three things: the scope grew without the timeline growing, one specific technical problem is blocking everything else, or the person building it is at capacity. The fix is different for each, so the first job is working out which.
What matters now
- Name the actual blocker: scope, a specific technical problem, or capacity
- Freeze the feature list until it’s launched
- Get a written scope for whatever’s left
What can wait
- Rebuilding from scratch
- Switching frameworks
- New features
- Redesigning anything
Common risk at this point
Restarting. A rebuild feels like progress and usually resets you to zero with the same scope problem still unsolved.
What I’d suggest
Depends on the blocker. If it’s one technical thing, a Backend, API & Security Module Sprint (from $1,500, 2–4 weeks) fixes it and hands it back documented. If it’s scope, a Discovery Sprint re-cuts it. If it’s capacity, tell me what’s on the list.
One next action
Book a call and describe what’s stuck. If it’s a 20-minute answer, I’ll give you the 20-minute answer.
Think this is close?
This is a general answer built from one sentence about your situation. Thirty minutes gets you a specific one.