Make the experience simple.
Make the operating model explicit.

01 · Executive concept and decision

KEYBALO connects drivers with a specific, well-described vehicle, transparent trip terms and a documented handover. The eventual private-owner proposition is “make idle availability earn.” The initial commercial product is “find a locally available vehicle from a licensed supplier, verify, book, drive and return.” Do not present one as proof that the other is lawful.

Decision: proceed with UX and a non-transactional prototype now. Proceed with a paid pilot only when a licensed rental partner signs, its vehicles are individually eligible, the insurer binds coverage and the payment/acquiring structure is approved. Do not purchase a fleet merely to satisfy an assumed licensing shortcut. No partnership, insurer quote or regulatory confirmation has been obtained in this work.

02 · Israeli regulatory findings

Evidence labels below distinguish legal/regulatory material from product interpretation. Official websites sometimes returned 403 errors; where noted, only indexed official text was available. This research has not established the absence of later amendments or special permits. Have Israeli transport counsel verify the consolidated law and obtain written agency clarification before trading.

Direct answer: the evidence does not establish a lawful general-purpose “private owner → renter” model. It supports a regulated rental route. We cannot presently promise that a private owner remains privately registered, needs no business status, or can use normal personal insurance. If the owner becomes a business for tax purposes, that does not itself authorize transport activity.

Tax work required: determine who supplies the rental, who issues each invoice, commission VAT, rental VAT, owner income classification, deductible vehicle expenses/input VAT, withholding, National Insurance and tourism treatment. Do not assume a foreign tourist is automatically exempt or that every owner is an exempt dealer. Tax Authority interpretation on private-vehicle input VAT and a published 2020 rental-related VAT judgment were identified; the judgment’s full text was inaccessible, so no holding is asserted. Neither establishes a P2P exemption. [12–13]

Consumer law: prepare distance-sale disclosures, statutory cancellation rules and accessible cancellation channels with counsel. The Consumer Council explains statutory distance-sale rights; Hertz’s own domestic policy illustrates a 14-day/two-day structure but is not law for this platform. Do not hardcode a foreign marketplace’s non-refundable policy. [14–15]

03 · Legal-model alternatives

Maintain a legal-supplier ID and operating-model code on every listing, quote, contract, policy and payment. Never silently replace the supplier at checkout. Shared brand presentation cannot conceal the legal contracting company.

04 · Insurance architecture

Verified insurer wording, not an arranged product: AIG’s 2026 policy wording lists rental as a distinct permitted use when specified in the schedule. The existence of that category does not show that this marketplace or any private owner is accepted. Ordinary “any driver” coverage is not confirmation of rental use. [5]

Structure options: partner’s fleet policy with approved rentals; endorsed trip cover; broker-arranged group structure if legally available. No Israeli temporary P2P product has been verified. Seek terms from licensed commercial motor brokers and insurers with rental underwriting; AIG, Harel and Phoenix are potential inquiry targets, not partners. Separate policy insurance from a contractual excess waiver. No insurance margin is included in the base case.

Bind a policy version to each booking. If coverage cannot be confirmed for the full trip, decline the booking. Show the insurer, actual coverage, excess by event, exclusions, deposit, claims route and emergency contact before payment.

05 · Recommended operating structure and precedent

Use a technology company contracted to two or three licensed rental operators. Supplier remains the disclosed lessor, controls release of the car and maintains approved vehicle/insurance records. Start with supplier as merchant of record through hosted payment; platform invoices commission. A split-settlement arrangement is a later option after PSP and legal approval. Avoid holding customer balances or building an unlicensed wallet.

MYCAR2GO verified historical fact: Shagrir’s 26 June 2018 stock-exchange filing describes CAR2GO leasing cars long-term to customers, who offered unused windows through CAR2GO; CAR2GO credited them part of the short-rental charge. This demonstrates company-mediated shared leasing, not unrestricted rental of privately registered cars. The filing does not disclose the exact vehicle registration entries or policy wording. Contemporary reporting said maintenance and insurance were included, but complete policy scope remains unverified. [4,16]

2026 interpretation: a similar experience may be technically reproducible within a currently approved operator’s fleet. Its historical existence is not permission for our structure. Obtain the current operator conditions and written insurer acceptance. Why it stopped or changed has not been established from reliable evidence; do not invent a failure narrative.

