How a project goes
These are the same steps in every project. The examples on this page come from a fictional company, but they look exactly like what my clients receive.
Understand before building
- What happens
- One or more calls about how you work today, then I write down what I understood.
- What you receive
- A spec in Arabic: the problem, modules, roles, data, integrations and open questions.
- Typical time
- Days
- What I need from you
- Time with the people who know the daily work, and examples of your current files.
See your system before you sign
- What happens
- I build a clickable prototype of your system with sample data, and record a short video that walks through it. Free when the project is a good fit.
- What you receive
- A link to the prototype that works on a phone, and a walkthrough video.
- Typical time
- Days
- What I need from you
- Honest feedback on the prototype.
An offer priced item by item
- What happens
- I turn the spec and prototype into an offer priced item by item.
- What you receive
- An offer with the price and timeline of each item, release dates and payments.
- Typical time
- Days
- What I need from you
- Choosing the items for the first version.
Releases you test yourselves
- What happens
- I build in releases, and each one reaches you on a staging environment.
- What you receive
- The staging link, and written notes for each release.
- Typical time
- Weeks, depending on the items
- What I need from you
- Testing each release, then approving it or sending your notes.
Yours from day one
- What happens
- Every account and service is created in your company's name, from the repository to the domain.
- What you receive
- An ownership checklist: the repository, servers, domain, store accounts and documents.
- Typical time
- From day one
- What I need from you
- Opening the accounts in your company's name. I'll walk you through each step.
With you after launch
- What happens
- After launch I fix any bug during the support period, then maintenance is optional.
- What you receive
- A support period set in the offer, usually 60 to 90 days.
- Typical time
- After launch
- What I need from you
- A description of the problem when it appears, with a screenshot or screen recording if possible.
How changes work
Any addition outside the items is priced, with its effect on the timeline, before I start on it. Nothing is built without your written approval.
How payment works
In milestones tied to approved releases. You don't pay for a release before you've tested it.
What I'll say no to
- I won't build what a platform you pay for already does well.
- I won't promise a date I can't keep.
- I won't add a feature nobody on your team needs.
- I won't build on accounts that aren't in your company's name.
Samples of what you receive
Two documents for a fictional company, exactly as my clients receive them. The numbers are illustrative.
Tell me about one process
If a process in your company still runs on spreadsheets and group chats, tell me about it. I'll tell you honestly whether a custom system is worth it.