Product Case Study · Rendin × Moving Services
The gap after
the signature
A product opportunity analysis on how Rendin — Estonia's rental protection platform — could close the tenant journey at the moment it currently stops: the day the contract is signed.
01 — Problem
A to Z?
Not quite.
I recently signed a rental agreement on Rendin, moving from Tartu to Tallinn. The contract was seamless. What came next wasn't — and that gap is what this case study examines.
Rendin describes its mission as a safe rental experience "from A to Z — from listing to handover protocol." The platform handles almost every step well: discovery, background checks, legal agreements, insurance, damage claims.
Rendin handles the legal and trust layer of renting well. The practical move itself — the actual day — sits just outside what the product currently covers.
The core insight
Rendin already has the tenant's move-in date, the property address, and verified identity. No moving company in Estonia or Poland holds this data. Rendin may be sitting on one of the strongest intent signals in Estonia's moving journey — and may not be fully using it yet.
This is not a critique. At 20 people across two countries, focus is essential. But it is a clear white space: a high-intent moment in the post-signing journey where a well-designed partnership feature could add value to tenants, bring in revenue with zero capex, and sharpen Rendin's claim to take users from A to Z.
The handover gap
The handover protocol is a legal moment that happens at move-in. A smoother move may improve handover completion and documentation quality. If that correlates with fewer disputes or clearer claim resolution, it could create indirect value for Rendin — though the link is not proven.
Expat friction
A growing portion of Rendin's users are international. Expats in Tallinn have no local network to find trusted movers, and the market has no clear quality signal for newcomers.
Post-signing silence
After signing, tenants go quiet on the platform until there's a problem. A moving feature creates a useful re-engagement point at precisely the right moment.
02 — User Research & Personas
Who actually
moves in Estonia?
Estonia has significant internal mobility — Tallinn pulls population from smaller cities — alongside a growing expat and digital nomad community drawn by e-Residency and EU digital infrastructure. Moving24.ee, one of Tallinn's larger operators, reports over 140 residential moves per day in Tallinn alone. These are Rendin's users.
Note on methodology
The personas below are hypothesis-driven, built from observed market contexts and public signals rather than direct interviews. Each flags the specific pain and need that primary research would validate or refute.
Alisa, 27
Software Engineer · Moved from Tartu to Tallinn for a new job
Alisa found her apartment on Rendin and liked the deposit-free process. Two weeks before move-in, she spent three evenings comparing movers on Google, reading Estonian-language reviews she could barely parse, and getting quotes that varied wildly. She picked by gut feel and paid too much.
"I trusted Rendin for the contract — I'd have trusted them if they'd recommended a mover too."
Mihkel & Kadri, 34 & 32
Family · Upgrading from 2BR to 3BR in Kristiine, Tallinn
Second-time Rendin users who actively trust the brand. Their concern is not finding a mover — it's finding a reliable one. The last time they moved independently, the company showed up two hours late and scratched their dining table. They want certainty and will pay a modest premium for it.
"We'd pay €20–30 more for a mover someone vouches for. We don't need cheap, we need reliable."
Priya, 29
UX Designer · From India, 4 months in Estonia via tech job
Priya used Rendin entirely in English — one of the reasons she chose it over KV.ee. For her, the moving market is opaque. A curated English-first recommendation would have saved her hours. She ended up asking Slack colleagues, got three different opinions, and picked randomly.
"I didn't know if I was being ripped off. There's no Trustpilot for Estonian movers in English."
Common thread
None of them struggle to find a mover. The problem is finding a trustworthy one at a fair price — and trust is exactly what Rendin has already built. That equity transfers.
03 — Market Sizing
How big is
the opportunity?
This starts from Rendin's own disclosed numbers and builds outward. A bottom-up approach is more credible for an early-stage feature than broad industry estimates.
Bottom-up funnel: Estonia only
Each step below is an assumption, not a measured figure. The ranges reflect the spread between a difficult early pilot and a product with established trust. The base case is used for the revenue model; the scenario table below shows how the output changes if the assumptions move.
Scenario sensitivity — commission revenue (Estonia, year 1)
Pool held constant: 273 eligible tenants/month (600 agreements × 70% Estonia × 65% need moving help). Only booking conversion varies — that is the most uncertain and most testable assumption.
| Scenario | Booking conversion | Bookings/month | Net revenue / year |
|---|---|---|---|
| Conservative | 10% | ~27 | ~€10k |
| Base | 20% | ~55 | ~€20k |
| Optimistic | 35% | ~95 | ~€34k |
The conservative case reflects a cold start — poor prompt placement and no established partner trust. The base case assumes the prompt is well-placed and partners are vetted before launch. The optimistic case is realistic by month 6–9 if early data supports it. Revenue calculated at €250 average move, 12% commission.
↓ V1 revenue — referral commission · base case (55 bookings/month)
V1 · Partner Commission
Moving company pays Rendin ~12% of each booked move. The tenant pays nothing extra — the commission comes entirely out of the partner's margin. Rendin carries no credit risk, no billing logic, no collections. The partner benefits from a warm lead with move-in date and address already known.
On an average €250 move, this is ~€30 per booking. At 55 bookings/month (base case, 20% conversion), that's ~€1,650/month. The model resets each month — no compounding, no carry.
Phase 2 — only if V1 conversion and NPS are strong
Partners pay a flat monthly fee for priority placement. Adds a predictable floor (~€7k/year from 2 partners) independent of booking volume. Only worth introducing once partners have seen referral value from V1.
Poland — larger upside, separate validation needed
Poland offers larger theoretical upside, but expansion economics should not be extrapolated from population alone. Conversion rates, partner quality, tax treatment, and local service norms would each need separate validation. The feature framework built in Estonia would transfer — but product-market fit would not be assumed.
04 — Solution & UX Flow
What the
feature looks like
The design principle: zero extra friction for users who don't want it, high value for those who do. The feature slots into the existing post-signing experience as a contextual prompt — additive, not disruptive.
Rendin should not build a moving service. It should build a curated partner widget — 2–3 vetted movers, surfaced at the right moment with move-in date and address already filled in from the contract.
Agreement signed — the trigger
When a tenant signs, Rendin already sends a confirmation email and in-app notification. This is the insertion point. A secondary card: "Your move-in is [date]. Need help moving?" — pulling data Rendin already holds.
Mover selection — curated, not open
Tenants see 2–3 vetted partners, not a full marketplace. Each shows a rating, price range, and availability for the move-in date. Fewer choices drive higher conversion and create a cleaner incentive for partners to maintain quality.
Quote request — pre-filled from contract
The form is pre-populated with destination address (from contract), move-in date, and apartment size (from listing). The tenant only adds number of boxes and items. This is measurably lower friction than any standalone moving site.
Booking — off-platform, tracked
Booking happens on the partner's site or via API if supported. Rendin gets a webhook confirmation and logs the referral for commission tracking. No payment infrastructure needed — the referral model keeps this lean.
Post-move — handover protocol prompt
After the scheduled move-in date, Rendin prompts both parties to complete the digital handover protocol. This closes the loop — the moving feature feeds directly into Rendin's core product and raises protocol completion rates.
Brand protection
Rendin's real risk: if a referred mover damages belongings, trust in Rendin takes the hit. Mitigation: vetting requires insurance, minimum 4.3★ Google rating, and background-checked staff. Rendin's communication is "Rendin Recommended" — not "Rendin Guaranteed." Fast-offboarding clause for any partner with two or more tenant complaints.
05 — Partnership Model & Revenue
Who are the
right partners?
The partnership structure should be exclusive per city, non-exclusive nationally. Each city gets 1–2 preferred partners, creating a competitive incentive to keep quality high. Rendin never owns trucks.
| Company | Base | Strength | Fit | Priority |
|---|---|---|---|---|
| Moving24.ee | Tallinn | 5,000+ moves, high-volume ops, English-capable | Large enough to absorb Rendin referral volume without strain | High |
| Uksest Ukseni | Tallinn / Harju | Published rate card, transparent pricing, furniture assembly | Pricing clarity maps well to Rendin's brand values | High |
| Sealt Siia OÜ | Tallinn | International moves, strong Google reviews, fast turnaround | Strong fit for Rendin's expat tenant segment specifically | Medium |
| Adduco / MoveMaster | Tallinn + Tartu | FIDI/IAM accredited, international network, 30+ year track record | Good for a premium tier — justifies a higher referral rate | Medium |
| FidsTrans | Tallinn / Harju | Budget-friendly, competitive pricing, local reach | Broadens addressable audience for price-sensitive tenants | Secondary |
V1 revenue model
Start lean. V1 is a pure referral model — no financing, no billing infrastructure, no credit exposure. Rendin earns a commission from the moving partner on each confirmed booking. The tenant pays nothing extra. Booking happens off-platform.
Referral Commission — V1
RECOMMENDEDRendin earns 10–12% of each booked move value, paid by the moving partner after the job is confirmed. The tenant never sees this fee — it comes out of the partner's margin, not the tenant's invoice. No payment infrastructure needed on Rendin's side.
The partner gets a warm lead: move-in date known, destination address known, tenant identity verified. That context makes a 10–12% commission easy to justify — the conversion cost is low compared to cold acquisition. Revenue resets monthly with new bookings; no compounding, no carry risk.
Placement Fee — Phase 2
Once the feature has 3–6 months of conversion data, Rendin can offer a paid priority slot in the widget — a flat monthly fee of €200–400 per partner. Introduced only after partners have seen referral value and Rendin can demonstrate conversion rates. Organic ranking still exists; the fee buys visibility, not a pass on vetting.
V1 revenue picture — Estonia, year 1
Commission alone generates ~€20k/year at the base case (20% conversion, 55 bookings/month) — with no logistics operations, no billing infrastructure, and no credit exposure, though partner quality and referral-related trust risk would still need active management. The optimistic case (~€34k at 35% conversion) is possible by month 6–9 if early data supports it. Poland would require separate validation.
These models can coexist, but their combination should be tested carefully. A partner paying both commission and a placement fee — while Rendin controls customer access and the referral flow — creates real economic pressure. That dynamic risks partner resistance or pricing distortion if introduced too quickly or without transparency about how referral volume is actually distributed.
06 — Metrics & Risks
How to know
if it's working
Metrics are ordered sequentially — each one sits earlier in the funnel than the next. A drop at any step narrows the diagnosis before you reach revenue.
| # | Metric | What it tells you | Threshold to watch |
|---|---|---|---|
| 1 | Prompt view rate | Share of eligible tenants who see the "Need help moving?" card after signing. Confirms the prompt is surfaced correctly before anything else is evaluated. | Baseline only — establish in week 1 |
| 2 | Prompt CTR | Share of tenants who tap the card. Low CTR means the message or timing is wrong — fix this before looking at anything downstream. | <10% → messaging problem |
| 3 | Quote form completion rate | Of those who clicked, how many submitted the quote form. A big drop here means the form asks for something tenants don't have to hand, or the pre-fill isn't working. | <40% → form friction |
| 4 | Quote-to-booking rate | Share of quote requests that result in a confirmed booking. Measures whether partner pricing and availability are competitive once a tenant has shown intent. | <8% after optimisation → weak demand |
| 5 | Complaint rate per 100 bookings | Tenants who contact Rendin about a partner quality issue after the move. This has a hard cap — not a percentage target — because even a small number of unresolved complaints affects brand trust disproportionately. | >3% → partner quality issue |
| 6 | Post-move NPS or CSAT | Feature cohort vs. control group after move-in. If tenants who used the prompt score no differently from those who didn't, the feature isn't adding perceived value even when it works technically. | Feature cohort ≥ control |
| 7 | Incremental revenue per eligible tenant | Commission earned divided by total eligible tenants (not just those who booked). The denominator matters — this normalises revenue against the full addressable base, not just opt-ins. | Track monthly from launch |
Decision gates — 3-month pilot
Kill
- CTR <10% after two messaging iterations
- Booking conversion <8% after form optimisation
- Complaint rate >3% with no clear partner fix
Iterate
- CTR 10–20% — test prompt copy, timing, or placement
- Quote completion <40% — reduce form fields, improve pre-fill
- NPS neutral — feature works but adds no perceived value yet
Scale
- CTR ≥20% and booking conversion ≥15%
- Complaint rate <2% across first 100 bookings
- Feature cohort NPS ≥ control group
Risks
Partner quality failure damages Rendin's brand
A bad moving experience gets associated with Rendin even if it isn't Rendin's fault. The tenant recommended the mover through Rendin; the accountability feels shared. Mitigation: strict vetting criteria (insurance required, minimum 4.3★ Google rating, background-checked staff), annual re-qualification, and clear "Rendin Recommended" language — not "Rendin Guaranteed." Fast-offboarding clause for any partner with 2+ tenant complaints within a rolling 90-day window.
Low conversion makes the feature not worth maintaining
If fewer than 15% of eligible tenants engage, the economics don't justify the partner management overhead. Set a 3-month pilot with a clear kill threshold. If conversion is below 15% at month 3, run one round of UX testing before deciding to kill or pivot to landlord-side (e.g. "find move-out services").
Regulatory complexity in Poland
Referral arrangements with Polish moving companies may have different tax and commercial law implications. Replicate the Estonia model only after a local legal review. Phase the Poland launch 6 months after Estonia proves conversion.
Rendin may already have looked at this
There is a real chance Rendin has evaluated and deprioritised this, or has it on a near-term roadmap. This case study is a structured product exercise, not a claim to have found a blind spot. The analysis stands regardless — the gap exists, the model is viable, and the fit is clear.
07 — Conclusion
Plausible.
Not yet proven.
Rendin may be sitting on one of the stronger intent signals in Estonia's moving journey — move-in date, address, verified tenant identity — that no moving company currently holds. That is the hypothesis. Whether tenants would act on a post-signing moving prompt, and whether partners would pay meaningfully for those referrals, remains untested.
The strongest next step is a lightweight Estonia pilot: one or two curated partners, the prompt surfaced after contract signing, success measured through CTR, quote completion rate, booking conversion, complaint rate, and post-move satisfaction. That data would confirm whether post-signing services could become a viable expansion surface — or whether the hypothesis doesn't hold in practice.
What this study shows
The opportunity is credible but unproven. The referral model is structurally simple enough to test without major investment — and the intent signal Rendin already holds is rare enough to be worth finding out.
What needs validation
Tenant opt-in rate, partner willingness to pay commission, and whether the Rendin brand extends credibly into a new category. None of these can be assumed from the analysis alone.
Decision criteria for continuing
If a 3-month pilot shows ≥15% booking conversion and no measurable drop in post-signing NPS, the model is worth scaling. If not, the data would still clarify whether the problem or the solution needs rethinking.
Independent product case study prepared for portfolio purposes. All figures are estimated from publicly available data. Rendin's actual roadmap or internal evaluation of this opportunity is not known to the author.
Assumptions & Limitations
- Personas are hypothesis-based unless otherwise noted
- Conversion and pricing assumptions are directional, not measured
- No internal Rendin data was used
- Claims reduction impact is unvalidated
- Poland estimates are illustrative only