Founders and business owners
Plan Your App Before You Build It
A written plan for your app, website or system that developers can quote from.
Who this is for
- You have an idea and no idea what it costs or how long it takes.
- You're about to talk to developers and don't want a quote based on a guess.
- You're raising money and need a solid product plan.
- You've started building and the work keeps growing every week.
Who this isn't for
- You only want a price estimate. This is a planning service, not a quote.
- You want me to build it or manage the team. The written plan is what you get.
- Your idea is still one sentence. Start with a Quick Call.
How it works
Two sessions that turn your idea for an app, website or system into a clear written plan: what it does, what goes in the first version, the stages, the team you need, the timeline, the budget range, and the risks. I write the plan between the sessions, and in the second one we go through it until you're confident in it. It's the document you'd hand to developers or investors.
-
You fill in a short form
What the business does, who it's for, what already exists, your budget range and your deadline. Sketches, notes, or the competitor you admire all help.
-
Session one: 90 minutes of decisions
We decide what the product must do and who uses it, then the hardest part: what stays out of the first version. Most of the savings come from what we leave out.
-
I write the plan
Within 7 days you get the full document: features, first version, stages, team, timeline, budget range, outside services, and the risks with what to do about each.
-
Session two: 60 minutes to test it
We go through the plan and you question every part. I update it afterwards. Then you have 21 days of questions while you take it to developers or investors.
What you get
- A written project plan: features, first version, stages, team, timeline, budget range, outside costs, and risks
- A clear list of what is not included, which keeps the budget under control
- A second session to test the plan, and an updated version after it
- 21 days of questions while you take it to developers or investors
What happens next
- When you book you get the short form
- Within 5 days session one, 90 minutes
- Within 7 days of session one your written plan
- Then the 60-minute review, an updated plan, and 21 days of questions
We decide
- What the business and its users need
- The main features
- Who uses it, and what each user can do
- What goes in the first version, and what waits
- The stages of the project
- Technical needs
- The team you need
- How long it will take
- What it should cost
- Outside services it relies on
- The main risks
Why it's worth it
Software projects rarely fail because of the code. They fail because nobody wrote down what was being built, and it's discovered one costly change at a time. The plan costs less than a month of a developer working from a vague brief.
Before we start
Fill in the short form before session one. Send any documents, sketches, or apps you keep comparing yours to. If a developer has already quoted you, send that too.
Questions
Can the plan be in Arabic?
Yes. Arabic, English or both. Tell me which when you book. Technical terms stay in English.
Is the budget range a real number I can plan with?
It's a range with its assumptions written next to it, and it changes if the scope changes. It's reliable enough to plan with and to compare quotes against, but it isn't a fixed quote.
Will you sign an NDA?
Yes. Send it before session one.
Can you recommend developers afterwards?
I'll tell you what to look for and how to read their quotes. I don't take referral fees, so I point you to clear criteria rather than names.
Book when you're ready.
A written plan for your app, website or system that developers can quote from.
Two sessions, with the written plan in between. For anyone preparing to talk to developers, agencies, partners or investors.