Rebind

Quick commerce finance is brutal on close cycles. Rebind turns month-end PDFs into a treasury dashboard founders and boards can trust.

Comment

Inspiration

What it does

Startup financial data is still far more manual than it should be. Founders and finance teams spend hours pulling information from bank statements, invoices, reports, spreadsheets, and other documents just to answer basic questions: How much runway do we actually have? Where is cash going? What changed this month? What needs attention? On the other side, investors often have the same problem across their portfolio—financial information arrives inconsistently, reporting is delayed, and getting a clear picture of portfolio health requires a lot of manual work. I'm exploring Rebind: an AI-driven financial intelligence platform designed to turn fragmented financial information into continuously updated, actionable insight for startups and their investors. The goal isn't another dashboard. It's to make financial intelligence something that works autonomously in the background, rather than something teams have to assemble manually every month. I'm particularly interested in hearing from founders, CFOs, finance teams, and investors: What financial task do you still find unnecessarily manual?

How we built it

Tech Stack: React TailwindCSS Lumina Design System Python FastAPI Firestore(Google/gcp)

Challenges we ran into

Started late No revenue yet Accomplishements:Mission Accomplisded@REbind

What we learned

Tech schooling in a month

What's next for Rebind

Build Google XPrize @Moonshots.com

Built With

Share this project:

Updates

posted an update —

Title: Rebind front-end update: I gave permissions a personality

Quick confession before the update: I spent a week making sure a "guest" role literally cannot break anything, and somehow that felt more satisfying than any feature I've shipped this year. Anyway. Here's what changed.

Stack's still the same overachiever lineup: React 19 + TypeScript, Vite, Tailwind v4, shadcn/ui, TanStack Query, Zustand, Playwright watching everything like a disappointed parent.

Role-based access control, or: teaching the app to say "no." The original design had a portal switcher with zero actual security — anyone could just click their way into being a VC. Bold strategy, but not great for a fintech app. So I built a real permission system: five roles, one policy table, and every route and button now checks in with it before doing anything spicy.

export const ROLE_POLICIES: Record = { admin: { label: 'Administrator', portals: ['founder', 'vc', 'admin'], canMutate: true }, founder: { label: 'Founder', portals: ['founder'], canMutate: true }, user: { label: 'Team Member', portals: ['founder'], canMutate: false }, vc: { label: 'VC Partner', portals: ['vc'], canMutate: true }, guest: { label: 'Guest', portals: ['founder'], canMutate: false }, } Twenty lines of code, and now a "Team Member" can look at the dashboard all they want but can't touch the "Execute Transfer" button no matter how hard they click it. I tested this personally. Repeatedly. It never worked. Beautiful.

Six environments, because one was never going to be enough. Dev, qa, qa2, uat, uat2, production — each with its own config, all from the same codebase. Yes, qa2 exists. No, I don't know what happened to qa1's dignity. It's just called qa now. qa2 is the sequel nobody asked for but everybody needed.

The Great Icon Diet. Turns out Google's icon font wanted 3.96MB of my users' data just to draw some outlines. I said absolutely not, swapped in lucide-react behind a translation layer, and the app lost weight without losing a single icon. If only real diets worked by just changing the label on the box.

Feature folders, because chaos is not a personality trait. Treasury, portfolio, review, documents, admin, onboarding, settings — each one gets its own tidy little home instead of living in one 4,000-line file that only I understood and only on days I'd had coffee.

10 Playwright suites, aka 10 tiny robots whose entire job is to distrust me. They click every button, try every role, and file a complaint the moment something's off. Genuinely the most judgmental teammates I've ever had, and also the most useful.

What's next: expanding the review queue and document lineage views, and probably renaming something else "v2" out of habit.

Curious what breaks first when you try to log in as a guest and mash every button — go ahead, I dare you. Drop your role-based chaos stories in the comments.

Log in or sign up for Devpost to join the conversation.