Discovery call
Project context, target users, current workflow, risks, and success metrics get mapped first.
Process
How I work
A useful project starts with the business case: who needs it, what should become easier, where the value is, and what counts as a win.
MVP shape
The first working version is defined clearly. Nice-to-have features wait.
Agreement
Scope, investment, timeline, milestones, and responsibilities are written before build starts.
Heithem
Discovery, scope, build
Hey Heithem. I want to launch a store, startup, or web app. What should be clear before we start?
Happy to help. Send the rough version first: what the product should do, who will use it, and where it should make money or save time.
A free 30-minute voice or video call is usually enough to map the idea, the risks, the first version, and the success metric.
Good. What kind of investment should I expect for the web app?
The investment becomes clear after discovery. It depends on scope, complexity, timeline, integrations, and what the first version needs to prove.
For a working online store with the important parts included, investment usually starts around $1.5k to $3k. Complex platforms need discovery first, then a clean number.
Makes sense. Let’s start with the call.
Voice call
38 min
Discovery call: project goal, users, MVP scope, risks, timeline, and success metrics.
Okay, what happens now?
Next comes a short agreement: scope, investment, timeline, milestones, what is included, and what is needed from your side.
MVP agreement.pdf
Scope, investment, timeline
Clear. We can start.
Perfect. Once you give the OK on the agreement, work starts.