Fund A Future

Paywalls block potential. "Fund A Future" empowers people to donate to specific tool funds. We then issue secure virtual cards to those who need it most. Simple, direct, accountable.

Comment

Inspiration

This year, a personal experience collided with a local phenomenon. I was laid off twice, facing a tough job market where the digital tools needed to upskill and build a portfolio felt like a luxury I could no longer afford. I was lucky to have savings, but I saw countless others online who were stuck, possessing the talent, but blocked by a paywall.

At the same time, an Indonesian animated film, "Jumbo," became more than just a movie; it became a national phenomenon and the most-watched Indonesian film of all time. What makes this story so powerful is that it was the director's very first film. His dream to create animation began as a child, sparked by a single trip to the cinema with his parents.

That personal dream created a powerful ripple effect. An organic movement emerged online called #BuzzerJumbo, where strangers started buying movie tickets for kids who couldn't afford them. The hope was that this one act of sharing access could ignite that same spark in a new generation, potentially inspiring the next "Jumbo" from a child who just needed to see what was possible.

I realized the spirit of #BuzzerJumbo could be the solution to the problem I was facing. What if I could build a platform that let a global community provide direct, accountable access to the digital "tickets" people need to build their own futures? That question is the reason I built Fund A Future.

What it does

"Fund A Future" is a platform for social good that connects generous "Backers" with "Members" who need access to essential digital tools and services.

It works on a Pooled Fund model. Backers can contribute any amount to specific funds (e.g., "Adobe Creative Cloud Fund", "Figma Pro Fund"). Whether it's a recurring subscription like Figma or a one-time purchase like a professional certification course, our system is designed to handle it.

Once a Member's request is approved, my platform uses Stripe's Issuing API to instantly generate a secure, virtual card for the exact cost.

How I built it

I built this entire platform this weekend using a modern, scalable tech stack:

  • AI Development Platform: I used Bolt.new as my primary engine to rapidly build the user interface, generate frontend components, and write backend logic.
  • Framework & Styling: The application is built on Next.js and styled with Tailwind CSS for a clean, minimalist, and responsive design.
  • Backend & Database: Supabase serves as my backend, managing all the data in a PostgreSQL database and handling user authentication securely.
  • Payments & Financial Infrastructure: Stripe is the heart of the financial system. I use Stripe Payments to accept contributions from Backers and the Stripe Issuing API to programmatically create the virtual cards for Members.

Challenges I ran into

My journey this weekend involved tackling challenges on two main fronts: the complexity of the external APIs and the nuances of building with a new development tool.

The first major challenge was overcoming the initial intimidation of the financial technology stack. This was my first time using Stripe in a project of this scale. The documentation is vast, and a product like "Issuing" has its own deep ecosystem of rules. At first, I was concerned about potential geographical limitations, so I was even prepared with a Plan B, having researched Lithic as an alternative. However, I committed to a process of careful reading and trial-and-error in Postman. The breakthrough moment when I successfully created my first configured virtual card in the sandbox was a massive confidence boost.

The second set of challenges came from the development process itself using Bolt.new. On one hand, Bolt was incredibly fast for prototyping; it generated the UI and initial flows for the entire application just as we had specified. It got me from zero to a working prototype in record time.

However, as I moved into refining the details, I ran into a few hurdles. I noticed that fixing what seemed like a "small" issue in the UI could sometimes consume a surprising number of tokens. There were also moments where the AI seemed to lose context from our earlier agreements, or generated code with different stylistic conventions for similar pages. While these were all fixable with follow-up prompts, it taught me a great deal about precise prompt engineering and managing the iterative lifecycle of an AI-generated project.

The most nerve-wracking challenge came near the end. I discovered the project was being built on Next.js 13 and was experiencing an intermittent bug where the app would get stuck loading. After some debugging, I manually upgraded the project to Next.js 14, which thankfully resolved the issue completely. Seeing the app run smoothly after that final fix was a huge relief and validated the entire effort.

Accomplishments that I'm proud of

I'm incredibly proud of building a fully functional, end-to-end fintech application in a single weekend as a solo developer. Specifically:

  1. Full-Cycle Financial Simulation: This project is more than a concept; it's a complete simulation of a real-world financial system. I successfully implemented the entire lifecycle: from a Backer making a contribution via the Stripe Payments API, to my Supabase backend processing it, to programmatically creating a secure, configured virtual card using the Stripe Issuing API in a live sandbox environment.
  2. Navigating & Taming a Complex API: I'm proud of successfully tackling a professional-grade tool like the Stripe Issuing API for the first time. I moved from initial uncertainty to a deep, practical understanding, overcoming roadblocks and implementing features like monthly spending limits and merchant category controls.
  3. Building Something Personal: More than the code, I'm proud that I was able to take a personal hardship and a local inspiration and turn them into a project with a clear, hopeful vision and a working technical foundation.

What I learned

This hackathon was a powerful lesson for me in the difference between theory and reality, on both the fintech and AI development fronts.

  1. Finance is a different league of complexity. I learned that it's not just about if the code works. Every API call has deep implications for security, legal compliance, and geography. I had to think like an engineer, a lawyer, and a compliance officer all at once.

  2. Always have a Plan B. My research into Lithic as a backup wasn't wasted time; it was strategic. It taught me that when building on critical infrastructure, you must have alternative services in mind. Relying on a single service without a backup plan is a huge risk.

  3. The "Sandbox" is your best friend. The ability to fail, experiment, and learn in a secure test environment is the most powerful tool a developer has. I learned to embrace the "error" responses from the Stripe API as guideposts, not roadblocks.

  4. AI Development has a unique rhythm. I learned that building with an AI partner like Bolt.new is different from traditional coding. It's unbelievably fast for the "zero-to-one" phase—getting a full prototype up and running. The next phase, refinement, requires a different set of skills: less about line-by-line debugging and more about strategic prompting, context management, and guiding the AI to the perfect final state.

  5. Trust, but verify the foundation. The Next.js 13 issue taught me a critical lesson. While the AI can build the house for you, it's still my responsibility as the engineer to inspect the foundation. Checking core dependencies and framework versions early is crucial for ensuring stability and preventing last-minute surprises.

What's next for Fund A Future

This hackathon project is the blueprint for a platform I am passionate about building into a real-world venture. My next steps are focused on turning this project into a sustainable, scalable platform:

  1. Launch Legally: My immediate next step is to navigate the legal requirements to launch a project like this. This means registering a legal entity and going through Stripe's full onboarding process to move from the sandbox to a live environment.
  2. Build Approval Automation: To scale beyond a handful of users, the manual approval process needs to evolve. My plan is to build a semi-automated, and eventually fully-automated, system for vetting and approving Member requests based on clear, transparent criteria.
  3. Expand Gifting & Partnership Models: The virtual card is just the first method of delivery. My future vision includes:
    • Direct Partnerships: Working with platforms to generate unique promo codes for our Members.
    • Integrated Checkout: Creating a "Pay with Fund A Future" button that could be integrated directly on partner sites.
    • Exploring other payment flows that make it even easier and more secure to deliver access.

Built With

Share this project:

Updates