TheArchive.

Every company starts with a personal annoyance. For us, it was the "Empty Fridge" feeling opening your phone on a Friday night, wanting to go out, but finding nothing but noise. This project began as a university assignment. It wasn't pretty but it was the start of something bigger.

rallyp0int Begins: Throughout the final semester of 2024, we poured our energy into developing a basic web application. The goal was straightforward: fetch global event data and display it to users on an interactive map interface. At the time, it felt like just another project to pass, but this little application turned out to be the unexpected catalyst for the wild year that followed.

The project, originally named 'eventHub', started its life as a modest web application capable of pulling and presenting event data from various sources across the globe. This early iteration, though crude, crystalized a fundamental idea: what if the hassle of finding local activities could be replaced by a seamless, mobile-friendly experience? It was the moment the vague potential of the idea became tangible.

Before diving into the complexities of building a robust, production-ready codebase, we spent weeks conducting informal user testing. We hauled our local server prototype into our university classes, badgering our peers to try it out. This was less about coding and more about honest, face-to-face feedback.

The initial burst of excitement that fueled the early concept development finally wore off, replaced by the crushing reality of constructing a scalable, professional backend. This month was defined by relentless burnout. Attempting to manage demanding university coursework while simultaneously learning entirely new database architectures led to countless hours of staring at blank screens.

Moving forward into the new year, 2025, the outlook for the project was anything but extraordinary. In fact, it was quite the opposite. 'eventHub' had been untouched since the assignment submission and was given little thought over the summer break. The quiet period was deceptive, a calm before an unexpected storm of activity.

Upon returning to university after a summer break, the grind restarted. Our standard curriculum included a mandatory group project creating a Windows desktop application. After about a week of reluctant planning, I approached the teacher and asked for a monumental concession: could I attempt to build an iOS application instead?

To my genuine surprise, he agreed, giving me a strict four-week deadline to deliver a viable proof of concept. Failure meant immediate reversion to the original desktop project. At the time, I had absolutely no idea the undertaking I was beginning.

The early days of this new endeavor were a deep dive into uncertainty, mostly comprised of intensive research. I experimented heavily with Swift, Flutter, and React Native to find the most suitable framework for my needs. Ultimately, I settled on Flutter due to its promise of near-true cross-platform functionality and the abundant public resource availability. But solving the framework problem immediately led to the next, even bigger existential question.

The title truly captures the feeling of the moment. I had settled on the technical stack, but I had absolutely no idea what a viable or meaningful project could even be. That's when a conversation provided the answer: "What about making 'eventHub' into an app? It solves a clear problem we all have finding events through usual social feeds with little awareness of what is actually occurring around us daily."

With the subject finally chosen, we started building the real mobile application, which we named 'rallyp0int'. We envisioned a mobile app that could ruthlessly cut through the noise. However, building a social platform brings a heavy responsibility: safety.

It was time to return to the project that unknowingly started it all. I compiled a rigorous list of all features from the original 'eventHub' that were to be retained, alongside those that would be cut. Starting with a blank slate, the basic architecture for what would become rallyp0int began to take shape, initially comprising just three simple, core pages.

With a crude but semi-functional prototype in hand, I presented it to my tutor. He gave me cautious but firm permission to proceed. This phase was a gritty mix of low-level DevOps work blended with trial and error. Slowly, viable progress began to emerge.

The next week, I traveled to Christchurch. There, the excitement grew exponentially as people saw the true usability and value proposition. The only question now was whether I, a single student, could really pull it off.

We reached a critical juncture where we had successfully connected the front-end to a functioning back-end, allowing development progress to accelerate. With the majority of the main interface pages now roughed in, our focus shifted to adding the essential utility pages that would make the app practical for daily use.

With the application becoming measurably more functional day by day, personal drive and motivation were at an all-time high. There is a special kind of feeling in seeing your creative idea becoming tangible right in front of your eyes, and I knew at this point that I had to capitalize on this momentum and push the vision forward.

This was the pivotal moment we transitioned mentally and legally from "hobbyists in a garage" to a recognized entity. We realized the scope of our vision was far bigger than just one event app. We began planning Blank Software Ltd. This new company was designed to act as a protective parent company an umbrella that would not only hold rallyp0int but also future projects like lanc1t, and critically, a contracting arm designed to help fund our more ambitious ideas.

With the end of the semester rapidly approaching, the project had fundamented shifted from a mere assignment into a personal mission. For the first time, I clearly saw the true viability and commercial potential of the project. I used the last of my available capital to purchase the rallyp0int.com domain and a personal Apple Developer Membership. This purchase plunged me into one of the most challenging stages: preparing and shipping what I naively thought was a finished product.

