Before Monesize Was a Company, It Was My Spreadsheet
How a personal bookkeeping habit, a few Google Forms, and about 25 individual setups eventually led me to build a software company.
I didn't set out to build a software company when I started keeping records of my finances. I wasn't researching the accounting software market, looking for a startup idea, or trying to identify a gap in the Nigerian technology ecosystem. I simply wanted to keep better track of my money movements.
On January 1, 2024, I started recording my expenses using Google Forms and Google Sheets. I wanted a simple way to document what I spent, when I spent it, and what I spent it on. I didn't want to rely on memory, scroll through bank transaction histories whenever I needed to understand my spending, or guess where my money had gone at the end of the month.
I wanted records. Actual records.
What started as a personal financial tracking exercise eventually became the foundation of Monesize, a company that has since taken me through product development, customer acquisition, market research, commercial experiments, a major product shutdown, and an entirely different approach to building enterprise software.
Looking back, the interesting part isn't that I eventually built a company. It's how an ordinary spreadsheet gradually turned into something I never initially intended to build.
It Started With Google Forms and Google Sheets
My first setup was fairly straightforward. I created a Google Form through which I could submit expense entries, then connected it to a Google Sheet where the responses accumulated.
Whenever I spent money, I opened the form, entered the details, submitted it, and moved on with my day. Google Forms handled data collection while Google Sheets maintained the records.
I didn't need to open a spreadsheet every time I wanted to record something. I didn't need to remember a particular cell or worry about accidentally modifying an existing entry. The form provided a consistent input interface, and the spreadsheet stored everything.
I could also categorise transactions and attach descriptions to them. Over time, the spreadsheet became more than a collection of numbers. It became a historical record of my financial activity.
I kept doing this every single day.
That consistency matters because financial tracking only becomes genuinely useful when you maintain it over time. A spreadsheet containing three days of expenses tells you very little about your financial behaviour. A spreadsheet containing months or years of transactions starts revealing patterns that you might never notice otherwise.
I wanted to know where my money went, but I gradually gained something more valuable: the ability to look backwards and understand my financial decisions with actual data.
I wasn't particularly concerned about building an elaborate accounting system. I had found a workflow that worked, and I stuck with it.
Then Other People Started Asking for the Same Thing
At some point, people started noticing what I was doing and asking me to create similar setups for them.
They wanted their own financial tracking systems. They wanted to record expenses, categorise transactions, maintain historical records, and have everything organised in a spreadsheet.
The solution seemed obvious because I already had a working example.
I would create a new Google Form for someone, configure the relevant fields, create a Google Sheet, connect the form to the spreadsheet, and make sure the setup worked. Each person received an independent arrangement that they could use to record their transactions.
Then I would do the same thing for the next person.
I eventually created these setups for approximately 25 people at different points in time.
Think about what that meant. I had started with a personal workflow that I found useful, and other people independently wanted essentially the same arrangement. I didn't need to convince them that keeping financial records was useful. They had already recognised the value and wanted a practical way to do it.
But I also started noticing the problem with how I provided the solution. Every new person required another round of manual configuration. I had to create another form, another spreadsheet, configure the fields, establish the connection, and make sure everything worked. The underlying functionality remained largely the same, but I repeated the setup process for every individual.
There was nothing particularly sophisticated about the work. It was repetitive.
I could continue creating Google Forms and Sheets for anyone who asked, but that approach had an obvious limitation. I was effectively operating a manual setup service for something that people could use independently if I turned the workflow into an actual product.
That was the point where I started thinking differently about what I had built.
Why Create 25 Setups When One Product Could Do the Job?
The problem wasn't Google Forms or Google Sheets. They had served me well, and I had successfully helped other people use them too. The problem was the duplication.
Why should I create a new spreadsheet for every person when I could build one application that allowed people to create their own accounts and start recording transactions immediately?
Why should someone depend on me to configure their financial tracking system when the software could handle the entire process?
I had already done the work of figuring out the workflow. I understood the fields, the categories, the transaction structure, and the relationship between data collection and financial reporting. I had also seen that other people wanted the same functionality.
Building a product seemed like the natural next step.
I could take the workflow I had already established, turn it into software, and make it accessible without requiring anyone to contact me for a custom Google Sheets setup. That was the thinking behind the initial Monesize idea.
I wasn't trying to invent a new financial concept. I wanted to take something I already used and had configured for other people and turn it into a reusable product.
In hindsight, that was my first real experience with productisation. I had identified a repetitive manual process, recognised that the underlying requirements remained largely the same across users, and decided to build software that could eliminate the repetitive work.
Money + Size = Monesize
Even the name came from the original idea. I styled it from two words: Money + Size.
Money represented the financial aspect of the product, while Size gave the name its identity. I combined them into Monesize.
It wasn't the result of an elaborate naming exercise or a branding agency's research. It came directly from the idea I wanted to build around.
The name stuck, and eventually it became the identity of the company.
By July 17, 2024, I had pushed the first commit of the Monesize backend repository to GitHub. That marked a significant transition from thinking about a product to actually engineering one. I spent the following months working through the backend, designing the application, implementing its functionality, and turning the original concept into something people could use.
On April 8, 2025, I completed the MVP backend. On April 29, 2025, we officially launched Monesize.
The product had come a long way from my original Google Form, but the underlying motivation remained recognisable. I wanted to make financial record-keeping easier and more accessible.
From My Personal Spreadsheet to a Bookkeeping Product
The original Monesize application focused on bookkeeping and financial analytics. We wanted to help small business owners understand their income, expenses, and financial position without requiring them to have an accounting background.
We were building primarily for Nigerian small businesses.
The product aimed to simplify something that many business owners handled through notebooks, scattered spreadsheets, receipts, and occasionally an accountant they called whenever they needed to make sense of their numbers.
We launched, onboarded users, spoke to business owners, and started learning what happened when people used the product outside our development environment.
We had customers who paid for access to the product. We also had people who expressed interest, joined our waiting list, tested the application, and gave us feedback. But building a product and getting people to use it consistently turned out to be two very different challenges.
One of the most important lessons came from observing actual user behaviour. People could tell us that they liked the idea, appreciate the interface, and request additional functionality, yet still struggle to develop a consistent habit of using the application.
We had to understand why.
I remember reaching out to inactive users individually, asking questions, and trying to understand what had happened after they initially signed up. Those conversations forced us to examine the difference between what people said they wanted and what they actually needed to manage their businesses every day.
That investigation eventually influenced a significant change in our product direction.
We Discovered That Bookkeeping Wasn't Always the Immediate Problem
As we spoke to more business owners, we started noticing a recurring pattern. For many retailers, inventory management and sales recording created more immediate operational pressure than bookkeeping.
They needed to know what they had in stock, what they had sold, what remained, and how those activities affected their finances.
A bookkeeping application could help them understand their financial records, but it didn't necessarily solve the operational problems that generated those records in the first place.
That distinction changed how we thought about the product.
We expanded Monesize beyond its original bookkeeping proposition and introduced inventory management, sales recording, and automatic bookkeeping capabilities. Instead of asking users to maintain separate operational and financial records, we wanted the application to connect those activities.
I personally spent considerable time building the backend infrastructure for this expanded product. I also built internal tools to understand user activity, investigated adoption patterns, and continued experimenting with ways to make the application more useful.
We were no longer simply trying to replicate my personal spreadsheet in a commercial application. We were trying to understand how businesses actually operated and what kind of software could make their daily activities easier.
Well well… That was a much bigger problem than the one I had started with.
The Difference Between Interest and Commercial Demand
One of the more interesting experiments we conducted involved bank synchronisation.
Users repeatedly requested the ability to connect their bank accounts and automatically import transactions. It sounded like a valuable feature, and there was enough expressed interest to justify investigating it.
However, bank integrations come with costs. We didn't want to commit to that expense simply because people said they wanted the functionality. So, we decided to test willingness to pay before proceeding.
We created an enrolment and prepayment process, then gave the experiment 45 days to generate enough commercial interest. At the end of the experiment, one person had paid. That person was me.
I had essentially paid for my own experiment.
It was funny in retrospect, but the result told us something important. People could genuinely want a feature without wanting to pay for it. Expressed interest, feature requests, positive feedback, and actual purchasing decisions don't carry the same commercial weight.
That experience changed how I evaluated product opportunities. I became much more interested in what people were willing to commit to than what they said they would use someday.
It also reinforced a lesson that I continue to apply when building software: a product can solve a real problem and still struggle commercially if the problem doesn't create enough urgency for the target customer.
April 30, 2026: We Shut Down the Original Application
After almost two years of building, experimenting, speaking with users, changing direction, and trying different approaches, we reached a point where we had to make a difficult decision.
On April 30, 2026, at 11:59 PM, the original Monesize SMB bookkeeping application went offline permanently.
I wrote about that decision at the time. I described the product as the most valuable research and development exercise we could have undertaken.
That wasn't an attempt to dress up a disappointing outcome. Running the product had given us access to the actual financial and operational behaviour of small businesses. We learned how they approached bookkeeping, why certain habits formed, why others never developed, and where a lightweight application stopped providing enough value.
We also learned a great deal about market segmentation and consumer psychology.
The shutdown marked the end of that particular application, but it didn't mark the end of Monesize.
The experience had exposed a different opportunity. We had spent considerable time studying the relationship between business operations and financial information, and we increasingly saw the limitations of treating them as separate systems.
That thinking contributed to the development of Monesize Core, our finance and operations platform for mid-market businesses.
The product direction changed significantly. Our target market changed. Our engineering priorities changed. The scale and complexity of the problems we wanted to solve changed too.
Today, Monesize has evolved beyond the original bookkeeping application into a broader product ecosystem. The original application no longer exists, but the company that emerged from that journey continues to build.
The Interesting Part Is That My Own Bookkeeping Never Stopped
There is one detail about this entire journey that I find particularly interesting.
I shut down the application, but I never stopped keeping my own financial records.
I started on January 1, 2024, using Google Forms and Google Sheets. I have continued every single day up to the moment I wrote this post (November 4, 2026).
In 2024, I tracked expenses exclusively. In 2025, I expanded the system to include income tracking. I have maintained that practice through changes in employment, different income sources, business activities, personal commitments, and everything else that has happened along the way.
The original spreadsheet still exists.
As of November 4, 2026, it contains 3,818 expense entries and 161 income entries. Those numbers represent actual transactions recorded throughout the period, not sample data or a synthetic dataset created to demonstrate an application.
The spreadsheet predates Monesize. It contains the personal financial history that helped inspire the original product, and it continues to grow even though that product no longer exists.
I find that distinction worth noting because it separates the underlying problem from the software we built around it.
The application was one attempt to solve a problem. My personal need to maintain financial records existed before the application, and it continues after its shutdown.
I still use the same general approach: record transactions, categorise them, maintain the history, and review the numbers when I need to understand my financial position.
The tools may seem ordinary, but the consistency has given me something that I value considerably: a continuous financial history that I can examine rather than reconstruct from memory.
What I Take Away From This
When I look at the journey from January 2024 to today, I see several different decisions that eventually connected.
I started recording expenses because I wanted to understand my own finances. Other people wanted the same setup, so I started creating individual Google Forms and Sheets for them. After doing that for approximately 25 people, I recognised that I could turn the repetitive process into software.
That decision led to Monesize.
Building the original product exposed me to a different set of problems. I learned that personal utility doesn't automatically translate into commercial demand, that user interest doesn't always translate into consistent adoption, and that businesses often need operational solutions before they need better financial reports.
We changed the product, experimented with new functionality, studied customer behaviour, and eventually decided to shut down the original application.
Then we took what we learned and built in a different direction.
I don't think every founder needs to turn a personal problem into a company. Sometimes a spreadsheet is just a spreadsheet, and there is absolutely nothing wrong with that. But when other people repeatedly ask for the same solution, it is worth paying attention. There may be an opportunity to turn a manual process into something reusable.
I also think there is a difference between being attached to a product and being committed to understanding the problem it attempts to solve. Shutting down the original Monesize application was difficult, but preserving it simply because we had spent years building it would not have made much sense.
The company had to evolve. And through all these changes, the original habit remained.
I still have the spreadsheet. I still record my transactions every day. I still have the historical data from the period before Monesize existed, through the years when we built the original application, and beyond its eventual shutdown.
Sometimes I open it and look through old entries. I can see what I earned, what I spent, the things I bought, the commitments I made, and how my financial circumstances changed over time.
It is an unusually personal record of the journey.
Before Monesize became a company, it was a spreadsheet I maintained for myself. Before it became a product, I had already spent months building the habit that inspired it. And even after the original product disappeared, I never stopped doing the thing that started it all.
That is probably the simplest way I can explain where Monesize came from.
And before I close out, I need to give a shoutout to everyone who has been part of the journey, so far (at different points in time). My loudest shoutout goes to Mr Opeyemi Dada, the current CMO and Co-founder, who has been part of the mission from day one and has been an integral part of every single transition we have gone through till this very moment.
May Monesize succeed.
(Drops pen) ✍️
Comments
Post a Comment