.png){kind=small}
Partner Portal
Jetty is a B2B2C fintech company that partners with property managers to offer financial products to renters, embedding our products directly into the leasing workflow.
Project Summary
Built Jetty’s first Partner Portal (0→1) to retain B2B partners — our primary growth lever in a B2B2C model.
Background & Context
From '21 to '23, Jetty’s revenue 2x'd — but our flagship product, Jetty Deposit, was still unprofitable, with a loss ratio over 100%.
Although our product offerings expanded, the platform became increasingly difficult for partners to navigate. Property managers relied on emails and siloed manual processes to configure offerings, submit claims, and track performance — contributing to both partner churn and internal inefficiencies for Jetty.
Partner churn meant losing the opportunity to monetize on their entire renter portfolio. Therefore, in order to hit our '24 targets and sustain a 37% YoY growth rate, improving partner retention and operational efficiency became critical.
Problem Statement
Managing Jetty's products required partners to navigate a fragmented set of tools, systems, and workflows — hurting adoption, operational efficiency, and satisfaction.
The Solution
Jetty Partner Portal — a centralized platform for property managers to onboard properties & users, configure products, manage claims, and monitor portfolio performance — all in one place.
To accelerate time to market, we scoped the MVP by prioritizing (1) minimum security & compliance requirements, and (2) high-friction touchpoints — onboarding properties and managing claims. We built the frontend in Retool and exposed it directly to partners — cutting development time by over 50%.
To enable future scalability, we decoupled core business logic into modular services and APIs, making it easy to migrate to a custom frontend later without rewriting backend functionality.
Results & Learnings
Key Results
Our core business goals — like revenue growth and partner retention — were lagging output metrics. To better evaluate the Portal’s impact, we defined leading input metrics across product reliability, partner adoption, satisfaction, and internal efficiency.
These provided more immediate signals of product value and traction:
| Business Goal (Lagging Output) |
Metric Category | Input Metric (Leading Indicator) |
|---|---|---|
| Product Reliability | Health & Reliability |
97.2% of claims successfully submitted
|
| Revenue Growth | Adoption & Engagement | 72% of active partners onboarded + submitting claims within 4 weeks |
| Partner Retention | Customer Satisfaction | +15% increase in Partner NPS post-launch |
| Operational Efficiency | Internal Efficiency | ↓ 60% avg. claims processing time (7 min → 2.5 min) |
Learnings
When building a 0→1 platform product, assumptions about user needs and workflows have compounding effects. I realized that even small misreads can force major rework across foundational layers — like the data model or information architecture.
One of my biggest learnings was how leveraging third-party tools like Retool enabled us to move faster, deliver value sooner, and validate key assumptions before investing in a custom-built solution. This speed gave us clarity and saved us from building the wrong thing.
// WORK
ABHI
SINGH