06 · Target customer

Primary hypothesis: central-Israel residents needing a specific comfortable car for a two-to-four-day domestic trip, plus occasional local business travel. Proposed pilot underwriting segment: age 25+, at least three years’ licence experience; these are commercial assumptions, not universal legal minimums. Test younger and older drivers only if the insurer supports them. Avoid urgent same-hour replacement promises until support is reliable.

Interview 20 renters before paid acquisition: last rental, total bill, supplier frustration, pickup distance, deposit tolerance, actual willingness to book at the all-in price. Measure behavior with a clearly labeled waitlist; do not manufacture bookable inventory.

07 · Target supplier and future private owner

Launch supplier: a licensed small or midsize operator with 10–30 eligible vehicles, maintained records and stable daytime pickup. Concentrate available stock, not nominal fleet size. Require authority to list, licence checks, bank account match, financing consent, accurate images, mileage terms and an actual booking calendar.

Future owner hypothesis: an owner with secure parking, a well-maintained family/EV vehicle, predictable unused weekends and willingness to accept wear and documented handovers. Reject owners relying on guaranteed income or whose lease/loan prohibits the proposed use. Private applications do not enter search results.

08 · Beachhead comparison

These are strategic hypotheses, not measured Israeli market scores. Prices below are prototype inputs, not scraped quotes.

Start with 60% family/hybrid, 30% EV, 10% premium as a test allocation, not a demand forecast. Ben Gurion publishes specific rental-company facilities and authorization arrangements; access must be separately resolved. [11]

09 · Competitors and principles to borrow

Brand directions: KEYBALO / דרך (journey, working choice), NUA / נוע (movement), KEYVA / קיווה (keys/access). No trademark or commercial-domain clearance performed. Palette: deep forest, warm off-white, muted lime; large photos, minimal forms, real trust evidence. Use true listing photography at launch; current stock images are explicitly illustrative.

10 · Renter journey

Location/date/time → results with all-in quote → vehicle and legal supplier → identity/driver eligibility → supplier acceptance → hosted payment and separately disclosed deposit → booking contract → arrival and original-document match → signed condition record → drive → repeat return record → reconciled adjustments → double-blind review. Provide a clear pending state and expiry; a payment authorization is not a confirmed rental.

Show exact car versus category substitute explicitly. Initial product uses request-to-book, not instant booking. Preserve selected dates when returning from verification. Display Asia/Jerusalem times and handle daylight-saving changes server-side; do not treat a calendar day as always 24 hours.

11 · Supplier / owner journey

Choose licensed operator or private feasibility path → authenticate → verify authority and bank account → vehicle documents and inspection → eligibility review → photos/specification → pickup hours, availability, rates and mileage → publication only after approval → accept request → handover → return → claims window → settlement statement. Expired policy or registration automatically removes future availability and escalates affected bookings.

Private owners see “feasibility review” until an approved path exists. Do not collect their sensitive documents merely to grow a marketing waitlist. Owner calendar, pricing and bank-account changes require reauthentication; payout-account changes trigger review and cooling-off.

12 · Verification architecture

Store verification outcomes and provider references, not reusable ID scans in the product database. Identity provider: hosted document/liveness flow with a data-processing agreement and Israeli document support. Driver validity is not proven solely by OCR; use legally available authoritative checks or documented manual review and original-document inspection. Do not imply unrestricted government database access.

Owner checks: person/company, phone, address, beneficial authority where needed, bank match, registration/ownership, encumbrance/financing permissions, operator licence, vehicle eligibility and policy. Renter checks: document identity, licence category/expiry, age/experience, authorized extra drivers, payment match and underwriting restrictions. Visible badges represent a specific completed check with expiry, never raw ID/address. Allow manual appeal of risk decisions.

13 · Booking architecture

Use a server-owned state machine: draft → quote → verification_pending → supplier_pending → payment_pending → confirmed → pickup_pending → active → returned → settlement_pending → completed. Side paths: declined, expired, cancelled, incident_hold. One-off actions require an idempotency key. Every transition has an actor, reason, timestamp and version.

