Why I do this
The expensive part is rarely the decision. It's the months spent unsure.
I started out writing code, then led the teams writing it, then sat in the rooms where roadmaps and budgets were decided. In every one of those seats I saw the same thing: good companies losing months to questions an experienced eye could settle in an afternoon.
Startups pick a stack over a weekend and live with it for years. Large organizations launch transformation programs that stall because nobody owns the technical picture end to end. Different sizes, same cost.
So now I work directly with founders, CTOs and leadership teams. Short, honest conversations, a clear recommendation, and a plan for what comes next.
Who I work with
Startups
From first prototype to the first real scale.
- Choosing a stack and architecture you won't regret in two years
- Hiring your first engineers, and knowing when you need a CTO
- Technical due diligence before you raise
- Shipping an MVP fast without building a mess
Corporations
For teams changing how they build software.
- Cloud and platform modernization plans that actually finish
- An independent second opinion on vendors and large tech bids
- Engineering team structure and delivery speed
- Practical AI adoption that survives contact with production
How a consultation works
- 1
Create your account
Your name, your mobile number and a password. That's all.
- 2
Pick a 30-minute slot
Sunday to Thursday, 09:00–17:00 Riyadh time. Add a line about what you'd like to discuss.
- 3
Talk it through
Bring the problem. Leave with a clear recommendation and a next step.
Bring the decision you've been putting off.
30 minutes with Mohammad. Sunday to Thursday, 09:00–17:00 Riyadh time.