Liftly – Building the Version the Business Needed First

The Problem

The founder's real vision was a broader logistics marketplace with sophisticated, variable pricing. Building that pricing complexity first would have delayed launching a platform that first needed to prove the basic operational loop: can a customer book a job, can the business see and manage it, can payment happen reliably.

Our Solution

We separated the vision from the first release. V1 shipped the operational foundation — booking, pickup/dropoff, serviceability and distance eligibility, job and customer details, deposit and payment, and admin controls — as a complete, usable system on its own. The Pricing Engine V2 (service minimums, distance bands, labor and movers, stairs, urgency, specialty and heavy items, junk-removal load estimation, disposal estimates, admin overrides, customer approval flows, and margin protection) was designed and documented for a later phase, once the operational core was proven. Pricing Engine V2 was planned and designed, not built — it has not shipped.

The Results

• Shipped a working operational V1: booking, pickup/dropoff, serviceability, and payment
• Built internal admin and booking controls for day-to-day operations
• Designed a distance- and eligibility-based serviceability model for job intake
• Scoped a more sophisticated Pricing Engine (service minimums, distance bands, labor, urgency, specialty items) as a defined V2 — not built prematurely into V1
• Kept the broader marketplace vision intact while sequencing what had to ship first