Freeze a signed price breakdown, policy version and contract version at acceptance. Reserve inventory transactionally with expiring holds; PostgreSQL exclusion constraints prevent overlapping active intervals. Include cleaning/inspection buffers in the blocked range. Recheck legal eligibility at confirmation and release, including full-trip coverage and extensions. Confirmation must depend on a verified payment-provider event, not a browser redirect. [18]

14 · Vehicle handover and evidence

Required capture set: front, rear, right, left, all four wheels, windshield, interior, dashboard, odometer, fuel/battery and existing-damage overview. Add detailed damage close-ups and accessories/keys. Obtain independent owner and renter confirmations against the same immutable manifest. Repeat at return, compare odometer and levels, and record disagreements without forcing a false agreement.

Production evidence: direct authenticated upload, MIME/size checks, malware scanning, original bytes, SHA-256 hashes, server receipt time, uploader/booking/stage IDs and append-only manifest. EXIF and device time are supplementary and untrusted. Store signed acknowledgments and revisions; never overwrite originals. Encrypt storage, restrict access per trip/claims role, log access and enforce a counsel/insurer-approved retention schedule and legal holds. Hashes help integrity; they do not prove when or where a photo was taken. Offline captures stay pending until secure upload is acknowledged.

15 · Payment, deposit and payout flow

Initial proposal: supplier merchant account → PSP-hosted checkout → signed webhook → booking confirmation. Platform commission invoiced to supplier. If a PSP supports approved split settlement, use submerchant onboarding and contractual distribution rather than an internal wallet. Select provider after written confirmation of Israeli entity support, rental MCC, local/international cards, 3DS, authorization duration, partial capture, refunds and dispute handling. Do not assume Stripe-style marketplace capabilities are available locally.

Collect or authorize rental price at the contractually approved time; authorize the security deposit close to pickup so it does not expire prematurely. Reauthorize explicitly where permitted for extensions. Deposit is not revenue or guaranteed collection. Post-trip: release undisputed hold promptly per provider/contract; route damage claims through evidence and notice; charge only with valid authorization and resolution. Fines/tolls need trip matching, supporting notices and a lawful transfer/charge process. Never auto-charge a claimed scratch or silently retain the full deposit.

Ledger accounts: customer receivable, PSP clearing, supplier payable, commission revenue, VAT, refunds and dispute reserve. Reconcile daily to provider events and bank settlements. Platform acting as agent versus principal changes gross/net accounting and regulatory exposure; obtain CPA/legal agreement. Israeli payment-service regulation is active; using a gateway alone does not settle the platform’s licensing status. [19]

16 · Damage and disputes

Late returns, smoking, cleaning, fuel and EV charging use disclosed schedules and actual evidence, with no duplicate recovery. Vehicle suspension, booking intervention and payout hold are distinct permissions; preserve emergency support for an active driver even if an account is suspended.

17 · Marketplace economics

Illustrative licensed-supplier case, not a quote: one three-day trip at ₪800/day, rental GMV ₪2,400 including assumed 18% VAT. Commission is charged as a share of VAT-inclusive rental price and is itself VAT-inclusive. No renter fee in the base table. Processing assumption: 2% of collected GMV + ₪1 = ₪49/trip. Variable support ₪35 + fraud/claims provision ₪25 = ₪60/trip. Acquisition ₪120/new paying customer; initial booking bears the full cost. Supplier funds its fleet/insurance costs in this base case. Platform is assumed to bear processing; contract could allocate it differently.

*Remittance is rental receipts less gross commission, not supplier net profit; supplier accounts for VAT and all operating costs separately. CM = gross fee / 1.18 − 49 − 60; after-CAC CM subtracts another 120. Provision is a planning reserve, not insurance. Fixed payroll, engineering, legal, financing and overhead are excluded.

Insurance stress: if the platform instead absorbs ₪60/day of cover, subtract ₪180/trip: 20% after-CAC CM becomes −₪2.22. At ₪120/day, subtract ₪360: it becomes −₪182.22. These premiums are sensitivity inputs, not obtainable prices. At 20% the maximum extra trip-insurance cost consistent with zero first-trip CM is ₪177.78, before overhead. At an EV rate of ₪420/day with the same three-day duration, 20% produces ₪213.56 ex-VAT revenue − ₪26.20 processing − ₪60 variable costs − ₪120 CAC = ₪7.36 before any incremental insurance or overhead. Broad adoption does not rescue poor per-trip economics.

