01 · Admin portal
Ops runs the fund here
The internal console: investor directory, borrower book, loan pipeline, document generator, and journal entries that post straight to accounting.

One login replaces a spreadsheet-plus-Documint-plus-email stack. Three role-scoped portals share the same backend: admin, investor, and borrower. Click any of them below and poke around.
Spotlight · Admin portal
A redacted clone of the admin side, using the same code as production with sample investors, borrowers, and loans in place of real data. Investor directory, borrower book, loan pipeline, and cap-table snapshot in one view, with journal entries and payment runs posting straight to accounting.
Three role-scoped portals
Each tile is the real app running in your browser. Tap to go fullscreen and drive it like a real user.
01 · Admin portal
The internal console: investor directory, borrower book, loan pipeline, document generator, and journal entries that post straight to accounting.
02 · Investor portal
What an LP sees on login: positions, distributions, projections, and statements. Names and numbers are redacted for the demo; the flow is live.
03 · Borrower portal
Draw requests, payment schedules, document uploads, and loan-level status, all scoped to the borrower's own deals. Same backend, different lens.
Challenge
Conduit Capital needed a secure investor portal with role-based access, automated workflows, and real-time reporting. Spreadsheets, Documint, and email threads were eating the team's week and making every close a fire drill.
Solution
Merkra built the platform from scratch, aligned to Conduit's internal process, investor expectations, and security posture. Three role-scoped front-ends share one ledger.
Results
The Conduit team stopped hand-assembling investor statements and stopped chasing borrower paperwork through email. The same humans now run a larger book without adding headcount.
Want something similar?
Fixed-price proposals on the first call. Working demo in week one. Full code ownership at delivery.