Founders and business owners
Choose the Right Tech for Your Project
Know what to build your project with, and why, in writing.
Who this is for
- You're about to start building and haven't chosen the technology.
- Three developers gave you three different answers.
- Your system was built quickly and is now slow or hard to change.
- You're paying for a build and want an independent opinion on the technical choices.
Who this isn't for
- You want me to build it. This session is for decisions, not development.
- You want me to approve a choice you've already made. I'll tell you when I disagree.
- You're not sure yet what the product should do. Start with Plan Your App Before You Build It.
How it works
A 60-minute session before you build or rebuild. We decide what your project should be built with: the programming tools, the database, where it's hosted, and which parts to buy ready-made instead of building. I read your requirements before we meet, so the hour goes into deciding. You get the decisions in writing, plus 14 days of questions.
-
You send what you have
A description of the product, a feature list, how many users you expect, any developer quotes, and what's breaking if a system already exists. Rough notes are fine.
-
We decide, one choice at a time
For each choice you get my recommendation, what it costs, and how hard it would be to change later.
-
You get the decisions in writing
Within 5 days: the technology, the reason for each choice, the main risks, and a rough idea of cost and time. Written so you can hand it to a developer or an investor.
-
14 days of questions
Message me as the build starts and the first real questions come up.
What you get
- A written decision document: the technology, the reasons, the risks, and a rough idea of cost and time
- A clear answer on what to build and what to buy ready-made
- 14 days to message me questions as you start
What happens next
- When you book you get a short form and a list of what to send
- Within 5 days the session, after I've read your material
- Within 5 days of the session your decisions in writing
- For 14 days after questions by message as the build starts
We can decide
- Which technology to build with
- A website, a mobile app, or both
- Which database fits your data
- Where to host it, and what it will cost each month
- Connecting to other services such as payments, maps and messaging
- Security basics
- Getting ready for more users
- Building a part yourself or buying a ready-made tool
- What it will cost to maintain later
Why it's worth it
A wrong technology choice rarely shows in the first month. It shows a year later as a rebuild, and rebuilds cost far more than getting it right at the start.
Before we start
Send whatever you have: a product description or feature list, the number of users you expect, developer quotes, your budget range, and what's breaking if a system already exists.
Questions
Can we talk in Arabic?
Yes. The written document can be in Arabic, English or both. Tell me which when you book.
Will you sign an NDA?
Yes. Send it before the session and I'll sign it. Either way, what you share stays between us.
Will you just recommend the technology you use?
Only when it's the right answer. I'll tell you when something else fits better, including no-code tools when they're enough.
What if my developers disagree?
That's a useful conversation. Send me their points within the 14 days and I'll answer them.
Book when you're ready.
Know what to build your project with, and why, in writing.
Decisions based on what your business needs, not on trends or a developer's favourite tools.