Separate-fee variant: 15% supplier commission plus 5% renter fee yields ₪360 + ₪120 gross fees; customer pays ₪2,520 and supplier receives ₪2,040. Revenue ex VAT ₪406.78; processing ₪51.40; after-CAC CM ₪175.38 under the same assumptions. The prototype’s 12% renter fee is a UX scenario only and is not this recommendation. Evaluate full customer price and supplier retention together, not take-rate alone.

Pilot scale scenario: 50 vehicles × 8 booked days × ₪420 = ₪168,000 monthly rental GMV. At 20%, fee revenue ex VAT is ₪28,474.58. Assuming 133.33 trips at three days, processing ₪3,493.33, variable support/provision ₪8,000 and 60% first-customer trips × ₪120 CAC = ₪9,600, monthly contribution is approximately ₪7,381 before incremental insurance and fixed costs. This is a scenario, not a forecast; use actual cohorts and repeat rate before scaling.

18 · Monetization and pricing

Test 15%, 20% and separate-fee structures with suppliers; retain 10–30% as sensitivity bounds. Do not finalize commission until insurer and PSP quotations exist. No launch subscription. Later: optional delivery, corporate accounts, fleet software and clearly labeled sponsored results. Any insurance remuneration requires licensed distribution analysis; assume zero until contracted.

Supplier sets base price and duration/mileage limits. Suggested prices initially use explicit manually maintained ranges and historical booked outcomes only when available. Label low-confidence suggestions. Phase 2 dynamic pricing should respect supplier floors/ceilings and require opt-in; avoid changing accepted prices. Earnings calculator separates available days from booked days, gross receipts from remittance and contribution from profit. Year/location are descriptive inputs until a real pricing model exists.

19 · Supply acquisition and liquidity

Referral design: reward only after a verified eligible vehicle completes its first undisputed paid trip; cap credits, prohibit self-referrals and linked-account abuse. Illustrative reward budget ₪150 per activated vehicle, included in acquisition cost, not promised today. Community, Tesla and car-club content can recruit feasibility interest; no scraping or publishing private owners’ cars without their authorization.

20 · Demand acquisition

Start with exact-intent local landing pages (“weekend car in Tel Aviv”, EV trial trip), supplier cross-referrals and concierge partnerships with central-area hotels only after availability exists. Test creative on total price and pickup convenience, not “cheaper than traditional luxury rentals” without comparable quotes. Run 20 customer interviews and 10 moderated booking tests. Budget cap for a first controlled demand test: ₪3,000 as a planning assumption, released only after a bookable pilot.

Measure search → eligible results → verification → request → accepted → paid → completed. Attribute CAC to first completed paid rental, deduct cancellations, separate repeat cohort and count referral subsidies. Proposed scale gate: positive contribution after acquisition over the first three rentals, no unresolved critical safety incident, and stable supplier acceptance. These are management targets, not measured performance.

21 · MVP scope and implementation status

All demo records are browser-local and can be cleared; no local record confers legal eligibility. Images are illustrative stock photography, not proof of inventory. Core booking rules and a relational schema are included in source as a starting point, not a deployed backend.

Live MVP adds server authentication, supplier-scoped access, provider integrations, transactional booking, signed contracts, private evidence storage, notifications, reconciliation and incident support. Phase 2: delivery, instant booking, pricing suggestions and foreign-driver workflows. Phase 3: vetted remote unlock/telematics, corporate accounts, airport operations and new jurisdictions. No remote immobilization during a drive.

22 · Technical stack and integration plan

Current deployable artifact: dependency-light HTML/CSS/JS, private hosted preview. Production target: Expo/React Native for iOS/Android, React-based responsive web, TypeScript service API, PostgreSQL with PostGIS for radius search, private object storage, managed job queue and append-only audit storage. Expo documents a universal native/web route; choose package versions at implementation time. [20]

