I build products for clients, and I also build products of my own and pay for every part of them myself. BY BANKS funds and runs Atlas & Aisle for destination weddings, SealedWorks for construction procurement and RIDARIS for cycling fit alongside its client work, which means I spend most weeks on both sides of the table. Paying the bill changed the advice I give founders more than any amount of client work had, and everything it taught me applies to your product as much as to mine.
The First Version Is Always Too Big
Every founder arrives with a list, and every item on it feels essential, because they have lived with the idea for a long time and can already see the finished product in their head. I am no different when the product is mine. Paying for it yourself is a quick way to learn the difference between what a product needs and what its founder wants, and the question I now put to every feature is whether a customer could sign up, do the one thing they came for and pay without it. If they could, it waits.
Launch Is Where the Spending Starts
Founders tend to treat launch as the finishing line and plan their money as though the costs end there. A live product has to be hosted, watched, backed up and kept secure, customers find problems that no test did, and the features you held back begin to matter once people are using what you shipped. All of that is simply what owning a product involves, and the founders who cope best are the ones who kept money and energy back for it instead of spending everything on reaching launch day.
The Parts Nobody Sees Decide Whether It Holds Up
When the money is yours, the temptation is to spend it on what you can see, because screens are what you show to investors, partners and friends. The decisions that come back to hurt you sit underneath: how the data is organised, how accounts and permissions work, how payments are taken and where the product is hosted. They cost little to get right at the start and a great deal to change once real customers and real records depend on them, which is why we settle them before any code is written. Getting a product to launch is the easier half, and whether it still holds up when the customers arrive was decided early, in the parts nobody will ever compliment you on.
Customers Will Not Use It the Way You Planned
However well you know your market, the first real users will pass over the feature you were proudest of and lean heavily on something you nearly left out. I have seen it on every product I have been close to, my own included, and it is the best argument I know for a smaller first version. Whatever you did not spend before launch is what lets you respond to what people really do, and a founder who has spent the lot is left watching the evidence arrive with no means of acting on it.
The Questions I Ask When It Is My Money
| Founders usually ask | When I am paying, I ask |
|---|---|
| What else can we fit in before launch? | What could a customer do without on the first day? |
| How good can it look? | Would somebody pay for it as it stands? |
| Can it handle a million users? | Will the first thousand arrive without anything needing to be rebuilt? |
| What will it cost to build? | What will it cost me every month once it is live? |
| What are our competitors offering? | What is the one thing that would make someone choose this? |
There is nothing foolish about the questions on the left, and I have asked every one of them. The ones on the right are closer to what decides whether a product is still running a year after it launched.
Why I Work for a Fee
Founders sometimes ask whether I would take a share of the company in place of a fee, and the answer is no. Having put my own money into my own products, I know how much a founder's ownership is worth to them later, and I would sooner be paid for the work and leave the company entirely yours. The same thinking is why the code, the hosting and every account are set up in your name from the start, so that the product you paid for belongs to you whether or not we carry on working together.
What I'd Tell Any Founder
Launch smaller than feels comfortable
If the first version does one job well for one kind of customer, it is big enough. Everything else can earn its place after launch.
Keep money back for afterwards
Plan for the running costs and for the changes your first customers will ask for, because both arrive whether you planned for them or not.
Get the hidden parts right first
Data, accounts, payments and hosting are where a small product either grows by being added to or has to be rebuilt.
BY BANKS shapes, builds and runs apps and platforms for founders and new ventures in the UAE, the GCC and internationally, with the same senior engineer from the first conversation to long after launch. If you have an idea or a product in progress, get in touch and I will tell you what I would do if the money were mine.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation