3
10 Comments

Technical Co-Founder Wanted (25% Equity) — Instant Settlement / Fintech

Hey Indie Hackers 👋

I’m building Noble, an ambitious fintech platform focused on instant settlement infrastructure for merchants and payments — and I’m looking for the right technical partner to build it with me from day zero.

Full transparency: we are currently at the idea stage. No fake traction — I’m intentionally looking for a hands-on technical co-founder to help design, build, and ship the MVP properly.

I care much more about building something real and technically solid than rushing out a half-baked product.

⸻

🧩 The opportunity

The vision is to build modern payment infrastructure that delivers:
• Near-instant settlement for merchants
• Clean, developer-friendly architecture
• Strong unit economics from day one
• Real long-term defensibility in the payments stack

This is a swing for a venture-scale outcome — not a lifestyle side project.

⸻

🔧 Who I’m looking for

You might be a great fit if you:
• Are strong in backend or full-stack engineering
• Can architect and ship an MVP end-to-end
• Are excited by fintech, payments, or money movement
• Move fast but care about building things properly
• Want real ownership and long-term upside

Big bonus if you have:
• Payments or banking API experience
• Ledgering or money movement systems
• Compliance/regulatory exposure
• AI/automation experience

Timezone overlap with Australia is helpful but not required.

⸻

💰 Equity

I’m offering 25% equity (standard vesting) for the right technical co-founder.

This is a true partner role — not a contractor position. I’m looking for someone who wants to help shape the product, tech, and company from the ground up.

posted to Icon for group Looking to Partner Up
Looking to Partner Up
on February 25, 2026
  1. 1

    Now day's building is also not easy but i can help you also on gtm and getting first 20 paying users.

  2. 1

    At Code Colonies, we work with founders through our Startup Engine Model, acting as a co-founder-level tech partner to architect, build, and scale products from scratch. With experience in building scalable backend systems and complex platforms, this aligns well with what you're looking. Our model operates on an Equity + Minimal Charges Basis.

    Happy to connect and explore further.

  3. 1

    This sounds interesting. I’ve been building AI products and backend systems recently and enjoy working from zero —> product. Curious what stage the product is at (idea, MVP, or traction)? Would love to learn more about the problem you’re solving.

  4. 1

    Looking to partner up

    breifly I can build software backed by research papers

  5. 1

    Hey @Founder22, this is a compelling vision. Instant settlement is a massive pain point for merchants, and building the infrastructure for it requires a very specific technical 'paranoia' regarding data integrity.
    I’m a Senior Software Engineer (5+ YOE) specializing in Golang,Python and Distributed Systems. I've spent a lot of time thinking about ledgering systems and how to maintain ACID compliance at scale—which is the backbone of what you’re building with Noble.
    A few quick technical thoughts on your MVP:

    • Immutability: For an 'Instant' system, the ledger service needs to be separate from the settlement logic to ensure zero-loss tracking.
    • Architecture: I’d lean toward a message-driven architecture (like SQS/Kafka) to handle the asynchronous nature of payment clearing while maintaining low latency for the merchant-facing 'instant' feel.
    • Security: From day zero, we’d need to bake in idempotency keys for every transaction to prevent double-charging—a common pitfall in early fintech MVPs.

    I’m based in India (which offers a great 4-5 hour overlap with the Australian workday), and I’m looking for a venture-scale partnership exactly like this.
    I’d love to hear more about your specific strategy for the 'settlement' layer—are you looking at local rails or international corridors? Let me know if you’re open to a quick technical sync.

    1. 1

      Hey — really appreciate the thoughtful reply. The ledger integrity and idempotency points are exactly the kinds of things I’ve been thinking about with Noble’s internal settlement rail.

      The architecture you mentioned (separating the immutable ledger from settlement logic and using a message-driven system) is very much aligned with the direction I’ve been exploring.

      I’d be keen to hear more about the distributed systems you’ve worked on and whether you’ve built or maintained any financial or ledgering infrastructure before.

      Also curious about your thoughts on handling institutional exposure and reconciliation if external rails fail.

      Happy to jump on a quick technical call sometime this week if you're open.

      1. 1

        Hey @Founder22, thanks for the reply! While my recent background is in high-scale Legal Tech at UniCourt, the core challenges are identical: data integrity, high-concurrency, and sub-200ms latency. I've spent the last 5 years architecting distributed systems using GoLang, AWS Lambda, and Elasticsearch to handle complex data workflows.
        I have a few specific ideas on how we can use Event-Driven architecture to handle those 'failed rail' scenarios you mentioned.
        To ensure we can move fast on the MVP, I have cleared my schedule starting tomorrow. I’ll be available for a sync or deep-dive at any time that suits your timezone in Australia.

        1. 1

          Hey, really appreciate the thoughtful response. The distributed systems work you mentioned sounds very relevant to what I'm trying to build with Noble.

          Would you mind sending me your email so we can continue the conversation there and set up a call to discuss the architecture and MVP in more detail?

          1. 1

            Hey @Founder22, that sounds like a great next step. You can reach me at "sudheeshbgole@gmail. co m".
            The platform was blocking the direct email format, so I’ve added two extra spaces, so please ignore those empty spaces.
            I’m really looking forward to diving into the architecture for Noble.
            Regarding the call, I have prioritized my schedule starting tomorrow to align with your Australian timezone, so I’m available at your convenience.

  6. 1

    This is a strong vision, especially your focus on building solid infrastructure from day one. We help founders go from scratch to MVP and through product positioning to market launch.

    If you are open to it, how can we support you in building and scaling Noble the right way. Feel free to share your email so we can connect and take it forward.

Trending on Indie Hackers
Your build-in-public audience is not your market. I learned the difference the slow way. User Avatar 257 comments Most founders don't have a product problem. They have a visibility problem User Avatar 61 comments Day 4: Why I Built a $199 Workspace Nobody Asked For User Avatar 40 comments How to automatically turn customer feedback into high-converting testimonials User Avatar 39 comments Built a "stocks as football cards" thing. 5 days in, my launch tweet got 7 views. What am I missing? User Avatar 34 comments Spent months building LazyEats AI. Spent 1 day realizing I have no idea how to get users. User Avatar 29 comments