Use a modular monolith initially: identity, supplier/vehicle eligibility, availability, quoting, booking, evidence, payments/ledger, claims and messaging. Publish domain events through a transactional outbox. No microservice fleet is needed for the pilot. A Worker deployment requires HTTP-compatible database access and queue/storage bindings; select that hosting path only after backend requirements and data residency review.

Provider contracts: identity adapter returns signed decision/reference/expiry; PSP adapter owns hosted checkout and signed webhooks; insurer adapter or dual-reviewed manual process returns binding reference, vehicle/driver eligibility and coverage window; maps use a licensed map/geocoder and approximate public pickup locations; SMS/email/push carry minimal data. Analytics excludes ID documents, payment tokens and exact trip locations. Admin requires separate MFA and roles for support, compliance, claims and finance.

API outline: POST /quotes; POST /booking-requests (idempotent); POST /bookings/:id/accept; POST /payments/webhook; POST /evidence/upload-intents; POST /handovers/:id/acknowledgments; POST /claims; POST /claims/:id/responses; POST /reviews; GET /owner/settlements. Client cannot set verification status, coverage status, price totals or payout eligibility.

23 · Security, fraud and operating controls

Protect against stolen ID/licence/card with liveness, payment authentication, document consistency, velocity checks and manual review. Ownership and insurer records are checked independently of uploaded images. Mitigate account takeover through passkeys/MFA, session revocation, login alerts and bank-change holds. Minimize precise vehicle-location disclosure; telematics requires a lawful basis, purpose limits and access logs. GPS alone is not proof of custody.

Enforce authorization on every object, private signed URLs, encryption, malware scanning, rate limits, secrets management, backups and restore drills. Use signed webhook verification, replay protection, event deduplication and reconciliation. Require dual approval for sensitive payout changes and exceptional adjustments. Detect duplicate/reused damage photos but send decisions to human review.

Administrative suspensions must be separately scoped to user, vehicle, booking and payout. Record reason, actor, duration and appeal. A payout hold must not automatically suspend legitimate emergency support. Before release, perform security review focused on cross-user evidence access, webhook spoofing, booking races and bank-account takeover.

24 · Launch plan and release gates

Zone: Tel Aviv, Ramat Gan and nearby Herzliya pickup clusters only when inventory is dense. No nationwide promise. Proposed minimum public pilot: 30 bookable eligible vehicles, preferably 50 listed from two–three suppliers, with five useful choices for at least 80% of sampled weekend searches. Validate this threshold against actual query demand. Define pickup hours and Shabbat/holiday support explicitly; never imply unattended access.

1. Legal: written operating-model opinion, current supplier/vehicle eligibility and contract/disclosure review.
2. Insurance: bound coverage with documented uses, drivers, exclusions, periods and claims process.
3. Payments: approved merchant/acquiring structure, tested authorization, refunds, disputes and settlements.
4. Product: independent authenticated users, no overlapping confirmed bookings, complete evidence and accurate prices.
5. Operations: named incident owner, roadside escalation and a successful end-to-end dry run.

After gates: 10 supervised transactions, then 50, then 100. Proposed targets: supplier acceptance >85%, supplier cancellation <3%, handover completion >95%, zero unauthorized charges. Review incidents daily; stop expansion for coverage or safety gaps regardless of growth.

25 · 90-day roadmap

Planning envelope only: legal/compliance ₪20–50k; insurance structuring/operational setup ₪15–40k excluding premium; engineering/security ₪80–200k; pilot operations/acquisition ₪20–50k. Total ₪135–340k before insurance premiums, reserves, VAT and ongoing salaries. Obtain quotes before treating this as a budget. The prototype does not substitute for this work.

26 · Unresolved questions and next concrete actions

Prepared outreach briefs: counsel receives this model matrix and exact flow; broker receives vehicle classes/values, pilot ages, durations, delivery exclusions and claims protocol; PSP receives merchant roles, expected GMV, deposit amounts and refund examples; operators receive a 10-vehicle supervised pilot proposal with no subscription and commission to be negotiated. No outreach has been sent and no counterparty has been represented as engaged.

Core answer today: an idle privately owned vehicle is not yet established as safely and legally bookable through this platform. A licensed-fleet marketplace is the strongest supported starting path, subject to the listed release gates. The experience has been built so an approved private-owner structure can be added later without hiding who is responsible.