Data is inherently messy. When we attempted to integrate global event data into a specific New Zealand context, the application began crashing repeatedly. The root cause was simple yet brutal: computers are fundamentally literal. If the app's database expected a mandatory "State" field but a New Zealand address only provided a "Region," the entire system would break.

We quietly released a limited, test version of rallyp0int onto the App Store. This was a "soft opening," akin to a restaurant inviting only family and friends to test the service. We didn't announce it to the world; we just wanted to see if the engine caught fire when real people started using it.

Before the trial app was ultimately released, we endured a total of thirteen failed submissions to Apple. With each rejection, we diligently absorbed the feedback and continually resubmitted, all while the deadline for our planned local demo release was bearing down on us. The final submission attempt was made late the night before the demo party.

The next morning, I woke up to no update. I drove to the venue feeling the heavy weight of disappointment. Then, I checked one last time. On our fourteenth submission, on the very day of the party, we had been approved. rallyp0int was officially live.

After a single month in the App Store, we made the tough decision to temporarily pull the release. Our focus shifted entirely to fixing the high-priority issues flagged by early test users. The feedback received from these early adopters was undeniably valuable; as a small team, we simply didn't have access to a large enough volume of test users to simulate real-life bugs at scale.

During the beta phase, we received some refreshingly brutal feedback: "It works great, but honestly, it looks like an engineer designed it." They were right. We had been so intensely focused on the robust backend code that the UI felt clunky and utilitarian.

At this point, we had begun to thoroughly implement the critical changes identified. This included a significant overhaul of the database implementation and security protocols, coupled with a dramatic modernization of the UI. Our goal was to ensure that when we re-released, users would immediately recognize the considerable progress.

The comprehensive test phase officially concluded. We intentionally pulled the beta version down to begin final preparations for the real launch. We had gathered sufficient quality feedback to know precisely what users actually wanted versus what we *thought* they wanted. The time for testing was over; it was time to get ready for the main stage.

We entered the final, frantic phase of execution, focused entirely on the primary release date scheduled for September 12th, 2025, in Christchurch. We systematically clicked tasks off the backlog. Crucially, we also received our DUNS number, a critical step that allowed us to begin the lengthy process of accrediting our business with Apple pre-release. This administrative undertaking was one of the most complicated ordeals of the entire project.

Just before our planned re-launch, Apple intervened. They pointed out a significant gap: if we allow users to post public content, we must have an immediate mechanism to stop bullying or inappropriate posts. We didn't have the resources for a human moderation team, so we built automated tools.

On September 8th, four days behind schedule, we submitted what we were confident was the final version. However, due to the volume of new features, we ran into repeated guideline breaches. We spent the next three stressful days right up until the morning we flew to Christchurch reviewing feedback and rapid-firing resubmissions. On the morning of the flight, we made one last attempt. True to how the journey began, we landed and... nothing. We proceeded with our first night feeling a bit deflated.

We introduced a $200.00 annual subscription for premium business features. However, asking for that kind of money requires extreme clarity. You can't just have a simple "Pay" button; you need contracts and explicit transparency.

Just before we headed out for the first event of the weekend, I checked my emails one last time and saw the review status had been finalized. I crossed my fingers. We continued with our night until, while in the Uber home, a notification popped up on my phone: "Congratulations! rallyp0int is now live on the App Store!!!"

We had finally passed the final gauntlet of reviews. rallyp0int officially hit the App Store. Since we had virtually no marketing budget, we relied on "shoe-leather marketing" physically running around university campuses putting up 150 QR code posters and talking directly to people in bars.

The Win: Despite the rushed, chaotic launch, the core app held up beautifully. We achieved a 0% crash rate in the first month. All the time spent stressing over data "translation" and safety checks had paid off.

We realized the impossibility of effectively running a national platform from behind a single desk. When we flew down to Christchurch, not for a vacation, but for a deep-dive operational trip. We walked the streets and manually verified venues, sleeping on couches and working out of public libraries.

From this day forward, we truly began to publicly formalize and promote the application. We are immensely grateful for the involvement and belief of everyone who has supported the project so far!

With one application successfully launched, we immediately started on our second major project: lanc1t, a dedicated marketplace for student freelancers. We switched our core technologies to Python to handle the complex money transaction logic.

We were celebrating the successful launch of two platforms when the first truly terrifying bill arrived. Cloud computing feels free during development, but once you have real users uploading high-resolution images, storage costs explode.

