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.
Working terms
Clear from the start.
These points go into the project agreement before work begins.
Payment
50% is due before the build starts. The remaining 50% is due after the agreed work is delivered.
Small revisions
Three small revisions to the agreed work are included. Further revisions are billed separately.
Changes in scope
Major changes or new features are quoted separately before that work begins.
Common questions
What clients ask before we start
These are the questions clients ask me most often.
- Do you need to visit my business to install the system?
- No. We handle the full setup online. Web apps open from a link. For a local desktop system, you install a small launcher and enter the licence key. I send you the admin link and your access tokens.
- Where do you deploy the app, and who pays for it?
- You choose any available domain, and I can set it up for you. I suggest hosting based on the number of users and the app’s needs. Free plans include Vercel and Netlify. Paid options include Hostinger, Oracle Cloud, a VPS, or AWS for large company systems. If you already chose a provider, we use it. You pay the domain and hosting fees directly.
- How much does a project cost?
- The price depends on the work, time, and project size. I price each project after we agree on the scope.
- Do you offer support after launch?
- Yes. Basic questions and help after handover are free. Ongoing maintenance and technical support are available when needed for a monthly fee.
01
02
03
04