Founders often arrive with a picture of the finished product. A marketplace. An app on both stores. A dashboard for every role. A year of features drawn as one diagram.
We ask to see last week. What did you do yourself, more than once, while a customer was waiting?
Sometimes it is a spreadsheet that has been renamed final, then final2. Sometimes it is a WhatsApp thread where bookings get confirmed by hand. Sometimes it is a form that three people fill in three different ways. That repeated task is the first product. The wide platform can wait until strangers are actually trying to use the narrow one.
Spend the first budget on a person, not a diagram
Ambition can stay on the wall. The money and the months still belong to something a real person will touch. A clear site, a simple account, and the one workflow you are tired of doing by hand will teach you more than twelve empty modules.
You will also find out what you were wrong about, while the cost of being wrong is still small. That is the part a big first release steals from you. Once every role has a screen, deleting one feels like failure. In the first month, deleting one is the work.
A scope that fits on one page
We like the first scope to be short enough to read aloud:
- Who uses it this month. Names, if you have them.
- The one job it must finish.
- What you will still do manually, on purpose.
- How you will know it helped, in a number you already track. Fewer calls. Faster confirmations. A week of evenings given back.
Leave a line at the bottom for the thing you are willing to cut if the schedule slips. If you cannot name it, the scope is still a wish.
When that small loop is busy, then it is time to talk about the app, the extra roles, and the pieces that need to grow. North Tech would rather ship the narrow thing well than draw a platform you will have outgrown before it launches.