Commissioning Custom Software — From an Idea to a Working System
Eight lessons that take a non-technical owner from “we need a system” to a written requirements brief any developer can price — and to knowing what to own, what to test, and what to sign.
$109Subscription — one-time, lifetime access
01 — Overview
Overview
Most software projects do not fail technically. They fail because both sides signed while imagining different things, because nobody was there to decide, or because the word “done” had two meanings.
This course teaches the role that decides the outcome more than any technical choice does: yours. You write no code and need no technical background.
I teach it as the party that builds and sells these systems, and much of it makes me harder to deal with — you will write a scope that stops me expanding it, ask for acceptance criteria I am measured against, and hold a final payment until you are satisfied. That is deliberate.
02 — What you will learn
What you will learn
Where projects actually fail — and why three of the four causes sit in your court
Three questions that may end the project before it starts, and save you the money
The one-page scope a stranger can understand, including what to put out of scope
User stories and acceptance criteria that make “done” mean one thing
How to read a quote: the risk margin, the six forgotten lines, fixed price versus hourly
Phases tied to payments, review points, and the early warning signs of delay
What you own: data, code, domain, hosting — and the question that tests it
How to test a delivery, classify what you find, and what to check before the final payment
03 — The lessons
The lessons
- Why Software Projects Fail — and Where Your Role Sits
- From “an Idea” to a Written Scope: The One-Page Exercise
- User Stories and Acceptance Criteria
- Time and Cost Estimates: How to Read a Quote
- Phases, Payments and Review Points
- Ownership: Code, Data, Domain and Hosting
- Testing and Delivery: How to Accept a System with Confidence
- After Delivery: Maintenance and Support — and the Capstone
04 — What you get
What you get
8 interactive lessons in short sections
~4 hours including hands-on tasks
A quiz per lesson + completion certificate
Two full editions: Arabic + English
05 — How subscribing works
No online payment — three simple steps
Send your request
Fill the short form: name, phone, email. This site never asks for any payment details.
I contact you personally
We confirm the details and arrange payment in cash or by local transfer — whatever suits you.
Your activation code arrives
A one-time code unlocks the product on one device, with lifetime access. Changing devices later is a message away.
06 — Questions, answered
Questions, answered
Is this a course to make me hire you?
It teaches the opposite habit. Lesson one asks three questions that may stop the project entirely, lesson six is about not being tied to any one developer, and the capstone tells you to send your brief to three of them and compare. A course that only pointed at me would be worth nothing to you.
Do I need a technical background?
No, and you will write no code. It is written for an owner or manager who is about to commission software, or who is in the middle of a project and wants to steer it.
What do I actually walk away with?
A requirements brief written in your own hand: the problem, the users, the stories with acceptance criteria, the priorities, the phases, and the commercial terms to ask for. Plus a fifteen-line checklist to run before you sign anything.
How do I pay and get access?
There is no online payment on this site. Send the request form, I contact you personally, we arrange payment (cash or local transfer), then you get a one-time activation code for one device with lifetime access.
07 — Send your request
Subscribe to Commissioning Custom Software — From an Idea to a Working System
Send your details and I will contact you personally within hours to complete the subscription — payment happens after we talk, and no online payment is ever requested.