In early tests of lanc1t, we identified a human problem: once a client received their work, they frequently forgot to leave a review. Since freelancers live and die by their star ratings, this was proving fatal to the ecosystem.

The data is in. Nearly 50% of our new users are finding rallyp0int simply by searching the App Store we aren't paying for them to come to us. This is the industry definition of "Product-Market Fit." It confirms that we successfully solved a real problem. Now, our focus shifts entirely from building the engine to meticulous tuning for maximum speed as we head into the summer.

While rallyp0int grew publicly, we quietly completed the "Blank Software" ecosystem internally. We finalized our internal toolset and the "Master Channel" knowledge base. We are no longer just building an app; we are running a software company with fully functioning internal logic, automated workflows, and a scalable tech stack ready for mass adoption.

We stand at the edge of our next evolution. With a live platform, verified revenue, and a battle-tested team, we have formulated the 10-Year Master Plan. We are no longer bootstrapping survival; we are engineering dominance. Today marks the beginning of our capital raise to fuel the fire and take the 330 users to the global stage.

We released a major update to rallyp0int, version 2.5. This update included a complete redesign of the user interface, improved performance optimizations, and several new features based on user feedback.

After 2.5 we went quiet. No launches, no posts, no promises. The work did not stop; it moved underneath. We polished rallyp0int through versions 2.5.2 and 2.5.3, and built an AI workspace that reads our own files, code and documents and answers questions about them with the sources attached.

From the outside it looked like nothing was happening. On the inside, three things were being built at once: a second product, a rebuilt rallyp0int, and the operating system that would run the company.

FlatMatch began. Renting in New Zealand is slow, scattered and stressful, and most of it still happens on a classifieds site built for selling cars. We wanted a place built only for renting: rooms in flats, whole homes, and the landlords and property managers behind them.

The first prototype was a phone app: swipe through places, chat, see it all on a map. It was rough, but it proved the idea worked in the hand.

rallyp0int had outgrown its foundations. Every new feature fought the old ones, and ticketing, the thing hosts kept asking for, did not fit at all. So we made the hardest call a small team can make: rebuild instead of patch.

Version 3 started from the ground up. A new backend and database, our own ticketing with QR codes, chat, follows and reporting, and the app finally carrying one name everywhere: rallyp0int.

August was the month FlatMatch became a real platform. Pre-registration opened, and behind it we built the parts a renting business actually runs on: landlord accounts and billing, enterprise contracts for property managers, a connection to property management software, a help centre, and calendar sync for short stays.

We started telling property managers about it before it existed in public, with one date in every conversation.

Local businesses kept telling us the same thing: they had been quoted too much for a website that did too little. We could fix that, so we set up a proper way to do it, with a sales process, a proposal template and a clean split between the people who sell and the people who build.

Hugo Moffett came on to lead sales and marketing for the new division, BSL Web. The first demo sites for real local businesses followed within weeks.

After months of silence we rebuilt the front door. A new public site, a new team page, and soon after, a new mark: blank. The portfolio, a blog and pages for each thing we do followed, so the work could finally speak for itself.

On the date we had promised since August, FlatMatch went live, with real payments switched on. A week earlier we had retired the first prototype and rebuilt the iPhone app in a single day; on September 24 it reached TestFlight.

Launch was not the finish line. Within days came the admin tools to run it, report and block across the whole platform, and Flatti, an assistant that answers renters from our own help centre.

In January we said we were running a software company, not just building an app. In September we rebuilt the engine that does it. One home for the whole company: tasks, proposals and invoices, clients and leads, and the products themselves, all behind a single sign-in.

Then we connected Claude to it. The same tools the team uses can now be used by an AI working alongside us, under the same permissions.

The web division shipped. Enlighten Electrical in Hamilton went live first, with a new site and a quote estimator, moved off their old platform. Welsford Chartered Accountants in Christchurch followed on October 1.

Then the rest: Empowerment & Potential, Wilds Yard Management, and Brainless Productions, a Christchurch events crew whose site is a working desktop, games included. Five client sites live on their own domains, and clients started leaving us reviews of their own.

The rebuild that started in June came home. rallyp0int.com was rebuilt for buying tickets and running events, and 258 users were carried across from the old app. Hosts can now sell tickets, run drops with a queue, scan people in at the door, and get paid; buyers get their tickets in Apple Wallet.

Before going further we swept the whole platform for security, moderation and legal gaps, then prepared build 44 for App Review.